Issue when applying background in DeskScapes » Forum Post by ChicagoRican

Have you tried the latest Beta 11.0.2.0? I think this version fixed that issue.

Successfully updated karma reason!

Yes. I have the current beta build.

I've had this problem for about the three last builds.

Successfully updated karma reason!

Hello,
Sorry to hear you are having issues. Have you tried changing this settings?

Also, try changing the video setting in "Performance" tab. Try all 3 and see if any of them help.

Thank you.
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

Thanks for the suggestions. I applied them all, but it did not help. I also went into the Advance tab and cleared out the caches.

Successfully updated karma reason!

Is this a new system install with Windows 11 24H2? or an upgrade install from Win 11 23H2?

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

It's an upgrade from 23H2.

Thanks Basj.

Successfully updated karma reason!

I still had the issue with 23H2.

Successfully updated karma reason!

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

Hi Basj,

I gave the purge and reinstall a try. I actually did it twice. I also applied the performance tab changes as you had directed before. I also went into the Advance tab and cleared out the caches.

I applied this fix on my user account and also to the Administrator account.

The problem unfortunately still continues. It is only affecting animated wallpaper. Static wallpapers work fine.

Thanks again,

Milton

Successfully updated karma reason!

Please try cleanboot and see if there is conflicting issue with other software: https://forums.stardock.com/485954/deskscapes-support-faq#cleanboot.

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

I tried cleanboot and it completely trashed my computer. I get a blue screen now. It gives me 3 options that only take me to the same blue screen and one option that takes me to the bios.

Successfully updated karma reason!

Quoting ChicagoRican,

reply 11

I tried cleanboot and it completely trashed my computer. I get a blue screen now. It gives me 3 options that only take me to the same blue screen and one option that takes me to the bios.

That's happened to me before. You have to be really careful when initiating a clean boot that you don't turn off any Windows services. And always perform a image backup before starting a clean boot just in case. It's really not something for the inexperienced user should attempt.

Successfully updated karma reason!

Any help on getting my pc back? I have a recovery usb flash drive.

The blue screen that I get is:

Recovery

Your PC/Device needs to be repaired

A required device isn't connected or can't be accessed

Error code 0xc0000225

You'll need to use use Recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

Press Enter to try again

Press F1 to enter Recovery Environment

Press F8 for Startup Settings

Press Esc for UEFI Firmware Settings

When I Press Enter, I get:

File: /WINDOWS/system32/winload.efi

Error Code: 0xc0000225

Successfully updated karma reason!

What happens if you press F8?

If your BIOS is configured to boot from a USB drive before the SSD or HD, you should be able to recover if you have backup media stored somewhere. If you don't have backup media, I'm not sure what your options are.

Try the Startup Repair shown in Reply #15

Successfully updated karma reason!

How to use the Startup Repair Function on Windows 11

Startup Repair helps you fix common problems that can prevent Windows from starting up.

Note: If you’ve encrypted your device, you’ll need your BitLocker key to start in safe mode.

First, you need to enter the Windows Recovery Environment (winRE). To do this, you will repeatedly turn your device off, then on:

Hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
On the first sign that Windows has started (for example, some devices show the manufacturer’s logo when restarting) hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
When Windows starts again, hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
This time, allow your device to fully start up.
Select Advanced options.
Now that you're in winRE, on the Choose an option screen, select Troubleshoot > Advanced options > Startup Repair > Restart.

Successfully updated karma reason!

Well, Dell Tech instructed me to completely wipe out my pc and all attached hard drive and NVME drives. Everything. Pristine New Installation. Everything else wiped out too. I have to reinstall everything I had before I Clean Booted my PC.

Successfully updated karma reason!

Hello,

I am sorry this happened to your system. I have asked client doing Cleanboot a lots, and so far I never have a client reporting back with blue screen issue due to the cleanboot steps. Its the second most suggested steps after "purge and reinstall" guide from me. I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Once again, I am sorry.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

Quoting basj,

reply 17

Hello,

I am sorry this happened to your system. I have asked client doing Cleanboot a lots, and so far I never have a client reporting back with blue screen issue due to the cleanboot steps. Its the second most suggested steps after "purge and reinstall" guide from me. I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Once again, I am sorry.

Basj,
Stardock Community Assistant

I find that suggesting to a user to clean boot their machines is very risky, especially for an inexperienced user. It is very easy to end up like ChicagoRican. I know first hand because it has happened to me, and I am an advanced user. Thankfully, I had an image backup from a week before it happened and all my files were backed up on OneDrive.

My recommendation would be to only advise those who you know to be experienced enough to perform the operation to try a clean boot. In my opinion, advising people who you no nothing about, nor their experience level, to clean boot their machine is not really a good path to take.

pelaird

Successfully updated karma reason!

If you read through Clean boot Documentation from Microsoft : Cleanboot which the same link posted in that Stardock guide link I posted above and another Stardock Deskscape Cleanboot new support page : https://support.stardock.com/space/SHC/1346928700/DeskScapes+Clean+Boot. I don't see any warning on these steps. No warning at all posted by Microsoft in their own documentation for clean boot. I believe there are something wrong already in the system itself prior Cleanboot was done. Anyway, I have forward this issue to support for their review and advice on this one.

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

Hi Basj / Peliard,

Now that I have my pc in pristine "Dell/Alienware" condition, I reinstalled the Stardock software. Deskscapes is at 11.02 version. My Windows build is now 23H2.

I have no problems to report now.

You may closeout any trouble ticket with Tech Support.

Thanks,

ChicagoRican

+1

Successfully updated karma reason!

Quoting ChicagoRican,

reply 20

Hi Basj / Peliard,

Now that I have my pc in pristine "Dell/Alienware" condition, I reinstalled the Stardock software. Deskscapes is at 11.02 version. My Windows build is now 23H2.

I have no problems to report now.

You may closeout any trouble ticket with Tech Support.

Thanks,

ChicagoRican

Happy to hear you got your PC back in working order. I'm sure it was very frustrating. Having to rebuild everything from scratch can be very tedious, especially when trying to get application settings back to where you had them prior to the crash. If you don't have one, get yourself an external HD and use backup software to backup an image of your boot drive at least once a week. Most backup software allows you to automate this process, so it can run at night while you're sleeping.

+1

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+645

Quoting pelaird,

reply 18

I find that suggesting to a user to clean boot their machines is very risky, especially for an inexperienced user. It is very easy to end up like ChicagoRican. I know first hand because it has happened to me, and I am an advanced user. Thankfully, I had an image backup from a week before it happened and all my files were backed up on OneDrive.

My recommendation would be to only advise those who you know to be experienced enough to perform the operation to try a clean boot. In my opinion, advising people who you no nothing about, nor their experience level, to clean boot their machine is not really a good path to take.

pelaird

Quoting basj,

reply 19

If you read through Clean boot Documentation from Microsoft : Cleanboot which the same link posted in that Stardock guide link I posted above and another Stardock Deskscape Cleanboot new support page : https://support.stardock.com/space/SHC/1346928700/DeskScapes+Clean+Boot. I don't see any warning on these steps. No warning at all posted by Microsoft in their own documentation for clean boot. I believe there are something wrong already in the system itself prior Cleanboot was done. Anyway, I have forward this issue to support for their review and advice on this one.

Thank you,

Basj,
Stardock Community Assistant

While I sympathize with the end user, basj is pointing out a view we share; that a clean boot is not a Stardock recommendation alone, it's a well-documented Windows from Microsoft themselves one. Several things were tried before this and when this eventual step was reached, it clearly exposed a root issue with the PC. If any more evidence was needed for this, when a clean reinstall was done, all is reported working, windows itself as well as our product.

I am pleased that this did not turn out to be some form of hardware failure.

Sean Drohan
Stardock Product Lifecycle Manager

+1

Successfully updated karma reason!

Quoting sdrohan,

reply 22

While I sympathize with the end user, basj is pointing out a view we share; that a clean boot is not a Stardock recommendation alone, it's a well-documented Windows from Microsoft themselves one.

Yes, everything you say is true, but the System Configuration utility is a very powerful tool, and if the directions are not followed correctly, it can lead to an unusable system. All I was saying, is that one's experience level with the Windows Operating System should be considered when advising a Clean boot on their system.

All it takes is forgetting to check the box "Hide all Microsoft services," and your in real trouble.

Maybe add a precaution like, "If you are comfortable with running an advanced system utility" before recommending a Clean Boot to a user. Also, maybe recommend backing up their boot drive before performing a Clean Boot.

+2

Successfully updated karma reason!