Windows 10 Anniversary Update will not boot when WindowsBlinds 10 is installed

It sounds like you are running a somewhat old version of WindowBlinds.

Please upgrade to WindowBlinds 10.5.

Hi,

Thanks for the response.  I believe that I have version 10.5.  I will check when I get back home and let you know.

I would recommend uninstalling it, rebooting it and clean installing a new copy in case files were not replaced.

WB 10.05 had an issue like that with Anniversary update, but 10.07 and then 10.50 were released both of which should work fine.

Probably best if you had uninstalled all Stardock products before installing the anniversary update. When that loads correctly then re-install Windowblinds etc. This is the way I did it with no problems.

I wasn't having that problem after the anniversary Update; However, I was getting an error message that Windowblinds was not correctly installed.  Strangely, though, I was still able to apply skins, so it didn't bother me too much.  Well not until I realised there was an update and I couldn't access it using the 'check for updates' in WB Config.

Anyway, to cut a long story short, I uninstalled WB, rebooted and ran Ccleaner prior to reinstalling the latest edition that I downloaded from Stardock.the error message is now gone.

The upshot, Windowblinds activated without issue and all is well on my desktop.

Well I followed the advice that you gave me and now Windows 10 is fully updated and WB is functioning correctly.  Thanks a lot for your help

This happened to me too. While I love WB because I can't stand white as a background for everything, I'm really disappointed here. I had issues with it in Win8.1 (periodic loss of mouse control), and when I first installed it in Win10, my machine wouldn't boot and needed a recovery resintall. I contacted support and was told a new version was coming, so I waited. Then a new version did come out which worked OK, however I couldn't install Win10 Anniversary Update and had to revert.

Basically, I tried 2X (its a long process) separated by a few months, and only thought of uninstalling WB before the update due to your post.

Stardock should send an e-mail to every registered user of WB10 describing the issues and the solutions. Hopefully it'll work fine with the upcoming Creator's Update. They should have a note on the download page. I'd love it if searching on microsoft.com or google.com would return a clear answer, if Stardock could contact those companies. I just got lucky finding your post.

I've been a Stardock customer since OS/2 and overall I like their software.

its mainly due to the way the ui is ever changing in windows 10.unfortunately this i assume is hard to patch and fix all the time.each time windows updates the os the ui seems to change.they are talking about changing the ui even more.i got rid of my insider buils because they broke the skinning of windowblins and the looping ever since these past few insider builds lately.

yes its a hassle but stardock cannot predict what windows does.best it can do is work on a fix as good fast and efficient as they can.

especially for the insider build people know this.test at your own risk but theyve been screwing with it so much lately its not going to be worth it for awhile and prolly should just wait until the april official udate comes out.whitch as any insider knows is what we are testing on to get the final project.much like we had the anniversary build before anyone else.we saw it build from the ground up but still had the final project weeks before it came to public.

i will finish it with this statement:if you think you can do better than what stardock has been able to do over the years make your own functional program that has all the capabilities that stardock offer.if your skilled to do that let us know how many problems with windows ten you get before you get something stable.

just think its funny people can complain and blame stardock,like its so easy to accomplish.if that were the case you would be getting our subscription money,not stardock.

just food for thought

Hi juggalofrost1, I completely agree with you. I am not blaming Stardock, I was just trying to get to the root of the problem.

It I true that Stardock has to constantly play catch up with Microsoft on the Win10 UI. I was just wondering of there was an update or hot fix available for the issue. The suggestion that I completely uninstall object desktop before the update worked like a charm. Now everything works as before, with the exception of the flashing screen issues with window transitions. (Although that is a Deskcapes / Nvidia issue.) I will continue to use WB in the future as I have in many years past and continue to tinker around to find a permanent solution. Until  lthen keep the comments coming

@gef  You were correct in your analysis! Thanks so much! I would have hated to not be able to use Stardock anymore.