KB5046400: Windows Recovery Environment update for Windows 10, version
21H2 and 22H2: October 8, 2024
KB5044615: Safe OS Dynamic Update for Windows 10, version 21H2 and 22H2: October 8, 2024
Requirements:
Sufficient WinRE partition space (minimum 250 MB free space)
WinRE version number less than 10.0.19041.5000
KB5031539 or later SSU installed to apply this update
Check WinRE Version number:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
-> WinREVersion
i.e.
only offered...
if WinRE version is less than 10.0.19041.5000
if device has an active WinRE partition
Detailed Info reference: <https://support.microsoft.com/en-us/topic/kb5046400-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-october-8-2024-62ea1496-d349-4dfb-b326-28dd7b9f99b9>
<https://support.microsoft.com/en-us/topic/kb5044615-safe-os-dynamic-update-for-windows-10-version-21h2-and-22h2-october-8-2024-22adef4f-207c-4b57-9bf4-44fb126a3bca>
VanguardLH wrote:following should have been installed:
"...winston" <winstonmvp@gmail.com> wrote:
KB5046400: Windows Recovery Environment update for Windows 10, version
21H2 and 22H2: October 8, 2024
KB5044615: Safe OS Dynamic Update for Windows 10, version 21H2 and 22H2: >>> October 8, 2024
Requirements:
Sufficient WinRE partition space (minimum 250 MB free space)
WinRE version number less than 10.0.19041.5000
KB5031539 or later SSU installed to apply this update
Check WinRE Version number:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
-> WinREVersion
i.e.
only offered...
if WinRE version is less than 10.0.19041.5000
if device has an active WinRE partition
Detailed Info reference:
<https://support.microsoft.com/en-us/topic/kb5046400-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-october-8-2024-62ea1496-d349-4dfb-b326-28dd7b9f99b9>
<https://support.microsoft.com/en-us/topic/kb5044615-safe-os-dynamic-update-for-windows-10-version-21h2-and-22h2-october-8-2024-22adef4f-207c-4b57-9bf4-44fb126a3bca>
Wonder which rescue method is better. Both are possible, but seems only
one is really needed.
I'm more inclined to not venture into debating which is better.
Imo, having multiple 3rd party tools(like backup images using different imaging apps(Acronis, Macrium), latest o/s bootable media(USB), ISO file, and Windows built-in system recovery and tools is a better approach.
i.e. forget about what's better - just have what's available at your disposal.
Fyi...
If one is running Windows 10 22H2 and met the requirements(sufficient WinRE partition free disk space, active recovery WinRE partition(preferably located after the Windows partition)...and updated Windows 10 22H2 with the Oct 8 2024 updates, the
KB5044273 LCU/SSU 19045.5011
KB5044615: Safe OS Dynamic Update
KB5046400: Windows Recovery Environment
Powershell commands should show the results
Get-Volume
- WinRE partition size and free space
Reagentc /info
- WinRE location \\?\GLOBALROOT\device\harddisk#\partition#\Recovery\WindowsRE\winre.wim /index:1
=> where # in the location output will be your specific hardisk and partition #
=> Then use that full path in the DISM /Get-ImageInfo /ImageFile: command to see the WinRE Service Pack Build number and modified date
e.g.
DISM /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1
The DISM command for 22H2 should show Service Pack Build 5000 and a modified date on the same or relative near date when the above 3 KB's were installed. Update History should show the KB's for LCU/SSU and WinRE.
Note: You probably will not see the Safe OS KB in Update History or Installed Updates, but one can read KB5044615 for additional info on files version numbers that were installed.
Likewise, similar updating in October 2024 occurs on Windows 11(LCU/SSU, SafeOS, WinRE).
On Thu, 10/10/2024 12:14 AM, ...winston wrote:following should have been installed:
VanguardLH wrote:
"...winston" <winstonmvp@gmail.com> wrote:
KB5046400: Windows Recovery Environment update for Windows 10, version >>>> 21H2 and 22H2: October 8, 2024
KB5044615: Safe OS Dynamic Update for Windows 10, version 21H2 and 22H2: >>>> October 8, 2024
Requirements:
Sufficient WinRE partition space (minimum 250 MB free space)
WinRE version number less than 10.0.19041.5000
KB5031539 or later SSU installed to apply this update
Check WinRE Version number:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
-> WinREVersion
i.e.
only offered...
if WinRE version is less than 10.0.19041.5000
if device has an active WinRE partition
Detailed Info reference:
<https://support.microsoft.com/en-us/topic/kb5046400-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-october-8-2024-62ea1496-d349-4dfb-b326-28dd7b9f99b9>
<https://support.microsoft.com/en-us/topic/kb5044615-safe-os-dynamic-update-for-windows-10-version-21h2-and-22h2-october-8-2024-22adef4f-207c-4b57-9bf4-44fb126a3bca>
Wonder which rescue method is better. Both are possible, but seems only >>> one is really needed.
I'm more inclined to not venture into debating which is better.
Imo, having multiple 3rd party tools(like backup images using different imaging apps(Acronis, Macrium), latest o/s bootable media(USB), ISO file, and Windows built-in system recovery and tools is a better approach.
i.e. forget about what's better - just have what's available at your disposal.
Fyi...
If one is running Windows 10 22H2 and met the requirements(sufficient WinRE partition free disk space, active recovery WinRE partition(preferably located after the Windows partition)...and updated Windows 10 22H2 with the Oct 8 2024 updates, the
KB5044273 LCU/SSU 19045.5011
KB5044615: Safe OS Dynamic Update
KB5046400: Windows Recovery Environment
Powershell commands should show the results
Get-Volume
- WinRE partition size and free space
Reagentc /info
- WinRE location \\?\GLOBALROOT\device\harddisk#\partition#\Recovery\WindowsRE\winre.wim /index:1
=> where # in the location output will be your specific hardisk and partition #
=> Then use that full path in the DISM /Get-ImageInfo /ImageFile: command to see the WinRE Service Pack Build number and modified date
e.g.
DISM /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1
The DISM command for 22H2 should show Service Pack Build 5000 and a modified date on the same or relative near date when the above 3 KB's were installed. Update History should show the KB's for LCU/SSU and WinRE.
Note: You probably will not see the Safe OS KB in Update History or Installed Updates, but one can read KB5044615 for additional info on files version numbers that were installed.
Likewise, similar updating in October 2024 occurs on Windows 11(LCU/SSU, SafeOS, WinRE).
KB5046400
2GB partition defined (TestMachine 4930K, W10 2x4 disks, for later tracking)
0x80070643 "Download Error"
:-)
What is interesting, is the file in Scratch has exactly the same
SHA1SUM value as the one in the 2GB partition. After I took a hash
of the file in Scratch, it was removed.
Name: update.wim Thursday, October 10, 2024, 11:27:21 AM
Size: 481405782 bytes (459 MiB)
SHA1: 60ECEC41C19005991D06F964176B01850C977D5A
Name: winre.wim Monday, September 2, 2024, 11:29:46 AM
Size: 481405782 bytes (459 MiB)
SHA1: 60ECEC41C19005991D06F964176B01850C977D5A
The Registry key is missing, which is likely why the update tried to run.
No, I did not remove it.
If one is running Windows 10 22H2 and met the requirements(sufficient WinRE partition free disk space, active recovery WinRE
partition(preferably located after the Windows partition)...and updated Windows 10 22H2 with the Oct 8 2024 updates, the following should have
been installed:
KB5044273 LCU/SSU 19045.5011
KB5044615: Safe OS Dynamic Update
KB5046400: Windows Recovery Environment
Powershell commands should show the results
Get-Volume
- WinRE partition size and free space
Reagentc /info
- WinRE location \\?\GLOBALROOT\device\harddisk#\partition#\Recovery\WindowsRE\winre.wim /index:1
=> where # in the location output will be your specific hardisk and partition #
=> Then use that full path in the DISM /Get-ImageInfo /ImageFile:
command to see the WinRE Service Pack Build number and modified date
e.g.
DISM /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1
The DISM command for 22H2 should show Service Pack Build 5000 and a
modified date on the same or relative near date when the above 3 KB's
were installed. Update History should show the KB's for LCU/SSU and WinRE. Note: You probably will not see the Safe OS KB in Update History or
Installed Updates, but one can read KB5044615 for additional info on
files version numbers that were installed.
Paul wrote:following should have been installed:
On Thu, 10/10/2024 12:16 PM, Paul wrote:
On Thu, 10/10/2024 12:14 AM, ...winston wrote:
VanguardLH wrote:
"...winston" <winstonmvp@gmail.com> wrote:
KB5046400: Windows Recovery Environment update for Windows 10, version >>>>>> 21H2 and 22H2: October 8, 2024
KB5044615: Safe OS Dynamic Update for Windows 10, version 21H2 and 22H2: >>>>>> October 8, 2024
Requirements:
Sufficient WinRE partition space (minimum 250 MB free space) >>>>>> WinRE version number less than 10.0.19041.5000
KB5031539 or later SSU installed to apply this update
Check WinRE Version number:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
-> WinREVersion
i.e.
only offered...
if WinRE version is less than 10.0.19041.5000
if device has an active WinRE partition
Detailed Info reference:
<https://support.microsoft.com/en-us/topic/kb5046400-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-october-8-2024-62ea1496-d349-4dfb-b326-28dd7b9f99b9>
<https://support.microsoft.com/en-us/topic/kb5044615-safe-os-dynamic-update-for-windows-10-version-21h2-and-22h2-october-8-2024-22adef4f-207c-4b57-9bf4-44fb126a3bca>
Wonder which rescue method is better. Both are possible, but seems only >>>>> one is really needed.
I'm more inclined to not venture into debating which is better.
Imo, having multiple 3rd party tools(like backup images using different imaging apps(Acronis, Macrium), latest o/s bootable media(USB), ISO file, and Windows built-in system recovery and tools is a better approach.
i.e. forget about what's better - just have what's available at your disposal.
Fyi...
If one is running Windows 10 22H2 and met the requirements(sufficient WinRE partition free disk space, active recovery WinRE partition(preferably located after the Windows partition)...and updated Windows 10 22H2 with the Oct 8 2024 updates, the
being present using the Powershell DISM route I noted in my earlier reply to VanguardLH.KB5044273 LCU/SSU 19045.5011
KB5044615: Safe OS Dynamic Update
KB5046400: Windows Recovery Environment
Powershell commands should show the results
Get-Volume
- WinRE partition size and free space
Reagentc /info
- WinRE location \\?\GLOBALROOT\device\harddisk#\partition#\Recovery\WindowsRE\winre.wim /index:1
=> where # in the location output will be your specific hardisk and partition #
=> Then use that full path in the DISM /Get-ImageInfo /ImageFile: command to see the WinRE Service Pack Build number and modified date
e.g.
DISM /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1
The DISM command for 22H2 should show Service Pack Build 5000 and a modified date on the same or relative near date when the above 3 KB's were installed. Update History should show the KB's for LCU/SSU and WinRE.
Note: You probably will not see the Safe OS KB in Update History or Installed Updates, but one can read KB5044615 for additional info on files version numbers that were installed.
Likewise, similar updating in October 2024 occurs on Windows 11(LCU/SSU, SafeOS, WinRE).
KB5046400
2GB partition defined (TestMachine 4930K, W10 2x4 disks, for later tracking)
0x80070643 "Download Error"
:-)
What is interesting, is the file in Scratch has exactly the same
SHA1SUM value as the one in the 2GB partition. After I took a hash
of the file in Scratch, it was removed.
Name: update.wim Thursday, October 10, 2024, 11:27:21 AM
Size: 481405782 bytes (459 MiB)
SHA1: 60ECEC41C19005991D06F964176B01850C977D5A
Name: winre.wim Monday, September 2, 2024, 11:29:46 AM
Size: 481405782 bytes (459 MiB)
SHA1: 60ECEC41C19005991D06F964176B01850C977D5A
The Registry key is missing, which is likely why the update tried to run. >>> No, I did not remove it.
A second install, went more normally. Registry
value was present, and ended in 3920, update applied
and now it reads 5000. That's the AMD machine and
disk 30A.
Paul
First, backing up a bit to your earlier post.
If the device(test machine) os was previously updated with either of the two earlier WinRE updates(way back in July 2023 and Dec 2023(or Jan 2024) then the reg key would be present.
If the device(test machine) was recent install(disk or vm) then the reg key would not be present but would not be a reason why the update tried to run(the Service Pack Build number, modified date, etc. can be found in the image with/without the reg key
:) It never crossed my mind or even considered that you would remove that reg key.probably before or after or coincidental with Win11 23H2 Oct. 224 LCU/SSU.
I'm more inclined to think the initial failure(since KB5046400) is only offered via Windows Update(not stand-alone Catalog option) was due to other reasons.
Similarly, with respect to that same reg key...it's not always present on Win11 even after the having applied those earlier(Jan.'24, Oct.'23, June '23, ) Win RE Updates. The Oct. 2024 WinRE update(and SafeOS) will still be applied in Win11 23H2 and
- For Win11 23H2 KB5044617 indicates the latest(Oct 2024) WinRE version(10.0.22621.4305).
Paul wrote:updates(20H2, 21H1, 21H2, 22H2)
Since the partition was 2GB, the right flavor, and so on,it installed. The registry setting, I missed it, but it *was*
there, and it was 3920, now it is 5000.
My head is in the barrel, but I still didn't nab an apple.
Paul
For Windows the barrel is more likely full of pickles.
Here's one for you to ponder about the Oct.2024 Win10 WinRE update
Background"
Much older device
Surface 3, Win10 Pro 64 Bit, Atom chip, 8 GB RAM, 128 GB SSD(60 GB free space), 128 GB SDXC(90 GB free space), WinRE partition(1 GB, 447 MB Free)
- Monthly LCU's and SSU always take up to 30-45 minutes to check for updates, download and install before the required restart, and another 5-10 minutes before logon screen followed by another minute or so to desktop.
- Feature updates since Win10 2004 always fail to install via Windows Update(no amount of troubleshooting - Windows Update, DiskCleanup, DISM Health or Component store, rename Software Distrib. etc. fixes WU inability to install the last 4 feature
What does work and only works for feature updates is the ISO with the *.wim image) when running setup.exe after copying the mounted ISO's files to new folder on the root of C: drive.Features Installed Updates.
This month took an unusual route to install all Oct 2024 updates.
Windows Update installed LCU/SSU without issue. Not installed - .NET cumulative, WinRE
WU update successfully installed Win10: (took about 30 min)
- KB 5001716(Windows Update Service Components)
- KB 5044273 (LCU/SSU 19045.5011)
WU did not install:
- KB 5044091 (.NET 3.5, 4.8, 4.8.1 Cumulative)
- KB 5046400 (WinRE Service Pack Build 5000)
Rerunning Windows Update 2x(twice)failed to install .NET and WinRE updates and notified with the same error code.
- 0x899705b4 => usually indicates timeout issue
No change after the usual troubleshooting(Windows Update, DiskCleanup, DISM, Sfc, rename Software Distribution) and rerunning WU(same error code).
Was going to sit on it/comeback later, then noticed in Update History that no .NET 3.5/4.8/4.8.1 updates had been installed since July 2024.
Went to the Microsoft Catalog for Oct 2024 .NET's KB5044091 which was two separate downloadable KB's 5044020 and 5044029)
- Downloaded both and installed both successfully, restarted
Reran Windows Update => KB 5044091 (WinRE) offered, successfully installed and updated to WinRE Service Pack Build 5000 - Free space on WinRE partition dropped by 16 MB(431 MB free space)
Sometimes the barrel is full of briny pickle juice.
Go figure - only partially convinced that .NET was the root cause, but it worked.
- and after WinRE was updated, uninstalled those 2 standalone .Net KB's(4020, 4029) then reran Windows Update and was offered KB 5044091 .NET Oct 2024 update, installed fine(shows up as its KB# in Update History and only as KB5044029 in Programs&
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 361 |
Nodes: | 16 (2 / 14) |
Uptime: | 123:27:35 |
Calls: | 7,716 |
Files: | 12,861 |
Messages: | 5,727,955 |