Recent Discussions
26063 deduplication data corruption is still there.
From Server 2022 up to this newest 26063 build, they all have the same problem, as described here: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-deduplication-data-corruption/m-p/4047321 I am out of energy for today and give up for today. It seems to be impossible to get Microsoft to care for actual OS bugs instead of marketing.4.7KViews1like26CommentsHyper V Server 2019 VM Paused-Critical Disk(s) encountered critical IO errors
I am running Hyper V server 2019 and running 2 windows 10 VM (only OS running) and 1 Windows server essentials 2019. It worked fine for 6 months just running basic AD tasks. a management software was installed and we had issues since. The 2 windows 10 VM can't start up. An error occurred while attempting to start the selected virtual machines 'Windows 10 VM' failed to change state When I starte the windows server 2019 essentials a Paused-Critical shows on STATE and Status is 'Disk(s) encountered critical IO errors. there's plenty of available storage space in the VM Can anyone help? thank youWindows 11 automatically restarting after install security Update — With GPO and WSUS.
Hi everyone, I’m facing a strange behavior with Windows 11 devices that receive updates through WSUS and are fully managed via Group Policy. Here’s the scenario: We have a GPO configured as follows: -Configure Automatic Updates → 4 (Auto download and schedule the install) -Scheduled installation every day at 10:00 -Install during automatic maintenance → disabled -Active Hours configured -Turn off auto-restart for updates during active hours → Enabled -Update deadlines set to 0 (to avoid any forced restart) -No other restart-related policies set in the domain Even with this configuration, after updates are installed, Windows 11 shows the following message: “Your organization manages update settings. We will restart and install this update at X minutes.” And then the device automatically restarts, even when: -a user is logged in -it is outside Active Hours -deadlines are disabled -no-auto-restart is enabled This behavior does not happen on Windows 10 — only on Windows 11.48Views0likes1CommentUnable installing extensions from a different feed
I added a new feed from a path, and WAC is telling me it can't read the feed or update the corresponding catalog. I followed the instructions in this link: "https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/using-extensions#installing-extensions-from-a-different-feed". In fact, since my network isn't connected to the internet, I also followed the instructions in this other link: "https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/using-extensions#installing-extensions-on-a-computer-without-internet-connectivity". Regarding adding a file share as a source, it must meet the criteria outlined in this link: "https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/using-extensions#installing-extensions-from-a-different-feed". However, I'm getting these error messages and therefore don't have any extensions available to add:11Views0likes0CommentsWindows Admin Center 2410 not updating Server 2025
Hi, I have 3 new 2025 servers all updated and on the domain. Windows Admin center is working fine with all other servers (2012, 2016, 2019, and 2022). For these 3 new servers, I can connect and login through Adm Center and when I choose the "updates" tab the circle in the middle of the screen spins indefinitely. It never even shows if updates are available or not, it just spins. If I log onto the servers locally, I can see and install updates manually. But when I go back and connect through ADM Center, I just get the spinning circle. I currently only have 3 2025 servers, so for me it appears to be an issue with how they talk to ADM Center concerning updates. (and this makes me hesitate to update other servers) I've tried RDP, registry, Powershell, etc (all through ADM Center). It ALL works, but updates never do. Additionally the 2025 servers are able to communicate just fine to report update status to our WSUS server. If I click the "update history" tab on the updates page in Admin Center, I then see an error, but not sure what would be denying anything, when the connection already seems to be made: "Message We couldn't check update history. Error: (1) RemoteException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (2) RemoteException: The property 'ServerSelection' cannot be found on this object. Verify that the property exists and can be set. (3) RemoteException: You cannot call a method on a null-valued expression. (4) RemoteException: You cannot call a method on a null-valued expression." I tried to temporarily disable the firewall with no change in behavior. The account I'm using is a domain admin account and also added to the local admin group for testing.150Views1like2CommentsVM Load balance is not working
Hi All, I have 4 node cluster in which VMs are manually distributed and now when i enabled the load balance feature via Windows Admin Center it not load balancing the VMs i double checked the load feature via PowerShell and it shows true. kindly suggest form where i should start the troubleshooting.57Views1like3CommentsWindows Admin Center Preview - 2511 English [MSI Corrupt]
When attempting to launch the WindowsAdminCenterPreview_2511.msi, I received an error message (See Below). In addition, when I test the MSI using 7zip, the archive fails to validate. This occurred downloading the installer package twice over a two-day period. My system info is below.68Views1like2CommentsAnnouncing Windows Server vNext Preview Build 26534
Hello Windows Server Insiders! Today we are pleased to release a new build of the next Windows Server Long-Term Servicing Channel (LTSC) Preview that contains both the Desktop Experience and Server Core installation options for Datacenter and Standard editions, Annual Channel for Container Host and Azure Edition (for VM evaluation only). Branding remains, Windows Server 2025, in this preview - when reporting issues please refer to Windows Server vNext preview. If you signed up for Server Flighting, you should receive this new build automatically. This is our last preview for 2025. Please join us in January 2026 for new features and new content! What's New Windows Server Flighting is here!! If you signed up for Server Flighting, you should receive this new build automatically later today. For more information, see Welcome to Windows Insider flighting on Windows Server - Microsoft Community Hub Feedback Hub app is now available for Server Desktop users! The app should automatically update with the latest version, but if it does not, simply Check for updates in the app’s settings tab. Known Issues SMBDirect - Live Migration Users may experience performance issues during live migration of cluster nodes resulting in timeouts triggering failures across the stack. Network traffic is not flowing in through RDMA among cluster nodes resulting in a fallback to TCP/IP and reduced performance of up to 5x Live Migration times causing timeout-related failures. This will be addressed in a future preview release. Download Windows Server Insider Preview (microsoft.com) Flighting: The label for this flight may incorrectly reference Windows 11. However, when selected, the package installed is the Windows Server update. Please ignore the label and proceed with installing your flight. This issue will be addressed in a future release. Available Downloads Downloads to certain countries may not be available. See Microsoft suspends new sales in Russia - Microsoft On the Issues. Windows Server Long-Term Servicing Channel Preview in ISO format in 18 languages, and in VHDX format in English only. Windows Server Datacenter Azure Edition Preview in ISO and VHDX format, English only. Microsoft Server Languages and Optional Features Preview Keys: Keys are valid for preview builds only Server Standard: MFY9F-XBN2F-TYFMP-CCV49-RMYVH Datacenter: 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67 Azure Edition does not accept a key. Symbols: Available on the public symbol server – see Using the Microsoft Symbol Server. Expiration: This Windows Server Preview will expire September 15, 2026. How to Download Registered Insiders may navigate directly to the Windows Server Insider Preview download page. If you have not yet registered as an Insider, see GETTING STARTED WITH SERVER on the Windows Insiders for Business portal. We value your feedback! The most important part of the release cycle is to hear what's working and what needs to be improved, so your feedback is extremely valued. Please use the new Feedback Hub app for Windows Server if you are running a Desktop version of Server. If you are using a Core edition, or if you are unable to use the Feedback Hub app, you can use your registered Windows 10 or Windows 11 Insider device and use the Feedback Hub application. In the app, choose the Windows Server category and then the appropriate subcategory for your feedback. In the title of the Feedback, please indicate the build number you are providing feedback on as shown below to ensure that your issue is attributed to the right version: [Server #####] Title of my feedback See Give Feedback on Windows Server via Feedback Hub for specifics. The Windows Server Insiders space on the Microsoft Tech Communities supports preview builds of the next version of Windows Server. Use the forum to collaborate, share and learn from experts. For versions that have been released to general availability in market, try the Windows Server for IT Pro forum or contact Support for Business. Diagnostic and Usage Information Microsoft collects this information over the internet to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Microsoft server operating systems can be configured to turn diagnostic data off, send Required diagnostic data, or send Optional diagnostic data. During previews, Microsoft asks that you change the default setting to Optional to provide the best automatic feedback and help us improve the final product. Administrators can change the level of information collection through Settings. For details, see http://aka.ms/winserverdata. Also see the Microsoft Privacy Statement. Terms of Use This is pre-release software - it is provided for use "as-is" and is not supported in production environments. Users are responsible for installing any updates that may be made available from Windows Update. All pre-release software made available to you via the Windows Server Insider program is governed by the Insider Terms of Use.246Views2likes0CommentsAnnouncing Windows Server vNext Preview Build 26525
Hello Windows Server Insiders! Today we are pleased to release a new build of the next Windows Server Long-Term Servicing Channel (LTSC) Preview that contains both the Desktop Experience and Server Core installation options for Datacenter and Standard editions, Annual Channel for Container Host and Azure Edition (for VM evaluation only). Branding remains, Windows Server 2025, in this preview - when reporting issues please refer to Windows Server vNext preview. If you signed up for Server Flighting, you should receive this new build automatically. What's New Windows Server Flighting is here!! If you signed up for Server Flighting, you should receive this new build automatically later today. For more information, see Welcome to Windows Insider flighting on Windows Server - Microsoft Community Hub Feedback Hub app is now available for Server Desktop users! The app should automatically update with the latest version, but if it does not, simply Check for updates in the app’s settings tab. Known Issues SMBDirect - Live Migration Users may experience performance issues during live migration of cluster nodes resulting in timeouts triggering failures across the stack. Network traffic is not flowing in through RDMA among cluster nodes resulting in a fallback to TCP/IP and reduced performance of up to 5x Live Migration times causing timeout-related failures. This will be addressed in a future preview release. Download Windows Server Insider Preview (microsoft.com) Flighting: The label for this flight may incorrectly reference Windows 11. However, when selected, the package installed is the Windows Server update. Please ignore the label and proceed with installing your flight. This issue will be addressed in a future release. Available Downloads Downloads to certain countries may not be available. See Microsoft suspends new sales in Russia - Microsoft On the Issues. Windows Server Long-Term Servicing Channel Preview in ISO format in 18 languages, and in VHDX format in English only. Windows Server Datacenter Azure Edition Preview in ISO and VHDX format, English only. Microsoft Server Languages and Optional Features Preview Keys: Keys are valid for preview builds only. Server Standard: MFY9F-XBN2F-TYFMP-CCV49-RMYVH Datacenter: 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67 Azure Edition does not accept a key. Symbols: Available on the public symbol server – see Using the Microsoft Symbol Server. Expiration: This Windows Server Preview will expire September 15, 2026. How to Download Registered Insiders may navigate directly to the Windows Server Insider Preview download page. If you have not yet registered as an Insider, see GETTING STARTED WITH SERVER on the Windows Insiders for Business portal. We value your feedback! The most important part of the release cycle is to hear what's working and what needs to be improved, so your feedback is extremely valued. Please use the new Feedback Hub app for Windows Server if you are running a Desktop version of Server. If you are using a Core edition, or if you are unable to use the Feedback Hub app, you can use your registered Windows 10 or Windows 11 Insider device and use the Feedback Hub application. In the app, choose the Windows Server category and then the appropriate subcategory for your feedback. In the title of the Feedback, please indicate the build number you are providing feedback on as shown below to ensure that your issue is attributed to the right version: [Server #####] Title of my feedback See Give Feedback on Windows Server via Feedback Hub for specifics. The Windows Server Insiders space on the Microsoft Tech Communities supports preview builds of the next version of Windows Server. Use the forum to collaborate, share and learn from experts. For versions that have been released to general availability in market, try the Windows Server for IT Pro forum or contact Support for Business. Diagnostic and Usage Information Microsoft collects this information over the internet to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Microsoft server operating systems can be configured to turn diagnostic data off, send Required diagnostic data, or send Optional diagnostic data. During previews, Microsoft asks that you change the default setting to Optional to provide the best automatic feedback and help us improve the final product. Administrators can change the level of information collection through Settings. For details, see http://aka.ms/winserverdata. Also see the Microsoft Privacy Statement. Terms of Use This is pre-release software - it is provided for use "as-is" and is not supported in production environments. Users are responsible for installing any updates that may be made available from Windows Update. All pre-release software made available to you via the Windows Server Insider program is governed by the Insider Terms of Use.2025-10 Cumulative Update for Windows Server 2019 (KB5066586) Undoes Update on Reboot
We have a Windows Server 2019 Standard which will not install the 2025-10 Cumulative Update for Windows Server 2019 (KB5066586) update. The installation part goes fine, but when the server is rebooted to finalize the update, it goes into "Undoing changes". Then it reboots again, and I am back where I started. The error code is 0x8007000d. I have done the following to debug this: Ran System File Checker sfc /scannow. No errors found. DISM /Online /Cleanup-Image /ScanHealth. No errors found. Ran Windows Update Troubleshooter. No errors found. Shut down Windows Update services. Renamed SoftwareDistribution and Catroot2 folders. Restarted services. No change. Ran ScanDisk. No errors found. Disabled antivirus. No change. Ran Disk Cleanup and manually deleted additional temp files. No change. Checked Event Viewer. Only error is Event 20 which is a failure of the Windows Update Agent. I am out of ideas. If anyone has some, I would much appreciate the help. I am out of ideas.1.1KViews0likes9CommentsSystemSettings. exe on Windows server 2025 crashes after installing Xbox game
I installed the Microsoft App Store on Windows Server and installed Minecraft. However, entering the system>display>graphics tab in the settings will cause the settings to crash.I tested both Bedrock and Java and found this issue. I think any Xbox game in the Microsoft Store should be able to reproduce this issue. + System - Provider [ Name] Application Error [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57} EventID 1000 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2025-12-04T08:55:23.2042032Z EventRecordID 27146 Correlation - Execution [ ProcessID] 10988 [ ThreadID] 20000 Channel Application Computer WIN-JSD290TH0EL - Security [ UserID] S-1-5-21-868965638-952098041-1598110278-1002 - EventData AppName SystemSettings.exe AppVersion 10.0.26100.7019 AppTimeStamp f88449de ModuleName Windows.Gaming.Preview.dll ModuleVersion 10.0.26100.7019 ModuleTimeStamp 8e7f4dfa ExceptionCode c0000005 FaultingOffset 000000000003aadd ProcessId 0x1230 ProcessCreationTime 0x1dc64fbb631455a AppPath C:\Windows\ImmersiveControlPanel\SystemSettings.exe ModulePath C:\Windows\System32\Windows.Gaming.Preview.dll IntegratorReportId f2340132-82be-40d6-9c76-ec8fcbb9d19e PackageFullName windows.immersivecontrolpanel_10.0.8.1000_neutral_neutral_cw5n1h2txyewy PackageRelativeAppId microsoft.windows.immersivecontrolpanel12Views0likes0CommentsAdmin Center choosing the wrong certificate
Windows Admin Center version 2410, build 2.4.2.1. We're encountering an issue following the instructions outlined https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/update-certificate?tabs=powershell when replacing the WAC certificate. We've installed a certificate from a third-party CA in the local machine store. The common name matches the DNS FQDN and hostname of the server. Despite specifying the thumbprint of the 3rd party CA cert with the "Set-WACCertificateSubjectName" cmdlet, WAC binds to a different certificate issued by our internal CA for WinRM. The WinRM cert shares the same common name, but it has a later expiration date. I suspect WAC is picking the certificate with the latest expiration date. This also happens when using the GUI, even when we specify the 3rd party cert during customization. We've confirmed that the NETWORK SERVICE account has rights to the private key on the cert as well. I tried deleting the binding using netsh and rebinding to the updated thumbprint. While this is successful, and the output from "netsh http show sslcert" shows the 3rd party CA cert on the port 443 binding, the browser still presents the Internal-CA cert on 443 even after restarting the WinRM and Windows Admin Center services (and rebooting). It seems like there is an issue when multiple valid certificates exist with the same common name in the machine store. Additionally, the "Set-WACCertificateAcl" seems to fail in this case. The Configuration log contains the error below whenever it is run. Set-WACCertificateAcl: Unable to find machine key path for certificate. Skipping setting access control list. We'd prefer to use the 3rd party cert for the HTTPS port and the internal CA cert for WinRM. Is this possible?Solved50Views0likes1CommentAllow VMs attached to internal switch on hyper-V win2k19 access Internet
Hi, I have 4 VMs attached to an internal switch with IPs 10.10.0.*, assigned 10.10.0.1 to the switch. One of the NICs on the host has the 192.168.1.70 which I shared its connection with the internal switch but I am not able to browse internet from the VMs. What can be missing? Thanks8Views0likes0CommentsWINGET is not recognized as a commandlet on win 2k19 server fresh setup
I have setup a new win2k19, I followed the instructions Install-PackageProvider -Name NuGet -Force | Out-Null Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null Repair-WinGetPackageManager When I try anu winget command I get winget is not recognized as a commandlet9Views0likes0CommentsAllow VMS on hyper-V host on win2k19 attached to internal network interface
Hi, how can allow VMs accssinternet on host Hyper-V on 2019? I have hyper-v on 192.168.0.* and my 4 VMs are 10.10.0.*. I assigned 10.10.0.1 to the virtual switch, on VMs I assigned default gateway to this switch11Views0likes0CommentsQuestion About MAK Windows Activation
Hello everyone. The question is the following. We have a customer with a subscription for Windows Server 2025 Standard - 8 Core License Pack 1 Year quantity 3 (from partner portal). From the servers that the key have been assign i see that the key is on MAK channel. The question is, if i remove the key with dism i will get back a activation? I mean at this time we have 0 activation remaining, if i remove the key the remaining activation number will increase to 1 from 0? I cant found a solid answer on the web so please help. Thanks. Best Regards SG41Views0likes1CommentWindows server 2022 Time (can not change)
Hi I have got windows server 2022 standard - AD Domain controler and I cant change time. when i want to change i see "some of these settings are hidden or managed by your organization" I checked gpo i dint find anything. Do You know where to find ? I really want change time manuwallySolved53KViews1like7CommentsAllow Hyper-V VM attached to Internal Switch access internet and host folders
I have Created an internal switch and attached it to 4 VMs (for a lab setup) on a win2k19 hyper-V host. The hyper-V is in the my local home subnet 192.168.0.1. The 4 VMs are configured with following IPs and gateway. VM1 10.10.0.10 -DefaultGateway 10.10.0.1 VM2 10.10.0.11 -DefaultGateway 10.10.0.1 VM3 10.10.0.12 -DefaultGateway 10.10.0.1 VM4 10.10.0.13 -DefaultGateway 10.10.0.1 In the lab document, it is not indicated how/where to assign the 10.10.0..1 IP? When I check the vEthernet (Private Network), It has "DHCP" for IP and got my local DNS IP. Checking its status, I see DHCP Enabled: Yes Autoconfiguration IPv4 Address: 169.254.32.39 IPv4 Subnet Mask: 255.255.0.0 IPv4 Default Gateway: Not sure where this 169.254.... IP comes from? I tried assigning the IP 10.10.0.1 to this but it fails. In fact I need to allow VMs to access some host folders as well as internet to download some Microsoft tools. Thanks for your help8Views0likes0CommentsSecuring ldap in WIndows AD
Hello everyone. I would like to secure the use of LDAP within an Active Directory domain. My domain has three Windows 2022 DCs. Searching online, I found these suggestions: Enforce LDAPS (LDAP over SSL/TLS) Disable Plain-text LDAP Bindings Block or Restrict Port 389 (Optional but Recommended) Enable Channel Binding Tokens (CBT) Does it make sense to only allow certain users to browse LDAP? Could limiting LDAP browsing to certain users cause problems? Thanks13Views0likes0CommentsBreaking Certutil changes in WS2025
I noticed yesterday that a certutil command I thought I could always rely on no longer works in Server 2025: >certutil -cainfo xchg CertUtil: -CAInfo command FAILED: 0x80070057 (WIN32: 87 ERROR_INVALID_PARAMETER) CertUtil: The parameter is incorrect. Executing certutil -cainfo xchg was a handy command which would ask the local certificate authority to output it's current CA Exchange certificate in Base64 format. If the CA didn't have a valid exchange cert at the time, it would immediately create a new one. Think of a CA Exchange certificate as a short-lived TLS cert which the CA provides clients when they need to upload private key material for archival. Anyway, looking at the help for certutil, the command still exists, however, it requires a new parameter: xchg [Index] -- CA exchange cert So, I figured [Index] had to refer to the CA certificate index. When you initially deploy an ADCS certification authority, the CA's initial certificate is at index 0. When you renew/re-key the CA, the new CA cert is at index 1. I tried using 0 for the [Index] parameter. No dice: >certutil -cainfo xchg 0 CertUtil: -CAInfo command FAILED: 0x80070057 (WIN32: 87 ERROR_INVALID_PARAMETER) CertUtil: The parameter is incorrect. I can't think of what else that parameter would be. Has anyone been able to successfully used this command on WS2025? If so, please share how!16Views0likes0Comments
Events
Recent Blogs
- Applies to: Windows Server 2022 and Windows Server 2025 Failover Clustering Failover Clustering has supported SAN storage since Windows NT 4.0 Server, Enterprise Edition was released in 1997! ...Dec 04, 2025322Views3likes3Comments
- Have you ever seen a user suddenly lose access to a resource, only to discover they were removed from a group—but with no record of when or how it happened? Tracking deleted group memberships in Acti...Dec 01, 2025253Views3likes1Comment