MS-DEFCON 4: 24H2 is a work in progress

Topic

New Reply

ISSUE 21.43.1 • 2024-10-22 By Susan Bradley Every month, I look back at the issues and oddities I’ve been tracking to see whether they are merely corn
[See the full post at: MS-DEFCON 4: 24H2 is a work in progress]

Susan Bradley Patch Lady/Prudent patcher

14 users thanked author for this post.

CADesertRat, KWGuy, JCpharm, jburk07, Alex5723, windbg, deuce120, M. N., DLivesInTexas, Mark, wosully, Kathy Stevens, SelfMan, lmacri

Reply | Quote

Replies

There’s a typo confusing photo app with phone app. Not a biggie but likely worth the edit.

How is “Classic Outlook” defined?

Reply | Quote

Microsoft is renaming the MS Office bundled Outlook shortcuts to “Outlook (Classic)” to push the “Outlook (new)” forward. I personally don’t like it.

1 user thanked author for this post.

Bookman

Reply | Quote

from the Newsletter: “I have not recommended iOS 18 on my Master Patch List because of the many complaints about the changes to the phone app.”

rebop2020 wrote:

There’s a typo confusing photo app with phone app. Not a biggie but likely worth the edit.

One of the phone apps is called Photo, hence “the phone app” refers, in particular, to the Photo app, if you read further.

Reply | Quote

The typo has been corrected.

1 user thanked author for this post.

WCHS

Reply | Quote

FYI – Since the September update, there is a problem uring the:
Remove-AppxPackage -allusers -Package <PackageFullName>
command, because the service host crashes with:
P1: svchost.exe_AppXSvc
P2: 10.0.19041.4355
P3: 9ce47784
P4: appxdeploymentserver.dll
P5: 10.0.19041.5007
P6: 738541ef
P7: c0000005
P8: 00000000002f7d39
P9:
P10:

The workaround is to disable the update using a override (needs reboot):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides]
“595276428”=dword:00000000

As seen on reddit, this is also causing issues in the Azure Virtual Desktop

This is important if you want to remove the AdobeAcrobatReaderCoreApp or AdobeAcrobatReaderDCCoreApp as many Security solutions (MDR) are marking it as Vulnerable.

Reply | Quote

SelfMan wrote:

FYI – Since the September update, there is a problem uring the: Remove-AppxPackage -allusers -Package command, because the service host crashes

Hi SelfMan:

Please clarify. Do you mean that all PowerShell v5.1.19041.5007 Remove-AppxPackage commands will fail for any UWP (Microsoft Store) and/or built-in Windows app (which your post # 2711915 seems to suggest), or just for certain third-party apps like AdobeAcrobatReaderCoreApp?

What is you Windows OS, and what is the URL for the reddit topic you mentioned in your post # 2711915.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.1.11.139-1.0.5072 * Macrium Reflect Free v8.0.7783

Reply | Quote

So far I’ve seen, anytime you use the -AllUsers switch with command that change things, it crashes.

Get-Appx* commands are working fine.

The related info

https://techcommunity.microsoft.com/t5/azure-virtual-desktop/azure-virtual-desktop-black-screens-on-logins-what-we-ve-tried/m-p/4250228

1 user thanked author for this post.

lmacri

Reply | Quote

Some of the commands I’ve seen online have the “-AllUsers” argument in the command twice, once close to the start and a second one at the end. I have found that if I remove the one at the end, the command works.

Without the “-AllUsers” the app is removed for the current User.
With the “-AllUsers” it is removed for the template that creates All Users on the computer.
There is also a command that will deprovision the App, so it is not reinstalled.

Reply | Quote

It’s because you’ve seen them “piped” like:
Get-AppxPackage -AllUsers AdobeAcrobatReaderCoreApp | Remove-AppxPackage -allusers

That means the result is passed to the next command that handles it.

The point of the AllUsers switch is that you as an administrator can remove the Windows App that is installed per user for all users at once. And this mechanism is now broken.

Reply | Quote

Since the September update every time my Win1022H2 system starts the AppXSvc service crashes twice and restarts automaticlly.  The event log records this–

Faulting application name: svchost.exe_AppXSvc, version: 10.0.19041.4355, time stamp: 0x9ce47784
Faulting module name: appxdeploymentserver.dll, version: 10.0.19041.5007, time stamp: 0x738541ef
Exception code: 0xc0000005
Fault offset: 0x00000000002f7d39
Faulting process id: 0x1cd4
Faulting application start time: 0x01db277d563631df
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: c:\windows\system32\appxdeploymentserver.dll
Report Id: 0dff28a0-17d5-4ad6-b151-a65d85c6198a
Faulting package full name:
Faulting package-relative application ID:

Reply | Quote

Probably because some installer is trying to remove an old version of the App and the AppX handling stuff is broken.
See the registry workaround. After creating the entry, you have to restart. Remember that this disables the applied patches, so restart twice so the installer can finish it’s job, then remove the registry entry and restart again. The crashing of svchost.exe_AppXSvc should be gone. At least until a new update wants to install.

Reply | Quote

@SelfMan, Windows does install updates to store apps AFTER the AppX Deployment service crash/restart events.  So the problem doesn’t seem to prevent updates from installing.

You wrote “The crashing of svchost.exe_AppXSvc should be gone. At least until a new update wants to install.”  If that’s the case I don’t see any reason to tweak the registry since this will be a recurring issue.

I read the thread from the techcommunity link that you posted.  Although the thread indicated that MS solved the AppXSvc problem with the October updates that doesn’t seem to be the case.  Maybe they only fixed the problem for Azure virtual desktops.  If it was fully remediated, I wouldn’t still be seeing the crash/restart events in the log.

 

Reply | Quote

It is certainly not fixed in Windows 10. I’ve seen this issue on several completely different devices. The issue is not with the installation but with the removal.

Reply | Quote

I’ve seen posts in the Autodesk forums about KB5043178 screwing up Autodesk Revit.

Reply | Quote

Updated and rebooted like normal, once I tried to log in to the desktop it pulled up a white screen asking me to either set up backup (I use onedrive) or remind me in 3 days. The usb mouse I usually use WOULD NOT work on that screen, ended up having to do a hard shutdown via the power button. It rebooted and so far seems to be working fine.

1 user thanked author for this post.

MrToad28

Reply | Quote

Question: Is it possible to apply updates without taking 24H2? We are getting really backed up, having not yet applying even September updates, or am I just confused?

Thanks.

BTW, I got your text at 3:45AM. What is up with that?

Reply | Quote

24h2 is a revamped version of windows 11 with many changes.

23H2 is still supported. You don’t “need” to upgrade to 24h2 yet.

Reply | Quote

Richard Mitnick wrote:

Is it possible to apply updates without taking 24H2?

Hi Richard Mitnick:

Yes, you can also set your Target Release Version (TRV) to any Windows operating system and version (e.g., Windows 11 / 23H2) to manage the timing of OS upgrades and/or version updates for your Windows OS, and Windows Update will continue to offer available security updates for your target OS to keep your system patched.

If you have a Professional edition of Windows 10 or 11 you can use the Local Group Policy Editor (Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select the Target Feature Update Version) to set your Target Release Version (TRV). For example, I have a Win 10 Pro v22H2 OS and currently have my TRV set to Windows 10 / 22H2 to prevent an unexpected upgrade to Win 11.  If you’re currently on Windows 11 v23H2 you can set your TRV to Windows 11 / 23H2 to delay the update to Win 11 v24H2. See Brink’s TenForums tutorial <here> for Win 10 Pro and ElevenForums tutorial <here> for Win 11 Pro.

If you have a Home (or Professional) edition of Windows 10 or 11 you can use GRC’s InControl tool to set your TRV and manage the timing of OS upgrades and/or version updates for your Windows OS.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

Reply | Quote

More bugs have been found in 24H2. This is why Microsoft is slowly rolling out to PCs in stages and not to everyone at once.  They may blocked some PCs with certain hardware until the bug is fixed.

This is why it is best to wait until it offered in Windows Updae.  24H2 doesn’t have any ground breaking features you need to use right away

Reply | Quote

Is it fair to assume that Windows 10 Pro 22H2 “Consumer” is good to go for updating?

Reply | Quote

DEFCON is at 4. Check Master Patch List for individual update status.

Reply | Quote

Re: News and Interests.

the MS thread indicates that this is a Edge update issue.  Is there an Edge update that I can uninstall to get rid of the the News and Interests?

I have a note to myself to not update Edge any more.  I never use it, and it seems to mostly be a way to enable MS intrusion.

Reply | Quote

You might be interested in #2711510. Also some of the discussion about News and Interest in the posts above it.

1 user thanked author for this post.

Perq

Reply | Quote

astro46: I have the same attitude about Edge as you. But I do update it occasionally because I fear that an out of date app could be compromised. Perhaps someone here can validate which is the correct choice to make???

Windows 10 Home. HP 12GB RAM 256GB SSD 4year old desktop.

Reply | Quote

Sad to say, not updating Edge did not keep “news and interests” from appearing.   Since writing the past post I updated another computer, win10, did not update Edge, and still have the pointless app appearing .   Shows no memory being used, hibernated.

Reply | Quote

See 2711510

Reply | Quote

Susan: You say “If you are a fan of POP mail, I strongly recommend that you start investigating alternative email platforms, such as Thunderbird”. Would you or someone else explain this more fully? Is IMAP safer than POP?

Windows 10 Home. HP 12GB RAM 256GB SSD 4year old desktop.

1 user thanked author for this post.

b

Reply | Quote

IMAP leaves a copy of a message on the server until deleted locally. POP3 deletes from the server automatically when downloaded to the local client. I use both for different accounts and different reasons.

2 users thanked author for this post.

teuhasn2, Bookman

Reply | Quote

rebop2020: Do you have any idea what Susan’s rationale is for “finding an alternate email provider”?

Windows 10 Home. HP 12GB RAM 256GB SSD 4year old desktop.

Reply | Quote

Not an alternate email provider.
An alternate email platform (App) such as Thunderbird, a third-party email program,

2 users thanked author for this post.

teuhasn2, Bookman

Reply | Quote

But why?

Reply | Quote

Bookman wrote:

rebop2020: Do you have any idea what Susan’s rationale is for “finding an alternate email provider”?

Because @Bookman confused email provider (ISP) with email platform (program/Thunderbird).

Reply | Quote

rebop2020 wrote:

POP3 deletes from the server automatically when downloaded to the local client.

I’m using Outlook (Microsoft 365) with all POP3 accounts.  The deletion from the server can be controlled in settings.  My POP3 accounts don’t delete the mail on the server unless I delete it on my end.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

PL1

Reply | Quote

IMAP is better because it’s, more or less, an exact replica of your mailbox but in a different application. Any changes you make are synced back to the host mailbox, including which emails are read, sent items, and emails moved to different folders.

From a security standpoint, I don’t know if it’s any “safer”, as long as the server is using a secure connection (TLS).

2 users thanked author for this post.

teuhasn2, Bookman

Reply | Quote

I would not call it better. It is different.

Sure the messages remain on the server so you can find them on any devices set to IMAP to see, retrieve, send etc.  But on one account where I want to store my emails ONLY locally, I have POP3. I have that same email account set to IMAP on my phone so I can view and delete there, but then when I “pop” from my home computer, it downloads all remaining and deletes them on the server.

There IS a place for both.

Most people use IMAP and store on the server. I prefer to store locally in literally hundreds of folders for accounts like credit cards, auto insurance, friends, family, on and on. Personal preference. It appear Outlook is going to discontiniue POP3 as they know what’s best for us 🙂

3 users thanked author for this post.

Cybertooth, GeeBeeDee, PL1

Reply | Quote

rebop2020 wrote:

POP3 deletes from the server automatically when downloaded to the local client.

That is OPTIONAL. The way I have POP setup is, I have multiple devices that leave the email on the server and only ONE that deletes it from the server after it downloads.

 

1 user thanked author for this post.

SkipH

Reply | Quote

KS wrote:

IMAP is better because it’s, more or less, an exact replica of your mailbox but in a different application. Any changes you make are synced back to the host mailbox, including which emails are read, sent items, and emails moved to different folders.

That all depends, better if you don’t mind someone holding on to your emails and having access to them. Personally, I like to delete them off the server entirely. (Not that they can’t be accessed before you delete them and not that they couldn’t be undeleted, but that is MY preference.)

I know of people that have their life long history on someone’s server with Imap. Mine, is stored on my computer, offline.

1 user thanked author for this post.

LH

Reply | Quote

Just updated and I wasn’t offered 24h2 yet. I’m on Windows 11 23h2.

1 user thanked author for this post.

MrToad28

Reply | Quote

Richard Mitnick wrote:

Question: Is it possible to apply updates without taking 24H2?

Use WUmgr to hide/block updates you don’t want.

Reply | Quote

Following the recommendation I installed the October updates for my Win 11 machine yesterday with no untoward behaviour apparent on restarting.  I now find that my update history has vanished from Xanatos’ Update Manager and Nirsoft’s Windows Update History Viewer.  The Command “wmic qfe list” gets just this:

https://support.microsoft.com/help/5012170 X Security Update KB5012170 NT AUTHORITY\SYSTEM 10/10/2023
https://support.microsoft.com/help/5027397 X Update KB5027397 NT AUTHORITY\SYSTEM 5/3/2024
https://support.microsoft.com/help/5044285 X Security Update KB5044285 NT AUTHORITY\SYSTEM 10/23/2024
X Security Update KB5043937 NT AUTHORITY\SYSTEM 9/24/2024
X Security Update KB5046247 NT AUTHORITY\SYSTEM 10/22/2024

(computer name obfuscated)

… which makes little sense.

What is going on?

(and where exactly is that information supposed to be stored?)

Reply | Quote

I tried the PowerShell approach from

https://www.minitool.com/news/how-to-check-update-history-on-windows-11.html :

++++

PS C:\Windows\system32> Install-Module PSWindowsUpdate

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘2.8.5.201’ or newer to interact with NuGet-based repositories. The NuGet provider must be available in ‘C:\Program Files (x86)\PackageManagement\ProviderAssemblies’ or
‘C:\Users\User\AppData\Local\PackageManagement\ProviderAssemblies’. You can also install the NuGet provider by running ‘Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force’. Do you want PowerShellGet to install and import
the NuGet provider now?
[Y] Yes [N] No Suspend [?] Help (default is “Y”): y

Untrusted repository
You are installing the modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure you want to install the modules from ‘PSGallery’?
[Y] Yes [A] Yes to All [N] No [L] No to All Suspend [?] Help (default is “N”):

+++

Is it trustable?    Even so, it is a surprise to be asked since NuGet is (apparently) already installed:  version 2.8.5.208.  (… ProviderAssemblies and … Roaming).  What to  do?

 

Reply | Quote

Another problem: SD card readers no longer work …  3 brands (2 examples of one), USB 3.0 and 2, no matter which port or hub is used.  Disk Management will not complete a scan until the device is unplugged.  Explorer does not work either.  USB sticks work properly.  All was fine previously.

Reply | Quote

Curiously, after another reboot all came good.

 

Reply | Quote

Ms Bradley,

your presentation about types of SSDs that will cause BSOD is confusing me – the code you suggest does not present any of the model numbers you have in the list just above.  – The response to the code  appears to be some text that is different .

Reply | Quote

It doesn’t list affected models if you don’t have one of those.

So if you don’t see a listed model your computer is not affected.

Reply | Quote

I didn’t have an impacted device to be an exact sample screenshot.  That was my machine which is not impacted.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

After applying the Oct 2024 patches to Win 10 Pro v22H2, when clicking a hyperlink in  an Outlook message (Outlook Microsoft 365 v.2402 build 17328.20612 Click-to-run on the semi-annual enterprise channel), get an error “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

Yet, the default browser opens behind the popup-error and loads the page in the hyperlink.

And fun times were had by all…

Casey

Reply | Quote

Frahaleah wrote:

The usb mouse I usually use WOULD NOT work on that screen, ended up having to do a hard shutdown via the power button.

In this situation, I’d suggest first to just unplug and re-plug the mouse first before you do the hard shutdown.  To date, it’s always worked for me.

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

No mention of KB5046400 in the master patch list, but Microsoft has presented it to several of my W10 22H2 computers a few days after the October updates were released. It appears to be another stab at the recovery partition based on Microsoft documentation that gives no clues to what it is trying to fix. I’ve blocked it for the time being, but does anyone know the point of this one? The previous KB5034441 installed successfully on two of the computers back in January. Apparently, that fix wasn’t enough?

Reply | Quote

ENShearin wrote:

No mention of KB5046400 in the master patch list…It appears to be another stab at the recovery partition based on Microsoft documentation that gives no clues to what it is trying to fix. I’ve blocked it for the time being, but does anyone know the point of this one? The previous KB5034441 installed successfully on two of the computers back in January.

Hi ENshearin:

The previous KB5034441 released in January 2024 (retired and re-released as KB5042320 in January 2024 so it would not be offered unless the WinRE partition had at least 250 MB of free disk space) updated the Win 10 WinRE build to Version 10.0.19041 / Build 3920.

This month’s KB5046400 will patch the Win 10 WinRE build to Version 10.0.19041 / Build 5000. There are multiple posts about KB5046400 in Susan Bradley’s 08-Oct-2024 October Updates Are Out.

It looks like the Master Patch List for the 10-Oct-2024 Patch Tuesday updates still incorrectly lists the re-released Jan 2024 KB5042320 (instead of the Oct 2024 KB5046400) as the latest replacement for KB5034441.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

ENShearin, WCHS

Reply | Quote

Imacri:  I am confused about the winre issue.   I have checked two win10 systems here.  Both have winreversion 10.0.19041.3920.  both show winre ‘enabled’

I updated one of them a few days ago, but it is not showing xxx.5000.  Disk Management shows three partitions, EFI system with 260 mb,  recovery partition with 849 mb, and recovery partition with 1000 mb.   All three are “100% free”.

Doesn’t this indicate that all 3 have no content? Or doesn’t disk manager recognize the content?   should I care that this system isn’t updated to xxx.5000.. ?   ( I  have full  monthly system images).

I haven’t updated the 2nd one yet.  Will get to it in a few days.

Reply | Quote

Disk Management doesn’t report the correct values for WinRe partitions.
Use a 3rd party tool like Partition Wizard Mini-Tool or Niubi Partition Editor.
Disk Mgmt:

Niubi Partition Editor:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

astro46 wrote:

I am confused about the winre issue. I have checked two win10 systems here. Both have winreversion 10.0.19041.3920. both show winre ‘enabled’ I updated one of them a few days ago, but it is not showing xxx.5000.

Hi astro46:

I can’t provide feedback about my own experience because my WinRE partition does not have 250 MB of free disk space, so Windows Update did not offer KB5046400 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: October 8, 2024). Do your Windows Update history (Settings | Update & Security | Windows Update | View Update History) and installed updates (Control Panel | Programs | Programs and Features | Installed Updates) both show that KB5046400 installed successfully with your other October 2024 Patch Tuesday updates?

To find details about your WinRE partition I’d suggest you run the following three commands from an elevated command prompt with Administrator rights. More information about these commands can be found at https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#check-the-winre-image-version.

IMPORTANT NOTE: The 1st command below shows my WinRE partition is located at harddisk0\partition4. If your WinRE partition is in a different location (e.g., harddisk1\partition3) you must edit the 2nd and 3rd commands below accordingly.

To find the location (path) of your WinRE partition:

reagentc /info

To find the total and free disk space of your WinRE partition:

fsutil volume diskfree \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

To find your WinRE version/build and date of installation:

Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1

I’ve attached output of these three commands for my own Win 10 v22H2 laptop, which show My WinRE partition:

• is located at harddisk0\partition4 (i.e., Partition 4 of my primary hard drive)
• has only 96.7 MB of free space
• is Version 10.0.19041 / ServicePack Build 3920 / ServicePack Level 0 and was installed (Last Modified) on 16-Jan-2024

———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CADesertRat

Reply | Quote

Here’s what I get. Thanks for the cmds. Any insight as to what all this means.

Microsoft Windows [Version 10.0.19045.5011]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 288dc357-60b3-11eb-a50f-e362183ee5b0
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>fsutil volume diskfree \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE
Total free bytes : 41,803,776 ( 39.9 MB)
Total bytes : 523,235,328 (499.0 MB)
Total quota free bytes : 41,803,776 ( 39.9 MB)

C:\WINDOWS\system32>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\winre.wim /index:1

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Details for image : \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (x64)
Description : Microsoft Windows Recovery Environment (x64)
Size : 2,155,325,460 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.19041
ServicePack Build : 1
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 3639
Files : 16323
Created : 12/6/2019 - 11:11:48 PM
Modified : 5/22/2021 - 6:24:55 PM
Languages :
en-US (Default)
The operation completed successfully.

C:\WINDOWS\system32>

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

CADesertRat wrote:

Version : 10.0.19041
ServicePack Build : 1
Modified : 5/22/2021 – 6:24:55 PM

Hi CADesertRat:

The output for your third command looks like it’s been truncated (i.e., I would have expected the image name to be something like \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\ winre.wim), but assuming you entered the command correctly your output shows your WinRE partition:

• Is located at harddisk1\partition1 (i.e., not harddisk 0),
• Only has 39.9 MB of free disk space, which implies you won’t be offered the KB5046400 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: October 8, 2024) update that would update your WinRE to Version 10.0.19041 / ServicePack Build 5000 since your partition has less than 250 MB of free disk space, and
• Hasn’t been updated since 22-May-2021 and is currently at Version 10.0.19041 / ServicePack Build 1 (Note: the Windows 10 version 21H1 Feature Update began rolling out on 18-May-2021, which might be relevant).

Did you install a second hard drive in your computer and move your WinRE partition to this drive, or is your Win 10 v22H2 OS also installed on harddisk1? Also, if you browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion in your Windows registry does it show your WindowsREVersion is 10.0.19041.1 (i.e., Version 10.0.19041 / ServicePack Build 1)? From my Win 10 v22H2 registry, which confirms my WinRE is currently Version 10.0.19041 / Build 3920 (installed 16-Jan-2024 by the WinRE KB5034441 update discussed in Susan Bradley’s Jan 2024 KB5034441 has led us astray, in a horrible way):

NOTE: Prior to January 2024 when KB5034441 installed ServicePack Build 3920, my previous WinRE update was ServicePack Build 3562 (installed 12-Oct-2023 as shown in the last image attached to my 16-Jan-2024 post # 2628138).
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v132.0.2 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.1.144-1.0.5088 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CADesertRat

Reply | Quote

lmacri wrote:

The output for your third command looks like it’s been truncated

Fixed that! 🙂

1 user thanked author for this post.

lmacri

Reply | Quote

lmacri wrote:

Did you install a second hard drive in your computer and move your WinRE partition to this drive, or is your Win 10 v22H2 OS also installed on harddisk1? Also, if you browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion in your Windows registry does it show your WindowsREVersion is 10.0.19041.1 (i.e., Version 10.0.19041 / ServicePack Build 1)? From my Win 10 v22H2 registry, which confirms my WinRE is currently Version 10.0.19041 / Build 3920 (installed 16-Jan-2024 by the WinRE KB5034441 update discussed in Susan Bradley’s Jan 2024 KB5034441 has led us astray, in a horrible way):

Drive 0 is a storage drive 😀 ( an HDD ), Drive 1 is OS Drive :C ( an NVME ) The drive selection for OS was chosen by windows on original installation. Haven’t checked the registry yet but will look tomorrow. I copied and pasted the cmds you listed into a text file and changed drive numbers as you directed and they looked the same as what you had listed, then copied and pasted into admin cmd window one at a time.

Sorry, should have used screenshots instead of copy/past of cmd window. Evidently the pasted cmd  info got truncated here.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

CADesertRat wrote:

Drive 0 is a storage drive 😀 ( an HDD ), Drive 1 is OS Drive :C ( an NVME ) The drive selection for OS was chosen by windows on original installation. Haven’t checked the registry yet but will look tomorrow.

Hi CADesertRat:

That sounds like the hybrid (dual-storage) hard drive system (a small-capacity/fast SSD for the OS plus a large-capacity/slower HDD for data) that used to be popular when I was shopping for a new Win 10 laptop in 2019, back when larger SSD drives were much more expensive than they are today. What is the total capacity of your SSD (harddisk1) and how much free disk space does it still have?

After you’ve checked your registry and confirmed your current WinRE ServicePack Build is out-of-date, if you want to install this month’s KB5048239 WinRE update for Win 10 v22H2 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: November 12, 2024) that bumps the ServicePack Build to 5025 or 5125 I’m guessing you’re going to have to use a third-party utility like MiniTool Partition Wizard Free to do two things:

1. Move your WinRE partition to the end (far left) of your SSD harddisk1 (assuming your current WinRE partition at harddisk1\partition1 isn’t already the last partition – see Alex5723’s 22-Jan-2024 post # 2629779 in Susan Bradly’s KB5034441 has led us astray, in a horrible way).
2. Increase the amount of free disk space on your relocated WinRE partition by at least 300 MB (and preferably 500 MB or more to accommodate future WinRE updates), assuming your SSD currently has enough free disk space to do this.

I do not plan to increase the size of my WinRE partition just to patch my WinRE version beyond ServicePack Build 3920 unless I hear that one of these updates patches a critical security vulnerability that is being exploited in the wild, so if this is something you want to try I’d suggest you create a full disk image of your entire SSD drive first in case something goes wrong and you have to perform an emergency recovery, and then create a new topic in this forum asking for assistance on how to do this safely from someone with more expertise managing disk partitions than I have. If you have a Professional edition of Win 10 and BitLocker disk encryption (Control Panel | System and Security | BitLocker Drive Encryption) is enabled I’d also ensure that you disable or suspend BitLocker before you start.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v132.0.2 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.1.144-1.0.5088 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CADesertRat

Reply | Quote

500 GB SSD, 372.3 free out of 476 GB. I do NOT use Bitlocker.

Not sure I want to mess with changing the win re if it won’t hurt me. Thoughts?

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I appreciate all the expertise here and your time to respond but since I don’t use Bitlocker and have no plans to do so, is it necessary to go through all those steps of which I am afraid to do LOL.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

CADesertRat wrote:

… since I don’t use Bitlocker and have no plans to do so, is it necessary to go through all those steps of which I am afraid to do LOL.

Hi CADesertRat:

Susan Bradley recommends ignoring these WinRE updates if they are not offered for your system by Windows Update (or whatever third-party Windows update manager you use). From Susan’s 22-Jan-2024 Patch Watch column KB5034441 has led us astray, in a horrible way:

“I am not comfortable advising you to resize your partitions. If you click on the wrong thing, you could accidentally delete your entire working hard drive. So I’m still going to strongly recommend that if you are not comfortable with resizing your partitions or using a partition tool to help, skip this update on your Windows 10 PCs.”

If skipping some of the recent WinRE updates like the Nov 2024 KB5048239 makes you uncomfortable you’re the only one who can decide if you have the technical expertise to follow n0ads’ instructions in post # 2717441 and increase the size of your WinRE partition to meet the minimum system requirements. Your comment that you are “afraid to do so” suggests to me that this isn’t something you should attempt.

If you decide to proceed with n0ads’ instructions just make sure you’ve created a full disk image and emergency recovery media like a bootable USB stick with disk imaging software (e.g., Macrium Reflect, Acronis True Image, etc.) before starting in case something goes wrong and you have to perform an emergency recovery.  I use Macrium Reflect Free v8.0 (not supported since Jan 2024 but still fully functional) and other good free options are listed in the June 2023 Tech Republic article Top 5 Free & Reliable Hard Disk Drive Cloning Software .
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5131 * Firefox v132.0.2 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.1.144-1.0.5088 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CADesertRat

Reply | Quote

Thanks for the response. I do keep monthly clones of my computers but just not sure I want to delve into this WinRE work since my understanding is that it won’t hurt anything if I don’t, especially since I don’t use Bitlocker which I understand to be the main reason.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

@lmacri See #2709725 and my conclusion there. Aii of my Win10 continue to be updated by the WinRE patches (I haven’t done Nov updates yet).

 

Reply | Quote

PKCano wrote:

See #2709725 and my conclusion there. Aii of my Win10 continue to be updated by the WinRE patches

Hi PKCano:

The information in your post # 2709725 shows that your WinRE partition is located at harddisk0\partition2 and that the total size is ~ 2.8 GB but nothing there tells me how much of that 2.8 GB is currently free. Assuming you have more than 250 MB of free disk space in that WinRE partition I would not expect you to have a problem installing this month’s KB5048239 WinRE update for Win 10 v22H2 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: November 12, 2024) to bump your ServicePack Build to 5125.

CADesertRat’s situation is quite different because the output of their fsutil command in post # 2716964 shows their 499 MB WinRE partition at harddisk1\partition1 currently has only 39.9 MB of free disk space. Since you have more expertise in this area than I do, how would you suggest CADesertRat increase the amount of free disk space in their WinRE partition if they decide they’d like to install this month’s KB5048239 WinRE update?
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v132.0.2 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.1.144-1.0.5088 * Macrium Reflect Free v8.0.7783

Reply | Quote

When my WinRE partitions were not “part4 after OS part” and less free space than needed, I used Mini Tool Partition Wizard to cut the necessary space out of the OS partition, usually enough to make the WinRE around 1GB +/-.  Even if it’s not adjacent to the WinRE partition, there is a way in Mini Tool to merge the free space in the WinRE’s current location without having to recreate the partition.

I don’t remember the exact steps I took, I just figured it out as I went along (first time use of Mini Tool in I can’t remember how long). There is also a way to move partitions. Since mine were updating, I didn’t bother with that.

I would imagine Image for Windows has a facility to do the same as the free Mini Tool. Make a full disk image and try.

Note: I am not using encryption on any of my installations.

 

1 user thanked author for this post.

lmacri

Reply | Quote

It’s simple “drag & drop” to rearrange partitions using MiniTool Partition Wizard.

Important: make a full backup of your disk beforehand!

To increase the Recovery partition size:

1-Make a note of the exact location of the Recovery partition reagentc /info

2- Disable the Recovery partition reagentc /disable

3- Resize a “different” partition to free up the amount of space you want to add to the Recovery partition.

4- Move the unassigned space so it’s located immediate after the Recovery partition.

5- Extend the recovery partition to include the unassigned space.

6- Re-enable the Recovery partition reagentc /enable

Note: If step 5 fails to re-enable the Recovery partition, use the backup you made to restore all it’s files/folders and try again.

Reply | Quote

astro46 wrote:

I am confused about the winre issue. I have checked two win10 systems here. Both have winreversion 10.0.19041.3920. both show winre ‘enabled’ I updated one of them a few days ago, but it is not showing xxx.5000.

Hi astro64:

Two general comments in addition to my post # 2712497 about the WinRE partition.

If you haven’t already done so, I’d advise that you permanently DISABLE your Windows Fast Startup power option as instructed in Brink’s TenForums tutorial Turn On or Off Fast Startup in Windows 10 (instructions for Win 11 users are <here>) and then re-boot a few times to ensure the setting change takes effect. The Fast Startup power option (also known as hybrid boot-up / hybrid shutdown) is enabled by default in Win 10 and Win 11 but it can sometimes interfere with the loading and initialization of drivers and services at boot-up and cause all sorts of unexpected glitches and problems with a wide range of programs, including Windows Update. For example, see the Microsoft support article Updates may not be installed with Fast Startup in Windows 10.

If you use the built-in Windows Update to apply updates (i.e., rather than a third-party tool like WUMgr) then when you see the prompt in your system tray notifications to “Restart Now” always check first at Settings | Update & Security | Windows Update and ensure that the Status of ALL your updates is “Pending Restart” before you restart your computer. There is a known bug where Windows Update will display an early prompt to “Restart Now” if an update for the Microsoft .NET Framework 3.5, 4.8 and 4.8 is offered with the other Patch Tuesday updates. This glitch was first observed over a year ago – for example, see TechTango’s 02-Oct-2023 post # 2591028. This month I received KB5044091 (Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64: October 8, 2024) with my October 2024 Patch Tuesday updates and saw this early “Restart Now” prompt (see image below), and I waited until my monthly KB5044273 Quality update  (OS Build 19045.5011) finished installing and reached a Status of “Pending Restart” before I restarted my computer.

———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

280park

Reply | Quote

lmacri wrote:

If you haven’t already done so, I’d advise that you permanently DISABLE your Windows Fast Startup power option as instructed in Brink’s TenForums tutorial Turn On or Off Fast Startup in Windows 10 (instructions for Win 11 users are <here>) and then re-boot a few times to ensure the setting change takes effect. The Fast Startup power option (also known as hybrid boot-up / hybrid shutdown) is enabled by default in Win 10 and Win 11 but it can sometimes interfere with the loading and initialization of drivers and services at boot-up and cause all sorts of unexpected glitches and problems with a wide range of programs, including Windows Update. For example, see the Microsoft support article Updates may not be installed with Fast Startup in Windows 10.

Or just Restart as instructed:

In order to make sure pending updates are completed, you have to choose Restart from the Power menu.

Reply | Quote

lmacri wrote:

It looks like the Master Patch List for the 10-Oct-2024 Patch Tuesday updates still incorrectly lists the re-released Jan 2024 KB5042320 (instead of the Oct 2024 KB5046400) as the latest replacement for KB5034441.

A correction to my post # 2712433. The release notes for the Jan 2024 KB5042320 (which installs Safe OS Dynamic Update KB5034232) state that “This update replaces the previously released update KB5034441“, but the release notes for the Oct 2024 KB5046400 (which installs Safe OS Dynamic Update KB5044615) state “This update does not replace any previously released update“.

The WinRE KB5042320 and KB5046400 updates are not listed in the Microsoft Update Catalog so I can’t check their supersedence chains, but the Safe OS Dynamic Updates they install that update the “Safe OS” used to update the WinRE are listed.  The Jan 2024 KB5034232 package details <here> and the Oct 2024 KB5044615 package details <here> both confirm that KB5044615 does supersede (replace) the older KB5034232 “Safe OS”  files.

At this point, however, I still have no idea what the Oct 2024 WinRE update KB5046400 actually patches, aside from the latest  KB5044615 Safe OS Dynamic Update that “makes improvements to the Windows recovery environment“.  I know the Jan 2024 WinRE update KB5034441 (and its replacement  KB5042320) fixed the BitLocker Secure Boot bypass vulnerability CVE-2024-20666 (see the Neowin article Microsoft kills unfixable KB5034440/KB5034441 updates, replaces with KB5042321/KB5042320) but I don’t know if the Oct 2024 WinRE update KB5046400 is a just feature update for the “Safe OS” or if it includes a bug fix for a security vulnerability.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783[/size]

Reply | Quote

MS-DEFCON 4 for Windows 10 Pro 64-bit 22H2 – October updates for consumers/small business computers.

We have now updated all of our computers without incident.

 

3 users thanked author for this post.

MrToad28, TechTango, jburk07

Reply | Quote

Win 10 22H2- On my AMD and Intel Desktops updated with no problem. MSRT, KB 5044091 .net, KB 5044273 Cum 22H2. SSU 10.0.19041.4950.

NOTE: My HP ProBook laptop got an extra security updt KB 5046400 and all the updates started downloading and got to about 10% and just quit. I checked reliability history and it showed that WU had stopped so I restarted Windows and KB 5046400 was no longer there and the other updates finished without incident. Not sure what happened but restarting seemed to fix whatever the problem was.

Out of curiousity, did anyone else have the KB 5046400 problem like I did or am I special 🙂

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

1 user thanked author for this post.

Win7and10

Reply | Quote

I had the same thing happen to me.

All October updates installed and the offer of KB5046400 was no longer there. The computer restarted, updated and the KB was not in the installed history as well as no longer offered.

I wonder why it was offered in the first place? It disappeared after the restart.

Win 10 Home 22H2

1 user thanked author for this post.

CADesertRat

Reply | Quote

have to say i am having a problem dealing with enlarging the recovery partition (it does have less than 250mb of free space).

Niubi doesn’t have a resize option in free version

aomei can’t stack steps, have to each step separately, before know the app will accomplish the rest.

Easeas: went fine until asking to execute.  offered an ad to buy, then back to ‘execute’,

minitool couldn’t get itself installed

paragon would only put unallocated space after the resized partition 5.  even though I give the resize number and set the ‘unallocated amount After partition’ set to 0.  where else would it go if not after. apparently not to before, where it needs to be to expand the recovery  partition 4.

guess i’ll either keep looking for a free partition manager,  or give up on it.

I haven’t gotten a reason why it is important to keep recovery up to date.

Reply | Quote

astro46 wrote:

have to say i am having a problem dealing with enlarging the recovery partition (it does have less than 250mb of free space) … minitool couldn’t get itself installed…

I haven’t gotten a reason why it is important to keep recovery up to date.

Hi astro46:

Do you mean MiniTool Partition Wizard Free? If so I have no idea why that application will not install on your PC, unless the latest installer is triggering a false positive detection by your antivirus. If you are certain you want to install KB5046400 I’d suggest you start a new topic and ask for personalized advice on how to increase the size of your WinRE partition.

I’d also suggest you re-read Susan Bradley’s Jan 2024 Patch Watch column KB5034441 has led us astray, in a horrible way about the previous WinRE patch in the free edition of the AskWoody Newsletter (Issue 21.04.F • 2024-01-22), as well as user feedback to that column posted <here>. Susan’s column states in part:

“First, a caveat. I do not believe that consumer users should be installing KB5034441 in the first place. This update fixes a vulnerability that allows attackers to boot into the recovery partition, then access a drive protected with BitLocker. Most consumers don’t have BitLocker enabled through their own actions, so I think very few consumers are affected …

… To further reinforce my advice not to resize yet, I used a free partition tool on one of my impacted computers. After it ran, the recovery partition was no longer recognized. I fixed that by extracting WinRE.wim from a Windows 10 ISO, then forcing the system to repair itself with a fairly complex process. I’m not going to describe it because I don’t recommend you try it, but it illustrates the danger associated with the problem.”

There is no detailed description about the purpose of the October 2024 WinRE bug fix in the KB5046400 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: October 8, 2024) release notes, which only state:

Summary

“This update automatically applies Safe OS Dynamic Update (KB5044615) to the Windows Recovery Environment (WinRE) on a running PC. The update installs improvements to Windows recovery features.”

Just to repeat, the WinRE partition on my own Win 10 v22H2 laptop does not have 250 MB of free disk space and is not being offered KB5046400, and I have no plans at present to increase the size of my WinRE partition unless I learn that there is evidence that KB5046400 fixes a critical security vulnerability that is being actively exploited.  This is in line with Susan’s current advice in the AskWoody Plus Newsletter (Issue 21.42 • 2024-10-14) to avoid KB5046400:

“We are once again getting new versions of KB5046400 and KB5044615 that impact the Windows Recovery Environment update. Neither will be offered if you have a small recovery-partition size. I continue to recommend skipping this update.”

———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

Reply | Quote

well, well.  Nice to know that now. I won’t bother dealing with the issue in the other 3 computers.  I had read in one of the threads about checking winre version number, and how if it doesn’t end in 5000 it is because the winre partition is too small.  so I naively (I guess) tried to increase winre partition size.  after spending several hours, trying 5 different free partition managers (some free ones won’t resize, it turns out. Easeus, which I used in the past now gets to point of effecting the resize, but only after getting payment) it became clear that winre partition can’t be changed with an app.  Apparently it is protected.  A web search found MS step by step instructions for enlarging Winre partition using diskpart: here.    This took only 15 mins. Half spent figuring out that a space was missing in some of the instructions.

I then ran win10 update again.  It found nothing to update. So I still have the winre version that I started with.  No sense of satisfaction here.

Reply | Quote

Astro,

Try downloading the latest Win 10 ISO file and do an Over-the-Top install keeping your files, programs, and settings. Should solve the problem.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

after posting about the attempts to enlarge the winre partition and finally getting it done with diskpart (holy cow, back to pre windows days)  I received another reply about how this whole winre update is not worth paying attention to.  so, for now, I think that is what I will do,  not pursue it further.  If it updates on this computer, fine.  As for the others, I won’t bother expanding the partition until I hear that it matters.

However, thanks for the suggestion.

Reply | Quote

Win 10 Pro 22H2 older desktop. Just completed Oct updates. Following this thread, I checked into my Recovery partition size/dates/standings. See Attached results.
Note: *In January, using winshowhide and with Susan’s reco, I hid KB5034441 to be safe due to the chaos then (as I had little winRe room.) That KB later disappeared from my ‘hide’ list. I was never offerred KB5042320 as a replacement in Jan. or later.
This month, my winRE size bloomed to 509 MB (?), alas only 90.8MB free. Thus wasn’t offerred this months KB5046400.*
Post Oct updates, I’m still on Service Pack build 3562. Any harm in staying there?? Why am I not on build 3920 at least? I don’t have acumen nor hair at this point in resizing my winRE. And why? If advised to do so, pls explain why go to such great lengths in layman’s terms pls:)

(I had just done an ‘over the top’ repair install last fall – is this now a quarterly need with Windows?)

(PS I had a diff experience with search/news & interest, will post in that topic.)

Reply | Quote

Your WinRE doesn’t have Build 3920 because KB5034441 was not installed to update it.
If installed, KB5046400 updates the WinRE to Build 5000. But you only have 90MB free space, so it probably won’t install.

Reply | Quote

I have w10 22H2. I was offered 5046400 today. I am not sure if I should install it or not. Too many comments and replies have occurred since earlier this month to know what applies to me. What should I check/look for?

Reply | Quote

I would skip it.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Ken

Reply | Quote

Hello, I received KB 5046400 on windows update for October and it did not install. Can I skip it and if it is ignored, can I hide it or will it be always there and error out?

Win 10 Home 22H2

Reply | Quote

Hello, I received the update and it will not install, however, the version from several months ago did install. First time something like this happened on this laptop. Sorry for the duplicate post.

Win 10 Home 22H2

Reply | Quote

Win7and10 wrote:

…I received KB 5046400 on windows update for October and it did not install.

Win7and10 wrote:

…however, the version from several months ago did install. First time something like this happened on this laptop.

So, just for clarity’s sake, you’re saying that KB5034441 from the January/February time frame was offered for the laptop and it DID install successfully, but that KB5046400 from last month, October, was offered but did NOT install successfully on the laptop, correct?

1 user thanked author for this post.

Win7and10

Reply | Quote

Yes that is correct, KB503441 installed from Jan/Feb but KB5046400 did not. I am currently trying to retry several times, however, waiting to see if it will install after the other updates complete.

Win 10 Home 22H2

1 user thanked author for this post.

Bob99

Reply | Quote

Oddly enough, after all the updates installed and pended restart for the October updates, the WU checked again (RETRY) and the offer of KB5046400 was no longer there. The computer restarted, updated and the KB was not in the installed history as well as no longer offered.

Win 10 Home 22H2

Reply | Quote

Deo wrote:

Post Oct updates, I’m still on Service Pack build 3562. Any harm in staying there?? Why am I not on build 3920 at least?

Hi Deo:

I don’t see any harm if you stay on WinRE Build 3562 (installed 29-Oct-2023) ***.

See the Aug 2024 Neowin article Microsoft kills unfixable KB5034440/KB5034441 updates, replaces with KB5042321/KB5042320, which states in part:

” … Microsoft released these WinRE (Windows Recovery Environment) updates to address a BitLocker Secure Boot bypass vulnerability under “CVE-2024-20666”. Microsoft said that the security flaw could allow attackers to bypass BitLocker encryption if they managed to get physical access to an unpatched PC.”

Even if Control Panel | System and Security | BitLocker Drive Encryption shows BitLocker is turned ON on your Win 10 Pro machine I don’t see a pressing need for you to install the Jan 2024 KB5034441 / KB5042320 (Build 3920) update that patches CVE-2024-20666, since the chance of someone stealing your home computer or somehow gaining physical access AND knowing how to exploit this BitLocker vulnerability is extremely low. If you had a business computer that stored confidential customer information protected by BitLocker encryption (e.g., patient healthcare information, client financial data) then this update should be applied.

AFAIK the Oct 2024 KB5046400 WinRE (Build 5000) update installs the KB5044615 Safe OS Dynamic Update that updates many of the “Safe OS” files used by the WinRE (e.g., BootMenuUx.dll, upgradeagent.dll, etc.) to v10.0.19041.5000, but I don’t know of any security vulnerability / CVE patched by KB5046400 that is currently being exploited. Unless I hear otherwise, I won’t be increasing the amount of free disk space on my own WinRE partition (currently at 97 MB) just to install KB5046400.

*** NOTE: In addition to requiring 250 MB of free disk space, the Prerequisites section of the release notes for the Oct 2024 KB5046400 (Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: October 8, 2024) also state that “The WinRE version installed on the device must be greater than or equal to version 10.0.19041.3920. For information about version 10.0.19041.3920, see update KB5042320.” In your case I assume this means that KB5046400 would not be offered to you, even if your WinRE partition had more than 250 MB of free disk space, because your WinRE version is still on Build 3562.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

Reply | Quote

lmacri wrote:

Unless I hear otherwise, I won’t be increasing the amount of free disk space on my own WinRE partition (currently at 97 MB) just to install KB5046400.

Hi @lmacri,
Do you mean “increasing the size of used disk space ..”?

See @n0ads reply <here>. Not in every case does installing KB5046400 change used/free space in a WinRe partition.

Reply | Quote

WCHS wrote:

Do you mean “increasing the size of used disk space ..”?

Hi WCHS:

No, I meant free. My WinRE partition currently has 97 MB of free disk space, and I don’t plan to increase (expand) that free disk to 250 MB or more in order to meet the system requirements for KB5046400. From the Oct 2024 KB5046400 release notes:

Prerequisites

Your device must meet the following to apply this update:

• The PC must have 250 MB of free space in the recovery partition to apply this update successfully.
• The WinRE version installed on the device must be greater than or equal to version 10.0.19041.3920. For information about version 10.0.19041.3920, see update KB5042320.

I think n0ads meant the used disk space of your WinRE partition may not change after applying KB5046400 because it simply updates the version number of previously existing “Safe OS” files (i.e., it does not add additional files / features to your WinRE that would use space in your WinRE partition).
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

Reply | Quote

Susan Bradley wrote:

If you are a fan of POP mail, I strongly recommend that you start investigating alternative email platforms, such as Thunderbird.

Why?

Reply | Quote

What client are you using to handle POP email now?  If is working, fine, keep using it.

I was using the installed version of Outlook. About a year ago it stopped working with some providers, eg: gmail.  Gmail doesn’t like Outlook.  Thunderbird works fine with Gmail.

 

Reply | Quote

I use Outlook but don’t use POP, only Exchange and IMAP, and Gmail works fine.

I’d like to understand why POP users are apparently being warned off Outlook.

1 user thanked author for this post.

Perq

Reply | Quote

I curious as to which Outlook are you using?  365?, new?, installed with office(which year)?  one of the other 500 apps named Outlook?

Did you know that in the MS cafeteria, all the items for sale are called “Outlook”?

Reply | Quote

365 and New.

(Classic and New are the only two Outlook for Windows apps.)

Reply | Quote

OK. I finally had to look. WHICH partition are we discussing? I’m assuming my 100MB but could it be the UEFI partition?

 

Reply | Quote

rebop2020 wrote:

WHICH partition are we discussing?

Hi rebop2020:

As RetiredGeek noted in post # 2712494, “Disk Management doesn’t report the correct values for WinRe partitions.”

See my post # 2712497. Entering the command reagentc /info in an elevated command prompt with Admistrator rights displays the disk and partition number where your WinRE is located. In my case it’s on harddisk0\partition4 (i.e., Partition 4 of my primary hard drive).

———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

Reply | Quote

Thanks. But mine shows partiton 4 as as I showed above I see 3 partitions?

Reply | Quote

lmacri wrote:

I don’t plan to increase (expand) that free disk to 250 MB or more

“Expand” clears it up.

I was thinking of my situation instead of yours. Even though I had only 204MB of free space, KB5034441 was delivered in March and installed, leaving 177MB, and then KB5046400 was delivered Oct 8. I plan on installing it and I don’t expect free/used space to change — I think it will still be 177MB free.

So, I don’t have to think about “expanding”. Evidently, the amount of free space I had before KB5034441 and what I have now (in both cases, less than 250MB) isn’t a issue when it comes to getting these WinRE patches and installing them.

Reply | Quote

WCHS wrote:

Even though I had only 204MB of free space, KB5034441 was delivered in March and installed, leaving 177MB, and then KB5046400 was delivered Oct 8 …. Evidently, the amount of free space I had before KB5034441 and what I have now (in both cases, less than 250MB) isn’t a issue when it comes to getting these WinRE patches

Hi WCHS:

The recommendation to have at least 250 MB of free disk space in your WinRE partition doesn’t seem to be an absolute system requirement. Windows Update installed the Jan 2024 KB5034441 / Build 3920 update (later recalled and replaced with KB5042320) without any issues even though my WinRE partition only had 123.0 MB of free disk space – see the “before-and-after KB5034441” images in my 16-Jan-2024 post # 2628138 in Susan Bradley’s Ready for the New Patching Year?.

My WinRE partition only has 96.7 MB of free space now since KB5034441 was installed and Windows Update is NOT offering the Oct 2024 KB5046400 / Build 5000 WinRE update, so perhaps Microsoft is being a bit more stringent this time around about how much free space the WinRE partition actually needs.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5011 * Firefox v131.0.3 * Microsoft Defender v4.18.24080.9-1.1.24080.9 * Malwarebytes Premium v5.2.0.140-1.0.5073 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

WCHS

Reply | Quote

Scrolling thru the posts I see a couple who’ve updated without issue, but the vast majority are discussing complex issues and problems. I’m going to use the start stop method to skip this update and hope for a clearer path next round.

Reply | Quote

MrToad28 wrote:

I’m going to use the start stop method to skip this update…

What technique does that entail? I’ve never heard someone call an updating control method by that name.

@MrToad28 , if it helps, I’ve successfully updated two Windows 10 22H2 machines with no issues this month. No added items on my Start menu, no intrusion from Copilot in any way, shape or form, no mysterious update for my recovery partition, no mysterious update for Outlook Classic or any other type since I don’t have and never have had Outlook installed on either computer.

I can’t speak to the monthly update for Windows 11 23H2, though, because I don’t have a machine with Windows 11, only the two with Windows 10.

Outlook, and the various updates for the recovery partition are the bulk of what folks above have been talking about this time. So, if you are on Windows 10 and don’t have any form of Outlook that you need or use, and were never offered KB5034441 back in January or February (or you hid it if it was ever offered to you and you never tried installing it), then you are probably not going to have any issues with this month’s updates.

Reply | Quote

I have updated 2 computers that have Outlook 2021 installed.  No issues that I can see.

Reply | Quote

Start-Stop method: Search update to pull up windows update settings, Click Resume updates, immediately click pause updates ..for Win10 keep poking the button till max weeks, For Win11 use drop down menu for max weeks.

Hope this helps.

I’m more risk/complexity averse than most since I’ve had more problems with boloxed updates than viruses and Avast handles the latter.

Reply | Quote

I just finished updating 3 of my computers to 24H2 today. Two went very smoothly as an upgrade from 23H2 leaving behind a lot for “Disk Cleanup”, and a much smaller footprint.

Computer 1 is supported and I used an iso DL for an over the top install. No issues.
Computer 2 is Not-Supported and I used a Rufus Blessed USB for an over the top. No issues.
Computer 3 is Not-Supported and was previously on Win10 22H2. I tried to use Rufus 24H2 for the upgrade. That failed. So I clean installed using Rufus 24H2 USB and it installed very quickly.

Besides the PITA it is to clean install, I have two minor issues on computer number three. First, Open Shell is not working like the other two computers. If I don’t “Replace The Start Button”, Windows Start Menu opens. So, I have to replace the button and it is not perfect. I tried clean installing Win11 23H2 and I got the same results. I can live with it, but I can’t figure out why this particular computer is acting up, since it works fine with 22H2.

Second, the two Non-Supported computers do not show the Webroot Trustworthy Checkmarks, which assess the site you go to in Google. If I toggle the settings in the Webroot extension, the checkmarks appear again, until the browser is restarted. It’s minor, but I just can’t figure that out as well. Very odd.

Finally, I notice a little lag after the upgrade on all three systems. And I got quite a few updates to 24H2.

ETA: I forgot to mention, the Webroot check mark works fine on Chredge and Chrome, this is only affecting the Opera browser, which is Chromium based like the other two.

Reply | Quote

PL1 wrote:

…I have two minor issues on computer number three. First, Open Shell is not working like the other two computers. If I don’t “Replace The Start Button”, Windows Start Menu opens. So, I have to replace the button and it is not perfect. I tried clean installing Win11 23H2 and I got the same results. I can live with it, but I can’t figure out why this particular computer is acting up, since it works fine with 22H2.

Any luck using the solution that worked for @garbo and, I presume, @n0ads in the “October updates are out” thread? The solution I’m referring to is in post #2714023 from @garbo .

1 user thanked author for this post.

PL1

Reply | Quote

Bob99 wrote:

Any luck using the solution that worked for @garbo and, I presume, @n0ads in the “October updates are out” thread? The solution I’m referring to is in post #2714023 from @garbo .

No, this is something totally different. That was regarding a delay. But, it may be indicative of MSFT trying to kill off 3rd party start menus.

1 user thanked author for this post.

Bob99

Reply | Quote

Bob99 wrote:

Any luck using the solution

My solution was to buy Start11. It’s all working fine now!

1 user thanked author for this post.

lmacri

Reply | Quote

PL1 wrote:

Computer 3 is Not-Supported and was previously on Win10 22H2.

Another minor issue that came up with my clean install of Win11 24H2 is that my lighted keyboard was not automatically turning on and shutting off the way it did with Win10 22H2.

I realize this is a Motherboard issue, and I fixed it by setting the BIOS APM Configuration > Erp Ready to [Enable (S4+S5)] on my Asus board, but it is very strange how it worked fine in Win10 with the setting off, yet it requires this setting with Win11. 🙂‍↕️

Also, I find the Snap Windows “feature” (when hovering over the maximize button) quite annoying. To turn it off: System> Multi Tasking> Snap Windows> Off

Reply | Quote

@Imacri and PK, this didn’t post as a reply for some reason.

Update: Evidently my older HP laptop went through the WinRE updates when both my desktops did not. I just ran the Nov updates on the laptop and there was an aditional update of KB 5048239 which is WinRE related so I checked my laptop using the cmd’s you gave and the regedit path you gave and the results are included.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

CADesertRat wrote:

I just ran the Nov updates on the laptop and there was an aditional update of KB 5048239 which is WinRE related …

Hi CADesertRat:

Thanks for the status update.

Your .txt file shows the output for your command **

fsutil volume diskfree \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE

didn’t run correctly (you added some extra text at the end of the command) so I’m not sure how much free disk space you still have in your WinRE partition, but no worries.  If the total disk space used by your WinRE partition is 4 GB I’m sure you had much more than the 250 MB of free space required to install this update.

Everything else in your output indicates the KB5048239 update (Windows Recovery Environment Update for Win 10 Version 22H2: November 12, 2024) installed correctly and patched your WinRE to the latest Build 5125 on your laptop.

** Note to others – this command is customized for the location of CADesertRat’s WinRE partition (i.e., harddisk0\partition2).
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5131 * Firefox v133.0.0 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.2.154-1.0.5101 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

CADesertRat

Reply | Quote

Thanks and yes I see the cmd error I made LOL.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

TL;DR

Just offered KB5048239 for the first time ever. Should I install this? I’m going to block it until I hear back here. Win 10 22H2

Thanks.

Reply | Quote

I have W10 22H2. On 12/20 KB 5048239 was offered. This is concerning WinRE. I do not understand any of this, there have been too many posts about WinRE. I sent a message to Susan since I could not find anything but have not heard.

What should I do?

Reply | Quote

In short : If you use / plan to use Bitlocker and have 250GB+ free space on WinRE you should install KB 5048239. Otherwise hide the update using WUmgr / wushowhide

1 user thanked author for this post.

Ken

Reply | Quote

Thanks Alex. No bitlocker in my future 🙂

Reply | Quote