Windows 10: "Shadow Copies of volume C: aborted" (Event ID 36)...

Hi,



The error wiil also crop up when you run Wise Diskcleaner's Advanced cleaning and let it create a restore point while have the feature disabled.
Possibly any other software that tries to do the same thing too.



Cheers, *Wink

 

Macrium (and pretty much every backup software) uses VSS.

Funnily enough I replaced Apple HFS driver with Paragon HFS driver as it didn't cause the issue. Perhaps their EXTFS is less good or it could be a red-herring.

If you don't care to make restore points and whatever backup software you use works I'd not worry about it but the drivers are loaded earlier in the boot process. You'd have to stop the driver loading with autoruns not just disable the service.

 

I use Macrium Reflect to frequently save image files to an external hard drive. That works well for me. It is the main reason I feel OK with disabling System Restore.

Are shadow copies the same as restore points, or how are they related to one another?

I'm not inclined to remove ExtFS for Windows. I don't use it all of the time, but it is handy to have every once in a while.

Is there anything else you'd recommend doing to address the Event ID 36, or can I safely ignore?

Thanks for all the info!

 

In the case of Macrium and like software, shadow copies are simply a snapshot mechanism to "freeze" a pic of the image while it's being created. So as to not try to deal with a moving target. There are several VSS writers, at least 5 or 6, that capture any data trying to be written so the image is pure. When Macrium and others finish, you will see they are "closing" VSS, which means they are checkpointing the data held back.....flushing it to get the SSD/HDD back up to date. They're not Restore Points, just temp holding areas.

 

What @f14tomcat says is correct. My Apple HFS driver broke VSS (so both restore points and Macrium).

If Macrium is working (and it tells you if it is not) then don't worry about it.

 

Hi,



The event log is generated by Windows itself in this case. It tries to create a restore point but it can't due to the imposed space limit.
That's why I suggested TS to look at the registry because something is not correct.
No big deal if left as is but still.


Cheers, *Wink

 

Thanks for the replies and info.

Yes, I just did an image backup with Macrium Reflect, and it reported successful completion.

I will take a look at the registry info fdegrove posted in reply #10 and compare it to mine. I'll see if I can determine why Windows thinks system protection is enabled.

Thanks again *Smile

 

I did not see anything obviously wrong with my registry entries for volsnap and enum. Below are screen clips of registry and my system properties showing protection off for all drives.

Let me know if you see anything "off" that I may have missed. My next step will be to follow the instructions from the support forum...

Thanks!