DISM /restorehealth fails at 83.8%, Windows Update shows same error, 0x80246008

gessyoo · Jul 4, 2018

I've tried everything to get Windows update working again on Windows 10 x64 Pro Build 1803. In-place upgrade doesn't complete. I used Macrium Reflect to clone C: drive to a larger drive. Windows runs and I really don't want to clean install everything. I disabled all non-Microsoft start-up services, virus scanner is Windows Defender. Secure boot and Device Guard are running. The SFCFix log points to the Windows Hyper-V Supervisor program data directory (I think), but I don't have any VMs running. Windows won't let me disable Hyper-V probably because Device Guard is using it. I've run the Windows Update troubleshooting tool, but no joy. Any assistance appreciated.
____________________
FileScan::
WARNING: There may be further unlisted copies of some of these files on the system.

[0: 1] C:\ProgramData\Microsoft\HVSI\323031382f30362f31332f30343a30323a3534\Base\Files\Windows\System32\config\DEFAULT
File is untraceable.
Found: /jPG4b8ve5wR3YQXGsA7sfOKn29FYs+cfgYTv0yHknU=
Version number not available.
Trace not available.

[1: 1] C:\ProgramData\Microsoft\HVSI\323031382f30362f31332f30343a30323a3534\Base\Files\Windows\System32\config\RegBack\DEFAULT
File is untraceable.
Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
Version number not available.
Trace not available.

[2: 1] C:\ProgramData\Microsoft\HVSI\323031382f30372f30342f30353a35373a3234\Base\Files\Windows\System32\config\DEFAULT
File is untraceable.
Found: /jPG4b8ve5wR3YQXGsA7sfOKn29FYs+cfgYTv0yHknU=
Version number not available.
Trace not available.

[3: 1] C:\FRST\Hives\DEFAULT
File is untraceable.
Found: qxC0fjeIKj47QRuPpTSOV6DCi9+s5wXTXQzMNT9fNCc=
Version number not available.
Trace not available.

[4: 1] C:\ProgramData\Microsoft\HVSI\323031382f30372f30342f30353a35373a3234\Base\Files\Windows\System32\config\RegBack\DEFAULT
File is untraceable.
Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.

Sysnative Windows Update · Jul 4, 2018

Hello and welcome to Sysnative! I'll review the logs and get back to you.

Sysnative Windows Update · Jul 4, 2018

I have had a look at your logs and I don't have good news I'm afraid. You have 18,000 + corrupt files which cannot be surgically fixed in a reasonable amount of time.

Have you checked your HDD for bad sectors? I have noticed that you cloned to a larger HDD, but you may have cloned an already damaged system, which is no good.

I can try and get you going with a Repair Install if you wish, but there may be a possibility that we will have to go the clean install route. Please answer my question and let me know what your decision is.

gessyoo · Jul 5, 2018

I ran a disk check for errors for new C drive: and there were no errors. Maybe there were errors on the original drive? I tried an in place upgrade, but it failed. I've got working 2 other Windows 10 pro installs on other drives in the computer that were clones but they're from a previous Windows 10 pro build (1709?). Is there any way to copy or import another possibly good component store or the registry hive into the C: drive registry, since it's running on the same computer and Windows version? If you have suggestions on a repair install, please let me know, thanks for your time and help.

Sysnative Windows Update · Jul 5, 2018

Please do restore to 1709 and run the scans. If all goes well, we'll get you up to 1803 from that one provided that one is not corrupt too.

gessyoo · Jul 5, 2018

softwaremaniac said:
Please do restore to 1709 and run the scans. If all goes well, we'll get you up to 1803 from that one provided that one is not corrupt too.

I've got a working install of Win 10 1709 on a different drive in the same computer. No boot disk errors, SFC reports no integrity violations, DISM shows no component store issues. I could clone the good drive over to the larger drive, but it's not activated. I upgraded 8.1 to 10 long ago during the free upgrade offer, and I'm not sure how to locate the original product key. Can the working install be used to fix the component corruption? Maybe DISM /Online /Cleanup-Image /RestoreHealth /Source:[Working install} D:\Windows? Can I import the component store or registry hive from the known good install? Thanks again.

Sysnative Windows Update · Jul 5, 2018

No, that cannot be done due to the complexity of the Windows update and the keys that are being deployed during each and every Windows Update install.

Search

Search

DISM /restorehealth fails at 83.8%, Windows Update shows same error, 0x80246008

gessyoo

New member

Attachments

Sysnative Windows Update

Inactive

Sysnative Windows Update

Inactive

gessyoo

New member

Sysnative Windows Update

Inactive

gessyoo

New member

Sysnative Windows Update

Inactive