I went to my StarDock account and saw that there's v10.65 and no v10.71. Did I miss the meeting? I'm currently running 10.71 on my Win 10. Was there a problem with it and should I go back to 10.65?
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
AzDudeStardock 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://www.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.
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 .
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
