Registry cleaner possible cause of Windows backup error 0x8078005d

CCleaner for Windows CCleaner Windows Bug Reporting
1

I upgraded to Windows 10 from Windows 7 many months ago, but prefer the still offered 'Windows 7 backup' which creates an image as well as daily file backups vs the Windows 10 file history method. I have been running the 'Windows 7 backup' every evening at 4 AM without error.

After running the registry cleaner in CCleaner, the version was that immediately prior to 5.16.5551 (64-bit) the next morning I noticed that my backup had failed. All attempts to run it immediatly, to a variety of drives, failed with an error report that backup cannot find the drive assigned as output. The error code is 0x8078005d.

I found this article: https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/when-i-backup-i-get-error-0x8078005d/774fcb06-edf9-4fd1-b244-5c47d87483b4?auth=1

The article suggested three registry changes to restore functionality. They didn't help.

The 2nd suggested change was to unregister WMIUTILS.DLL, reboot, re-register WMIUTILS.DLL, reboot and try to rerun backup.

That change was successful and backup has been writing to the backup drive successfully each evening for the last week, just has it had been doing for months prior to the difficulty.

I do not know if CCleaner created some issue re WMIUTILS.DLL registration, but it seems possible. I have run CCleaner for so many years without backing up the registry changes and never experiencing any issues. I will avail myself of the backup registry change option when I run the registry cleaner in the future.

Ron Stordahl

2

While I am sorry you had difficulties, it sounds, to me, like you blindly cleaned everything that came up in the registry section without prejudice, despite ccleaner giving you multiple chances to look at and only remove the ones you know you don't need. As you've now experienced, this can be quite hazardous to the computer. This would be true, if not truer, with other registry cleaning software too.

In the future might I suggest following the advise below this post, in my signature.