[SOLVED] Windows update issue and DISM errors

rclarke · Jan 26, 2023

Hi,
This was the result

Code:

C:\Windows\system32>reg query HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160} /s

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}
    (Default)    REG_SZ    RuntimeBroker
    AppID    REG_SZ    {9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}\LocalServer32
    (Default)    REG_SZ    C:\Windows\System32\RuntimeBroker.exe

Maxstar · Jan 26, 2023

Hi,

This looks good, before Windows Update is failing each time the Event log showed this error as well (Event ID 7043):

Code:

The Update Orchestrator Service for Windows Update service did not shut down properly after receiving a preshutdown control.

Let's try to change the first failure state and see what happens.

Open services.msc and scroll down to the Update Orchestrator Service.
Right click the service and select Stop if it is started.
Right click the service and select properties and open the recovery tab.
Set the option "First failure" to restart the service and click the Apply button.

Afterwards, attempt to update and post the result. If it fails attach a new copy of the CBS and Event logs.

rclarke · Jan 26, 2023

Hi,

Unfortunately it failed again.
Here is the event logs nd the CBS folder.
This server just does not seem to want to be fixed

Maxstar · Jan 26, 2023

Code:

2023-01-26 12:56:45, Error                 CSI    000002cd (F) HRESULT_FROM_WIN32(1142) #11761129# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_InstallDeployment(Flags = 0, a = f6c67b0f02e06d36cdb20ae334942986, version 11.0.14393.2007, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_1061_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.5022289-2175_neutral', rah = '3', manpath = (null), catpath = '\\?\C:\Windows\Servicing\Packages\Package_1061_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.cat', disp = 0)[gle=0x80070476]
2023-01-26 12:56:45, Info                  CBS    Failed to begin deployment installation for Update: 5022289-2175_neutral [HRESULT = 0x80070476 - ERROR_TOO_MANY_LINKS]
2023-01-26 12:56:45, Info                  CBS    Failed to execute item[0] in Package: Package_1061_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7, Update: 5022289-2175_neutral [HRESULT = 0x80070476 - ERROR_TOO_MANY_LINKS]

At least we've got a new error this time, please run the following command and post the result.

Click the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator.
Copy and paste the following command line and press Enter.

Code:

fsutil hardlink list %systemroot%\Servicing\Packages\Package_1061_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.cat > "%userprofile%\desktop\fslist.txt"

When finished, a logfile called fslist.txt is saved on your desktop.
Post the logfile as attachment in your next reply.

rclarke · Jan 26, 2023

Hi, Here is the new fslist.txt

rclarke · Jan 26, 2023

Hi, @Maxstar I really appreciate all of your efforts so far.
I am now on annual leave until Wednesday of next week. So I will resume the testing then.
Look forward to any replies or suggestions in the meantime.
Thanks.

Maxstar · Jan 28, 2023

Hi,

Start the

Farbar Recovery Scan Tool again.

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

Download the attachment fixlist.txt and save it to your desktop.
Right-click on FRST.exe and select "Run as administrator".
Press the Fix button.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

rclarke · Feb 2, 2023

Hello @Maxstar
I am now back at work and have run FRST tool again with the file you provided.
Here is the result of the fix.
The tool did not prompt for a restart so I have not restarted.

I look forward to resuming this work to fix this server.
Thanks.

Maxstar · Feb 2, 2023

Hi,

Pleas uninstall FRST, and after the reboot attempt to update again. If it fails attach a new copy of the CBS logs.

Follow the instructions below to remove

FRST and all the log files.

Rename the file FRST64.exe to uninstall.exe and run it as Administrator.
This will remove all files and folders created by FRST and the tool itself.
To complete this the system must be restart.

rclarke · Feb 2, 2023

Hi,
Removed FRST and re-booted.
Unfortunately it has failed once again. Here is the CBS folder.

Maxstar · Feb 2, 2023

Rich (BB code):

2023-02-02 12:23:13, Error                 CSI    000001e0 (F) HRESULT_FROM_WIN32(1142) #7598692# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_InstallDeployment(Flags = 0, a = 9073c793495d24dc5a737d437d3f1c86, version 10.0.14393.4046, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_822_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.5022289-1599_neutral', rah = '2', manpath = (null), catpath = '\\?\C:\Windows\Servicing\Packages\Package_822_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.cat', disp = 0)[gle=0x80070476]
2023-02-02 12:23:13, Info                  CBS    Failed to begin deployment installation for Update: 5022289-1599_neutral [HRESULT = 0x80070476 - ERROR_TOO_MANY_LINKS]
2023-02-02 12:23:13, Info                  CBS    Failed to execute item[0] in Package: Package_822_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7, Update: 5022289-1599_neutral [HRESULT = 0x80070476 - ERROR_TOO_MANY_LINKS]

Open an elevated command prompt and run this command again. Attach fslist.txt to your next post.

Code:

fsutil hardlink list %systemroot%\Servicing\Packages\Package_822_for_KB5022289~31bf3856ad364e35~amd64~~10.0.1.7.cat > "%userprofile%\desktop\fslist.txt"

rclarke · Feb 2, 2023

Here is the requested file

Maxstar · Feb 2, 2023

Thanks, are you able to clone this server so we can safely test a more rigorous fix?

rclarke · Feb 2, 2023

Hi, Not easily. It is hosted for us by a 3rd party.
Most likely that I would have to get it signed off to have the work done and the charge for extra resources.
But if it gets that bad that it is not fixable, then we wouldn't have much choice, i guess.

Maxstar · Feb 2, 2023

Hi,

I would try to delete the following directory C:\Windows\WinSxS\Temp\ and all the subfolders and files. After attempting to update again it will recreated, so you could also make a complete image and then try the following fix. I've tested this on one of my VM's and solved the same issue I had reproduced.

So the fix is not that bad, but with production servers I'am very carefully.

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

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

Download the attachment fixlist.txt and save it to your desktop.
Right-click on FRST.exe and select "Run as administrator".
Press the Fix button.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

rclarke · Feb 2, 2023

Could you please confirm the order of things.
Do you mean to delete C:\Windows\WinSxS\Temp\ > then use the FRST tool.
Or to run the FRST tool first > then delete the C:\Windows\WinSxS\Temp\ as a last resort?

Maxstar · Feb 2, 2023

In the previous fixes with FRST (Fixlist.txt) we have removed the following folders showed in the result of fsutil.

C:\Windows\WinSxS\Temp\InFlight\6a78b5c86926d901e0780000f4087c3c

The last Fixlist in post#75 will remove the complete %temp% folder inside the WinSxS directory.

1. So run FRST again with the attached Fixlist in post#75 and post the result.
2. If successful, we can remove FRST again to delete all the (hardlinked) items from the FRST Quarantaine directory.
3. Then we could try to update again, to see if it still reporting the 0x80070476 - ERROR_TOO_MANY_LINKS error.

rclarke · Feb 2, 2023

Thanks for the clarification.
I have run the tool and here is the output file.

Maxstar · Feb 2, 2023

You're welcome. Please uninstall FRST again and reboot the server. Afterwards attempt to update. If it fails attach a new copy of the CBS log(s).

Follow the instructions below to remove

FRST and all the log files.

Rename the file FRST64.exe to uninstall.exe and run it as Administrator.
This will remove all files and folders created by FRST and the tool itself.
To complete this the system must be restart.

rclarke · Feb 3, 2023

Hi,
I renamed the tool uninstall.exe yesterday afternoon and ran as administrator. The server is still running the process this morning. Should it take that long?

The folder C:\Windows\Winsxs\Temp no longer exists
Should I reboot it anyway?

[SOLVED] Windows update issue and DISM errors

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member