Closed sameerasw closed 9 months ago
Do you have "Launch folder windows in a separate process" enabled, if not please enable it.
Do you have "Launch folder windows in a separate process" enabled, if not please enable it.
Yes, I do have it enabled... Seems like it's a hit on the CPU. And I have other users NOT having this issue so I will do some digging on my side as well. :)
https://github.com/Maplespe/ExplorerBlurMica/assets/68902530/f5e12f27-6efd-416f-8371-d78d46ba703f
Or try shutting down the standalone process? I'm not sure if this is caused by WASDK or something else .
Or try shutting down the standalone process? Clueless... because v1.0.7 is fast as without the .dll ...
I'll try a dism and sfc scan and re-try ... Might be a system file issue... Also will check if any other device experience this.
Or try shutting down the standalone process? Clueless... because v1.0.7 is fast as without the .dll ...
I'll try a dism and sfc scan and re-try ... Might be a system file issue... Also will check if any other device experience this.
Any update? Im running into this issue too on Windows 10. Are you using OldNewExplorer?
By the way, did you also use StartAllback at the same time?
By the way, did you also use StartAllback at the same time?
Me? No.
I've updated the attachment. Please re-download it and try it. It should be better. @tadghh @sameerasw
I've updated the attachment. Please re-download it and try it. It should be better. @tadghh @sameerasw
Thanks! It's fixed and 100% better now! <3
https://github.com/Maplespe/ExplorerBlurMica/assets/68902530/8ca23a5e-9c2c-47cc-9b53-c752e15b0b8c
Latest stable Windows 11 all up to date. i7 - 8750H + 16GB DDR4 + m.2 system drive
This behavior wasn't present back in previous versions.