My Windows Update (like KB5074109) keeps failing or getting stuck. What do I do?

[zaasmi]

Since we are in late January 2026, the Windows landscape is currently dealing with several “borked” updates. Based on the latest reports from this morning, here are the most critical FAQs for the issues you’re likely facing.

---

🚨 Current Windows 11 Critical Alert (January 2026)

Q: Why won’t my computer shut down or go to sleep?

• The Issue: The January 13th update (KB5073455) for Windows 11 23H2 broke the shutdown/hibernate process on many PCs, especially those with System Guard Secure Launch enabled. Instead of turning off, the PC just restarts.
• The Solution: * Manual Shutdown: Use the command line for a “hard” shutdown that bypasses the glitched UI:
  shutdown /s /t 0
• The Fix: Microsoft has released an emergency “Out-of-Band” (OOB) update to fix this. Check Windows Update for KB5078127 or newer.

Q: I’m seeing a “Black Screen of Death” with code UNMOUNTABLE_BOOT_VOLUME. How do I fix it?

• The Issue: Update KB5074109 (released Jan 13 for versions 24H2/25H2) is causing physical PCs to enter a boot loop.
• The Solution:

1. Force your PC into WinRE (Turn it off and on 3 times quickly during the boot logo).
2. Go to Troubleshoot > Advanced Options > Uninstall Updates.
3. Select Uninstall latest quality update.
4. Once back in Windows, skip the KB5074109 update until the patched version is offered.

Q: Why are Outlook, OneDrive, and Notepad crashing or not responding?

• The Issue: A bug in the January cumulative patch accidentally corrupted the way certain “Inbox Apps” (like Notepad, Paint, and Outlook Classic) handle memory and cloud-synced files.
• The Solution: * Install the emergency update KB5078127.
• If that’s not available yet, move your Outlook .pst files out of the OneDrive synced folder to a local path (like C:\LocalData).

---

🛠️ Essential Windows Discussion & Troubleshooting Guide

Feature	Issue	Best Fix / Command
System Health	Slow performance or 0x800… errors	DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow
Windows Update	Update stuck at 0% or 100%	Reset the SoftwareDistribution folder (Stop wuauserv service, delete folder contents, restart service)
Hardware/Audio	“Insufficient system resources” (Code 10)	Recent bug in 25H2: Re-install audio drivers from the manufacturer’s site, not Windows Update
Windows 10	ESU (Extended Security) glitches	MSMQ and legacy printer features are currently broken; use the KB5071546 offline installer

---

💡 Quick Tips for 2026 Users

• Pause Updates: Given the high failure rate this month, it is recommended to go to Settings > Windows Update and Pause for 1 week until Microsoft stabilizes the current patches.
• Check for OOB Fixes: Microsoft is releasing “emergency” fixes outside of the normal schedule right now. If your PC is acting up, check for updates multiple times a day.

[zaasmi]

As of late January 2026, Microsoft has officially released the emergency “Out-of-Band” (OOB) patch to address the chaos caused by the earlier January updates.

Depending on your specific Windows version, you need one of the two patches released on January 24, 2026.

---

📥 Direct Download & Manual Install Links

If Windows Update is stuck or not showing the fix, you can download the standalone installers directly from the Microsoft Update Catalog:

For Windows 11 (Versions 24H2 and 25H2)

• KB Number: KB5078127
• Fixes: Outlook Classic crashes/freezes, App unresponsive errors, and File Explorer “save-to-cloud” hangs.
• Manual Download: Search KB5078127 on Microsoft Update Catalog

Tip: Choose the x64 version for standard Intel/AMD PCs, or ARM64 if you are using a Surface Pro (Snapdragon) or similar ARM device.

For Windows 11 (Version 23H2)

• KB Number: KB5078132
• Fixes: The “Restart loop” instead of Shutdown, and Remote Desktop authentication failures.
• Manual Download: Search KB5078132 on Microsoft Update Catalog

---

🛠️ How to Resolve Error 0x800f0922 (The Update Fails to Install)

If you try to install the fix but get error 0x800f0922, it usually means the “System Reserved” partition is full or a service is blocked. Try these three steps:

1. Check System Reserved Space: Ensure your primary drive has at least 15-20GB of free space. The update requires a temporary “staging” area.
2. Enable App Readiness: * Press Win + R, type services.msc, and hit Enter.

• Find App Readiness, right-click it, and set it to Automatic, then click Start.

3. Flush the Update Cache (CMD):
   Open Command Prompt (Admin) and run these exactly:

net stop wuauserv
net stop bits
del /f /s /q %windir%\SoftwareDistribution\*.*
net start wuauserv
net start bits

---

❓ Frequently Asked Questions (Jan 2026)

Q: I still have a Black Screen. Can I install the fix?
No, you must get to the desktop first. Use the WinRE (Recovery Environment) to “Uninstall latest quality update” first. Once you can log in, then run the manual KB5078127 installer above.

Q: Is there a fix for Windows 10?
Yes. For Windows 10 users (specifically those on ESU/Enterprise), look for KB5078129. It addresses similar app-freezing issues.

Q: Should I wait for the February update instead?
If your Outlook or OneDrive is freezing, do not wait. These OOB (Out-of-Band) updates are stable and designed specifically to fix the critical bugs in the January 13th release.

[zaasmi]

@Germony-Germon said in My Windows Update (like KB5074109) keeps failing or getting stuck. What do I do?:

The Problem: Updates often fail due to a corrupted “SoftwareDistribution” cache or interference from third-party antivirus.

@secntoai please reply

[leotech1]

To ensure you download the correct fix, you need to identify your specific Windows Version and OS Build. Since we are in late January 2026, Microsoft has released separate “Out-of-Band” (OOB) updates for different versions to fix the recent Outlook crashes and boot loops.

1. Identify Your Windows Build

The quickest way to see exactly what you’re running is the Winver command:

1. Press Windows Key + R on your keyboard.
2. Type winver and hit Enter.
3. A dialog box will appear. Look for the lines that say Version and OS Build.

---

2. Match Your Version to the Correct Fix

Based on the data as of January 27, 2026, here is which patch you need:

Windows Version	Required Build After Fix	Update ID (KB Number)	Primary Issues Fixed
Windows 11 25H2	26200.7628	KB5078127	Outlook crashes, unresponsive cloud apps
Windows 11 24H2	26100.7628	KB5078127	Outlook/OneDrive hangs, UI lag
Windows 11 23H2	22631.6495	KB5078132	Shutdown acting as Restart, RDP bugs
Windows 10 22H2	19045.xxxx	KB5078129	App freezes (ESU/Enterprise only)

---

3. How to Download Manually

If your “Check for updates” button isn’t working or the update fails to install automatically:

1. Go to the Microsoft Update Catalog.
2. Enter your KB Number (e.g., KB5078127) in the search bar.
3. Choose the correct Architecture:

• x64: For most standard Intel or AMD laptops/desktops.
• ARM64: For newer “Copilot+” PCs or Surface devices with Snapdragon processors.

4. Download the .msu file and run it.

⚠️ Warning: If you are currently experiencing a Black Screen or cannot log in, do not try to install these yet. You must first go into Recovery Mode (WinRE) and Uninstall the latest quality update (likely KB5074109) to restore system stability before applying these new fixes.

[Rana ahram]

The error 0x800f0922 is quite common with the January 2026 patches. It usually indicates that your PC is having trouble communicating with the update servers, or more commonly, that there isn’t enough space in the System Reserved Partition to handle the new boot files.

Here is the step-by-step resolution guide:

---

🛠️ How to Fix Error 0x800f0922

1. Enable the “App Readiness” Service

In many 2026 builds, this service is set to “Manual” or “Disabled,” which blocks the final staging of an update.

• Press Win + R, type services.msc, and hit Enter.
• Find App Readiness in the list.
• Right-click it, select Properties, change the Startup type to Automatic, and click Start.
• Try the update again.

2. Clear the Windows Update “Staging” Area

If a previous attempt failed, the corrupted files might still be sitting in your cache.

1. Right-click Start and select Terminal (Admin) or Command Prompt (Admin).
2. Type the following commands one by one, hitting Enter after each:

net stop wuauserv
net stop bits
rename c:\windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

3. Restart your PC and try the manual .msu installer again.

3. Repair the .NET Framework

Error 0x800f0922 is frequently tied to a broken .NET installation.

• Press Win + S, type Turn Windows features on or off, and open it.
• Uncheck everything related to .NET Framework 3.5 and 4.8. Click OK (this will uninstall them temporarily).
• Restart your PC.
• Go back into the same menu and re-check those boxes. Let Windows download the files again.

4. Check the System Reserved Partition

If you have a very small System Reserved partition (common on older SSDs upgraded to Windows 11), the update will fail because it can’t write the new “Secure Boot” data.

• Right-click Start and select Disk Management.
• Look for a small partition (usually 100MB to 500MB) labeled “System Reserved” or “EFI System Partition.”
• If it shows 0% free space, you may need a third-party tool (like MiniTool Partition Wizard) to expand it to at least 600MB–1GB.

---

💡 Discussion: Why this is happening in 2026

The KB5078127 update includes heavy security changes to the Windows Kernel to protect against new UEFI-level threats discovered late last year. Because it modifies the very first files your computer reads when it turns on, any tiny error in your disk structure or a blocked service causes the “0x800f0922” safety abort.

[zaasmi]

Checking the free space on your hidden system partition is a smart move. Because that partition doesn’t have a drive letter, it’s “invisible” to standard tools like File Explorer.

Here is the precise PowerShell command to see exactly how much space you have left.

---

🖥️ Step 1: Check System Partition Free Space

1. Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
2. Copy and paste the following command and hit Enter:

Get-Partition | Where-Object { $_.GptType -eq "{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}" } | Get-Volume | Select-Object SizeRemaining, Size | Format-List

• SizeRemaining: This is your free space in bytes.
• Size: This is the total size of that partition.
• The Goal: You generally need at least 15MB to 30MB of free space for a standard Windows update to succeed. If SizeRemaining is very low (e.g., less than 15,000,000 bytes), the update will fail with error 0x800f0922.

---

🧹 Step 2: How to Clean the System Partition (If Full)

If the command above shows almost no space, you can often clear up room by removing old font files or logs that shouldn’t be there.

1. Mount the partition temporarily:
   In the same Admin Terminal, type:
   mountvol Y: /s
   (This assigns the letter Y: to that hidden partition so you can look inside).
2. Navigate to the Fonts folder:
   cd Y:\EFI\Microsoft\Boot\Fonts
3. Delete non-essential files:
   You can safely delete the font files to make room for the update:
   del *.* /q
4. Unmount when finished:
   mountvol Y: /d

---

📊 Quick Comparison: What “Healthy” Looks Like

Metric	Ideal (Healthy)	Warning (Update will fail)
Total Partition Size	100MB to 500MB	Less than 100MB
Free Space	Above 25MB	Less than 15MB
File System	FAT32	RAW or Unknown

---

⚠️ A Note for January 2026

If you are seeing “0MB” free space, it is likely that a previous failed update left “trash” files behind. Running the mountvol cleanup steps above is the most effective way to unblock KB5078127 without having to resize your entire hard drive.

[zaasmi]

Since we are dealing with the specific “System Reserved” space issue commonly associated with error 0x800f0922 in 2026, I have designed a “Check and Clean” script.

This script safely mounts the hidden partition, checks for the “font bloat” caused by recent updates, and clears it to make room for the KB5078127 fix.

---

📜 The “0x800f0922 Recovery” Script

Instructions: 1. Right-click Start and select Terminal (Admin) or PowerShell (Admin).
2. Copy the entire block below and paste it into the window.

# 1. Identify the EFI/System Partition
$targetPart = Get-Partition | Where-Object { $_.GptType -eq "{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}" }

if ($null -eq $targetPart) {
    Write-Host "Critical Error: Could not find EFI System Partition." -ForegroundColor Red
    return
}

# 2. Check current free space
$initialSpace = (Get-Volume -UniqueId "\\?\Volume$($targetPart.Guid)\").SizeRemaining
Write-Host "Current Free Space: $([math]::Round($initialSpace / 1MB, 2)) MB" -ForegroundColor Yellow

# 3. Mount and Clean (If space is less than 30MB)
if ($initialSpace -lt 30MB) {
    Write-Host "Low space detected. Starting cleanup..." -ForegroundColor Cyan
    
    # Mount to Y:
    mountvol Y: /s
    
    # Target the Font directory which often holds 20MB+ of unneeded files
    $fontPath = "Y:\EFI\Microsoft\Boot\Fonts"
    if (Test-Path $fontPath) {
        Remove-Item -Path "$fontPath\*.ttf" -Force -ErrorAction SilentlyContinue
        Write-Host "Cleanup complete: Font cache cleared." -ForegroundColor Green
    }
    
    # Unmount Y:
    mountvol Y: /d
} else {
    Write-Host "Space looks sufficient, but running a reset on update services for safety..." -ForegroundColor Gray
}

# 4. Final Reset of Update Services
net stop wuauserv /y
net stop bits /y
Write-Host "Ready! Please try installing the update again." -ForegroundColor Green

---

🔍 What this script does:

• Safety Check: It only runs if it finds the official GPT “System Partition” GUID.
• The “Font Fix”: Windows stores multiple language font files in the boot partition. In 2026, many updates have failed because these files reached the 100MB limit. Deleting the .ttf files here is safe; Windows only needs the basic system fonts to boot.
• Service Reset: It stops the Update and BITS services to clear any “pending” status that might be blocking the install.

💡 What if it still fails?

If the script says “Ready” but the update still fails with 0x800f0922, there is one final hardware-level check:

• Manufacturer Bloat: Brands like HP and Dell sometimes store “BIOS Update” logs in the EFI partition.
• Solution: You may need a third-party partition manager to resize the EFI partition from 100MB to 500MB by “stealing” space from your C: drive. This is a permanent fix for the rest of 2026.

[InvoiceTemple]

If the cleanup script didn’t provide enough space, you’ll need to manually resize the partition. Since Windows Disk Management cannot extend the EFI (System) partition, you must use a third-party tool.

As of January 2026, here are the most reliable free tools for this specific job:

---

🏆 Top Recommended Free Tools (2026)

1. MiniTool Partition Wizard (Free Edition) – Most Popular

This is the “go-to” for most Windows users. It is very visual and easy to use for beginners.

• The Pro: Very stable; specifically has an “Extend Partition” wizard that can “borrow” space from your C: drive even if they aren’t right next to each other.
• The Catch: In 2026, some advanced boot-level features require the “Pro” version, but basic resizing is usually free.
• Download: Official MiniTool Site

2. DiskGenius (Free Edition) – Best for “Full” Partitions

If your partition is so full that other tools error out, DiskGenius is excellent at handling “clogged” system sectors.

• The Pro: It has a built-in “Verify and Repair Bad Sectors” tool which is helpful if your update failed due to disk health issues.
• Download: Official DiskGenius Site

---

🪜 How to Resize the EFI Partition (Step-by-Step)

Most of these tools work the same way. Here is the general workflow to fix error 0x800f0922:

1. Backup: Before touching partitions, ensure your important files are backed up.
2. Shrink C: Drive: * Right-click your C: Partition in the tool.

• Select Move/Resize.
• Drag the left side of the C: partition to the right to create 500MB of “Unallocated Space” between the EFI partition and C:.

3. Extend EFI Partition:

• Right-click the EFI/System Partition (usually formatted as FAT32).
• Select Extend or Resize.
• Drag its boundary into that new unallocated space until it is roughly 500MB to 1GB.

4. Apply Changes: Click the Apply button at the top. The computer will likely need to restart into a “Pre-OS” mode to move the files safely.

---

⚠️ The “MSR” Partition Warning

On many Windows 11 systems, there is a tiny 16MB “Microsoft Reserved” (MSR) partition sitting between your EFI and your C: drive.

• The Problem: This 16MB block often blocks you from extending the EFI partition.
• The Solution: Most 2026 tools (like MiniTool) will allow you to delete this 16MB partition safely. It is a “placeholder” and is not required for Windows to boot. Once deleted, you can merge that space into the EFI partition.

[wiqijan2002]

Finding a good walkthrough is the final step to getting this sorted. Since the 16MB “MSR” (Microsoft Reserved) partition usually blocks you from extending your EFI partition, DiskGenius is actually the more powerful tool for this specific 2026 update fix.

Here is the most reliable walkthrough based on current technical forums:

---

📺 Step-by-Step: Extending EFI with DiskGenius

Step 1: The Setup

1. Download: Get the Free Edition of DiskGenius.
2. Backup: (Always recommended) Ensure your personal files are backed up to an external drive.

Step 2: Shrink the C: Drive (from the Left)

To give the EFI partition space to grow, you must take space from the beginning of your main Windows drive.

1. Open DiskGenius. Right-click your (C:) partition.
2. Select Resize Partition.
3. Look at the graphic bar. Drag the left edge of the C: partition toward the right.

• Aim for 500MB to 1GB of “Unallocated Space” at the front.

4. Click Start. The computer will restart into a special “WinPE” mode to move your Windows files safely. Let it finish.

Step 3: Handle the 16MB MSR “Blocker”

Once you are back in Windows/DiskGenius, you will likely see a tiny 16MB partition between your EFI and your new unallocated space.

1. Right-click the 16MB Microsoft Reserved (MSR) Partition.
2. Select Delete Current Partition.

Don’t panic: Windows 11 does not need this partition to boot; it is a placeholder. Deleting it allows you to merge the EFI partition with the empty space you just created.

Step 4: Extend the EFI Partition

1. Right-click your EFI System Partition (the small one, usually FAT32).
2. Select Extend Partition.
3. Choose the Unallocated Space you created earlier.
4. Click Start. DiskGenius will instantly grow the partition.

---

🔗 Recommended Video Resources

Since I cannot play video directly, I recommend searching for these specific titles on YouTube, as they match the 2026 partition layouts perfectly:

• “How to Increase EFI System Partition Size | DiskGenius Tutorial” (Look for videos by Murugan S or Quick and Easy Tools—they are highly rated for this specific fix).
• “Fix Windows Update Error 0x800f0922 - Resize EFI Partition” (This will show you the visual “drag and drop” method).

---

✅ Final Check

After the restart, run the Winver command again. If your EFI partition now shows as 500MB+ in Disk Management, go to Settings > Windows Update and click Check for Updates.

The KB5078127 (or whichever patch was failing) should now install without the 0x800f0922 error.