Windows 10: Windows 11 Security Update Quietly Disabled Legacy Modems - Here’s Why

A recent Windows 11 security update has left some users confused and frustrated after their modems suddenly stopped working. While many initially assumed it was another Patch Tuesday mishap, Microsoft says the behavior is intentional — not a bug.

A Modem “Failure” That Wasn’t an Accident


Following the January 2026 Windows 11 security update (KB5074109), reports began appearing from users whose dial-up and legacy modem hardware no longer functioned. Given the update’s association with other serious issues — including GPU glitches, app crashes, and boot problems — the modem failures were quickly lumped into the growing list of update complaints.

However, Microsoft later clarified that this particular issue was expected.

In the official release notes, the company confirmed that the update removed several outdated modem drivers from Windows 11. Devices that rely on those drivers can no longer operate after the update is installed.

Which Drivers Were Removed?


The update eliminates multiple legacy modem drivers that date back many years, including both 32-bit and 64-bit versions. These drivers were still present in Windows primarily for backward compatibility, but Microsoft says they contain unpatched security vulnerabilities.

From a security standpoint, removing them reduces the system’s attack surface — but it also means affected hardware is effectively deprecated overnight.

Why Users Were Caught Off Guard


While the driver removal was documented, many users never noticed the change until their hardware stopped working. Some even reported that newly purchased modems labeled as “Windows 11 compatible” failed immediately after the update.

This has caused particular disruption in niche but still-active environments, such as:

• Legacy phone answering and logging systems
• Industrial or specialized setups that depend on modem drivers
• Businesses still using older hardware for logging or connectivity

In many cases, manufacturers no longer provide updated drivers — leaving users with limited options.

Can You Fix It?


There is a temporary workaround, but it comes with risks:

1. Uninstall update KB5074109 to restore modem functionality.
2. Pause Windows Update to prevent the patch from reinstalling.
3. Use the time to migrate to supported hardware or a newer connection method.

This isn’t a long-term solution. Running an unpatched system increases security risk, especially if the device is connected to the internet or used inside an organization.

A Security Win With Real-World Consequences


Microsoft’s move highlights a broader reality: security improvements increasingly require dropping legacy components. Most users won’t notice this change at all, but those who rely on older modems are discovering that Windows can remove compatibility overnight — even if the device still worked before Patch Tuesday.

If your setup depends on one of those legacy drivers, uninstalling the update may buy you time, but the real fix will likely require replacing the hardware.

Thank you for being a Ghacks reader. The post Windows 11 Security Update Quietly Disabled Legacy Modems - Here’s Why appeared first on gHacks Technology News.

read more...

 

Windows 8 Secure Boot Feature: Not So Secure?

• Linux
• Linux
• Linux
• Linux
• Oh and OSX

Here is a statement from a Kernal Developer at Red Hat:

I'm not sure this exploits the legacy BIOS but rather it exploits the legacy boot method on MBR drives, injecting a signed key before the OS boots, which you are correct in that it has nothing to do with Windows 8. And the simplest fix would just be to require boot drives use GPT when Secure Boot is enabled in UEFI.

 

Secure boot isn't turning on in HP laptop (windows 11)

Hello Mohd_357,

Welcome to Microsoft Community.



I understand the frustration you’re facing with Secure Boot on your HP laptop. Let’s troubleshoot this issue step by step:

1. Load HP Factory Default Keys:
   
   • Go into the BIOS settings.
     
   • Navigate to System Configuration > Boot Options.
     
   • Look for an option to Load HP Factory Default Keys. If available, select it.
     
   • Check if Secure Boot becomes available after doing this.
     
2. Disable Fast Startup:
   
   • Boot into your operating system (Windows 11).
     
   • Open Settings.
     
   • Go to Updates & Security > Recovery.
     
   • Click Restart Now under “Advanced startup.”
     
   • Wait for your PC to boot into the system recovery menu.
     
   • Select Troubleshoot and then choose Advanced options.
     
   • Finally, select UEFI Firmware Settings.
     
3. Check BIOS Mode:
   
   • Ensure that your Windows 11 installation is in UEFI mode, not legacy mode.
     
   • If your notebook’s BIOS mode is set to legacy, you won’t be able to enable Secure Boot. You may need to reinstall Windows 11 from an EFI boot source.
     
4. Reset BIOS settings to Default:
   
   • Reset BIOS settings may restore secure boot settings to normal factory state.
     

Regarding TPM 2.0:

• Your PC may not have TPM (Trusted Platform Module) support, which is required for Windows 11.
  
• Additionally, Windows 11 requires an Intel 8th gen core processor or newer.
  

I hope it can solve your problem.

Thank you for your patience and cooperation.



Best Regards,

 

how to disable secure boot and be in legacy where I started

I have an Asus board z 390 and my builder set it to legacy. I am in UEFI.
I would like to enable secure boot w/o legacy and then go back to legacy with it disabled.
I have about exhausted help with Google, Asus etc.
If a clean install is not required can anyone ell me the steps to enable secure boot with legacy off, then how to disable secure boot and be in legacy where I started.
This would give me options and enhance my learning about the settings which I am trying to no avail to learn.
Please, and thank you so much