Windowblinds 10 suddenly stopped working

from Stardock Forums

Windowblinds suddenly stopped skinning my windows. I tried uninstalling and reinstalling WindowBlinds_10.7.4_setup_sd.exe with no effect. 

 

The WB system tray icon is also missing. If I run Windowblinds from the start menu, I get the usual interface, but the "Apply style to desktop" button just does the usual freezing and blurring of my screens with the Loading throbber...but doesn't actually apply the skin. 

 

I have no idea what triggered this...maybe one of those background Windows updates?

 

The only related thing I can find running in Task Manager is the WindowBlinds Service. 

 

Windows 10 version is 1803 (OS Build 17134.590).

 

Help! How do I fix this? The normal appearance of Windows 10 gives me hives, so this is kind of urgent...

windowblinds
9,502 views 8 replies
Reply #2 from Stardock Forums Top

Thanks for the reply. Tried what you suggested, but it didn't have any effect. 

Also ran sfc /scannow, but it didn't find anything. 

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from WinCustomize Forums Top

Oh hell! That would be frustrating standard Windows I hope you found a fix by now as there will always be one I thought it was me that always had the weird scenarios going on good luck!:hrmph:  

Reply #4 from Stardock Forums Top

The most frustrating thing is that I've been using the Lantana skin for, like, forever, so my desktop without it just looks so barren and alien. 

Wish I had some idea what caused this. Just woke up to it this morning. 

Reply #5 from WinCustomize Forums Top

Hello,

Sorry to hear you are having issues. Please try the cleanboot steps to see if there conflicting apps : https://forums.wincustomize.com/486023/windowblinds-support-faq#cleanboot

Try it and let us know.

Thanks

Basj,

Stardock Community Assistant.

Reply #6 from Stardock Forums Top

Okay, I did this:

 

1) Created a new Windows 10 administrator account.

2) Switched to that account.

3) Noted that the WB icon wasn't in the system tray.

4) Noted that windows weren't skinned.

5) Found that WB was in the Start Menu, so I ran it. 

6) Noted that most of the installed skins weren't available. Chose one that was, but after loading it, it didn't apply. 

7) Ran the Purge_WB.bat script.

8) Tried to reinstall WB, but was halted by the error "Setup can not create the following folder: C:\Users\Public\Documents\Stardock\Windowblinds\Diamond", after which the setup aborted.

9) Switched back to my normal Windows 10 user account, successfully reinstalled WB; rebooted.

10) Switched to the new Windows 10 account.

11) Noted that the WB icon wasn't in the system tray.

12) Noted that windows weren't skinned.

13) Found that WB was in the Start Menu, so I ran it.

14) Noted that there were only a few of the usual skins available; loaded the Win8 skin...successfully!

15) Switched back to my normal Windows 10 user account.

16) Noted that the WB icon wasn't in the system tray.

17) Noted that windows weren't skinned.

18) Found that WB was in the Start Menu, so I ran it.

19) Noted that all the usual skins were available. Loaded the Lantana 2 skin; it didn't apply. 

20) Tried loading the Win8 skin...and it worked!

21) Again tried loading the Lantana 2 skin, but this time nothing happened when I clicked the "Apply style to desktop" button. Restarted the WB program; the button still doesn't work. 

22) Noted that the WB icon was now in the system tray.

 

So I've managed to replace the ugly Windows 10 style...but why can I no longer access the Lantana skin?

Reply #7 from Stardock Forums Top

HA! Finally got it working!

1) Ran the Purge_WB.bat script again.

2) Noted that the script did not delete the C:\Users\Public\Documents\Stardock\Windowblinds\ folder. Deleted that folder manually.

3) Reinstalled WB, and was able to apply the Lantana 2 skin.

 

So...it's working, but what was the problem? 

And why the heck is WB storing its default skins in the C:\Users\Public\Documents\Stardock\Windowblinds\ folder???

Reply #8 from Stardock Forums Top

Hello,

Great, you solved it.

Thank you,

 

Basj,

Stardock Community Assistant