New Update Windows 11 Patch Tuesday January 2026 (KB5074109, KB5073455)

[silversurfer]

Microsoft has released Patch Tuesday updates for Windows 11 25H2, 24H2, 23H2, and 22H2. The 25H2 and 24H2 update is provided via KB5074109, build 26100.7623 on 24H2, and build 26200.7623 on 25H2, after applying the updates.

The changelog is given below:

• [Compatibility] This update removes the following modem drivers: agrsm64.sys (x64), agrsm.sys (x86), smserl64.sys (x64) and smserial.sys (x86). Modem hardware dependent on these specific drivers will no longer work in Windows.
• [Networking (known issues)]
  • Fixed: This update addresses an issue where mirrored networking in Windows Subsystem for Linux (WSL) could fail causing “No route to host” errors and preventing access to corporate resources over VPN connections, even when the Windows host remained connected. This might occur after installing KB5067036.
  • Fixed: This update addresses an issue where you might experience RemoteApp connection failures in Azure Virtual Desktop (AVD) environments. This might occur after installing KB5070311
• [Power & Battery] Fixed: This update addresses an issue where devices with a Neural Processing Unit (NPU) might stay powered on when idle. This could affect power performance.
• [Secure Boot] Starting with this update, Windows quality updates include a subset of high confidence device targeting data that identifies devices eligible to automatically receive new Secure Boot certificates. Devices will receive the new certificates only after demonstrating sufficient successful update signals, ensuring a safe and phased deployment.
• [Windows Deployment Services (WDS] This update introduces a change in behavior in which WDS will stop supporting hands-free deployment functionality by default. Detailed guidance for IT administrators is available in Windows Deployment Services (WDS) Hands‑Free Deployment Hardening Guidance.
• [WinSqlite3.dll] Fixed: The Windows core component, WinSqlite3.dll, has been updated. Previously, some security software might have detected this component as vulnerable.

Source: Windows 11 KB5074109, KB5073455 January 2026 Patch Tuesday updates out - Neowin

 

[Parkinsond]

Applied; no issues

 

[Miravi]

After installing this update, which went fine, I'm finally noticing new changes to the start menu that were announced a while back.

 

[Parkinsond]

After installing this update, which went fine, I'm finally noticing new changes to the start menu that were announced a while back.

No new menu for me as I'm still on 24h2

 

[Jonny Quest]

After installing this update, which went fine, I'm finally noticing new changes to the start menu that were announced a while back.

Like this? Which is how it was laid out when I opened Start. Update went well, no problems on both Windows 11 laptops.

 

[stonjean633]

Like this? Which is how it was laid out when I opened Start. Update went well, no problems on both Windows 11 laptops.

View attachment 294646

I thought this new start menu was rolled out on previous updates. Seems not yet fully implemented until today.

I'll give it a try on my lone W11 laptop (if not for my NPU, this will be on W10 together with the rest of my machines that I reverted back to W10)

 

[oldschool]

After installing this update, which went fine, I'm finally noticing new changes to the start menu that were announced a while back.

Like this? Which is how it was laid out when I opened Start. Update went well, no problems on both Windows 11 laptops.

View attachment 294646

Don't have it here yet but the update went fine.

 

[Jonny Quest]

Don't have it here yet but the update went fine.

And the amazing part, one Windows 11 laptop had the new start menu layout, and the other didn't after they both updated. I even did a couple of restarts just to make sure

 

[Divine_Barakah]

No new menu for me as I'm still on 24h2

I believe ur running IoT LTSC, right?

 

[stonjean633]

And the amazing part, one Windows 11 laptop had the new start menu layout, and the other didn't after they both updated. I even did a couple of restarts just to make sure

One of the things I hate with W11, even the update is broken. Oh boy.
Long live W10

 

[Divine_Barakah]

One of the things I hate with W11, even the update is broken. Oh boy.
Long live W10

I wait a week before applying the updates. I also create a system image before applying any updates.

 

[Divine_Barakah]

Using Group Ploicy I blocked the installation of feature updates and driver updates. I only update drivers using Dell Command Update.

 

[stonjean633]

Using Group Ploicy I blocked the installation of feature updates and driver updates. I only update drivers using Dell Command Update.

You can do it like that or use driver utilities like Driver Booster. Other manufacturers together with Dell does not regularly update their drivers on the website and in Command Center.

 

[Divine_Barakah]

You can do it like that or use driver utilities like Driver Booster. Other manufacturers together with Dell does not regularly update their drivers on the website and in Command Center.

I'm using a business class laptop and drivers get released almost on a monthly basis. Driver utilities are a red flag for me. Using a generic driver is the worst thing you could possibly do to yourself.

 

[Wrecker4923]

Like this? Which is how it was laid out when I opened Start.

I think the update came with the December patch, but it somehow wasn't shown until suddenly it was. I had three machines that behaved differently.

 

[Parkinsond]

I wait a week before applying the updates. I also create a system image before applying any updates.

I do so, but as I intend to reinstall W, I install the update immediately, hoping it will break something to justify the reinstall.

 

[Parkinsond]

I believe ur running IoT LTSC, right?

Yes; IoT LTSC, either 10 or 11, is the best of its version.

 

[lokamoka820]

Like this? Which is how it was laid out when I opened Start. Update went well, no problems on both Windows 11 laptops.

View attachment 294646

Nice, but I still prefer StartAllBack to the default Windows Start menu; it's lighter and easier to use.

 

[Jonny Quest]

Nice, but I still prefer StartAllBack to the default Windows Start menu; it's lighter and easier to use.

And I remember using Classic Shell for a long time during and after Windows 8 came out, all the way up to Windows 10. I've just let myself get accustomed to the start menu and options as they are now.