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.
Hello,I have forwarded your observation to the Stardock Support team for their review. We appreciate you feedback.
Thank You,BasjStardock Community Assistant.
Thanks for the report.
Whilst our position is always that we do not support Insider builds (especially Fast Ring ones!), we are able to reproduce the problem and have fixed it internally.
I cannot promise when any update would come out though as we are rather close to Christmas now.
Thanks for the update.
Looking forward to the fix. Desktop is looking pretty dull for now.
Merry Xmas to all of you!
Thanks. I am having the same problems.
I just installed 19536.1000 SR_Prerelease version and have been having problems with my desktop back ground not displaying properly (Displaying a black screen instead of Background), and the taskbar icons are not refreshing/mapping correctly. The program icons in the taskbar may show the same icon for all or more than one open program, and on the right side, the icons may be all bunched up/overlapping each other.
I do use Stardock's Deskscapes to display Animated backgrounds. This has never been an issue until now. Also, the desktop manager seems to be crashing and rebooting when I right-click the background. When that happens(And when I first login), the background displays correctly, but then it seems the desktop manager takes over agin and the background goes black.
And this is not an isolated incident, I have three separate machines, on different networks and domains that all are doing the exact same thing.
This is alas one of the risks of using fast ring build versions of Windows. Given Microsoft's recent decision to make the fast ring builds even more early alpha build level (starting with this insider build apparently) you may well start to experience more compatibility issues with software from many companies.
I would strongly urge that unless you need to run fast ring builds in a testing environment that they are avoided.
Any idea when an update will be released?
I have not yet heard about any update being released yet. I too, am anxious to get my Deskscapes working normally again.
Same here, desktop is pretty dull without DeskScapes.
I understand from your other post that you are not using this prerelease version of Windows that's the issue here which is unrelated to your problem.
The other post you are referring to was only simply to add clarification. I simply wanted to point that out to AzDude that the versioning info was in the OP.
As far as my system, I am on the fast ring myself and DeskScapes is a black screen . A new build is coming this week...
The new build 19541 did not correct anything as far as DeskScapes is concerned. Still black screen.
I am not seeing any change after the 19541.1 update either. I am hoping Stardock can come up with a fix for this soon.
Other issues I have seen as late are issues related to permissions... With Windows 10 getting more secure, it has been locking down permissions on file shares and other file storage.
Thank you. While I appreciate your “Get what you ask for” attitude, you should appreciate that those of us on the fast ring are on the front lines, and you should embrace that. WE are the front line of what is to come. Don’t berate us for being on the front line. HELP US!!!!!
The 'front line' is for people who know and understand that things WILL break.
You either live with that or you withdraw from 'the front line'.
If you want the latest and greatest with Microsoft Windows 10...all you will ever get is 'the latest'. It will NEVER be 'greatest'.
Been with Tecknet for years...and know for a fact that you are your worst enemy doing so...if you want pain-free computing...
There is exactly zero reason to play ambulance-chaser for Microsoft's alpha failures - only to see the time and effort reversed or futile after the next 'latest and greatest' release.
What an arrogant statement. You know nothing about me or my experience.
I have been dealing with Microsoft and Stardock products for a VERY long time (Think Decades). I am VERY familiar with TechNet (Notice there is no "k" in TechNet), and other products including the Fast Ring and other systems.
I am VERY aware of the inherent risks and dangers of these products. But, as a participant in these products it is also a responsibility to report issues that one is having. That is part of the responsibility of participating.
The only enemy and danger I see here are people that participate in forums and proceed to give arrogant uninformed lectures and not even offer a shred of constructive feedback or knowledge.
If you don't have something constructive to offer, please keep such criticisms to yourself.
If Stardock is not interested in hearing about issues end users are having, then maybe there should not be a forum.
Thanks Neil. This comment is appreciated, and I am looking forward to any possible fix you come up with.
But there-in lies the problem. When 'toying' with a beta it's perhaps your responsibility to report issues you are having with the provider of the beta...and that's actually Microsoft in this case.
Stardock's Object Desktop subscription service provides users with access to STARDOCK's program betas, and likewise it's the users' responsibility to communicate issues with the beta use...to Stardock.
What isn't going to be of real benefit is to communicate issues you have to the wrong party, though in your case I am certain Microsoft is not going to care one little bit that you have issues with a third party product. They are too busy trying to get their own OS to work properly with itself....
But there-in lies the problem. When 'toying' with a beta it's perhaps your responsibility to report issues you are having with the provider of the beta...and that's actually Microsoft in this case.Stardock's Object Desktop subscription service provides users with access to STARDOCK's program betas, and likewise it's the users' responsibility to communicate issues with the beta use...to Stardock.What isn't going to be of real benefit is to communicate issues you have to the wrong party, though in your case I am certain Microsoft is not going to care one little bit that you have issues with a third party product. They are too busy trying to get their own OS to work properly with itself....
I think it is ones responsibility to report the issue to all parties involved.... Which I have from the beginning.
At least from the Microsoft Team, I get some serious interest, not just deflection on how it's not their problem.
I am sorry you have such disdain for Windows, but rhetoric and baseless statements do not do anything to fix the problem.
Of course, Microsoft's answer could be to block an incompatible program from going forward, if it is found to be a problem with compatibility. I would hate to see Deskscapes put in that category.
Neil here at least has acknowledged the problem behavior, that is encouraging that maybe there is some serious investigation.
I reported the problem on MS Feedback hub the same day I posted in this forum.I agree that both parties need to be made aware of the issue as well.
100% agreement!
Not too close to Christmas now. Any idea if or when fix will be released?
It is awaiting QA as we want to be sure it doesn't break other OSes!
Excellent. Looking forward to it, little or no change moving on to version 19546
any updates forthcoming with DeskScape
There are many great features available to you once you register, including:
Sign in or Create Account
