What is new in Windows Server 2025
Check its advanced features and innovations
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 known issues and the servicing status for Windows Server 2025. 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.
Current status as of November 6, 2024
Windows Server 2025 is now generally available. It delivers security advancements and new hybrid cloud capabilities in a high performing, AI-capable platform. Windows Server 2025 is Microsoft’s latest Long-Term Servicing Channel (LTSC) release for Windows Server. To download a free 180-day evaluation, visit the Microsoft Evaluation Center.
Windows Server 2025 is offered as an Optional update for Windows Server 2022 and Window Server 2019 devices, if organizations want to do an in-place upgrade. We recommend you use these methods to deploy Windows Server feature updates as Windows Server 2025 is not automatically installed.
To learn more about Windows Server’s Lifecycle Policy, see the Windows Server 2025 lifecycle article.
- Get Windows Server known issues in Graph API
Data is available for supported Windows Server versions
Known issues
See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| GIF functionality in the Windows Emoji Panel might become unavailable This issue occurs because the previous GIF provider (Tenor) retired its service on June 30, 2026. | N/A | Confirmed | 2026-06-30 10:55 PT |
| Deleting a file from the Recycle Bin displays an internal filename in the dialog This issue only occurs within the confirmation dialog after installing the June Windows security update. | OS Build 26100.32995 KB5094125 2026-06-09 | Confirmed | 2026-06-18 20:53 PT |
| Updates installed via WUSA might fail if installed from a shared folder This issue might occur when installing an update from a network folder containing multiple .msu files. | OS Build 26100.4349 KB5060842 2025-06-10 | Resolved KB5094125 | 2026-06-11 16:15 PT |
Issue details
June 2026
GIF functionality in the Windows Emoji Panel might become unavailable
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2026-06-30, 10:55 PT Opened: 2026-06-29, 20:45 PT |
Starting on June 30, 2026, you might not see GIF options in the Windows Emoji Panel on some devices and instead see a message stating “GIF service is not available.” This issue occurs because the previous GIF provider (Tenor) retired its service on that date.
Next steps: We are working to release a resolution in a future Windows update and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 23H2
- Server: Windows Server 2025
Deleting a file from the Recycle Bin displays an internal filename in the dialog
| Status | Originating update | History |
|---|---|---|
| Confirmed | OS Build 26100.32995 KB5094125 2026-06-09 | Last updated: 2026-06-18, 20:53 PT Opened: 2026-06-18, 12:03 PT |
When permanently deleting a single item from the Recycle Bin, the confirmation dialog displays the internal Recycle Bin filename (for example, $Rxxxxx.ext) instead of the original filename. The Recycle Bin itself correctly displays the original filename, and restoring the item also restores it using the original filename.
This issue occurs after installing the Windows security update released on June 9, 2026 (KB5094125).
Workaround: A workaround is available for affected devices. To apply this workaround in your organization and mitigate the issue, please contact Microsoft’s Support for business.
Next steps: We are working to release a resolution in a future Windows update and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
August 2025
Updates installed via WUSA might fail if installed from a shared folder
| Status | Originating update | History |
|---|---|---|
| Resolved KB5094125 | OS Build 26100.4349 KB5060842 2025-06-10 | Resolved: 2026-06-09, 10:00 PT Opened: 2025-08-15, 11:56 PT |
Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files. These issues might occur on devices that installed updates released May 28, 2025 (KB5060842) and later.
WUSA is a method of installing updates using the Windows Update Agent API which is typically only employed in enterprise environments. It is not common in personal or home settings.
Please note that this issue does not occur when there is only one .msu file in the network share or when the .msu files are stored locally on the device. In addition, after installing an .msu file by double-clicking or using WUSA and restarting Windows, you might notice that the Update History page in Settings continues to indicate that a restart is required to complete the update. This is temporary and should be resolved on its own.
Resolution: This issue was resolved by Windows updates released June 9, 2026 (KB5094125), 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 June 9, 2026 (KB5094125) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and are experiencing this issue, you have the option to work around it by saving the .msu files locally on the device and install the update from this location. Also, if you've restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully.
Additionally, this issue was addressed using Known Issue Rollback (KIR) beginning September 2025, and was resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. IT admins can resolve this issue for managed devices which have installed the affected update and encountered this issue. It can be fixed by installing and configuring the Group policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. The special Group Policy can be found in Computer Configuration > Administrative Templates > [Group Policy name].
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 24H2 and Windows Server, version 2025 - Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2
- 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.