Win Update KB5050009 Windows 11 Cumulative Update build 26100.2894 (24H2) - Jan. 14

maur0 · Jan 14, 2025

instaled ok for now

HRPuffnstuff · Jan 14, 2025

This one is downloading slow af on 3 machines but my desktop got it pretty quick.

BrianInEngland · Jan 14, 2025

Worked as usual. No problems with DISM or SFC checks

The File explorer bug is STILL not fixed!

Cameraman1955 · Jan 14, 2025

hsehestedt said:
It looks like we have yet another failed attempt to resolve the issue with File Explorer where the "..." opens upwards only and not down. Today's update fixed it on one machine, but not on another. This follows last month's update where it fixed it on some of my other machines, but not on all of them.

Wow, even I am amazed at the astonishing incompetence of Microsoft lately.

Same here desktop dropdown menu repaired on my laptop still goes up, both running the same updates.

fg2001gf11F · Jan 14, 2025

This silly bug is becoming a joke.
How can MS still ignore this nonsense?
We still need to disable the useless feature id:51960011 with vivetool to get rid of this B.S.

RobertA · Jan 14, 2025

Update installed the quickest on our unsupported hardware Acer AIO, 2 x slower on our Lenovo AIO, but finalized, so far stuck at 10% for 1/2 hour on our custom build I7

forumwt · Jan 14, 2025

I don't have this explorer bug, all is fine for me. But also before this update I didn't see this bug

hsehestedt · Jan 14, 2025

forumwt said:
I don't have this explorer bug, all is fine for me. But also before this update I didn't see this bug

It does not happen on all machines. Also, last month's updates resolved the issue on some machines, but not all. I have a mix of machines both with and without this issue.

VaimneJuhtMur · Jan 14, 2025

always same of these updates fail but atlast manual install work almost always

asturias7 · Jan 14, 2025

I've yet to get out of 23H2 Beta... just a Q for everyone: How is your internet with 24H2? I know some people had problems with certain WiFi and Ethernet drivers when they updated to 24H2. If anyone is using Intel or Intel Killer drivers, is all fine with 24H2?

FrancoDT · Jan 14, 2025

asturias7 said:
If anyone is using Intel or Intel Killer drivers, is all fine with 24H2?

My Intel Killer drivers have been fine with 24H2 and recently updated on both my machines.

tda · Jan 14, 2025

Hello everyone,

I'm having issues injecting it into the .wim file I use for deployments.

As per MS Website and also Catalog download, the kb5050009 is bundled with the KB5043080.

The .wim I'm trying to patch was patched in December24.

Command and output is as following:

Batch:

C:\Windows\System32>dism /add-package /image:"C:\Work\DISM\mount\Windows" /ScratchDir:"C:\Work\DISM\scratch" /PackagePath:"C:\Work\DISM\updates\ALL"

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.2605

Processing 1 of 2 -
[==========================100.0%==========================]
[==========================100.0%==========================] Processing 2 of 2 -
[==========================100.0%==========================]
[===========================72.0%=========                 ] C:\Work\DISM\updates\ALL\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu: An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
 Error: 0x800f0984

Error: 0x800f0984

I don't understand why it's not able to slipstream the update into the .wim
Did someone had the same issue with .wim files?

Or I'm missing something here?
Thanks a lot.

hsehestedt · Jan 14, 2025

tda said:
Hello everyone,

I'm having issues injecting it into the .wim file I use for deployments.

As per MS Website and also Catalog download, the kb5050009 is bundled with the KB5043080.

The .wim I'm trying to patch was patched in December24.

Command and output is as following:

Batch:

C:\Windows\System32>dism /add-package /image:"C:\Work\DISM\mount\Windows" /ScratchDir:"C:\Work\DISM\scratch" /PackagePath:"C:\Work\DISM\updates\ALL" Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Processing 1 of 2 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 2 of 2 - [==========================100.0%==========================] [===========================72.0%========= ] C:\Work\DISM\updates\ALL\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f0984 Error: 0x800f0984

I don't understand why it's not able to slipstream the update into the .wim
Did someone had the same issue with .wim files?

Or I'm missing something here?
Thanks a lot.

I updated both my Win 11 24H2 and 23H2 images today. I updated the consumer edition ISO images, updating all 11 editions on each ISO for a total of 22 editions of Win 11 updated. All editions updated just fine. So far I have only performed a test installation from the 24H2 image, but that went smoothly and with no problems so it appears that my updates worked flawlessly.

Could you possibly provide more details on the steps that you are using? Maybe I can stop the differences in our processes.

BTW, the error code indicates that there is a missing binary in the original image.

Out of curiosity, have you tried the same procedure by updating a CLEAN Windows image rather than one that you had previously updated (you stated that "The .wim I'm trying to patch was patched in December24").

EDIT: Just noticed one oddity: Why are specifying a scratch directory for injecting updates into a WIM? I have never seen that done before. It may be merely something that I am not aware of, but it sure is not how I do it or have ever seen it done before. I typically only specify a scratch directory when capturing an image from a syspreped system.

Gordon Freeman · Jan 14, 2025

Up to date here

tda · Jan 14, 2025

tda said:
Hello everyone,

I'm having issues injecting it into the .wim file I use for deployments.

As per MS Website and also Catalog download, the kb5050009 is bundled with the KB5043080.

The .wim I'm trying to patch was patched in December24.

Command and output is as following:

Batch:

C:\Windows\System32>dism /add-package /image:"C:\Work\DISM\mount\Windows" /ScratchDir:"C:\Work\DISM\scratch" /PackagePath:"C:\Work\DISM\updates\ALL" Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2605 Processing 1 of 2 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 2 of 2 - [==========================100.0%==========================] [===========================72.0%========= ] C:\Work\DISM\updates\ALL\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x800f0984 Error: 0x800f0984

I don't understand why it's not able to slipstream the update into the .wim
Did someone had the same issue with .wim files?

Or I'm missing something here?
Thanks a lot.

EDIT:
I've saw

hsehestedt said:
I updated both my Win 11 24H2 and 23H2 images today. I updated the consumer edition ISO images, updating all 11 editions on each ISO for a total of 22 editions of Win 11 updated. All editions updated just fine. So far I have only performed a test installation from the 24H2 image, but that went smoothly and with no problems so it appears that my updates worked flawlessly.

Could you possibly provide more details on the steps that you are using? Maybe I can stop the differences in our processes.

BTW, the error code indicates that there is a missing binary in the original image.

Out of curiosity, have you tried the same procedure by updating a CLEAN Windows image rather than one that you had previously updated (you stated that "The .wim I'm trying to patch was patched in December24").

EDIT: Just noticed one oddity: Why are specifying a scratch directory for injecting updates into a WIM? I have never seen that done before. It may be merely something that I am not aware of, but it sure is not how I do it or have ever seen it done before. I typically only specify a scratch directory when capturing an image from a syspreped system.

Hello,
I will check the health of the image tomorrow, because I "inherited" the image where I'm currently working, so I didn't make it from scratch.
In any case the scratchdir is used only to specify a specific folder instead of the one inside the Windows folder

Also just to be sure I'm not doing a stupid mistake, could you please tell me which command do you use to inject the updates?

As said I downloaded and put both MSU inside a folder (C:\Work\DISM\updates\ALL)
Then :
dism /add-package /image:"C:\Work\DISM\mount\Windows" /ScratchDir:"C:\Work\DISM\scratch" /PackagePath:"C:\Work\DISM\updates\ALL"

I've also tried with pointing directly at the KB5050009 MSU (as described in the article of Microsoft:

Checkpoint cumulative updates

Starting with Windows 11, version 24H2, the latest cumulative update may have a prerequisite cumulative update that is required to be installed first. To install these checkpoint cumulative updates, call /Add-Package with the target cumulative update. The folder from -PackagePath will be used to discover and install one or more checkpoints as needed. Only the target cumulative update and any prerequisite checkpoint cumulative updates should be in the -PackagePath folder. Cumulative update packages with a revision less than or equal to the target cumulative update will be processed.

dism /add-package /image:"C:\Work\DISM\mount\Windows" /ScratchDir:"C:\Work\DISM\scratch" /PackagePath:"C:\Work\DISM\updates\ALL\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu" /PreventPending

fg2001gf11F · Jan 14, 2025

forumwt said:
I don't have this explorer bug, all is fine for me. But also before this update I didn't see this bug

What are your display settings?
As already said multiple times, the problem only happens with Display Scales that are not 100% or exact multiples like, 200%, 300%.
Fails solid with Scale of 125%, 150%. 175% etc.
This has been reported for months and completely ignored by MS.

The workaround is by disabling this useless attempted fix below that doesn't fix anything and instead is adding this silly bug.

[51960011] (FileExplorerTabLineFix)

fg2001gf11F · Jan 14, 2025

hsehestedt said:
It does not happen on all machines. Also, last month's updates resolved the issue on some machines, but not all. I have a mix of machines both with and without this issue.

See my post #36 above.

suatcini54 · Jan 14, 2025

hsehestedt said:
I updated both my Win 11 24H2 and 23H2 images today. I updated the consumer edition ISO images, updating all 11 editions on each ISO for a total of 22 editions of Win 11 updated. All editions updated just fine. So far I have only performed a test installation from the 24H2 image, but that went smoothly and with no problems so it appears that my updates worked flawlessly.

Could you possibly provide more details on the steps that you are using? Maybe I can stop the differences in our processes.

BTW, the error code indicates that there is a missing binary in the original image.

Out of curiosity, have you tried the same procedure by updating a CLEAN Windows image rather than one that you had previously updated (you stated that "The .wim I'm trying to patch was patched in December24").

EDIT: Just noticed one oddity: Why are specifying a scratch directory for injecting updates into a WIM? I have never seen that done before. It may be merely something that I am not aware of, but it sure is not how I do it or have ever seen it done before. I typically only specify a scratch directory when capturing an image from a syspreped system.

Hi.

You are correct. The MS updates are integrated into the .wim file without any issues. When I try to download KB5050009.msu update file, I see two updates: One is KB5043080 and the other is KB5050009. When I attempt to integrate both files into .wim file, KB5043080 does not integrate into .wim file but reads "The operation completed successfully". KB5050009 integrates into .wim file in two passes. Then .wim file is saved and unmounted.

The .wim file used is 24H2 build 26100.2605.

tda · Jan 14, 2025

suatcini54 said:
Hi.

You are correct. The MS updates are integrated into the .wim file without any issues. When I try to download KB5050009.msu update file, I see two updates: One is KB5043080 and the other is KB5050009. When I attempt to integrate both files into .wim file, KB5043080 does not integrate into .wim file but reads "The operation completed successfully". KB5050009 integrates into .wim file in two passes. Then .wim file is saved and unmounted.

The .wim file used is 24H2 build 26100.2605.

View attachment 122079

Hi,
So you are installing the two .msu separately?
From what Is written by Microsoft it should "automatically" install the update in the correct sequence if both are in the same folder.
In any case - first thing I'll try to check the health (I think I made it as a test earlier today, but I had something like: "The source files could not be found" or something like that.

Later I will retest the whole .... BTW you've made a script to do the injection?

asturias7 · Jan 14, 2025

FrancoDT said:
My Intel Killer drivers have been fine with 24H2 and recently updated on both my machines.

Do you use the Killer Control/Intelligence Center? If so, any problems?

Applies to	Symptom	Workaround
All users	We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows.	Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
All users	Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro editions of Windows are affected.	Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:\ProgramData\ssh and C:\ProgramData\ssh\logs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: `$directoryPath = "C:\ProgramData\ssh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl` Repeat the above steps for C:\ProgramData\ssh\logs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
IT admins	Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when restarting the device to complete the update installation, an error message with text similar to “Something didn’t go as planned. No need to worry – undoing changes” appears. The device will then revert to the Windows updates previously present on the device. This issue likely affects a limited number of organizations as version 2411 of the SRA application is a new version. Home users are not expected to be affected by this issue.	Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.

Win Update KB5050009 Windows 11 Cumulative Update build 26100.2894 (24H2) - Jan. 14

January 14, 2025 - KB5050009 (OS Build 26100.2894)​

Highlights​

Improvements​

Windows 11 servicing stack update (KB5050387)- 26100.2890​

Known issues in this update​

How to get this update​

Active member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Active member

My Computers

Active member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

New member

My Computer

Well-known member

My Computers

Well-known member

My Computer

New member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computers

New member

My Computer

Well-known member

My Computer

Similar threads

January 14, 2025 - KB5050009 (OS Build 26100.2894)

Highlights

Improvements

Windows 11 servicing stack update (KB5050387)- 26100.2890

Known issues in this update

How to get this update