KB5034441 rabbit hole

I have a recent clean install of 10P on MBR with the basic partitions: 1)system, 2)OS, 3)recovery. I thought getting past the KB5034441 update error would be simple since I had managed similar awhile ago on a different PC.

I tried the manual method for MBR disks posted:
https://support.microsoft.com/en-us/...9-24c8229763bf

It always fails with 'The Windows RE image was not found'. Something wrong with the steps since disk management should normally show the recovery partition as having no format instead of NTFS, and as "Healthy(Recovery Partition)" and not "Healthy(Primary Partition)".

reagentc /info ;originally showed disk 0 partition 3 was my recovery/RE location
reagentc /disable ;ok
diskpart ;ok
sel disk 0 ;ok
list part ;shows three partitions, 1) system, 2)OS, 3)recovery

Rather than use diskpart to shrink the OS partition, I used disk manager to free up
the additional 250MB suggested.

sel part 3 ;ok
delete partition override ;ok
list part ;partition 3 now gone
create partition primary id=27 ;ok
list part ;new partition 3 is type 'Recovery'
format quick fs=ntfs label="WinRE tools" ;works
list part ;works but partition 3 is now type 'Primary', not 'Recovery'
list vol ;shows volume 3 as "WinRE tools", NTFS, 773MB
exit ;ok
reagentc /enable ;FAILS - 'The Windows RE image was not found'
reagentc /info ;status disabled

Note that adding 'set id=27' after the format does not fix the failure.

Please run:

1) V2 log collector > post a share link

BSOD - Posting Instructions


2) Post an image disk management

How to Post a Screenshot of Disk Management

For the records, in MBR systems, after doing

format quick fs=ntfs label="WinRE tools"

the partition's id will change from 27 to 07. An additional command (inmediately after the previous one):

set id=27; with list part list disk sel part etc before if you want to be sure

not listed by MS fixes this. So the normal result of your diskpart section would be that you have no recovery partition.

What stranges me more is this:

reagentc /enable ;FAILS - 'The Windows RE image was not found'
reagentc /info ;status disabled

Unless I'm wrong, the expected result would be that the recovery partition contents is deployed in C:\Recovery , what has advantages and shorcomings not well known by me, but it's a normal result, maybe just not the most recommended one by MS.

Sorry if you already know this, but the instructions aren't just repeatable, or not in all cases.

What do you have under C:\Windows\System32\Recovery? This is where Windows stores the recovery partition or C:\Recovery folder when WinRE is disabled. If you don't do correctly the sequences WinRE-disable -> operations ->WinRE enable, or if an error happens, you'll lose the recovery partition contents, although you can recover it from the installing media with 7zip among other more difficult methods. I wouldn't do takeown etc of any involved partition, install a (free if you want) partitions tool and use its explore partition option.

- - - Updated - - -

PS: in diskpart, I would never do list volume or anything with "vol" or "volumes", only "disk" and "part" or "partition". I think not even the world's best professional croupier would do a more random list of partitions than what diskpart's "volumes" can do.

Dropbox - KB5034441-debug - Simplify your life

Please run > post share links


a) Tuneup plus:

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging

Batch files for use in BSOD debugging



b) Diskpar info:

https://www.tenforums.com/attachment...iskparinfo.bat

Batch files for use in BSOD debugging

Code:

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Disabled
    Windows RE location:       
    Boot Configuration Data (BCD) identifier: a241eced-8323-11ee-8808-f489d3181879
    Recovery image location:   
    Recovery image index:      0
    Custom image location:     
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

Code:

UniqueId             : {00000000-0000-0000-0000-60b0e8000000}ATA     WDC WD10EZEX-60WN4A2                         WD-WCC6Y5DX296U
AccessPaths          : {\\?\Volume{7fe07e32-0000-0000-0000-60b0e8000000}\}
DiskNumber           : 0
DiskPath             : \\?\scsi#disk&ven_wdc_wd10&prod_ezex-60wn4a2#4&3b9922aa&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
DriveLetter          :  
Guid                 : 
IsActive             : False
IsBoot               : False
IsHidden             : False
IsOffline            : False
IsReadOnly           : False
IsShadowCopy         : False
IsDAX                : False
IsSystem             : False
NoDefaultDriveLetter : True
Offset               : 999391494144
OperationalStatus    : Online
PartitionNumber      : 3
Size                 : 774 MB
Type                 : Unknown

1) Please make free or pay backup images

(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

Backup and Restore with Macrium Reflect



2) Reinstall the BIOS:

https://www.dell.com/support/home/en...ctcode=xps-630



3) Run the Dell full diagnostics:
https://www.dell.com/support/home/en...s-630/diagnose



4) Run Memtest86+ for 8 or more passes > take pictures > post images or share links

MemTest86+ - Test RAM

Memtest86+ | The Open-Source Memory Testing Tool

Code:

Event[954]:
  Log Name: System
  Source: Microsoft-Windows-HAL
  Date: 2024-02-20T16:03:46.5820000Z
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CV81LQ0
  Description: 
The platform firmware has corrupted memory across the previous system power transition.  
Please check for updated firmware for your system.

Code:

Event[1338]:
  Log Name: System
  Source: Microsoft-Windows-HAL
  Date: 2024-02-27T19:50:49.2490000Z
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CV81LQ0
  Description: 
The platform firmware has corrupted memory across the previous system power transition.  
Please check for updated firmware for your system.

Code:

Event[1625]:
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2024-02-28T11:59:05.2730000Z
  Event ID: 43
  Task: Windows Update Agent
  Level: Information
  Opcode: Installation
  Keyword: Installation,Started
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-CV81LQ0
  Description: 
Installation Started: Windows has started installing the following update: 
2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)

Event[1626]:
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2024-02-28T11:59:08.0950000Z
  Event ID: 20
  Task: Windows Update Agent
  Level: Error
  Opcode: Installation
  Keyword: Installation,Failure
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-CV81LQ0
  Description: 
Installation Failure: Windows failed to install the following update with error 0x8024200B: 
2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

Code:

Event[1136]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2024-02-22T15:34:49.1670000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-CV81LQ0
  Description: 
The system has rebooted without cleanly shutting down first. 
This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[1111]:
  Log Name: System
  Source: EventLog
  Date: 2024-02-22T15:35:06.3280000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CV81LQ0
  Description: 
The previous system shutdown at 9:01:42 AM on ?2/?22/?2024 was unexpected.

Code:

Event[781]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2024-02-19T18:11:39.8410000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-CV81LQ0
  Description: 
The system has rebooted without cleanly shutting down first. 
This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[764]:
  Log Name: System
  Source: EventLog
  Date: 2024-02-19T18:12:01.2050000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CV81LQ0
  Description: 
The previous system shutdown at 9:48:18 AM on ?2/?19/?2024 was unexpected.

Code:

Event[27]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2024-02-18T18:50:21.9390000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-CV81LQ0
  Description: 
The system has rebooted without cleanly shutting down first. 
This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[0]:
  Log Name: System
  Source: EventLog
  Date: 2024-02-18T18:51:01.8950000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CV81LQ0
  Description: 
The previous system shutdown at 7:15:44 PM on ?12/?9/?2023 was unexpected.

Code:

Event[1297]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2024-02-27T18:27:28.8940000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2393789657-1619576622-184760312-1002
  User Name: DESKTOP-CV81LQ0\Z
  Computer: DESKTOP-CV81LQ0
  Description: 
Windows removed bad memory regions from this PC.

Very recently I replaced a bad motherboard. Most or all of those suspicious looking logs date from the time when I was rebooting over and over trying to fix the problem. I didn't realize there would be so many entries. Instead of using the shotgun approach to chase down all that suspicious stuff, it is far simpler and faster to reinstall windows now that my HW is working properly.

If I still have an issue after that, I can always repost.
Thanks

A clean install should fix the recovery partition.

Run Tuneup plus after the clean install > post a share link

Reinstall the BIOS as the entry was 02/27.

And run Memtest86+ > post images or share links.



After the above monitor the computer using reliability monitor for:
hangs
freezes
unexpected shutdowns and restarts


View Reliability History in Windows 11 Tutorial | Windows 11 Forum

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using



Clean Install Windows 10

And if you don't want to create the next rabbit hole, run the setup with the correct partition size for your recovery.

After the clean install I manually ran the sfc, chkdisk, memtests, hw diags, crystaldisk, with all clean results.

Later I saw the Tuneup plus script nicely bundles some of that, so next time I'll try it.

I did run the Diskpar script.

I did reflash the Bios just to be sure, but one thing I noticed with the V2_log_collector is that it is not
showing the Bios information correctly in motherboard.txt. You can compare with msinfo32 to see that.
Other tools agree with msinfo32.

Dropbox - KB5034441-debug - Simplify your life

I did not use a newer installer or modify the partitions so the KB5034441 isn't going to install. As long as it does not block other updates I'll just wait on MS.