Hi,
No problem, I will see the result of the fix when you have run it! And thanks for your donation to Sysnative.
No problem, I will see the result of the fix when you have run it! And thanks for your donation to Sysnative.
[SOLVED] Windows Server 2022 Standard - 0x80073701
- Thread starter Zeno_
- Start date
Hi,
Please run the following DISM command to see if it fails with Error 2. If it fails attach a new copy of the CBS log.
Please run the following DISM command to see if it fails with Error 2. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealthHere's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
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 SFCFixScript.txt and save it to your desktop.
- Drag the SFCFixScript.txt 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.
Code:
DISM /online /cleanup-image /RestoreHealthPlease run the following command in an elevated prompt and copy paste the result in your next post.
Code:
DISM /online /cleanup-image /AnalyzeComponentStoreHere is the output:
Code:
PS C:\Windows\system32> DISM /online /cleanup-image /AnalyzeComponentStore
Deployment Image Servicing and Management tool
Version: 10.0.20348.681
Image Version: 10.0.20348.1850
[===========================99.3%========================= ]
Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 9.45 GB
Actual Size of Component Store : 8.74 GB
Shared with Windows : 5.69 GB
Backups and Disabled Features : 3.04 GB
Cache and Temporary Data : 0 bytes
Date of Last Cleanup : 2025-02-02 19:12:52
Number of Reclaimable Packages : 2
Component Store Cleanup Recommended : Yes
The operation completed successfully.Please run the following command as well and post the result.
Code:
DISM /online /cleanup-image /StartComponentCleanupHere is the output:
Code:
PS C:\Windows\system32> DISM /online /cleanup-image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.20348.681
Image Version: 10.0.20348.1850
[===== 10.0% ]
[==========================100.0%==========================]
The operation completed successfully.Great, please reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
Unfortunately still failing with error 0x80070002. Latest CBS attached. It's starting to seem like this issue never ends, lol. Feel free to let me know if you're tired of troubleshooting this one. I was trying to avoid reinstalling Windows, but I will if necessary.
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.
Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
Start the
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.
Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
Apologies for the delay in getting back to this. I ended up resolving the issue by reinstalling Windows Server 2022. After I ran the latest fix, Windows would boot to the point where the login screen should load, but instead it got stuck on a black screen where the cursor would flash in and out of view with the loading circle attached. I did a bit of troubleshooting at this point but could not get back into Windows properly even in safe mode. Instead, I decided to wipe and rebuild from scratch.
I do want to thank you for all of your help though, Maxstar! I greatly appreciate the effort and quick responses you gave. Many thanks to you and the Sysnative team for being awesome!
I do want to thank you for all of your help though, Maxstar! I greatly appreciate the effort and quick responses you gave. Many thanks to you and the Sysnative team for being awesome!
Hi,
That's odd, the last fix removed only some warnings as showed in the CBS logs.
That's odd, the last fix removed only some warnings as showed in the CBS logs.
Yeah, I'm not entirely sure what happened. More than likely it was an error on my part somewhere along the way. I definitely don't doubt your abilities to solve these issues given your reputation here and the sheer number of problems you've been able to resolve. Either way, thanks again for all the help. Going through this process and doing some further research into the fixes you suggested have given me a way better understanding of Windows Updates.
Has Sysnative Forums helped you? Please consider donating to help us support the site!