Windows 11 Pro can't update. Stuck on 21H2 (22000.434)

johnp · Jan 6, 2025

bobkn said:
I can't speak to all this.

However, you can go from 22H2 to 23H2 via a small enablement package. Rather than an upgrade.

KB5027397 Enablement Package for Windows 11 version 23H2 Feature Update

UPDATE 7/18: https://www.elevenforum.com/t/windows-11-2023-update-version-23h2-is-now-broadly-available-to-all.26877/#post-481661 Microsoft Support: Summary Windows 11, versions 22H2 and 23H2 share a common core operating system with an identical set of system files. Therefore, the new features...

www.elevenforum.com

This is the solution, the enablement package.

zbook · Jan 6, 2025

During 09/24 and 10/24 there were a very large number of disk errors.

One was:
The driver has detected that device \Device\Harddisk1\DR1 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.

Was one or more drives replaced?

zbook · Jan 6, 2025

Please post new event system and application links:

How to share event logs in case of a computer issue

This article explains how to share Event Logs from the event viewer in case if you have a Windows problem as investigation would help.

www.yourwindowsguide.com

raszyniaczek · Jan 6, 2025

Yes i replace one m2 drive but on this drive i have only steam games.

apps event viewer.evtx

system event viewer.evtx

zbook · Jan 6, 2025

raszyniaczek said:
Yes i replace one m2 drive but on this drive i have only steam games.

apps event viewer.evtx

system event viewer.evtx

The links were not able to be opened.

raszyniaczek · Jan 6, 2025

Please try now. New links below

apps event viewer.evtx

system event viewer.evtx

zbook · Jan 6, 2025

Applic worked
System failed to open

Update the progress updating defender (not windows).

Are you able to detach all non-windows drives now?

Then post a new V2 and diskpar info

https://www.tenforums.com/attachments/bsod-crashes-debugging/355861d1640707960-batch-files-use-bsod-debugging-diskparinfo.bat

zbook · Jan 6, 2025

Are you there?

Running out of waiting time (> 30 - 40 min)

raszyniaczek · Jan 6, 2025

Ok i need go to sleep now, but tomorrow i try detach all disks.

Defender is up-to-date now with latest build.

system event viewer.evtx

zbook · Jan 6, 2025

What were the problems with the links?

What had to be modified?

raszyniaczek · Jan 6, 2025

I had to change that if you have a link you can edit. Before it was only a preview.

zbook · Jan 6, 2025

On 12/03/2024 one of the drives reported a bad block.

(it could have been a disk or flash drive)

Run the chkdsk /b /v on all drives.

12/05/2024
A corruption was discovered in the file system structure on volume G:.

Dokładna istota uszkodzenia nie jest znana. Należy przeskanować struktury systemu plików w trybie online.

raszyniaczek · Jan 6, 2025

I want to make sure. I currently have a Windows Insider build - Dev channel.

The next update to 22H2 must also be for the Dev channel?

I'll have the image downloaded soon that @dacrone shared with me

I'll try to install it before I go to bed soon.

raszyniaczek · Jan 6, 2025

Okay, I'll try to scan all the drives one by one after I get some sleep.

Next, I'll take the computer apart and remove all the unnecessary drives.

zbook · Jan 6, 2025

Ok.

After running chkdsk /b /v on all drives post new event system and application.

When only the Windows is attached post new V2 and diskparinfo.

Goodnight

When available update the progress with post #20.

Code:

12/3/2024 10:51:18 AM

The device, \Device\Harddisk1\DR1, has a bad block.

12/11

Code:

The IO operation at logical block address 0x539aa2cc8 for Disk 4 (PDO name: \Device\000000aa) was retried.

11/11

Code:

The driver has detected that device \Device\Harddisk1\DR1 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.

12/4/2024 6:19:35 PM

Code:

Display driver nvlddmkm stopped responding and has successfully recovered.

12/04/2024

Code:

Chkdsk was executed in read/write mode. 

Checking file system on G:

Stage 1: Examining basic file system structure ...
  342528 file records processed.                                                         File verification completed.
 Phase duration (File record verification): 18.15 seconds.
  941 large file records processed.                                     Phase duration (Orphan file record recovery): 1.57 milliseconds.
  0 bad file records processed.                                       Phase duration (Bad file record checking): 1.11 milliseconds.

Stage 2: Examining file name linkage ...
  23 reparse records processed.                                         356282 index entries processed.                                                        Index verification completed.
 Phase duration (Index verification): 29.47 seconds.

 Phase duration (Orphan reconnection): 30.89 milliseconds.
The data written out is different from what is being read back
at offset 0xc0001400 for 0x400 bytes.
An unspecified error occurred (696e647863686b2e 204a).
An unspecified error occurred (6e74667363686b2e 1847).

raszyniaczek · Jan 6, 2025

Unfortunately, it didn't install from this ISO file.

I'm really tired of this. I'll try to scan all the disks today and see what happens.

Good night and thanks for help :)

zbook · Jan 6, 2025

From post #20:

Comment on the oldest and newest backup images.

Comment on the camera hardware.

Please make a new backup image before detaching all non-windows drives.

When only the Windows drive is attached post new V2 and diskparinfo.

Code:

Update Boot Code. Error: 0x80004005

Code:

Error: 0x80004005 - 0x50016

Code:

    HostOSVersion = 10.0.22000
    HostOSBuildString = 22000.1.amd64fre.co_release.210604-1628
    TargetOSBuildString = 10.0.22621.1 (ni_release.220506-1250)
    HostOSLanguageId = 1045
    HostOSEdition = Professional

Code:

 RegisteredAV = ESET Security

Code:

ESET Security, Path: C:\Program Files\ESET\ESET Security\ekrn.exe, Timestamp: Sun, 31 Dec 2023 02:48:39 GMT, State: 266240

Code:

2025-01-05 05:02:08, Info                  SP     >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2025-01-05 05:02:08, Info       [0x06412c] IBSLIB     SetCheckpoint: Checkpoint("SetupPlatformWinReRestoreCheckpoint") in progress...
2025-01-05 05:02:08, Info       [0x06412e] IBSLIB     SetCheckpoint: Checkpoint "SetupPlatformWinReRestoreCheckpoint" successfully set.
2025-01-05 05:02:08, Info       [0x06412c] IBSLIB     SetCheckpoint: Checkpoint("WinPEBootFilesRestoreCheckpoint") in progress...
2025-01-05 05:02:08, Info                  IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: System volume drive path is [K:\]
2025-01-05 05:02:08, Info                  IBSLIB     TrackVolume: Successfully marked that [$Setup_SystemVolume$] is on drive [K:].
2025-01-05 05:02:08, Info                  IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: K:\boot.ini does not exist, skip.
2025-01-05 05:02:08, Info                  IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: K:\ntldr does not exist, skip.
2025-01-05 05:02:08, Info                  IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: K:\NTDETECT.COM does not exist, skip.
2025-01-05 05:02:08, Info                  IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: K:\bootmgr does not exist, skip.
2025-01-05 05:02:08, Error                 IBSLIB     BCD: Unexpected length for BCD element. Length 200 Expected: 254 DataType: 285212673[gle=0x00000002]
2025-01-05 05:02:08, Error                 IBSLIB     BCD: Failed to get the size needed for the registry data. Element: 11000001, Status: c0000024[gle=0x00000002]
2025-01-05 05:02:08, Error                 IBSLIB     BCD: BcdCopyObjectEx: Failed to enumerate source elements. Target: {890f989b-7d40-11e2-8053-9b1bda41daaa} Flags: 0x4 Status: c0000024[gle=0x00000002]
2025-01-05 05:02:08, Error                 IBSLIB     BCD: Failed to clone store. Status: c0000024[gle=0x00000002]
2025-01-05 05:02:08, Error                 IBSLIB     BCD: BcdExportStore: Failed clone BCD to \??\C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot\BCD. Status: c0000024[gle=0x00000002]
2025-01-05 05:02:08, Error                 IBSLIB     OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: Failed to backup BCD database from "K:\EFI\Microsoft\Boot\BCD" to "C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot\BCD".[gle=0x00000006]
2025-01-05 05:02:08, Error      [0x064199] IBSLIB     SetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(6), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000006]
2025-01-05 05:02:08, Error      [0x06418a] IBSLIB     RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(6), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CCheckpointImpressario::SetCheckpoint(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)
void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000006]
2025-01-05 05:02:08, Error      [0x06414e] IBSLIB     RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint) failed. Disabling Rollback.[gle=0x00000006]
2025-01-05 05:02:08, Error                 SP         Error setting OS Switch Rollback checkpoint[gle=0x00000006]
2025-01-05 05:02:08, Info                  SP         CUpdateBootCode::DoExecute: Try to repair BCD file due to potential corruption error
2025-01-05 05:02:08, Info                  SP         SideLoadHandler: Side-loaded C:\$WINDOWS.~BT\Sources\bootsvc.dll (DLL name bootsvc.dll).
2025-01-05 05:02:08, Error                 SP         CUpdateBootCode::DoExecute: An error occurred while repair system partition. Root path [C:\Windows]. Error: 0x80070032[gle=0x00000032]
2025-01-05 05:02:08, Info                  SP     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2025-01-05 05:02:08, Error                 SP     Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]
2025-01-05 05:02:08, Info                  MOUPG  Finalize: Registering Setup Platform error: [0x80004005]
2025-01-05 05:02:08, Error                 SP     ExecuteOperations: Main operation execution failed. Error: 0x80004005
2025-01-05 05:02:08, Error                 SP     ExecuteOperations: Failed execution phase Finalize. Error: 0x80004005
2025-01-05 05:02:08, Info                  MOUPG  MoSetupPlatform: SetupPlatform::INewSystem::Finalize returned: [0x4]
2025-01-05 05:02:08, Error                 MOUPG  MoSetupPlatform: Finalize reported failure![gle=0x80004005]

raszyniaczek · Jul 25, 2025

Hey, I'm revisiting this thread. I managed to track down the faulty drive and replace it with a brand new WD Blue 1TB.

What steps can I take now to try to continue this thread?

Of course, the update still doesn't work. Neither from the ISO, nor from a USB drive with the ISO, nor through the Windows Update Assistant.

New V2 log: GAMING-PC-(2025-07-25_22-45-30).zip

Scannerman · Jul 25, 2025

Admittedly, I have not read every post on this thread BUT if this is a Hackintosh we are discussing or, if you're using parts or partial software pulled from an Apple this could present a bit of a problem. If this happens not to be the case then I have a question: Have you tried installing a fresh copy of 24H2 on a separate drive? Myself, I would have opted for a 1TB SSD for the OS. Hopefully that is what you did. Upgrades are finicky and I don't trust them. With a fresh install you cut to the chase instead of wasting hours and hours of time fiddling with the OS just to coax the thing into accepting an upgrade.

raszyniaczek · Jul 25, 2025

According to chatGPT, this old Insider Preview version of my system has a blocked update channel, which also prevents me from updating from an ISO via USB. He recommended trying a few settings in Rufus, which might help, including:

Rufus will display a special window with installation options.

Select:

Remove TPM 2.0 requirements

Remove Secure Boot requirements

Allow installation on unsupported builds ← MOST IMPORTANT

Preserve user data (if available)

I'll be trying this option soon – Allow installation on unsupported builds – if there's one to check in Rufus.

Windows 11 Pro can't update. Stuck on 21H2 (22000.434)

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer