I did notice in Task Manager under Details-UAC virtualization that DS was 'not allowed'.
Gary56
I'm a longtime Stardock user & have Object Desktop. Will certainly be looking forward to the new release!
Unfortunately the 4 second configwindow , which doesn't show a preview (because it's trying to load), doesn't allow for any activation within it. I did start from scratch by uninstalling DS, reboot, ran your .bat file, reboot, went to my latest download of DS on my Stardock page, downloaded, reboot. I was able to find those display controls for quality vs performance and they didn't have any affect with the configuration.exe. But I'm happy to be able to run DS dreams, even though I do
Hello, I did uninstall the Elecard and my Dreams actually ran fine w/o it, whereas with the previous Windows build, it needed the plug in. I rebooted each step of the way and again the configuration.exe stayed up for the 4 secs. before closing. I did notice that when the config window was previously working, it showed the preview Dream working, whereas now, before closing it says 'Loading Background Preview'. In other words when it was function
Thank you for the troubleshoot AzDude! Again, followed your directions to a 'T' and double checked on the Windows Firewall to make sure DeskScapesconfig.exe was allowed. Same 4 second results. Don't know if using Elecard Mpeg-2 plugin would affect this!? However, it never did in the past with the configuration.
Followed your directions perfectly AzDude (sorry for taking so long to get back. Process of finding a new home, packing, etc.) to a T. Unfortunately the same issue arises. Edition Windows 10 Pro Processor Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz 2.40 GHz Installed RAM 16.0 GB (15.9 GB usable) Device ID 26B43ECB-5453-45BA-B6CB-1F7D97071F8E Product ID 00330-80000-00000-AA601 System type 64-bit operating system, x64-based processor Pen
Has anyone else experienced DeskScapes suddenly closing after opening the configuration window? I'm Using Windows 10 Pro build 20H2 and any DeskScape I install or run, runs perfectly well. It's just the configuration window automatically closes down & noticed this only happening after the latest Windows update...