I have updated 17763.1 several times from .1 to .17, .55, .104, .107 and now to 17763.134.  Sometimes, the Stardock Service does not initialize properly after an update.  Make sure the service is running and set it to automatically start.  Press the Windows+R keys, and in the run box enter services.msc.   Go down to the Stardock Service.  If you right-click on the service and select properties, you can reset the service to Automatic.  Then make sure the service is running.  Quite often, this is all that is needed to restart Windowblinds.

I had to roll back to 10.65 because 10.74 went all bonkers on me when I tried to change a skin. It started flashing, fading in and out and then finally it just froze. Not responding. So I opened ASC's uninstaller and clicked to uninstall WB. It went fine until the unintaller for WB stopped working. It said up top not responding then Windows crashed. I had to forces a shut down. Booted back up and ASC said the uninstall was not complete so I opened it again and finished the uninstall. Rebooted and installed WB 10.65. Rebooted again and now things are relatively back to normal. I hope they fix this thing soon. Sorry, not able to provide a screenie this time.

service running normal here but still no go

We have no experience with the version (what it may lack or restrict) but I am curious if you, yourself, chose to use that version or if it is a corporate decision / mandate? If the latter, can any IT people perhaps shed some light on any reason any service would not function as expected (GPO restrictions, etc)

Sean Drohan
Stardock Support Manager

Beginning of opinion:

I believe that there are many users (worldwide) that deploy the enterprise version of Windows 10, but they do not reside in a enterprise environment.  Nor do I believe that the LTSC update ring, or any default group policies would affect the way the Stardock service initiates.  It is important for users of Stardock apps to have a clean windows image to work with prior to installing Stardock apps.  If windows is broken, corrupted, contains old video drivers, registry hacks, other customizations, etc., then I'm not sure that it is fair to expect Stardock apps like Windowblinds to work properly.  A good starting point is to do the following:

1. Use a stable release of Windows 10 like v1803 or v1809.  Make sure that release has the latest updates applied.  For v1803. that would be 17134.407.  For v1809, that would be 17763.134.

2. Make sure video drivers are up to date.

3. Make sure the Windows image is clean.  Open up an administrative command prompt and enter "SFC /SCANNOW".  If there are still integrity violations or corruption, then there are several DISM commandlines that can be used to restore the image without needing to completely reinstall Windows.

4. Install the lastest beta of Windowblinds.

5. Use a Windowblinds 10 skin or default skin for testing.  There are skins that will run, such as older XP skins, but some don't appear to skin everything or to skin properly.

Until one is certain that Windows 10 is not the culprit, then do not assume that it is Windowblinds that is the problem.

End of Opinion.

You are saying it is an update to 17763.134.  Update from what?  Update from v1803, update from v1809 17763.107 or earlier?  Was it a clean install of Windows 10 (not an update)?  If it is an update, then the prior version of Windows may have had some corruption.  You could start by opening a command prompt and entering SFC /SCANNOW.  Have a cup of coffee and wait for SFC to finish (it could take up to 15 minutes) and see what the message says.

So you've run sfc /scannow, Windows appears OK, the video driver worked before the 17763.134 update, the Stardock service is running, you are running the latest beta of WB, and it's still not working.  I would be curious to know if you could revert back to the version of Windows 10 prior to updating to 17763.134.  You could try reverting to a system restore point prior to the update.  But the problem with system restore points is that they don't always work!  Sometimes you can go back and sometimes you can't, even when there is a restore point.  If you can't go back to a prior restore point, then Stardock probably needs to work with you to see what went wrong during the update.  The .134 update is not supposed to be a feature update...just a security update.  So it should not have hosed anything (including your video driver).  You provide an interesting case.

I am currently running .134 and it works fine.  I know that doesn't help you, but I'm not sure what is different about your update from mine.  I've noticed that even though the Stardock service is set to automatic (on my system), that it does not always initialize or run.  Sometimes, I've had to manually start the service.  That might be something to double check.

Mine is different too. WB says I have the Enterprise Edition.

Oke I have done switching and the problem still remains so it has to be on my side ! I will wait for a new version to come out and try my luck again

It's likely a registry read (that's what it says) - it has no bearing on any issues. 

----------------
Sean Drohan
Stardock Customer Service Manager

Fixed my problem did a new install and now it works but still went back to my old system I will find the bottle neck eventually

any tips welcome

STILL NOT FIXED (more then year!): CONTROL BUTTONS IN TASKBAR PREVIEW POPUP NOT SHOWN!