Great point Al. I would like to know the same answer. 

Am I now waiting to click on something and have a major problem????????

Hello,

Wa What Happened ?

10.71 is getting a make over for another new release ,

after it came out they decided to pull it back and add even more fixes to it .

STAY _ TUNED 

AzDude
Stardock Community Assistant

Thanks for the update. I was having problems with the acrylic blur on the Naked Noir skin.

Colleagues:

If you need to download v10.71, as of yesterday, it could still be found at the following link:

https://stardock.cachefly.net/WindowBlinds_10.71_setup_sd.exe

However, my personal experience has shown that while it seems stable with Windows 10 v1803 17134.320, as you upgrade to Windows 10 v1809 17763.1 (October 2018 upgrade), it does not seem to properly skin the frames of the PC Settings screens.  The minimize, maximize, and exit buttons do not skin and work properly.  So keep in mind that if you decide to install 10.71, when you upgrade to the new version of Windows 10, it does not work correctly.  I have not tested 10.65 with the new Window 10 upgrade.

~Roger

I have been using 10.65 on win10 since it was released and have no problems or situations. Some have reported problems with this or that. some of these problems may not be noticed by some. I believe it has to do with some have this or that installed and some don't.

So if 10.71 doesn’t work on 1809 and you haven’t tested 10.65 what version are you using or you just using the Win 10 theme?

As for 10.71 I already have it saved in my Stardock back up folder. 

I have installed v1809 in a VM and on a separate PC.  Windowblinds v10.65 works perfectly on both.  v10.71 does not.  It has the problem with skinning the min,  max, and exit buttons on the PC Settings screen as previous mentioned.   So v10.65 has been tested and works for me.

That probably why Stardock pulled 10.71 so they can fix it for 1809.

Is WindowBlinds dead? The fix for the for the six month old Windows update has been pulled and now there's no fix in sight for the current Windows update. If Microsft continues its pattern of six month releases and Stardock continues to take more than six months to patch WindowBlinds there isn't much chance of a fix. It makes me sad!

No, Windowblinds is not dead.  Keep in mind that there is a license agreement to support the product that you paid for.  I think Stardock would let us know if they intended to stop updating and supporting Windowblinds.

I suspect that there have been some unforeseen and unexpected issues with the recent release of Windows 10.71 related to the new release of Windows 10 v1809.  My opinion is that these issues should have been anticipated better because Redstone5 has been out for quite awhile and Windowblinds should have been fully tested prior to the formal release of Windows 10 v1809.  If I were the project manager, I would be intensifying the effort to stabilize Windows 10.71, and re-release Windowblinds asap.  I suspect that something resembling this is going on with Stardock.

~Roger

Hello,

Sorry to hear you are having issues.

and Window Blinds is not dead and as seen this past week Microsoft doesn't even have v1809

right yet it was pulled back  , so when the next release for WB is ready all will be notified and it

will be available for download . Patience please till then . 

AzDude
Stardock Community Assistant

And here we are in 2020 and it still does not work right. Yes its dead. I feel sorry for people who paid for this in the past year. Take the money and run stardock. Its obvious you lack the programmers needed to keep up with windows 10 updates.

I'm on windows build 2004 I don't even use windowblinds any more untill there is a decend update tbh

What problems are you having since a Windows update?

I am not aware of any problems with the 2004 update and WindowBlinds.

BSOD out of the blue deinstalled windowblinds and they are gone even made a new windows install for that to make sure btw I'm not 100% sure windowblinds was the culprit but not even gone install it again to make sure not to be in the same situation again with the BSOD's

It should not be possible for a BSOD to be caused by WindowBlinds as a BSOD requires a kernel level issue and WindowBlinds does not have any kernel components.  The most likely cause is a buggy driver update.

Whatever I do have my reasons to think it was windowblinds no biggy not to use it at this point thx for the response

I am running WindowBlinds 10.84 (059 - Windows 10 Edition) - 64 bit OS on Windows 10, Version 2004, (OS Build 19041.450) here with absolutely no issues. A lot of my friends are too and have no issues. So I think what Neil is saying would probably be something to investigate masterbas.

It took me a month trough trial and error to figure out that it was caused specific on my system with windowblinds installed after removing the software I had zero BSOD's and with the software installed I had 3 BSOD at least a day so. That is the reason I answered with wathever because I had a lot of frustration for a month on my system and after stating it here on the forum I get nobody has problems with windows 2004 and windowblinds well I had so go figure that out. I rather would like an question as what could have coused the BSOD's and which combo of software running on my system caused the triggering in combination with the Windowblinds software then Neil his reply with the Kernel level not being used by windowblinds so that could not be the cause makes me feel being treated as a newby I have many years experience with windowclinds and trust me I have seen some weirds stuff in the past caused by combinations of different software just my 2 cents

Is your Windows event log showing any indication of what is happening?

Sean Drohan
Stardock Support Manager