Windows 10: VSS Failure: Failed to create Volume Snapshot. Result Code: 0x80042306

I have an HP Laptop that was native Windows 7 upgraded to Windows 10. Now in dealing with the User running out of HD space, I was going to use Macrium Reflect to clone the SATA HD to another larger SATA HD. In working with Macrium support and after attempting to use their "Fix VSS Errors" to re-register VSS/.dll, it did not resolve my issue and was advised to contact Microsoft since this is a VSS/Microsoft issue and not in their software. I have attached a few screen shots for reference. Any help would be great.Thank you kindly!

:)

 

Veeam backups failing since 1803 install with 0x80042306 VSS timeout error

On desktop machine here, post 1803 update, Veeam backups are repeatably failing. Associated event viewer information:

Veeam Agent 'Backup Job DIYNUC' finished with Failed.

Job details: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed.

Cannot create a shadow copy of the volumes containing writer's data.

VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].

Error: Failed to create snapshot: Backup job failed.

Cannot create a shadow copy of the volumes containing writer's data.

VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].

The shadow copy of volume \\?\Volume{0e1a4bd5-2758-4ab6-a00c-05bc7333610a} being created failed to install.

Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{0e1a4bd5-2758-4ab6-a00c-05bc7333610a} - 000000000000021C,0x0053c008,000001DDF8C0A6B0,0,000001DDF8C0B6E0,4096,[0]). hr = 0x80070079, The semaphore timeout period has expired.

This was working for months before 1803 installation. And works on my 1803 laptop.

Any suggestions?

 

Unable to take snapshot of a volume if the VSS requester and hardware provider installed on the same volume

Hi

I installed the VSS requester and VSS Hardware provider on a given volume(let say on Drive E) and my MSSQL database is configured on the same volume(let say on Drive E.

Now when i take a snapshot of the MSSQL database using the VSS requester and VSS hardware provider then snapshot creation fails with error 'Abort detected while committing the snapshot set 0x80042314' .

My observation is this is mostly happening because my provider and requester does not respond(since configured on the same volume) due to freeze of IO on the volume while creating snapshot by VSS framework.

The operation resumes after 10 seconds of timeout by VSS but by that time VSS snapshot already failed due to time out error.

I have few queries on it.

Is this kind of configuration supported i mean taking the snapshot of the same volume where the VSS requester and VSS hardware provider both are installed. If its supported am i missing anything in requester or hardware provider implementation.

Regards

Mi2

 

Failed to Create Volume Snapshot Macrium Error 0x8004230f VSS Error

Hi, you might try this:
Microsoft Volume Shadow Copy (VSS) Troubleshooting - Microsoft Volume Shadow Copy (VSS) Troubleshooting

or the free cautious repair tool
Tweaking.com - Windows Repair Free/Pro
- observing the steps and using only the relevant repairs

More:
How to Fix VSS Errors Step-by-Step

Otherwise I suggest- assuming your disk and file system are sound-
an in-place upgrade repair install which keeps all progs, data and most settings

You need an iso of the same base language and build- freely downloadable.