Win10.1809 repair / in-place upgrade failure

Topic

New Reply

I recently had a disk failure, and then recovered my c:\ drive (Win10.1809 installation) from an Easeus Backup (v11.5).  I was able to get Win10 to load and run successfully, but have been unable to successfully run sfc /scannow or DISM /Online /Cleanup-Image /RestoreHealth.

Console results (Admin PowerShell):

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 13% complete.

Windows Resource Protection could not perform the requested operation.

and

PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool

Version: 10.0.17763.1

Image Version: 10.0.17763.316

[===                        6.4%                           ]

Error: 4448

The WOF driver encountered a corruption in the compressed file’s Resource Table.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

PS C:\WINDOWS\system32>

The relevant (edited to contain only the most recent entries) dism.log and CBS.log files are available but not attached due to my inability to upload the relevant (.txt, .log, or .zip) files.

I then tried Media Creator inplace update using the Win10.1809 version.  That also failed, with this (rather cryptic) error message:  “0x8007001f-0x20006 The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation”.

Advice, please, about how to get back to a clean installation.  TIA.

 

Reply | Quote

Replies

Don,
You can link to files not on this site as long as the storage location is https:// (for example Dropbox)

1 user thanked author for this post.

dvhirst865

Reply | Quote

Hmm, don’t see an edit function for my previous post, so will use this reply to follow PK’s suggestion; thanks, PK.

The relevant log files are now in my dropbox.com public folder (edited.dism.log, edited.cbs.log) and shared.

 

Reply | Quote

Plug in your MCT media, open File Explorer to see what drive letter it has been assigned.  Then open an elevated Command Prompt and run the following command line, replacing “X” with the drive letter assigned in File Explorer.

dism /online /cleanup-image /restorehealth /Source:X:\RepairSource\Windows /LimitAccess

“Source:X:\RepairSource\Windows /LimitAccess” wrapped; notice the only space is before /LimitAccess.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

NetDef

Reply | Quote

@bbearren – Thanks for the hint, I’d found that one and several others which I tried without success.  Further searching lead me to the sysnative.com forum.  I reviewed a couple of their interactions with folks who needed help and was very favorably impressed with what I observed.  I signed in and provided a synopsis of my issue per their very clear and concise procedure.  A couple of days later (they are busy folks!) I got an email saying that one of their specialists was available to assist me.  We worked through several sets of tests and eventually found that a failing SSD drive (c:) made further progress impossible.  I replaced the SSD, recovered a previously saved system backup, and was able to get back into operation.  The help that sysnative.com provided was excellent, and I would encourage anyone with complex Windows 10 install / update issues to contact them.

My takeaways from this experience are:

1. Ensuring reliable hardware operations needs to precede any efforts at software recovery.
2. There are some very useful forums available online; Woody’s being one of them and sysnative.com being another.

DVH

Reply | Quote