Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Find information on recently resolved issues for Windows Server 2025. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Resolved issues
Summary | Originating update | Status | Date resolved |
---|---|---|---|
Authentication issues due to failed password rotation in Kerberos This issue is observed in a niche scenario when using PKINIT protocol and is resolved in the April 2025 security update. | N/A | Resolved KB5055523 | 2025-04-08 10:00 PT |
Some text might appear in English during the installation process This only occurs when utilizing certain media, such as CD or USB, to install Windows Server 2025 | N/A | Resolved KB5055523 | 2025-04-08 10:00 PT |
Error 'boot device inaccessible' might appear in iSCSI environments Servers might see error 'boot device inaccessible' after the installation of Windows Server 2025 | N/A | Resolved KB5051987 | 2025-02-11 10:00 PT |
Windows Server 2025 might not run as expected on devices with high core count This is observed on servers with 256 or more logical processors. Issues may not trigger consistently. | N/A | Resolved KB5046617 | 2024-11-12 10:00 PT |
Issue details
April 2025
Authentication issues due to failed password rotation in Kerberos
Status | Originating update | History |
---|---|---|
Resolved KB5055523 | N/A | Resolved: 2025-04-08, 10:00 PT Opened: 2025-04-07, 16:30 PT |
After installing Windows Server 2025, devices using the Identity Update Manager certificate/Public Key Cryptography for Initial Authentication (PKNIT), might experience an issue with passwords not rotating correctly, causing authentication failures. This issue occurs particularly when Kerberos Authentication is used and the Credential Guard feature is enabled. Note that machine certification using PKINIT path is a niche use case, and this issue affects a small number of devices in enterprise environments.
With this issue, devices fail to change their password every 30 days as the default interval. Because of this failure, devices are perceived as stale, disabled, or deleted, leading to user authentication issues.
Devices running Windows Home edition are unlikely to be affected by this issue, as Kerberos authentication is typically used in enterprise environments and is not common in personal or home settings.
Resolution:
This issue is resolved in the April 2025 Windows security update (KB5055523) and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: The feature Machine Accounts in Credential Guard, which is dependent on password rotation via Kerberos, has been disabled until a permanent fix is made available.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: Windows Server 2025
October 2024
Some text might appear in English during the installation process
Status | Originating update | History |
---|---|---|
Resolved KB5055523 | N/A | Resolved: 2025-04-08, 10:00 PT Opened: 2024-10-31, 13:12 PT |
When installing Windows Server 2025, some text might appear in English during the installation process, regardless of the language selected for the installation. This will be noticeable if a language other than English has been selected for installation.
Please note, this only occurs when utilizing media - such as CD and USB flash drives - to install Windows Server 2025. This issue is only present on Windows Server media 25100.1742 and above with the use of Multilanguage User Interface (MUI).
Resolution: This issue was resolved by Windows updates released April 8, 2025 (KB5055523), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: None
- Server: Windows Server 2025
Error 'boot device inaccessible' might appear in iSCSI environments
Status | Originating update | History |
---|---|---|
Resolved KB5051987 | N/A | Resolved: 2025-02-11, 10:00 PT Opened: 2024-10-31, 16:09 PT |
Servers which use iSCSI (Internet Small Computer Systems Interface) technology might display an error upon startup, with the message 'boot device inaccessible'.
This is observed on servers operating under NDIS Poll Mode booting from an iSCSI LUN. Under such configuration, the server will experience the error during startup, after the installation of Windows Server 2025 is completed.
Resolution: This issue was resolved by Windows updates released February 11, 2025 (KB5051987), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: None
- Server: Windows Server 2025
Windows Server 2025 might not run as expected on devices with high core count
Status | Originating update | History |
---|---|---|
Resolved KB5046617 | N/A | Resolved: 2024-11-12, 10:00 PT Opened: 2024-10-31, 13:11 PT |
Servers which have a high number of logical processors might experience issues running Windows Server 2025. This is presently observed on servers which have 256 or more logical processors.
On these devices, one or more of the following issues might be encountered:
- Windows Server 2025 installation or upgrading processes might fail or stop responding.
- Starting or restarting Server might take an excessive amount of time, such as 3 hours or more.
- An error message on a blue screen appears when starting, restarting, or trying to run an application.
Issues may not trigger consistently, for which it is also possible that the server will start and operate without problem.
To determine whether you are encountering this issue because the number of logical processors on the device exceeds 256, open the Windows Task Manager. This can be accomplished by pressing CTRL+SHIFT+ESC. From there, select the Performance tab and note the number of logical processors reported in the bottom half of the window.
Resolution: This issue was resolved by Windows updates released November 12, 2024 (KB5046617), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released November 12, 2024 (KB5046617) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and have this issue, you have the option to apply the following workaround:
To temporarily prevent this issue, you will need to limit the total number of logical processors on the server to 256 or under. Changing the number of logical processors will vary depending on the firmware installed on your device.
To adjust the number of logical processors, follow these steps:
- Restart your server and enter the UEFI Setup. Navigate through the firmware menus, which may vary by manufacturer.
- Locate any option which allows you to adjust the number of cores per socket.
- Set the number of cores per socket to a value that ensures the total number of logical processors is 256 or fewer. Important: The total number of logical processors is calculated by first multiplying the number of sockets by the number of cores per socket, and then multiplying that result by the number of logical processors per core.
- Restart the server.
Affected platforms:
- Client: None
- Server: Windows Server 2025
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.