Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Explorer cannot use the Mica effect. #408

Open
ColorAWA opened this issue Feb 10, 2024 · 3 comments
Open

File Explorer cannot use the Mica effect. #408

ColorAWA opened this issue Feb 10, 2024 · 3 comments
Labels
third-party This issue is caused by a third party.

Comments

@ColorAWA
Copy link

ColorAWA commented Feb 10, 2024

[·] I've read FAQ.
[·] I've restarted the affected app after adding rule for it.
[·] I've checked other issues and this is not a duplicate.

Describe the bug
The entire File Explorer window cannot use the Mica effect.

Rule
The default rule

Target Application

  • Application Name - Windows File Explorer
  • Application Version - 24H2 Build 26052.1000

To Reproduce
Steps to reproduce the behavior:

  1. Open Windows File Explorer.

Expected behavior
The entire window is using the Mica effect.

Screenshots
image

Windows Version
Windows 11 Build 26052 Insider Dev Channel

Other tools being used
[·] Rectify11

@ColorAWA ColorAWA added the third-party This issue is caused by a third party. label Feb 10, 2024
@e-t-l
Copy link

e-t-l commented Feb 16, 2024

I think I'm having the same problem as described above. Basically, I can get Mica/Acrylici effects in File Explorer's title/toolbar, or in the main window, but not both at the same time. Enabling either advanced option in MFE will make the main window transparent, but the titlebar and toolbar lose transparency.

EDIT: nevermind I think ExplorerFrame is what I needed. #373

EDIT: EDIT: Even with ExplorerFrame, there is one section of my File Explorer toolbar that is opaque.

image

@WiredSamurai
Copy link

I have the same issue, have you found a solution?

@G1tgo
Copy link

G1tgo commented Mar 3, 2024

same issue ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
third-party This issue is caused by a third party.
Projects
None yet
Development

No branches or pull requests

4 participants