Windows 11 23H2 KB5046633 Causes Windows Update to Fail

[terrym]

Windows 11 23H2 KB5046633 Causes Windows Update to Fail

Abbreviations

WUP = Windows Update

Resources

Pro Guide to Reset Windows Update Components Windows 10/11

How to reset Windows Update components in Windows 11/10 to fix the update issues? Read this post and you can find some ways to do this task.

minitool.com

########

First, I realize this is late as the Dec 2024 updates dropped today. However I hope it will help someone who is as bewildered as I was. It's pretty serious if WUP does not work.

########

I ran into something I have never seen before after installing the Nov 2024 Update KB5046633. I installed it successfully on a VBox VM using the MSU as always. After the final reboot everything looked good and I proceeded to install the rest up the updates using WUP.

First I got a list of updates using a C# utility I wrote

Updates Ready To Install
------------------------
1> Windows Malicious Software Removal Tool x64 - v5.130 (KB890830)
2> 2024-11 Cumulative Update Preview for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5048163)

Next I made sure the required Services were running

BITS (Background Intelligent Transfer Service
CryptSvc (Cryptographic Services
RPC (Remote Procedure Call (RPC)
UsoSvc (Update Orch Service
wuauserv (Windows Update

Then, after creating a System Restore Pt, I was ready to start WUP

Settings > Windows update
Get the latest updates as soon as available =OFF=

Windows Malicious Software Removal Tool x64 - v5.130 (KB890830)
Download error - 0x80004002

2024-11 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5045935)
Download error - 0x80004002

At this point I tried everything I could think of including the Windows Update Troubleshooter and rebooting.

The errors persisted. Next I found a MiniTool article with a VERY complete list of what to do if WUP
is broken. It included references to a service I have never had reason to deal with

appidsvc (Application ID

As soon as I started this svc everything worked. All I can surmise is that M$, in its finite wisdom, changed something and didn't tell us.

 

[ChatGPT]

It seems you've encountered quite the frustrating situation with the Windows Update Post-2024 KB5046633. Your detailed breakdown highlights several issues that many users are experiencing with the update process, especially regarding the Windows Update component and the appidsvc service. Let’s summarize and expand on what could be happening here:

1. Error Code 0x80004002: This typically indicates a "No such interface supported" issue, which can arise from various underlying problems, often related to corruption in update files or conflicts with services. Your experience seems to suggest that initiating the appidsvc (Application ID service) resolved some issues; this service is essential for Windows Store app updates and might have been inadvertently disabled or misconfigured before your update.
2. Service Checks: As you've noted, confirming that required services like BITS, RPC, and UsoSvc are running is critical before attempting to use Windows Update (WUP). It’s always best practice to check these services to ensure no corruption or disabling has occurred.
3. Using Troubleshooters: The effectiveness of the Windows Update Troubleshooter varies across systems. While it offers potential fixes for common issues, your experience reinforces that manual intervention (like starting specific services or clearing caches of Windows Update) is often needed when the troubleshooter fails.
4. Manual Processes: Your illustration of using additional resources (like MiniTool articles) to find solutions demonstrates an essential problem-solving approach for Windows users. Often, these solutions require a comprehensive understanding of Windows services, as you've engaged with.
5. Community and Resources: Engaging with resources such as forums and tech articles is invaluable, especially after updates. It helps to keep abreast of ongoing issues that many users face and potential fixes being shared among the community.

Additional Recommendations​

Besides what you've already implemented, here are a few more steps to consider:

• Perform a System File Check: Using the sfc /scannow command in an elevated Command Prompt may help in finding and repairing corrupted system files that can affect the update process.
• Resetting Windows Update Components: You mentioned doing much of this already, but for thoroughness, using the commands to stop services and deleting the folders in SoftwareDistribution and catroot2 can often yield positive results.
  

  bash net stop wuauserv net stop cryptSvc net stop bits net stop msiserver del /f /s /q %windir%\SoftwareDistribution\* del /f /s /q %windir%\System32\catroot2\* net start wuauserv net start cryptSvc net start bits net start msiserver

• Manual Downloading of Updates: If the WUP continually fails, manually downloading the updates from the Microsoft Update Catalog can serve as a workaround.
• Monitoring Hardware Compatibility: Ensure that your hardware (drivers, etc.) is compatible with the new updates, particularly with Intel graphics or audio driver updates leading to BSODs, as noted by many users recently.

Your persistence reflects a commendable effort in troubleshooting your Windows Update issues, and hopefully, the above suggestions can further aid in ensuring a smoother operation of your system. If you run into any specific error messages or peculiar behaviors in your next attempts, feel free to provide those for tailored guidance!
If you're looking for more detail or other user experiences with similar update issues, references can be found in discussions around KB5046633 and its consequences on the Windows 11 23H2, which are well documented on forums.

 

[terrym]

I should have mentioned I did

$ sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

$ DISM /Online /Cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.4460

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

HOWEVER the updates failed until I started appidsvc !!

 

[ChatGPT]

Your additional information clarifies that you've already taken significant steps to troubleshoot the Windows Update failure, including running both the sfc /scannow and DISM /Online /Cleanup-image /RestoreHealth commands. Both of these utilities are excellent choices for repairing system files and fixing image issues, and it's great to hear they reported successful repairs.
It sounds like the core issue persisted until you enabled the appidsvc (Application Id service). This perplexing situation underscores a couple of things:

1. Service Dependencies: It’s a common theme in Windows that sometimes services interact in unforeseen ways, and one service being disabled can affect the operation of others. As discovered, appidsvc is critical for Windows Store app updates and potentially for other system update processes, even if it seems tangential.
2. Corruption vs. Configuration: While the sfc and DISM commands addressed core file integrity issues, they don't always catch everything related to service configurations or dependencies. Your experience points to the possibility that the KB5046633 update may have inadvertently altered the status or configurations of certain services, leaving appidsvc in a disabled state when it was needed.
3. Investigating CBS Logs: If you're inclined to dig deeper, you can analyze the CBS.log file located at C:\Windows\Logs\CBS\CBS.log for specifics on the corrupt files it fixed. This might provide insights into whether the issues relate to crucial files that also affect the update process.

Final Thoughts and Tips​

Given your troubleshooting journey:

• Document Your Process: Keep a record of the steps you've followed, as it can serve as a useful guide not just for you but also for others experiencing similar difficulties. This could be valuable for community engagement on forums.
• Monitor Future Updates: Pay close attention to future updates and community discussions to see if others experience similar issues with the recents updates following KB5046633.
• Consider Feedback to Microsoft: If this pattern continues or seems widespread, providing feedback to Microsoft regarding the impact of their updates on configuration changes might help improve future updates.

It's impressive that you not only resolved the issue but also investigated thoroughly enough to find that the appidsvc was the key to your solution. Your experience highlights the sometimes hidden complexities in Windows Update processes. If you have any further queries or need more assistance, feel free to ask!