Raleigh, NC

32°F
Scattered Clouds Humidity: 79%
Wind: 2.06 M/S

Microsoft Resolves Windows Server 2025 Crashes and Setup Glitches

Microsoft Resolves Windows Server 2025 Crashes and Setup Glitches

Microsoft Fixes BSOD and Installation Bugs in Windows Server 2025 for High-Core Systems 

Microsoft has addressed several known problems that caused Blue Screen of Death (BSOD) crashes and installation failures on Windows Server 2025, especially on servers with a high number of CPU cores. 

Back in October, Microsoft acknowledged that affected systems could face a range of issues — such as failed or stuck installations, upgrades that don’t complete, and startup times stretching to over three hours. Some servers also experienced BSODs during boot-up, restarts, or while launching apps. These problems were mostly seen on servers with more than 256 logical processors. 

To check if a system is at risk, IT admins can look at the Performance tab in Task Manager and see if the server shows more than 256 logical processors. 

According to an updated support entry, these issues have been resolved in updates released after the KB5046617 cumulative update (part of November’s Patch Tuesday). Microsoft strongly recommends installing the latest security updates, as they include important bug fixes and improvements. 

For those unable to update right away, there's a workaround: 

  • Restart the server and enter UEFI Setup (BIOS). 
  • Find the option to adjust the number of cores per socket. 
  • Set it so the total number of logical processors is 256 or fewer. 
  • To calculate: (Sockets × Cores per socket × Logical processors per core) ≤ 256 
  • Restart the server again. 

Earlier this month, Microsoft also flagged another issue — some domain controllers running Windows Server 2025 could become unreachable after a reboot, affecting apps and services. 

Additionally, users of Windows Hello might have trouble logging in after the April 2025 update on both Windows 11 (version 24H2) and Windows Server 2025. 

Microsoft also fixed an authentication issue tied to Credential Guard when using the Kerberos PKINIT protocol. And for systems running SenseShield’s sprotect.sys driver, a safeguard hold was introduced to prevent compatibility problems that can lead to BSODs or black screens. 

Found this article interesting? Follow us on X(Twitter) ,Threads and FaceBook to read more exclusive content we post. 

Image

With Cybersecurity Insights, current news and event trends will be captured on cybersecurity, recent systems / cyber-attacks, artificial intelligence (AI), technology innovation happening around the world; to keep our viewers fast abreast with the current happening with technology, system security, and how its effect our lives and ecosystem. 

Please fill the required field.