Hello,
Sorry to hear you are having issues. But, I have yet to find another report from another on WB11 on Win10 or Win11 user with regards lagging to "total crawl" issue. Appreciate if we can learn more on your issue. Please provide more details: Please refer here: https://support.stardock.com/space/SHC/1387134987/Contacting+Stardock+About+WindowBlinds+Issue Ignore that.

Need to know if you interested to resolved it, need to know what troubleshooting steps you have tried on your system yourself? https://support.stardock.com/space/SHC/1346601085/WindowBlinds+Self-Support+Options

Thanks
Basj,
Stardock Community Assistant.

I am interested in fixing this issue.  I've uninstalled and re-installed the application, same results.  I've purged and reinstalled and it seems to be running better now, but I have no taskbar functionality.  What I mean is, I am not able to make it transparent.  I've checked all the settings in WB and they look fine the taskbar will not show transparent.  The start button does somewhat. 

So, just to confirm, the slow crawling issue is now gone after the purge and reinstall? If so need details on your system. Windows 10 or 11 and need its full version number too. And, please try cleanboot and see if there is conflict with other application or corruption issue with admin account. : https://forums.stardock.com/486023/windowblinds-support-faq#cleanboot

Thank you,

Basj,
Stardock Community Assistant

Yes that did rid me of the slow crawl. 

There is still an issue though, I am not able to get the full AERO effect unless I install Start11. Is that normal.

One of my programs will not work at all (the one I tested) REVO Uninstaller Pro.  Opens, then minimizes and I am not able to maximize it with Windowblinds running. so I have to put it in the exception list not to skin. 

I am running an admin account and even with a clean boot, the issue with uninstaller program is still there. 

I do have one other issue that I would like to address, Start11 and Fences both show update, in Object desktop, even though there isn't any new update available. 

For Object Desktop manager and Start11/Fences keep asking to updates this is a known issue, please ignore it until it get resolved. or Turn off ODM update check.

Not sure Aero effect. My system always have Start11 since I need my Start panel to be skin.

Some application will not work properly with Windowblinds and need to be excluded.

Thank you,

Basj,
Stardock Community Assistant

Having a problem with Visual Studio 2022 and the Winforms apps it generates.  It appears that VS2022 is painting the title bar with the menu commands, and that is throwing off the Windows Classic theme.  Also, the program I've written that is also a Winforms app that uses the DevExpress library that also has a ribbon is not painted correctly.  

Similar problems, different libraries.  I'm guessing MS doesn't use the DevExpress libraries in VS2022. 

There is an issue with the open source program natron, when themes are enabled on it a white background is added for no reason to some elements and its very annoying and causes visibility issues. the white areas should be gray just like the rest of the application, specifically color: rgb(48, 48, 48) Hex 303030. I would be very grateful If you could try to resolve the issue.

I have tried every combination of specific options and different themes to attempt to fix it and it just seems that windowsblinds is the issue as when I make it ignore the app the white background error disappears

This is likely skin specific. It's just that all the skins you've tried have white as a certain background element (not sure which specifically as I haven't done any testing). Experiment by modifying the skin you intend to stick with in the WB Configuration (Click Change System Colours). You can see which colours are currently set to white and as you know what colour you want to change that white to, it's just a case of finding the right one. As I say, I'm not sure which one that is but looking for ones with "background" in their name I should imagine is what'll work.

Hello, I have found a conflict between Windowsblinds and Whirlwind FX's SignalRGB on Windows 10 Pro. If I run the default Windows them SignalRGB runs perfectly fine. If I switch to any other theme SignalRGB crashes instantly. I have told Windowblinds to ignore SignalRGB but it doesn't seem to help. I have also reached out to SignalRGB's support team, but any insight you could provide would be appreciated. 

Hey, im using the Aero Theme and Whatsapp is NOT working with that.

https://imgur.com/a/FzWFAFw

This is the most epileptic stuff I've seen in a while.

Supermium is having issues. Namly, all works fine when launched with the --disable-windows10-custom-titlebar switch, however when using the new option in chrome://flags, WindowBlinds seems to avoid skinning.

I've diagnosed that this is some weird detection with WindowBlinds, since if the new flag is enabled, running chrome http://google.com/disable-windows10-custom-titlebar (which does NOT have any effect normally) tricks WindowBlinds into skinning properly.

If you are using command-line-detection (as it seems from my tests), could you add an option to skin anyway and ignore the command line?

Hello,
Sorry to hear you are having issues. From what I know, since the new update on Chrome and Edge, that Windowblinds workaround no longer work on chromium base browser. It is a known issue and so far, its nothing can be done for it yet.

Thanks
Basj,
Stardock Community Assistant.

Yes, however Supermium brings back support for --disable-windows10-custom-titlebar. It now works fine with that argument. However Supermium also has a flag for the same thing, which is better (since it works even if not launched from a custom shortcut), however WindowBlinds seems to not work with the flag. I have performed many tests and diagnosed that WindowBlinds is now at fault, namely due to WindowBlinds excluding Supermium unless the --disable-windows10-custom-titlebar flag is used.

I am afraid WindowBlinds cannot detect flags set inside of Chrome.  It can only detect using the command line.  Without that it correctly excludes the process to avoid half skinning it.

I realise that WindowBlinds cannot detect flags, however I would like an option to force-include Supermium, overriding the automatic exclusion.

Event 1000, Application Error with Lian Li L-Connect 2.exe

Event viewer gives:

Faulting application name: L-Connect 2.exe, version: 1.0.0.0, time stamp: 0x5c1bed83
Faulting module name: WBLIND.dll, version: 11.0.2.1, time stamp: 0x641a29db
Exception code: 0xc000041d
Fault offset: 0x0006d9bb
Faulting process id: 0x0x4F08
Faulting application start time: 0x0x1DA4FC68BB8E7DA
Faulting application path: C:\Program Files (x86)\LIAN_LI\L-Connect 2\L-Connect 2.exe
Faulting module path: C:\Program Files (x86)\Stardock\WindowBlinds\WBLIND.dll
Report Id: f576fd87-2335-4af3-9993-40da47b80768
Faulting package full name:
Faulting package-relative application ID:

L-Connect 2 does start up with windowblinds unloaded. There is nothing to see, so no screenshots! Have tried with included Corporate theme as well as Pavonis (downloaded).

Hello,
Sorry to hear you are having issues. It is known that some application can not work with Windowblinds properly. Please try to exclude this application from Windowblinds. Refer screenshot below.

Thanks
Basj,
Stardock Community Assistant.

Thanks! This works!

I know, but it slows down my PC and does not work very well at all, so I went back to L-Connect 2

I'm experiencing a compatibility issue with Macrium Reflect and latest Windowblind 11.0.2.1

Macrium Reflect is flickering under win 11 and become unresponsive. If I removed Windowblind, it works again.

Thanks...

Hello,
Sorry to hear you are having issues. You should be able to set WB to ignore any application that is not compatible with WB, by setting it into per application list.

Thanks
Basj,
Stardock Community Assistant.

Thank you. It worked.