WindowBlinds Not loading or working on Windows 10 Version 2004

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Hello,
Sorry to hear you are having issues. Please try uninstall Windowblinds, reboot and reinstall the latest version downloaded from your account. Reboot, retest and report back.

Thanks

Basj,
Stardock Community Assistant.

I have done this 3 times already with no luck.  There is no WB icon in the Notification area.  WB is running under services, but not skinning correctly.  Registry files look good.  

Please try the purge and reinstall steps. Use this link for it : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Just make sure to re-download the latest installer from your account. Reboot after the purge, reinstall using the installer you just download, reboot and retest. Report back.

Thank you,

Basj,
Stardock Community Assistant.

Still not working.  WB needs to be updated to work with the latest version of Windows.  Thanks.

I don't think its WB issue since, I believe, Stardock Dev team has been on it ever since v2004 on insider stage. And if it an issue, we should have more report from others on it.  Anyway, I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Will do.  The latest Windows release (2004) was released 8 days ago officially.  Most probably don't have it yet.  Thanks for your help.  I hope issue is resolved soon.

While waiting for them. Maybe you can elaborate more on this part. Which part is not skinning correctly? Which part look skinned, if any. And if the issue happen on all style or specific style.

Thank you,

Basj
Stardock Community Assistant.

The issue is for all four styles that I have tried even the pre-installed ones.  The specifics that aren't skinned are pretty much everything except for Explorer background color.  When WB style (.wba) is applied it will take a good minute before finished and with no changes. It seems to skin Google Chrome though.

Well I just update my VM system to Windows 10 v2004 and Windowblinds run without issue for me.

Would like to know what versions of Windowblinds you have installed in your system.

Note : BTW my VM have issues when I tried updating my V1909. Not really sure why but it keep revert back to v1909 on second boot after the v2004 installations. I finally manage to update to v2004 but its a fresh installed. And everything need to reinstalled. Not sure if that might help on your case too.

Thank you,

Basj
Stardock Community Assistant.

The most recent stable Windows 10 release is installed. I have read elsewhere that Stardock is working on a new version of WindowBlinds. We will see.

Do you use ESET antivirus?

There are no known issues with WB on Windows10 build 2004 so the problem will be something interfering with WindowBlinds.

I updated to 2004 and I have no problem with WB or any of the other Stardock programs. I think it's your computer. There's something interfering with WB.

Well Damn.  I am going to try to figure out what the problem might be.  The last thing I want to do is a clean install of windows.

No.  I use Bitdefender TS and MB

Please be sure that you are running the latest graphics adapter driver with Windows 10 v2004.  With some upgrades to new versions of Windows, the graphics adapter driver also needs to  be updated.  Switchable graphics on laptops can be quite temperamental as we migrate to newer versions of windows.

You can quickly access device manager by pressing the Windows + R key and entering devmgmt.msc to open the device manager.  Click on the plus sign next to "display adapters" and see which brand of adapter you have.  Then go to the manufacturers website and download the appropriate driver for your display adapter and install it.  Almost all adapters are either Nvidia, AMD, or Intel UHD graphics.

-R

I have found that if ESET Nod32 is installed, WindowBlinds will report an error after installation. Even after a reboot.
Since Nod32 cannot be simply turned off, the test is also difficult. To be sure, on the same hardware, the same Win10 v2004 (Build 19401.369) is reinstalled, WindowBlinds does not indicate an error. Only Nod32 can be the cause of the error.
Please contact them and clarify the problem.

This has been a known issue for quite some time, it would appear that Eset has no interest in addressing it.  You need to set a rule in Eset's HIPS section to allow WB.  I'm not sure how current this guide is, an update to Eset may have changed the layout, but hopefully you can follow it:

http://esupport.stardock.com/index.php?/default_import/Knowledgebase/Article/View/424/124/windowblinds-states-that-windowblinds-is-not-installed-correctly-on-this-pc

The suggested Nod32 settings solved the problem. Thanks for the solution.

Just wanted to mention that a fresh install of W 10 2004 has WB running flawlessly.  

Thanks for the help

Great, glad it get solved.

Thank you,

Basj,
Stardock Community Assistant