[SOLVED] Cannot Install Cumulative Updates - Windows 10 Home 22H2, OS Build 19045.5247

[Mighty Joe]

Hello,

For the last few months I've been unable to install cumulative updates, most recent one being KB5053606 where I am inevitably tossed the error 0x80070003. Security Intelligence Updates for Defender install for me with no problem and no problems with System Restore, either. After I attempt the install, it prompts me to restart my computer to complete the update. Computer reboots then, like clockwork: "Working on updates 7% complete" and...fail.

My specs are: Windows 10 Home 22H2 with OS Build 19045.5247. 64-bit Dell Inspiron 3847.

I'm tried the standard Windows troubleshooters to correct the issue and have also tried:
* Repairing permissions with Ultra Virus Killer
* UpdateFixer which had the same two suggestions depending on when I ran it: 1. clear and reset delivery files and reset key system folders 2. re- enable Windows Update registry settings
* batch file to reregister/reset WU components
* batch file to clear update history
* Setupdiag.exe which looked like a viable fix but couldn't figure out the switches/commands
* Reset Windows Update Tool (Gill)

Whether or not this is relevant, I'm not sure but I have 22 Hotfixes installed.
[01]: KB5050576
[02]: KB5050579
[03]: KB5011048
[04]: KB5015684
[05]: KB5048652
[06]: KB5050199
[07]: KB5014032
[08]: KB5032907
[09]: KB5037240
[10]: KB5037995
[11]: KB5039336
[12]: KB5040565
[13]: KB5041579
[14]: KB5041581
[15]: KB5043935
[16]: KB5043130
[17]: KB5046823
[18]: KB5050388
[19]: KB5050111
[20]: KB5052916
[21]: KB5005260
[22]: KB5034441

Here is an error I see frequently but not sure if this is the sole or a mitigating reason:
CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5425_none_7e0bb22e7c8f7e0e\wcp.dll' : got STATUS_OBJECT_PATH
CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5425_none_7e0bb22e7c8f7e0e\wcp.dll' : got STATUS_SUCCESS

Hopefully I haven't omitted any pertinent information to facilitate your assistance. I must mention that being realistic, the idea of an in-place repair is not one I will consider. I would just like the machine I have now to serve me consistently and provide the necessary updates for the next few months until the mandatory purchase of Windows 11.

Thank you so much and I look forward to hearing from you soon.

MJ

 

[Windows Update Bot]

Hi @Mighty Joe,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Mighty Joe]

Hello again,

As I've been bumped off the first page, I thought I'd check in -- and, well, bump my post, I suppose -- one last time to see if there is anything else I can provide, either further details or updated scan results, to make it easier to help me.

Unless you ask I give a nudge at a certain time (e.g. once a week), I won't hound you guys further as I've read how much demand you have vs. the number of volunteers. I appreciate all you're doing and hope to hear from one of you soon.

Thanks again

 

[Maxstar]

Hi,

Upload the setupapi.dev.log file

• Open Windows Explorer and browse to the C:\Windows\INF folder.
• Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
• Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
• Click on the Yes button here.

• Attach the file setupapi.dev.zip in your next reply.

 

[Mighty Joe]

Thanks for the assist, Maxstar. Log attached...

 

[Maxstar]

Hi,

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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs and the Setupapi.dev.log.

 

[Mighty Joe]

Thanks Maxstar. Just a heads up, I need to go offline for the remainder of the day so I'll jump on this next step later tonight.

 

[Mighty Joe]

Success. After running SFCFix, I was able to install the Cumulative Update KB5053606 which previously failed over and over.

I then ran another SFC / scannow and to my surprise corrupted files were found that Windows was unable to fix. I then ran DISM and it deemed the operation to be successful. I rebooted and ran SFC / scannow again. This time, corrupted files were found but Windows WAS able to repair them. Another reboot and another run of SFC / scannow. As I anticipated, this time it came back clean. Some weird stuff this time on the Component Scanner log.

I look forward to hearing your thoughts.

 

[Maxstar]

Hi,

This looks good, and the ComponentsScanner log is clean, the 'debug' log can be ignored and shows nothing strange too!

 

[Mighty Joe]

Thank you so much! If anything goes awry again, I'll circle back. But hopefully I'm good until Windows 11.

Thanks again. Donation forthcoming (wish it could be more).

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has ben resolved and thanks for your donation to Sysnative...