Windows Update Loop - Build 26200.8117 - FAILED [AppxPackage::Initialize:235] Error 0x80070032

Hello, I am facing a persistent Windows Update installation loop on Windows 11 Build 26200.8117 (KB5094126) and need some help before a travel deadline in 5 days. The update downloads to 100%, but during initialization it fails, loops endlessly, pins my CPU, and causes high thermal strain with loud fan noise when plugged into my AC charger.
CRITICAL CONSTRAINT: I am running a highly customized setup. I cannot run any automated repair scripts, in-place reinstalls, or tools that risk resetting or overwriting my legacy AMD graphics drivers, custom thin system fonts, or fine-tuned ASUS display brightness thresholds.
System Specifications:

• OS Edition: Windows 11 Home Single Language (Retail Channel, 25H2)
• OS Build: 26200.8117
• Hardware: ASUS Laptop M413A
• Processor: AMD Ryzen 7 4700U with Radeon Graphics

Troubleshooting Already Done:

1. Ran SFC /scannow and DISM RestoreHealth earlier this week (both report 100% clean component store, no corruption found).
2. Cleared out the C:\Windows\SoftwareDistribution cache and old .etl logs to get a clean data track.
3. Verified via Windows Security (Device Security) dashboard that Secure Boot is active and all certificate updates are perfectly applied. Note: The physical path C:\Windows\SecureBoot\Scripts does not exist on my drive.

Isolated Failure Trace (From clean logs right at the loop point):
2026/07/24 20:28:52.4477861 *FAILED* [80070032] Method failed [AppxPackage::Initialize:235]
Log Links (Split into 5 parts due to Pastebin text size limits, Part 1 holds the main crash lines around 20:28:52,):


Section 1: 2026/07/24 20:28:18.0597218 20460 6368 Misc Load undocked module: Uu - Pastebin.com

Rest are for reference:

Section 2: 2026/07/24 20:29:28.5193063 20460 10536 Agent Search Scope = {Machine - Pastebin.com

Section 3: 2026/07/24 20:30:37.3033286 20460 19152 Agent Total allowed fede - Pastebin.com

Section 4: 2026/07/24 20:30:55.2404793 20460 16452 Agent - Pastebin.com

Section 5: 2026/07/24 20:32:26.1325789 20460 6740 DownloadManager Handler (9) for update F - Pastebin.com
Does anyone know how to safely fix this specific AppxPackage initialization registry failure without touching or resetting my custom display configuration and active device drivers? Any insight would be greatly appreciated. Thank you!

For @zbook to analyze your log files you must follow these instructions as the logs have to be in a format his analyzer can read and interpret. Follow the instructions exactly and upload to any cloud provider. Post a SHARED link here. BSOD - Posting Instructions

KB5094126 is the June update. Have you had this problem since June? One solution would be to restore a system image made at a time when WU was working normally. (if you have one)

These are GENERAL WINDOWS UPDATE PROBLEMS things to try. Some which you indicated you tried, some you haven't, and others which you say you can't try or don't want to try for whatever reason. I learned a long time ago that at times we are at the mercy of the problem at hand and have to do what must be done when we experience certain issues. Not all issues have an easy, obvious fix.

1. Run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.

2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial

3. Open command prompt as administrator. Enter this command.
dism /online /cleanup-image /restorehealth
When complete, Restart computer

Then open command prompt as admin again and run sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair

4. CLEAN UP COMPONENT STORE - dism /online /cleanup-image /startcomponentcleanup
Analyze and Clean Up Component Store (WinSxS folder) in Windows 11 Tutorial

5. Do a repair install. This usually works when nothing else will. Repair Install Windows 11 with an In-place Upgrade Tutorial

glasskuter said:

For @zbook to analyze your log files you must follow these instructions as the logs have to be in a format his analyzer can read and interpret. Follow the instructions exactly and upload to any cloud provider. Post a SHARED link here. BSOD - Posting Instructions

KB5094126 is the June update. Have you had this problem since June? One solution would be to restore a system image made at a time when WU was working normally. (if you have one)

These are GENERAL WINDOWS UPDATE PROBLEMS things to try. Some which you indicated you tried, some you haven't, and others which you say you can't try or don't want to try for whatever reason. I learned a long time ago that at times we are at the mercy of the problem at hand and have to do what must be done when we experience certain issues. Not all issues have an easy, obvious fix.

1. Run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.

2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial

3. Open command prompt as administrator. Enter this command.
dism /online /cleanup-image /restorehealth
When complete, Restart computer

Then open command prompt as admin again and run sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair

4. CLEAN UP COMPONENT STORE - dism /online /cleanup-image /startcomponentcleanup
Analyze and Clean Up Component Store (WinSxS folder) in Windows 11 Tutorial

5. Do a repair install. This usually works when nothing else will. Repair Install Windows 11 with an In-place Upgrade Tutorial

Click to expand...

Thank you so much for this detailed troubleshooting list. I really appreciate how supportive and structured this community is compared to other platforms.

Because I am traveling on July 31st for a 4-month trip and my absolute highest priority is protecting my legacy AMD graphics profiles, thin system fonts, and fine-tuned ASUS display configurations, I want to completely avoid heavy overhauls like an in-place repair install. My system component store is already 100% clean according to SFC and DISM scans, but the update loop persists due to that AppxPackage::Initialize database roadblock.

To solve this issue as soon as possible without risking my custom driver settings, I am looking closely at the specific error code from my clean logs:
FAILED Method failed [AppxPackage::Initialize:235] with error code 0x80070032.

Instead of a general Windows Update reset, what do you think about running an elevated programmatic AppX Provisioned Package Rebuild directly through PowerShell? Specifically using this deployment script:

Get-AppxProvisionedPackage -Online | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -ErrorAction SilentlyContinue }

Does this provisioned script carry any risk of resetting custom hardware device properties or display profiles under Windows 11 Build 26200.8117? If this is safe, would it be the fastest way to directly repair the underlying Initialize registry baseline so the update can complete immediately?

Alternatively, if that carries any risk right before a flight, would a tool like GRC's "InControl" or the standard "WUShowHide" utility be a better, cleaner choice to just lock my system layout down safely so I can deal with it when I return in 4 months?

I would love to get your expert analysis on this specific PowerShell command vs the version-locking tools so I can execute the safest fix before tomorrow morning. Thank you!

If I understand correctly you try to install the cumulative update that gives you build 8117. Why don't you just skip this version and install a newer build? You can find the relevant updates in Microsoft Update Catalog. As for your drivers have a copy of the installers so if anything goes wrong you can remove any traces with DDU and reinstall the drivers. You can also export the drivers and import them again, but I don't trust that too much. I would rather manually keep a copy of the installers and reinstall them if necessary to have complete control of the process. Don't forget to always run Setup as Administrator to let installer replace files and Registry keys as required.

GreenBowl3344 said:

what do you think about running an elevated programmatic AppX Provisioned Package Rebuild directly through PowerShell? Specifically using this deployment script:

Get-AppxProvisionedPackage -Online | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -ErrorAction SilentlyContinue }

Does this provisioned script carry any risk of resetting custom hardware device properties or display profiles under Windows 11 Build 26200.8117? If this is safe, would it be the fastest way to directly repair the underlying Initialize registry baseline so the update can complete immediately?

Click to expand...

Regarding scripting and what each one does, I am far from knowing enough in that area to answer your question. Hopefully one of these more experienced guys in scripting will give you an answer. @garlin @dacrone @pseymour

have you tried downloading the update and the manually installing this update

Microsoft Update Catalog

it also maybe an idea to check and reset Windows update

https://windowsreport.com/how-to-reset-windows-update/

even if they fail to sort the problem they should lead in directions to give an idea what the problem is
you can also check these as well

#####
you can also check the reliability monitor to check for recent errors.
control panel > security and maintenance > maintenance > reliability monitor

#####
then check 'problem devices'
system tools > system information > components > problem devices

which should show any recent errors or events.
best of luck Steve ..

I've inspected those logs three times. There's nothing that stands out in the parts that have been posted.
Error code 0x80070032 is a generic failure.

This command will only re-register your UWP app packages, but it cannot repair a damaged package instance at the Windows level.

Meaning if your Windows isn't damaged, then it fixes the AppX instances for your individual user profile. A different local user wouldn't necessarily have the same broken experience with their apps. Good Windows -> you can fix your own Appx packages.

When Windows Update is stuck in a death loop with high CPU usage, it's a system-level fault regardless of who might have a broken user profile. There are two types of Appx packages: (non-removable) default Windows apps and Store apps. A Store app is any app that can be removed and re-installed by the Microsoft Store app. A default app can only be updated by a new Monthly Update.

If I had to guess, it's probably stuck on a default app which means something on the current system is corrupted.

With a hard deadline for a travel date, I would pause WU for whatever time you will be absent. Then if you're really concerned about this custom setup, then make a full backup before attempting any changes. A problem this severe normally calls for a repair reinstall.