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

Incompatibility with ExplorerBlurMica causing Explorer windows to become fully transparent #338

Open
SKCro opened this issue May 28, 2024 · 8 comments
Labels
Processed The issue has been resolved and is awaiting confirmation. question Further information is requested solved in upstream project This issue is already solved in the upstream project, just wait for the porting

Comments

@SKCro
Copy link

SKCro commented May 28, 2024

Describe the bug

A clear and concise description of what the bug is:

For some reason, recent versions of DWMBlurGlass seem to have some sort of incompatibility with ExplorerBlurMica, causing Explorer windows to become completely transparent. This is temporarily fixed by restarting Explorer, but comes back when an Explorer window is unfocused and refocused. I have also filed a bug report under ExplorerBlurMica (because I'm not sure which is causing the bug), available here.

To Reproduce

Steps to reproduce the behavior:

  1. Install DWMBlurGlass and change some settings.
  2. Install ExplorerBlurMica while DWMBlurGlass is enabled.
  3. Explorer windows will become completely transparent with no blur, no matter what settings are used. Disabling DWMBlurGlass seems to fix this problem.

Screenshots

If applicable, add screenshots to help explain your problem:

Screenshots aren't really enough to describe the problem, so here's a screen recording showing off the bug:

8mb.video-BGN-C9WigW5o.mp4

Additional information (please complete the following information):

OS Version : [e.g. Windows 11 23H2.22631.3085]
Software Version : [e.g. 2.0.1]

Windows 10 IoT LTSC 2021 - 21H2, Build 19044.4412
DWMBlurGlass 2.2.0 (Latest)
ExplorerBlurMica 2.0.1 (Latest release, apparently)

What other third-party software do you use:

[e.g. windhawk mods xxx]

ExplorerBlurMica :P

Additional context
Other versions of ExplorerBlurMica still cause the bug, so it might be an incompatibility within DWMBlurGlass. Other users have reported the same issue in the other bug report.

@SKCro SKCro added the question Further information is requested label May 28, 2024
@yungoxigen
Copy link

I am having the same issue. Have you been able to fix it?

@SKCro
Copy link
Author

SKCro commented Jun 5, 2024

I am having the same issue. Have you been able to fix it?

I have found that sometimes I can get it to work if I disable DWMBlurGlass, enable ExplorerBlurMica, then re-enable DWMBlurGlass. However, the bug comes back if I change any settings within DWMBlurGlass and save.

@ALTaleX531 ALTaleX531 added the solved in upstream project This issue is already solved in the upstream project, just wait for the porting label Jun 20, 2024
@tails101
Copy link

tails101 commented Sep 6, 2024

yea doesn't work on windows 10 but work on windows 11 with effect 2 from my tests.

@enoversum
Copy link

enoversum commented Nov 17, 2024

I can confirm, it makes it not suitable for using it together with ExplorerBlurMica. Windows 11 here. .

@SKCro
Copy link
Author

SKCro commented Nov 17, 2024

One of the developers marked this issue as "solved in upstream project" months ago, yet there has been no further communication about a release that solves this issue. I understand that it might be taking a while since, from what I can gather, it's a big backend rewrite that aims to solve several issues and improve performance, but there hasn't really been much communication on progress lately.

@enoversum
Copy link

One of the developers marked this issue as "solved in upstream project" months ago, yet there has been no further communication about a release that solves this issue. I understand that it might be taking a while since, from what I can gather, it's a big backend rewrite that aims to solve several issues and improve performance, but there hasn't really been much communication on progress lately.

Yeah, I've seen. I guess it's sitting in some kind of update that needs more work. Apart from that, they don't owe us anything. And you can use another blur mode in DWMBlurGlass to circumvent the behaviour for the time being, so all's not lost.

@SKCro
Copy link
Author

SKCro commented Nov 18, 2024

One of the developers marked this issue as "solved in upstream project" months ago, yet there has been no further communication about a release that solves this issue. I understand that it might be taking a while since, from what I can gather, it's a big backend rewrite that aims to solve several issues and improve performance, but there hasn't really been much communication on progress lately.

Yeah, I've seen. I guess it's sitting in some kind of update that needs more work. Apart from that, they don't owe us anything. And you can use another blur mode in DWMBlurGlass to circumvent the behaviour for the time being, so all's not lost.

That's fair enough, the devs can take as long as they want because, as you said, they don't owe us anything. I just thought maybe a quick status update from them would be kinda nice, but it isn't required. Anyway, I didn't know changing the blur method could fix the issue, actually. Might try that out later - thanks for the tip!

@enoversum
Copy link

One of the developers marked this issue as "solved in upstream project" months ago, yet there has been no further communication about a release that solves this issue. I understand that it might be taking a while since, from what I can gather, it's a big backend rewrite that aims to solve several issues and improve performance, but there hasn't really been much communication on progress lately.

Yeah, I've seen. I guess it's sitting in some kind of update that needs more work. Apart from that, they don't owe us anything. And you can use another blur mode in DWMBlurGlass to circumvent the behaviour for the time being, so all's not lost.

That's fair enough, the devs can take as long as they want because, as you said, they don't owe us anything. I just thought maybe a quick status update from them would be kinda nice, but it isn't required. Anyway, I didn't know changing the blur method could fix the issue, actually. Might try that out later - thanks for the tip!

Totally understood. It would be very lovely to get to know if there is an actual fix in the works, absolutely. They'll reveal at some point :) . And yes, I believe the two other blurring modes should be compatible with ExplorerBlurMica. Working on my machine, that is.

@Maplespe Maplespe added the Processed The issue has been resolved and is awaiting confirmation. label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Processed The issue has been resolved and is awaiting confirmation. question Further information is requested solved in upstream project This issue is already solved in the upstream project, just wait for the porting
Projects
None yet
Development

No branches or pull requests

6 participants