Windows 11 Pro Windows Update failure(s) on multiple Win11 22H2 then 23H2 PCs

Two PCs running Windows 11 Pro (22H2) that were "stuck" unable/unwilling to Windows-Update further, telling *me* that *I* was running an end-of-life OS/product and that *I* needed to jump thru (unknown) hoops to fix this. Then pointing me to useless URLs with generic info about Windows 7, Window Visa, Windows 10, etc.

Both PCs were *already* running Windows 11 (22H2). Running Microsoft's WindowsPCHealthCheckSetup.msi originally told me that (useless) TPMs weren't present, so I turned the TPM on in the AMI BIOS. After I did that and rebooted, WindowsPCHealthCheckSetup.msi told me that both PCs fully met all MS criteria for Windows 11 updating (even though they were both already running Win11 22H2) but still wouldn't Windows-Update anything.

Windows 11 22H2 => Windows Update fail
=> 23H2 ISO update-install fail
=> 23H2 by manually running an "enablement package" (MS's windows11.0-kb5027397-x64.msu) found after lots of web-searching.
This worked to update to 23H2 on these two PCs to 23H2 (at least per OS Properties), changing the version to 23H2 but not changing the install date.
=> 24H2 ISO update-install fail
=> 25H2 ISO update-install fail. This hokey-pokey worked on one of the Win11 PCs, after running the same 23H2 "enablement package", then 25H2 ISO. But not the other PC.

The still-failing-WinUpdate Win11 23H2 (after difficult non-WinUpdate update from 22H2) PC is a lightly-used desktop PC with an AMD mobo, built three+ years ago with a brand new legally-purchased Win11 Pro license. HDMI-connected to a TV monitor. Very little software installed -- a few simple utilities and several web browsers, used for streaming from assorted TV & streaming sources. No excuse for Win11 Windows Update to fail.

2025-11 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5068865)
Install error - 0x80070002

# Plenty of reboots.
# Windows Update is completely stuck and unable/unwilling to continue even with multiple retries.
# Tried running-as-admin a couple other Microsoft Windows utilities

# After lots of searching, found and ran these that also failed:

DISM.exe
Error: 0x800f081f

sfc /scannow
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file...

# You're not selling a product just to nerds who enjoy spending endless hours %$#@ around with a toy. Nor are they wiling to look thru 20-page logs of techno-babble to try to guess that's what's wrong with Microsoft's product & programmers, maybe after more nerd searches & guesses. You're selling it to non-computer-geek consumers who want to use it to actually get something useful done. The diagnosis here is simple, as is the "fix" -- *your* Windows Update doesn't work, and *Microsoft* needs to fix Windows Update. If you can't or are unwilling to provide a useful product, other companies and far smarter programmers can & will.

Only things I can think to try are a complete reinstall of Windows 11, or better, trashing the entire OS and installing a Linux OS that actually works.

And Microsoft has the gall to complain that people won't upgrade *working* Windows 10 computers to Windows 11...


################################################################
Device Specifications
Processor: AMD Ryzen 5 2600 Six-Core Processor 3.40 GHz
Installed RAM: 64.0 GB
System type: 64-bit operating system, x64-based processor

Windows Specifications
Edition: Windows 11 Pro
Version: 23H2
Installed on: 12/24/2022
OS Build: 22631.4317
Experience: Windows Feature Experience Pack 1000.22700.1041.0

C:\Windows\System32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.4317
[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


C:\Windows\System32>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 but was unable to fix some of 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.

Choose one computer for this thread and open a second thread for the other problematic computer.



1) Please run the V2 log collector > post a share link




2) Add WMIC:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~




3) Run upgrade_failure_info > post a share link






4) Run Tuneup plus > post a share link into the newest post






5) Download to a new desktop folder:

23H2 to 24H2 using In-Place Upgrade. (Option Two)
A 24H2 ISO will be needed
Say no to checking for updates

Then 25H2 enablement package or do another in-place with a 25H2 ISO.
The shortcut would be, attempting an in-place from 23H2 to 25H2 using a 25H2 ISO


You will need a 24H2 ISO for a 24H2 in-place upgrade ( I have one currently downloading for another member, about an hour away)

Or if you want to go from 23H2 straight to 25H2, try the 25H2 ISO from this (Option One)


Then do the in-place with whichever ISO you have acquired. OPTION TWO

RescueBlues said:

# You're not selling a product just to nerds who enjoy spending endless hours %$#@ around with a toy.

Click to expand...

Also, just to confirm, this is not a Microsoft forum, we are a community of volunteers.

IMO I don't think we can give 100% solid advice until more is known about the hardware you are running. Unlike earlier versions of 11, 24h2/25h2 has a strict non bypassable requirement in that your CPU has to support sse4.2 instruction set.

RescueBlues said:

Device Specifications
Processor: AMD Ryzen 5 2600 Six-Core Processor 3.40 GHz
Installed RAM: 64.0 GB
System type: 64-bit operating system, x64-based processor

Click to expand...

Doesn’t list the MB

CPU
Apr 19th, 2018

• MMX
• SSE
• SSE2
• SSE3
• SSSE3
• SSE4A
• SSE4.1
• SSE4.2
• AES
• AVX
• AVX2
• BMI1
• BMI2
• SHA
• F16C
• FMA3
• AMD64
• EVP
• AMD-V
• SMAP
• SMEP
• SMT
• Precision Boost 2