[SOLVED] Win10 - refuses to update to 22H2

[dsalch]

I have been trying to update to 22H2 on this win10 machine for months with no success. Everything runs fine, but update always fails at t late stage requiring a reversal, the whole process taking about 2 hours per attempt. I have tried SFC / DISM / CHKDSK / Inplace Update / online update / downloading and running update in safe mode / reinstall while keeping files. Nothing works. Finally I ran across SFCFix and ran it. The first time it went through a lot of steps and towards the end crashed with an exception. Log files are mostly empty. Now if I run it again it crashes immediately upon running with the same error.

The history: This was originally a win8 machine upgraded in place to win10. It is very old. There has been a viral infection maybe 2 - 3 years ago that was removed. There were also some HP printer drivers that are no longer needed but dont seem to be able to be removed. This is my main work related machine and rebuilding from a fresh install would be a horrendous task!

I have the requested log files but dont see how to attach them yet?

 

[dsalch]

I'll try attaching files now

 

[Maxstar]

Hi and welcome to Sysnative,

Do you still need assistance in this thread?

 

[dsalch]

Yes! I have tried everything to no avail. The logs may be different now though.

 

[Maxstar]

Hi,

Please run the following DISM command and attach a new copy of the CBS log(s).

DISM /online /cleanup-image /RestoreHealth

 

[dsalch]

here is the latest file after running DSIM again

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.1165

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

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

C:\WINDOWS\system32>

 

[Maxstar]

Hi,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[dsalch]

I did step 1, attached is the file

 

[Maxstar]

The fix completed succesfully so hopefully DISM will succeed as well.

 

[dsalch]

WOOHOO! Is this for real????

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.1165

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

 

[Maxstar]

Great, please attempt to update and let me know the result. If it fails attach a new copy of the CBS log(s).

 

[dsalch]

C:\WINDOWS\system32>
C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

 

[dsalch]

SFCfix still crashes with a "unhandled exception" . Is that a problem?

 

[Maxstar]

No, that's not a problem, you can ignore that message.

 

[dsalch]

Shall i try running windows update now?

 

[Maxstar]

Yes, please attempt to update. If it fails attach the latest CBS log(s) to your next post.

 

[dsalch]

Any chance you could explain (in laymans terms) what was wrong? I have battled this for months! you guys are genius!

 

[Maxstar]

Some files of the servicing stack were missing, which we have replaced with SFCFix.

 

[dsalch]

Well, DISM and SFC both passed with no errors. HOwever, the update failed.

IT ran through the installation part in windows, and took much longer than previously. Then it reset and had the black screen for "applying changes". That got to about 24% (and took about 2 hours) when suddenly it switched to "undoing changes" where it still is now.

 

[dsalch]

it is back to running, here is the CBS.log