Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Win 10 Pro 32bit No longer able to make a System Image

Jun 12, 2018 7:10AM PDT

Hi,

Since the last update of Win 10 the 32 bit version has been corrupted not allowing a System Image to be made either to DVD's or USB HDD.

Anyone found a fix for this?

It's across all Brands & Models of Desktops & Laptops.

Discussion is locked

- Collapse -
Update
Jun 12, 2018 4:18PM PDT

Hi,

When backing up the System Image to an SSD you get this message:- The backup Failed / The RPC server is unavailable. (0x800706BA).

When backing up to DVD you get Windows found errors on the media while saving a backup and cannot use it for additional backups.

I have reformatted the HD and loaded the prior version of Win 10 32bit and can make a System Image to both HHD & DVD's so the problem is Windows 10 April 2018 Update

- Collapse -
Time to report it to Microsoft.
Jun 12, 2018 4:32PM PDT

Please post such bugs on Microsoft's own forums where they are more likely to take notice.

If there's something you learn over the years is Microsoft Backup (pick an OS or app) by Microsoft is too unreliable to trust. Use anything else.

- Collapse -
Interesting, No Problem Here On x64 Windows 10 v. 1803
Jun 13, 2018 3:00PM PDT

I just made System Images and System Repair Disks on two separate computers using the Control Panel-Backup and Restore (Windows 7)-Create a System Image backup option but they're x64 Pro versions of Windows 10. On one computer, a desktop custom build with an Intel motherboard, I used the "DVD" option and copied the system image to 11 blank DVD disks. On the other computer, which is a Sony VIAO notebook, I copied the system image to a network drive on the other desktop. Although both computers are 64 bit machines and the PRO versions of the latest Version 1803 build #17134.112 which includes yesterday/Tuesday's cumulative update, I don't understand why having a 32 bit machine would make a difference.

Just a thought: Have you tried running CHKDSK on those machines?

It seems as though the Windows 10 "upgrade" process may not install all the files correctly, or maybe they're damaged, or maybe something else, but running Chkdsk has fixed quite a few of these minor glitches. Try running Chkdsk in "repair" mode to find any damaged files and correct them. Start by opening a command prompt as an admin. RIGHT click on the Start button, choose "Command Prompt (Admin). (Or type "Command" in the search line, then RIGHT click on the "Command Prompt" listing at the top, choose "Run as admin".) Once there, type chkdsk /f /r /x, leaving the appropriate spaces between the letters as shown, then press the Enter key. You should see a note that it can't be run till a restart is done, type "Y" for yes, then press the Enter key again. Close the command prompt and restart the computer. Chkdsk will run upon restart and will take quite a while to finish.. Don't panic when the progress bar stays at 10% for a long time. It's fairly normal and the Chkdsk process may take a couple of hours.

When it's finished, it will boot to your normal startup/lock screen and you can login normally and then see if things are working correctly again.

Hope this helps.

Grif