neveready

Windows 10 Build 19536.1

Windows 10 Build 19536.1

Not Working in New Windows 10 build

I just updated to Win 10 Build 19536.1 and desktop does not work. The program works and shows animated backgrounds but PC screen is totally black. I'm quite sure it is a Microsoft problem but just wanted to make you aware of it.

141,104 views 56 replies
Reply #51 Top

Quoting ot7849, reply 50

okvb,

The issue has been addressed by MS in their most recent build 19564.1005.
DS 10 is now working again as it should.

 

Confirmed!  Three workstations updated to 19564.1005 and Deskscapes is working on them again.  B)

Reply #52 Top

Confirmed.  Yes MS has addressed the transistion thingy as stated in their release notes.  Deskscapes 10 is working well in build 19564.

Reply #53 Top

Actually, my Build is 19559; Uninstalled DS 8; Rebooted; Ran DS Purge; Rebooted; Installed DS 10; Program runs, but does not run choice onto Desktop; Black Screen again

 

Uninstalled DS 10 again; Back to DS 8

Reply #54 Top

Quoting okvb, reply 53

Actually, my Build is 19559; Uninstalled DS 8; Rebooted; Ran DS Purge; Rebooted; Installed DS 10; Program runs, but does not run choice onto Desktop; Black Screen again

 

Uninstalled DS 10 again; Back to DS 8

You are correct, 19559 DOES NOT work, but if you update to 19564 it does work as it should.

Reply #55 Top

Quoting mike-MACS, reply 54


Quoting okvb,

Actually, my Build is 19559; Uninstalled DS 8; Rebooted; Ran DS Purge; Rebooted; Installed DS 10; Program runs, but does not run choice onto Desktop; Black Screen again

 

Uninstalled DS 10 again; Back to DS 8



You are correct, 19559 DOES NOT work, but if you update to 19564 it does work as it should.

 

Correct 19564 is the right one to upgrade and then DS10 will work flawlessly.

Reply #56 Top

Going to close this thread but make one last statement on it.

Stardock will no longer be 'soft supporting' Windows Insider builds on the Fast Ring.  While we technically never did, we will not work to resolve any issues unless they still exist in the Slow Ring.  This thread, and MS fixing what they broke, while still in the Fast Ring, should be evidence as to why we are going this route. 
 
That is NOT to say we don't want you all to still report issues - to us, that is still vital - however, we won't allocate any resources to resolve issues seen in the Fast Ring unless they still show up in the Slow.  
 
Again, thanks for the reports and your support.
 
Sean Drohan
Stardock Support Manager