Windows 10: Cannot create recovery disk in Windows 10 (VSS writer fail 0x800423f4)

Since installing (through Windows Update) Windows 10 Home 64-bit on my Windows 7 Home Premium 64-bit PC I have been unable to create a recovery disk. Each try ends with the error (event log) pasted below.

I hope someone could help me with this one. I have asked Microsoft in avail, also tried various solutions from different forums. This question is also asked by many others, but there seems to be no solution.

I have fixed several problems, including the corrupt image in edge (MicrosoftEdgeSquare44x44.scale-125_contrast-white.png), then succesfully running dism and sfc. Also fixed the CAPI2 error using SC sdshow MSLLDP.

Now this is the only problem I have left, but I am getting desperate.


Code: Log Name: Application Source: VSS Date: 21.8.2015 22:37:46 Event ID: 8229 Task Category: None Level: Warning Keywords: Classic User: - Computer: XXXXXXXXX Description: A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: PrepareForBackup event Context: Execution Context: Writer Writer Class Id: {9cd63585-aa61-4c1a-82db-8c04d8c273ce} Writer Name: WimCap Vss Writer Writer Instance ID: {4a116767-ee87-4e80-a5e0-cc6d05322eef} Command Line: "C:\WINDOWS\system32\RecoveryDrive.exe" Process ID: 5256 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="VSS" /> <EventID Qualifiers="0">8229</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-08-21T19:37:46.000000000Z" /> <EventRecordID>1921</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXXXXXXX</Computer> <Security /> </System> <EventData> <Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. </Data> <Data> Operation: PrepareForBackup event Context: Execution Context: Writer Writer Class Id: {9cd63585-aa61-4c1a-82db-8c04d8c273ce} Writer Name: WimCap Vss Writer Writer Instance ID: {4a116767-ee87-4e80-a5e0-cc6d05322eef} Command Line: "C:\WINDOWS\system32\RecoveryDrive.exe" Process ID: 5256</Data> <Binary>22D20436F64653A20575254575254494330303030353334382D2043616C6C3A20575254575254494330303030323636312D205049443A202030303030353235362D205449443A202030303030343631322D20434D443A202022433A5C57494E444F57535C73797374656D33325C5265636F7665727944726976652E65786522202D20557365723A204E616D653A205465656D75335353442D50435C5465656D75335353442C205349443A532D312D352D32312D333037313438313731312D333733373132343030392D323637363639393538332D31303030</Binary> </EventData> </Event>[/quote]

:)

 

0x800423f4 inhibits recovery drive creation

Thank you for the reply. Besides, error 513 is also generated trying to create a recovery drive.

I'm running Win 10 Home update from Win 7 Home.

This is the english translation:

From a VSS Writer was an event with the error "0x800423f4, a non-transitory error is detected for the generator. When the backup process is repeated, the error occurs most likely on again. "Rejected. Changes made to the writer components during the processing
of the event, are not available for the requester. Related events the host application of the VSS Writer, see the event log. operation: PrepareForBackup event context: Execution Context: Writer Generator Class ID: {9cd63585-aa61-4c1a-82db-8c04d8c273ce} Generator
Name: WimCap VSS Writer Generator Instance ID: {a1b52862-a113-477e-ac51-3c257141d127} Command line: "C: \ WINDOWS \ system32 \ recoverydrive.exe" Process ID: 12092

Thanks a lot

 

Windows 10, can't create recovery drive.

I upgraded to Windows 10 from Windows 8.1 last night. Tried to create a recovery drive just in case things go wrong (with a new version of Windows, I don't think that's unreasonable.) It fails, and it just says:

"A problem occurred while creating the recovery drive."

The event log shows the error I pasted after this message.

Any ideas?

[EVENT LOG]

Log Name: Application

Source: VSS

Date: 7/30/2015 2:55:29 PM

Event ID: 8229

Task Category: None

Level: Warning

Keywords: Classic

User: N/A

Computer: XXXXXXXXX

Description:

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,

the error is likely to reoccur.

. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:

PrepareForBackup event

Context:

Execution Context: Writer

Writer Class Id: {9cd63585-aa61-4c1a-82db-8c04d8c273ce}

Writer Name: WimCap Vss Writer

Writer Instance ID: {28a89bc4-0298-4df9-89a0-73044c9a5e5e}

Command Line: "C:\WINDOWS\system32\RecoveryDrive.exe"

Process ID: 5968

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="VSS" />

<EventID Qualifiers="0">8229</EventID>

<Level>3</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2015-07-30T21:55:29.000000000Z" />

<EventRecordID>735</EventRecordID>

<Channel>Application</Channel>

<Computer>XXXXXXXXXXX</Computer>

<Security />

</System>

<EventData>

<Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,

the error is likely to reoccur.

</Data>

<Data>

Operation:

PrepareForBackup event

Context:

Execution Context: Writer

Writer Class Id: {9cd63585-aa61-4c1a-82db-8c04d8c273ce}

Writer Name: WimCap Vss Writer

Writer Instance ID: {28a89bc4-0298-4df9-89a0-73044c9a5e5e}

Command Line: "C:\WINDOWS\system32\RecoveryDrive.exe"

Process ID: 5968</Data>

<Binary>2D20436F64653A20575254575254494330303030353334382D2043616C6C3A20575254575254494330303030323636312D205049443A202030303030353936382D205449443A202030303030383430382D20434D443A202022433A5C57494E444F57535C73797374656D33325C5265636F7665727944726976652E65786522202D20557365723A204E616D653A204348524953442D50435C4368726973274861636B6D6173746572446F63752C205349443A532D312D352D32312D313931313930353235362D333330373132353932332D313436383937303635342D31303031</Binary>

</EventData>

</Event>

 

It's an old reference but VSS has been around for a while, and so have its failures: http://thetazblog.taznetworks.com/20...x800423f4.html

 

Thanks for the info, Mark.

I googled around these .dll registration and found that this is a solution to WIndows Server 2003, one article even said that trying this might have catastrophic effects on Windows Server 2008 or newer. These of course server editions, but I feel uncomfortable trying this.

I guess this could do with uninstalling Acronis True Image WD Edition, which I had in Windows 7, uninstalled prior to Windows 10 upgrade, though. After installation (and after seeing this problem) I also uninstalled Nero 10 and LaCie Genie Backup, but this had no effect.

I was thinking maybe I could try and reinstall Acronis, and see if it clears this problem?

 

Hi,

I've upgraded 4 PC's at home and I'm having this same problem. Recoverydrive.exe has failed on 2 pc's I have just upgraded to Win10. There's no common factors I can see, and no visible reason why 2 PC's are ok and 2 not. The upgrade installation from Win7 to Win10 went well in all cases, no issues reported. I've run all the update checks and rebooted several times. All appears to be running well but reoverydrive.exe still fails with this error (and no more information) every time I attempt it. Looks like this isn't an isolated problem.

Any ideas from anmyone would be appreciated.
Thanks,
Rob

 

I ran Vssadmin list writers from elevated command prompt. After booting up and prior to trying to create recovery drive all writers are fine.

Code: C:\WINDOWS\system32>Vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {10cbcf70-c7f5-46b1-8ef0-db38444b0eab} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {44e04ca8-8a45-460c-94b6-d1da401050c3} State: [1] Stable Last error: No error Writer name: 'MSSearch Service Writer' Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2} Writer Instance Id: {a1e30871-dd4b-4ca0-ad90-a7df23c631e9} State: [1] Stable Last error: No error Writer name: 'MSMQ Writer (MSMQ)' Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a} Writer Instance Id: {297322a0-d3b8-4d07-bb6f-fc88eaa4bb49} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {3837eda9-53c7-4c89-9f11-19bded1431e7} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {733caaee-4a2e-496d-b1df-92f685956c6e} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {df7a6063-f37a-491a-b5cd-a3af5ae5f0a6} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {e9a38f81-12e0-4014-bbe7-746f85dc44a8} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {8ba00892-1ff3-4ff5-898b-3fd886633d9f} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {49676314-2a63-428f-b16a-980f5a4ed441} State: [1] Stable Last error: No error[/quote] After an unsuccesful recovery drive creation attempt it looks as follows:

Code: C:\WINDOWS\system32>vssadmin list writersvssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {8507f31a-fcd8-45ff-bf2e-7b80763d93f8} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {10cbcf70-c7f5-46b1-8ef0-db38444b0eab} State: [7] Failed Last error: Timed out Writer name: 'MSMQ Writer (MSMQ)' Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a} Writer Instance Id: {297322a0-d3b8-4d07-bb6f-fc88eaa4bb49} State: [7] Failed Last error: Timed out Writer name: 'MSSearch Service Writer' Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2} Writer Instance Id: {a1e30871-dd4b-4ca0-ad90-a7df23c631e9} State: [7] Failed Last error: Timed out Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {c58e6d31-fb80-47ee-b0c2-ff9a10ba7741} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {df7a6063-f37a-491a-b5cd-a3af5ae5f0a6} State: [7] Failed Last error: Timed out Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {0e8cb35f-e8aa-4a8f-856c-f9d3bf06fee1} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {8ba00892-1ff3-4ff5-898b-3fd886633d9f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {c9f76ed8-03d7-467b-8f28-a5d9d10b7321} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {49676314-2a63-428f-b16a-980f5a4ed441} State: [7] Failed Last error: Timed out[/quote] So all the following writers fail:

Writer name: 'System Writer'
Writer name: 'MSMQ Writer (MSMQ)'
Writer name: 'MSSearch Service Writer'
Writer name: 'IIS Config Writer'
Writer name: 'WMI Writer'
State: [7] Failed
Last error: Timed out

 

In the for what it's worth category, I have a brand new system preinstalled with Win 10, so the problem is not unique to upgrades. I have my system files on a SSD, which may impact the issue. I have turned off my antivirus software, turned off the wireless printer, and even remove the usb that signals my wireless mouse and keyboard. So, with a brand new system, and nothing extraneous running that I know about, I'm still unable to create the recovery drive.

 

Same, here. I can even recreate the error with just trying to perform an online scandisk with the standard windows right click menu.

Windows 10 has some annoying bugs...

Anyone have any luck?