Updated from Windows 10 to Widows 11 build 22000.348.
Get this error now, but backup still fine:
Failed - 0x80042306 - IDispatch error #8454 - Retrying without VSS Writers

Here is an article from the V8 Knowledge Base which may be helpful.  VSS Errors

I am running Windows 11 Pro, build 22000.675. The computer came with Windows 11, it has not been upgraded from Windows 10.
I am runni
I am seeing this same error running an incremental image backup (i.e. this has worked before but doesn't now):

Starting Image - Saturday, May 21, 2022 10:29 AM

Initializing
Write Method: Using Direct Disk I/O
Destination Drive: Seagate Expansion Drive (D - Free Space 979.76 GB
Image Guardian: Protected
Free space threshold: Delete oldest backup sets when free space is less than 50.00 GB

Creating Volume Snapshot - Please Wait
Failed: Failed - 0x80042306 - IDispatch error #8454 - Retrying without VSS Writers
ERROR: COM call L"m_pVssObject->Query(GUID_NULL, VSS_OBJECT_NONE, VSS_OBJECT_SNAPSHOT, &pIEnumSnapshots )" failed.
- Returned HRESULT = 0x80042306
- Error text: VSS_E_PROVIDER_VETO
ERROR: COM call L"m_pVssObject->Query(GUID_NULL, VSS_OBJECT_NONE, VSS_OBJECT_SNAPSHOT, &pIEnumSnapshots )" failed.
- Returned HRESULT = 0x80042306
- Error text: VSS_E_PROVIDER_VETO

Gathering Windows Events - Please Wait

--------------------------------------------------------------------------------
Backup aborted! - Failed To Create Volume Snapshot. Failed - 0x80042306 - IDispatch error #8454

I have tried the "Other Tasks->Fix VSS Problems", rebooting, vssfix64.exe, and resizing shadow storage. I have looked through the event viewer logs but haven't found anything other than informational messages that reference VSS, for example:

The size of the $LogFile on device \Device\HarddiskVolumeShadowCopy14 is 0x4000000 bytes with 0x1 fragments

I have noticed that the copy number (14 here) keeps increasing.

I have tried using vssadmin to get more information, but it's not very helpful:

C:\windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Error: The shadow copy provider had an error. Please see the system and
application event logs for more information.

I can't find any logs in the event viewer that relate to this. "vssadmin list writers" does work, but all of the writers report "State: [1] Stable" and "Last error: No error".

I gave up on doing an image on my Windows 11 computer and moved on to imaging a Windows 10 computer. Again I'm doing an incremental image. This backup process has worked repeatedly in the past on this same computer. But today I am seeing exactly the same error (same failure code, iDispatch error, same COM call) that I saw on the previously mentioned Windows 11 computer.

This time running Windows 10 Home, build 19044.1706, Macrium Reflect 8.0, build 6758.

It looks like the latest version of Boxcryptor was the source of the problem. After exiting from Boxcryptor, Reflect was able to complete image backups on both computers.

Just wanted to confirm I had the same experience with the latest version of Boxcryptor (v.2.51.2468) -- same error, same fix. Running the VSS repair options from Macrium makes no difference, nor do any of the recommendations in the KB article. The Boxcryptor changelog indicates they upgraded the version of CBFS Connect, so there you go.

+x

 

lkjlkjasdf2232 - 22 May 2022 12:32 AM

Just wanted to confirm I had the same experience with the latest version of Boxcryptor (v.2.51.2468) -- same error, same fix. Running the VSS repair options from Macrium makes no difference, nor do any of the recommendations in the KB article. The Boxcryptor changelog indicates they upgraded the version of CBFS Connect, so there you go.

Hi,

i have the same problem since last Boxcryptor Update :
Windows 11 22621.1
Macrium Reflect 8.0, build 6758
Boxcryptor 2.51.2468

Return to previous version of Boxcryptor 2.50.2196 fix the issue.
Which side will an update come from (Boxcryptor or Macrium) ?

Best regards.

@Christophe Dettmar  Thanks for the post.

VSS is a core Windows service provided by Microsoft. Macrium Reflect simply uses this service, it doesn't update or modify it. If VSS is broken then it's highly likely that the other Windows components that use it, such as System Restore Points, will also fail. As the cause of failure is clearly Boxcryptor, it's only this product can provide the solution.

Kind regards
Bala

Kind Regards

Balaji

Macrium Development

See our reviews on

+x

 

Balaji - 23 May 2022 8:11 AM

Which side will an update come from (Boxcryptor or Macrium) ?

@Christophe Dettmar  Thanks for the post.

VSS is a core Windows service provided by Microsoft. Macrium Reflect simply uses this service, it doesn't update or modify it. If VSS is broken then it's highly likely that the other Windows components that use it, such as System Restore Points, will also fail. As the cause of failure is clearly Boxcryptor, it's only this product can provide the solution.

Kind regards
Bala

Hi Bala,

thanks for answer. I have created a ticket at Boxcryptor support.

Kind regards

+x

 

Christophe Dettmar - 23 May 2022 10:18 PM

+x

 

Balaji - 23 May 2022 8:11 AM

Which side will an update come from (Boxcryptor or Macrium) ?

@Christophe Dettmar  Thanks for the post.

VSS is a core Windows service provided by Microsoft. Macrium Reflect simply uses this service, it doesn't update or modify it. If VSS is broken then it's highly likely that the other Windows components that use it, such as System Restore Points, will also fail. As the cause of failure is clearly Boxcryptor, it's only this product can provide the solution.

Kind regards
Bala

Hi Bala,

thanks for answer. I have created a ticket at Boxcryptor support.

Kind regards

Hi,
The Boxcryptor support  give me this solution :
"Please enable "Mount in Windows Mount Manager" and "Mount for all users" in the Boxcryptor setting/Advanced, then it should be working."
Kind Regards