Link to home
Create AccountLog in
Avatar of GCITech
GCITech

asked on

Volume Shadow Copy Service error when trying to restore pc using system image

We have numerous Windows 10 Pro Acer Switch 2 tablets that we have to prep for a customer and wish to image one and apply to the rest. Prepping includes installing latest build of Windows 10 pro, removing bloatware, and installing office, and any remaining windows updates. I have one machine prepped to "backup", and have done so using system image (windows 7 restore).
When i go to apply this image to another tablet (boot to windows 10 usb drive, repair pc, troubleshoot, system image restore)
select the image off of my external hdd, and get the following error immediately after starting the restore:

Re-image your computer

The system image restore failed.

Error details: A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information. (0x80042302).

Any idea what could be causing this?
Avatar of 8046586
8046586
Flag of United States of America image

Buy Acronis Snap Deploy licences (they are very cheap) and you can create the master image and deploy with standalone bootable USB. Very easy, very intuitive. Universal Restore feature is integrated (restoring to different hardware). Restore will reset all SID numbers on first boot. Image creation and deploy time is less than 15 min.
Avatar of Zaheer Iqbal
Have you tried to look for the service in services and what is its state ?

Microsoft Software Shadow Copy Provider".

Properties: Automatic startup, apply and the Start

Should be Automatic and Started.
SOLUTION
Avatar of McKnife
McKnife
Flag of Germany image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of GCITech
GCITech

ASKER

Thank you for the article! We ended up prepping the machines and imaging them before we updated Windows 10, allowing success because its on an earlier build. Glad to know the issue was not just me.