Five Errors with AOMEI Backerupper

I have a daily backup that fires with AOMEI Backerupper and it's triggering five errors every time it runs on Windows 11:

```
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {202f2c0a-1cea-4289-a06a-11dbd425a2e5}
```

```
Volume Shadow Copy Service error: Unexpected error while calling GetStorageDependencyInformation. hr = 0x80070032, The request is not supported.
.

Operation:
Automatically choosing a diff-area volume
Processing EndPrepareSnapshots

Context:
Execution Context: System Provider

Error-specific details:
Error: (0x80070032) The request is not supported.

```

```
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {202f2c0a-1cea-4289-a06a-11dbd425a2e5}
```

```
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {202f2c0a-1cea-4289-a06a-11dbd425a2e5}
```

```
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {202f2c0a-1cea-4289-a06a-11dbd425a2e5}
```

Any assistance would be appreciated.

Problem seems to be with VSS.

Google "fix aoemi vss problems" and the AI overview is surprisingly quite helpful (I rarely find that) with advice how to fix issues.

When does these errors occur , when making backup or restoring backup ......??

I did an online search for these types of VSS errors, and it can sometimes be related to the setup of some services in the Services Applet (services.msc) in Windows.

One service is called 'Volume Shadow Copy' the other is 'Microsoft Software Shadow Copy Provider'. One possible solution is to set these services to automatic then do a reboot.
There is quite a lot of information about this online, but you may need to do a search on Google.


(Microsoft Answers)

I don't guarantee this is the solution, but you may want to investigate this.

Thank you very much for all the assistance, all! I have to admit I got lazy here and searched "AOMEI Backerupper Forums" and decided to post here because a thread from this forum was one of the first results and I have had so much luck with TenForums.com

To start, this happens every night as part of my daily backup (not restore). Within the first minute of this process these five errors occur. Secondly I did do a search on these errors and I did find a couple sites that offered suggestions (Component Services permissions, etc), but none of them worked and wanted to do a ping here to see if there's any further thoughts.

> One service is called 'Volume Shadow Copy' the other is 'Microsoft Software Shadow Copy Provider'. One possible solution is to set these services to automatic then do a reboot.

Thank you for this suggestion. Volume Shadow Copy was set to automatic but the other was not... we'll see if that does anything.

Hi @mike_e

The other two things to try are to run sfc /scannow from an elevated command prompt to make sure there are no corrupt system files in Windows.
Also, try temporarily disabling the virus scanner and see if that makes any difference.

And have a peek-a-boo in the Event Viewer, it may reveal more about the errors you're getting.

Marcus Vinicus said:

The other two things to try are to run sfc /scannow from an elevated command prompt to make sure there are no corrupt system files in Windows.

Click to expand...

Whoa, I could have sworn that I ran this a week or so ago but it did indeed find some corrupt files and fixed them. We'll see if this does anything.

Bummer, still running into this issue. There's actually two issues that I am running into with this machine and I wonder if they are related.

Yesterday I noticed the BIOS was not the most current so I upgraded to make sure, but the problem still occurred overnight.

So this is a Hyper-V server (running on Windows 11) and I honestly wonder if I am running into a Windows 11 bug now with this. But in addition to this error (which happens when the system disks are backed up), I also have a much more serious error when BDR Server runs and backs up my Hyper-V instances.

When this happens the NVME disk that I use to host my images (different from the one AOEMI uses) simply goes offline and a bunch of disk warnings + errors flood my Event Viewer.

Most notably, when I go into BIOS the disc is not seen there. I have to turn off my machine and restart to see my disc again.