Windows Server Insiders topics

Resize-StorageTier / Expand Volume on Windows Server 2025 Campus Cluster does not work

ThomasS-aus-S — Thu, 23 Jul 2026 11:27:53 GMT

Hi Insider Community!

Want to expand a CSV on an S2D Windows Server 2025 Campus Cluster. (4-nodes)

I get an error message.

Resize-StorageTier : Not enough available capacity

FullyQualifiedErrorId : StorageWMI 40000,Resize-StorageTier

Any hint for me?

Does Microsoft know about the issue?

Best regards

Thomas

Windows Server Datacenter: Azure Edition preview build 29621 now available in Azure

StaceyCL_RM — Wed, 15 Jul 2026 16:38:53 GMT

Hello Windows Server Insiders!

We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 29621 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 29621 | Microsoft Community Hub.

HLK test failing for a KMDF driver with error “A lower driver failed IRP_MN_QUERY_STOP_DEVICE”

RakeshAgrawal — Wed, 15 Jul 2026 12:17:40 GMT

Subject: HLK DF‑PNP Rebalance Fail Restart Device: E: target widens to all volumes; QueryStop fails even without my driver installed.

Hi all,
I’m trying to pass all HLK tests for my driver.

Driver: KMDF PnP volume upper‑filter (attached via UpperFilters to the Volume/Disk class)
OS: Windows Server 2016 Datacenter, build 14393
HLK: 10.1.14393.8069
Test: DF - PNP Rebalance Fail Restart Device (Reliability)
Target volume: E: (NTFS)
Storage: PERC H330 Mini (DELL) (HBA)

Observed behavior

The DQ initially targets E:, but the test later widens to all STORAGE\Volume devnodes:

WDTF_TARGETS : INFO : - Query("IsDevice AND (DriverBinaryNames!='i8042prt.sys') AND (Class!=hdc) AND (Class!=scsiadapter) AND (DsmDevice!=TRUE) AND (IsDevice AND (DriverBinaryNames!='i8042prt.sys') AND (Class!=hdc) AND (Class!=scsiadapter) AND (DsmDevice!=TRUE) AND (DeviceID='STORAGE\VOLUME{01FEB6F1-3717-11F1-9707-806E6F6E6963}#0000000001000000'))")
WDTF_TARGETS : INFO : Target: Volume (E:) STORAGE\VOLUME{01FEB6..
WDTF_SUPPORT : INFO : - ClearSetupAPILogs()
WDTF_TARGETS : INFO : - Query("IsDevice AND (SemiUniqueTargetHardwareIdentifier='STORAGE\Volume')")
WDTF_TARGETS : INFO : Target: Volume STORAGE\VOLUME{01FEB6..
WDTF_TARGETS : INFO : Target: Volume STORAGE\VOLUME{01FEB6..
WDTF_TARGETS : INFO : Target: Volume (C:) STORAGE\VOLUME{01FEB6..
WDTF_TARGETS : INFO : Target: Volume (E:) STORAGE\VOLUME{01FEB6..

Failures report A lower driver failed IRP_MN_QUERY_STOP_DEVICE and PNP.RestartDevice() Win32=1 - Incorrect function.
For each of the 4 target volumes, it shows this error,

DTF_PNP : INFO : - EDTTryStopDeviceFailRestart()
WDTF_PNP : INFO : Target: Volume (C:) STORAGE\VOLUME{01FEB6EF-3717-11F1-9707-806E6F6E6963}#000000001F500000
WDTF_PNP : INFO : Result: A lower driver failed IRP_MN_QUERY_STOP_DEVICE. Rebalance tests cannot proceed...
WDTF_PNP : INFO : - EDTTryStopDeviceFailRestart()
WDTF_PNP : INFO : Target: Volume (E:) STORAGE\VOLUME{01FEB6F1-3717-11F1-9707-806E6F6E6963}#0000000001000000
WDTF_PNP : INFO : Result: A lower driver failed IRP_MN_QUERY_STOP_DEVICE. Rebalance tests cannot proceed...
WDTF_PNP : ERROR : PNP.RestartDevice() Win32=1 - Incorrect function.

WDTF_PNP : ERROR : PNP.RestartDevice() Win32=1 - Incorrect function.

Q1. I have tried multiple variations of the DQ query, and each successfully targets the E volume only. Why does this test later widen to all volumes even when DQ targets only E:? How can I force it to stay on E: ?

Q2. I also ran this on a physical server client and a VM client, but faced the same issue both times. I understand the system/boot volume may veto QueryStop, but why does each volume report ‘a lower driver failed IRP_MN_QUERY_STOP_DEVICE’ in this test?

Q3. I uninstalled my driver completely and still see the same failures when the test is running with only inbox drivers (e.g., msdmfilt.sys, volsnap.sys, volume.sys) listed by Driver Verifier for target E in the logs. That makes me suspect setup/config rather than my driver. Why would only these drivers fail the test as well, what am I missing here?

WDTF_DRIVER_VERIFIER : INFO : - EnableOnAllDriversOfDevices()
WDTF_DRIVER_VERIFIER : INFO : Target: Volume (E:) STORAGE\VOLUME{01FEB6F1-3717-11F1-9707-806E6F6E6963}#0000000001000000
WDTF_DRIVER_VERIFIER : INFO : Driver: msdmfilt.sys
WDTF_DRIVER_VERIFIER : INFO : Driver: volsnap.sys
WDTF_DRIVER_VERIFIER : INFO : Driver: volume.sys

Thanks for any guidance!

Announcing Windows Server vNext Preview Build 29621

StaceyCL_RM — Thu, 16 Jul 2026 00:11:28 GMT

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 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.

Build 29531 established a new Server preview baseline build. Please perform a clean install of Build 29531 (or later) using the installation media linked below.

Please note: Upgrades from Windows Server vNext preview builds older than 29531 are not supported. We encourage all Windows Server vNext preview users to perform a clean install using 29531 or later to successfully upgrade to future Windows Server vNext preview builds.

While upgrades from earlier Windows Server previews (Build 26525 and older) are not technically blocked by setup.exe, a number of known issues have been identified related to upgrades necessitating the establishment of a new baseline build for our Server vNext Preview Program.
The new baseline build (29531) will not be Flighted due to upgrade issues. Flighting support resumed with preview build 29550 or later.

What's New

[NEW] We're excited to announce Trusted Launch for virtual machines (TVMs) on Windows Server—a security feature you can enable when creating Generation 2 VMs.

This initial preview supports TVMs with Secure Boot, vTPM, and vTPM state protection (at rest), managed via PowerShell.

⚠ Not supported in this release:

Moving TVMs to another server

TVMs in failover clusters or Hyper-V Replica

Boot integrity verification

TVMs in Windows Admin Center (WAC)

Instructions

1. Install the latest ServerInsider preview build.

2. Enable Hyper-V (restarts the server):

Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

3. Set the registry keys:

New-Item -Path "HKLM:\SOFTWARE\Microsoft\AszIgvmAgent" -Force 

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\AszIgvmAgent" -Name "TvmWinServer" -Value 1 -PropertyType DWord -Force

4. Enable Trusted Launch:

Enable-WindowsOptionalFeature -Online -FeatureName "IsolatedGuestVm" -NoRestart

5. Verify IGVmAgent is running (should show Running):

Get-Service -Name "IGVmAgent"

If it isn't running, report the issue with the IGVmAgent and IGVmSystem Operational logs (Event Viewer → Applications and Services Logs → Microsoft → Windows).

6. Create an external virtual switch (if needed):

(Get-VMSwitch | Where-Object { $_.SwitchType -eq "External" }).Name

7. Create the TVM. With an existing Gen 2 VHDX:

New-VM -Name <VMName> -Generation 2 -GuestStateIsolationType TrustedLaunch -SwitchName <switch> -VHDPath <path to vhdx> -Path <config path>

Or with a new VHD, then attach a Gen 2–compatible guest OS ISO:

New-VM -Name <VMName> -SwitchName <switch> -NewVHDPath <new VHD path> -NewVHDSizeBytes 40GB -Generation 2 -GuestStateIsolationType TrustedLaunch -Path <config path> 

Add-VMDvdDrive -VMName <VMName> -Path <Guest OS ISO path>

Ensure the DVD drive is first in the firmware boot order so the VM boots from it.

8. Verify isolation type (should return TrustedLaunch):

(Get-VM -Name <VMName>).GuestStateIsolationType

9. Verify guest state protection: Stop the IGVmAgent service and restart the VM—without IGVmAgent running, a Trusted launch VM with guest state protection won't start.

For more information, please review our blog post: Announcing Trusted Launch for Virtual Machines for Windows Server Insiders | Microsoft Community Hub

Quick Machine Recovery available in Windows Server vNext Insider Previews.

Quick machine recovery (QMR) is now available for Server vNext Insiders to test. This feature enables the recovery of Windows Server devices when they encounter boot critical errors that prevent them from booting. QMR can automatically search for cloud‑based remediations to recover from widespread boot failures significantly reducing the burden on IT administrators when multiple devices are impacted. This supports the goals of the Windows Resiliency Initiative by enabling applicable fixes to be delivered through trusted Windows Update to restore affected devices, helping reduce downtime and minimize manual recovery efforts across enterprise environments.

This feature is currently enabled in the latest Server vNext Insider builds for customers to experience test mode. A Group Policy option to enable or disable the feature will be introduced in upcoming builds to provide additional administrative control.

To simulate the quick machine recovery experience, use the following commands from an elevated command prompt:

Enable test mode:

reagentc.exe /SetRecoveryTestmode

Configure Windows to boot to Windows Recovery Environment on the next boot:

reagentc.exe /BootToRe

Reboot your device. The system goes through autoremediation of a simulated crash safely and reboots back to Windows Server.

For more information, please review Quick machine recovery (QMR) and Windows Resiliency Initiative. When providing feedback using Feedback hub, please select QMR from the Recovery and Uninstall category in the app.

NVMe-over-Fabrics (NVMe-oF) extends the NVMe protocol—originally designed for local PCIe-attached SSDs—across a network fabric. Instead of using legacy SCSI-based protocols such as iSCSI or Fibre Channel, NVMe-oF allows a host to communicate directly with remote NVMe controllers using the same NVMe command set used for local devices. In this Insider build, Windows Server supports:

NVMe-oF over TCP (NVMe/TCP), allowing NVMe-oF to run over standard Ethernet networks without specialized hardware.
NVMe-oF over RDMA (NVMe/RDMA), enabling low-latency, high-throughput NVMe access over RDMA-capable networks (for example, RoCE or iWARP) using supported RDMA NICs.

For more information, please visit: Introducing the Windows NVMe-oF Initiator Preview in Windows Server Insiders Builds | Microsoft Community Hub

ReFS Boot is enabled for Windows Server vNext preview builds.

Known Limitations

ReFS Boot systems create a minimum 2GB WinRE partition.
When WinRE cannot be updated due to space constraints, the system may disable WinRE. Disabling WinRE does not remove the partition.
If the WinRE partition is deleted and the boot volume is extended over it, this operation is unrecoverable without a clean install.

For more information, please visit: Resilient File System (ReFS) overview | Microsoft Learn

Feedback Hub app is 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

A race condition in the TLS hybrid key exchange implementation may cause the LSASS service to crash when hybrid groups are negotiated by a TLS server. To avoid this issue until the fix is released, please disable hybrid groups (X25519_MLKEM768, SecP256r1_MLKEM768, SecP384r1_MLKEM1024) using TLS cmdlets or Group Policy, as outlined here.

Server Core Upgrades and AppCompat FOD: Enabling AppCompat FOD after reinstall may fail due to legacy 3rd-party license compatibility issues on Server Core devices. Server Core users may be unable to install the latest AppCompat FOD after upgrading to build 29574. This appears to be limited to Server Core installations with 3rd-party application licenses that fail compatibility checks after upgrade. This will be addressed in a future build.

Upgrading from older builds of Windows Server vNext previews (26525 or older) are not supported. Please perform a clean install of build 29531 or later. Users may experience failures when attempting to upgrade from earlier previews (build 26525 and older). VMs may fail to upgrade or start after upgrade from older preview builds impacting live migration and failover cluster scenarios.

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 vNext 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.

Windows Crash During NVMe Over TCP Disk Disconnect

ketanbaitule — Tue, 23 Jun 2026 18:17:09 GMT

While evaluating the Windows NVMe Initiator, we have observed that disconnecting an NVMe disk frequently results in a Windows system crash.

This occurs during the disconnect operation and appears to be reproducible in our test environment.

Questions:

Has anyone else encountered similar behavior?
Are there any known issues related to NVMe/TCP disconnect handling?
Are there recommended troubleshooting steps, logs, or diagnostics that we should collect to help identify the root cause?

Any insights would be greatly appreciated.

Multiple Namespace Detection in Windows NVMe Over TCP Initiator

ketanbaitule — Tue, 23 Jun 2026 18:13:29 GMT

We are evaluating the Windows NVMe Initiator and have observed an issue with namespace handling.

Our NVMe subsystem contains multiple namespaces. When we connect to the subsystem over TCP and establish connections to all namespaces, they are all shown as connected under the controller. However, only one namespace (shared block device) is exposed and accessible within Windows.

Based on our testing, it appears that the initiator may be mapping only the first namespace associated with a given Friendly Name. We were able to connect another subsystem, whose friendly name was different.

Questions:

Is support for multiple namespaces within a single subsystem currently available in the Windows NVMe Initiator?
If so, are there any configuration requirements or known limitations related to namespace discovery and mapping?
Is the initiator expected to expose all connected namespaces as separate disks within Windows?

We would appreciate any guidance or clarification on the expected behavior.

Follow up to Azure Host OS Article

Steskalj — Wed, 17 Jun 2026 15:32:17 GMT

When will there be a follow up to the Azure Host OS article? It would be great to learn more about how the NT kernel is being used inside Microsoft outside of standard Windows. This is the article:

Azure Host OS

Windows Server Datacenter: Azure Edition preview build 29602 now available in Azure

StaceyCL_RM — Wed, 10 Jun 2026 16:07:06 GMT

Hello Windows Server Insiders!

We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 29602 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 29602 | Microsoft Community Hub.

Server flighting not being offered on 29595 on 3 VMs

kevdog98 — Tue, 09 Jun 2026 20:58:31 GMT

Hi,

I'm on not getting build 29602 offered as a flight through Windows update on any of my VMs and I can figure out why, it has not been offered in the last couple of builds. Is anyone else experiencing this or have any ideas of how to fix this? Optional diagnostics are on and they are connected to my account under insider setting in Windows update settings. I am just not getting offered the build flight.

Thanks

Kevin

Announcing Windows Server vNext Preview Build 29602

StaceyCL_RM — Mon, 08 Jun 2026 20:28:46 GMT

Hello Windows Server Insiders!

Build 29531 established a new Server preview baseline build. Please perform a clean install of Build 29531 (or later) using the installation media linked below.

While upgrades from earlier Windows Server previews (Build 26525 and older) are not technically blocked by setup.exe, a number of known issues have been identified related to upgrades necessitating the establishment of a new baseline build for our Server vNext Preview Program.
The new baseline build (29531) will not be Flighted due to upgrade issues. Flighting support resumed with preview build 29550 or later.

What's New

Quick Machine Recovery available in Windows Server vNext Insider Previews.

To simulate the quick machine recovery experience, use the following commands from an elevated command prompt:

1. Enable test mode:

reagentc.exe /SetRecoveryTestmode

2. Configure Windows to boot to Windows Recovery Environment on the next boot:

reagentc.exe /BootToRe

3. Reboot your device.The system goes through autoremediation of a simulated crash safely and reboots back to Windows Server.

NVMe-oF over TCP (NVMe/TCP), allowing NVMe-oF to run over standard Ethernet networks without specialized hardware.
NVMe-oF over RDMA (NVMe/RDMA), enabling low-latency, high-throughput NVMe access over RDMA-capable networks (for example, RoCE or iWARP) using supported RDMA NICs.

For more information, please visit: Introducing the Windows NVMe-oF Initiator Preview in Windows Server Insiders Builds | Microsoft Community Hub

ReFS Boot is enabled for Windows Server vNext preview builds.

Known Limitations

ReFS Boot systems create a minimum 2GB WinRE partition.
When WinRE cannot be updated due to space constraints, the system may disable WinRE. Disabling WinRE does not remove the partition.
If the WinRE partition is deleted and the boot volume is extended over it, this operation is unrecoverable without a clean install.

For more information, please visit: Resilient File System (ReFS) overview | Microsoft Learn

Known Issues

[NEW] A race condition in the TLS hybrid key exchange implementation may cause the LSASS service to crash when hybrid groups are negotiated by a TLS server. To avoid this issue until the fix is released, please disable hybrid groups (X25519_MLKEM768, SecP256r1_MLKEM768, SecP384r1_MLKEM1024) using TLS cmdlets or Group Policy, as outlined here.

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

We value your feedback!

     [Server #####] Title of my feedback

See Give Feedback on Windows Server via Feedback Hub for specifics.

Diagnostic and Usage Information

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

in-place upgrade fails from b29574 to latest vnext b29595

Karl-WE — Tue, 30 Jun 2026 07:20:53 GMT

Hi all,

is anyone facing the same issue IPU fails on a fresh b29574 upgrading to latest using WU?

provided more information in feedback hub. Thanks for sharing your experience.

as a next attempt I will mount ISO and upgrade. mind b29574 was the base bare metal installation so no previous IPUs involved.
related feedback https://aka.ms/AA11g03n

Tested Upgrade Paths

Baseline	TargetOS	Result
29574	29595	fails
29574	29602	fails
29595	29602	fails

Installed roles:
- Hyper-V

Specialities:

tried SysWOW64 removal but failed to do so https://aka.ms/AA11eyy5
OS Drive is ReFS, potientially related https://aka.ms/AA11eyy8

<?xml version="1.0" encoding="utf-16"?> <SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag"> <Version>1.7.0.0</Version> <ProfileName>FindRollbackFailure</ProfileName> <ProfileGuid>3A43C9B5-05B3-4F7C-A955-88F991BB5A48</ProfileGuid> <FailureData>0xc1900101-0x20017 Error: SetupDiag reports rollback failure found.Last Phase = FinalizeLast Operation = Cleanup external drivers after installationError = 0xC1900101-0x20017</FailureData> <FailureData>LogEntry: </FailureData> <FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData> <FailureDetails>RollbackErrorCode = 0xC1900101, ExtendedCode = 0x20017, LastOperation = Cleanup external drivers after installation, LastPhase = Finalize</FailureDetails> <Setup360Result>0xc1900101</Setup360Result> <Setup360Extended>0x20017</Setup360Extended> <SetupPhaseInfo> <PhaseName>Finalize</PhaseName> <PhaseStartTime>06/06/2026 13:16:53</PhaseStartTime> <PhaseEndTime>06/06/2026 13:17:35</PhaseEndTime> <PhaseTimeDelta>0:00:00:42.0000000</PhaseTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupPhaseInfo> <SetupOperationInfo> <OperationName>Cleanup external drivers after installation</OperationName> <OperationStartTime>06/06/2026 13:17:35</OperationStartTime> <OperationEndTime>06/06/2026 13:17:35</OperationEndTime> <OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta> <CompletedSuccessfully>true</CompletedSuccessfully> </SetupOperationInfo> </SetupDiag>

also noticing uncommon links in root as if I were using FAT32.

BLOG: Windows Insiders - State of vbscript deprecation June 2026

Karl-WE — Fri, 12 Jun 2026 15:01:33 GMT

While I greatly appreciate the decision of vbscript / cscript / wscript removal, with security and hardening in mind – I would also appreciate if Microsoft could be actively using the vNext release channel, preparing for feature removal.

With this blogpost, I am sharing my point of view on the state of dependencies I am seeing in this regard, focusing on a way forward towards the full removal of vbscript. My findings show, that there is a quite some action required, and this stands a bit contrary to the announcement, Microsoft intends removing the optional feature of vbscript by default with the upcoming release - anticipated by fall 2027.

Given my lessons learned from Secure Boot CA2023 exchange initiative, Microsoft guidance, foremost PowerShell based scripts, tooling and dashboards have been released quite late, looking at the timeline, considering the impact and scale customers had to deal with, and consequences for their security posture if they are not ready and done, with first certificates to expire soon.
Taking this learning into account and and projecting it to vbscript deprecration I come to the following conclusion:

SMB customers, enterprises, Microsoft Products, see below, are required to be updated or replaced, in order of adopting this change.
I believe there is quite some communication and learning curve required for users, admins, enterprises and OEMs in adopting the implicated change and including changed workflows and automation processes.

Looking forward to the next Windows Insider and esp. Windows Server Insider vNext builds!
Both Windows Insiders and Windows Server Insiders, also including ISV and OEMs may assist in reviewing and validating the new workflows required - assuming vbscript deprecation is in effect, as planned.

Without further ado, I am sharing my observations in regard to VBScript deprecation. I will try to keep this blogpost updated as soon I am aware about public facing changes.

Third-Party

AMD

Chipset drivers so far is one of the major non MSFT related blockers.

Suggestions:
Microsoft should initiate talks with AMD and other ISV and OEMs fixing their dependencies, also offering other solutions, see below.
Currently AMD Chipset drivers silently using vbscript calls checking for OS and HW platform compatibility. The installer fails when vbscript optional feature is removed.

OEM, ISV and Enterprise

Potentially affected:

expected dependencies for imaging, deployment and management workflows. Related or unrelated to Microsoft products.
LOB apps
custom Office Integration
logon and logoff scripts
setup and installers

Recommendation:
Please observe vbscript related events in Windows Event Viewer at scale using PowerShell, Remoting or Windows Event Subscriptions:

VBScriptDeprecationAlert Event ID 4096 VBScript is scheduled for deprecation. Our telemetry indicates that your system is currently utilizing VBScript. We strongly recommend identifying and migrating away from any VBScript dependencies at the earliest. The following process has been detected as using VBScript. The associated process tree and call stack are provided below to assist in identifying the scenario in which VBScript was invoked.

Microsoft

Windows Server and Client OS

affected: slmgr.vbs / printer management vbscripts / product activation logic and UX,
setup.exe, slui.exe

Office 2024 LTSC
affected: slmgr.vbs / ospp.vbs / Office deployment toolkit / product activation logic
Microsoft has placed a new PowerShell based script into the respective OSPP folder.
This script however is rather offering on checking licensing and cannot activate the Office product at this time.

Microsoft 365 Business, Enterprise, Home, Family
Affected: ospp.vbs
despite being subscription based will also trouble with activation once vbscript is removed

Sconfig
Related to product activation. no changes so far, relies on external changes. The script itself is safe to comply with the change, now it has been reworked and updated using PowerShell , starting Windows Server 2022.

WinRM
Affected: the whole WinRM configuration command, e.g. winrm qc

Windows Server Roles and Features: KMS / ADBA

Potentially affected as they rely on slmgr for adding and removing CSVLK keys.

Windows Server Roles and Features: IIS
legacy IIS extension management.

Windows Server Roles and Features: WSUS
related deployment and configuration scripts.

System Center Products incl. ConfigMgr
there might be depencendies for OS deployments in regard to OS imaging.

ADK, esp. Windows Imaging Tools and VAMT 3
potentially affected. Need to adopt changes in regard to activation and other operations.

Suggestions:

Recommending all these scripts being converted using Claude or Copilot from vbscript to PowerShell.
Providing a serviceable PS modules, especially for printer management, product activation, which enables enterprises to automate their activations and printers, even though Microsoft is going to remove vbscript. The modules should be improved for existing day two adminstration tasks and workflows. slmgr, in particular, had some nuances that were tedious such as identifying and removing (stale) activation keys.
Existing tools like slmgr and other will not work well in remoting. They do something but their interactive parts and outputs are reserved for interactive user sessions. Example: you can use slmgr in a remote PowerShell session for installing and activating a key but therer is no result return to the shell.
Combining slui.exe and slmgr.vbs into aforementioned improvements in functionality and syntax.
Consider support for PowerShell 7 in WinRE and Offline Setup phase.

Many thanks for your consideration!

Directory: C:\Windows\System32\Printing_Admin_Scripts\en-US Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 10:43 AM 98756 prncnfg.vbs -a--- 4/16/2026 10:43 AM 66172 prndrvr.vbs -a--- 4/16/2026 10:43 AM 62698 prnjobs.vbs -a--- 4/16/2026 10:43 AM 95908 prnmngr.vbs -a--- 4/16/2026 10:43 AM 71616 prnport.vbs -a--- 4/16/2026 10:43 AM 44278 prnqctl.vbs -a--- 4/16/2026 10:43 AM 22612 pubprn.vbs Directory: C:\Windows\System32 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 4119 CallUxxProvider.vbs -a--- 4/16/2026 9:14 AM 145712 slmgr.vbs -a--- 4/16/2026 9:14 AM 1720 SyncAppvPublishingServer.vbs -a--- 4/16/2026 9:14 AM 204072 winrm.vbs Directory: C:\Windows\SysWOW64\Printing_Admin_Scripts\en-US Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 10:43 AM 98756 prncnfg.vbs -a--- 4/16/2026 10:43 AM 66172 prndrvr.vbs -a--- 4/16/2026 10:43 AM 62698 prnjobs.vbs -a--- 4/16/2026 10:43 AM 95908 prnmngr.vbs -a--- 4/16/2026 10:43 AM 71616 prnport.vbs -a--- 4/16/2026 10:43 AM 44278 prnqctl.vbs -a--- 4/16/2026 10:43 AM 22612 pubprn.vbs Directory: C:\Windows\SysWOW64 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 145712 slmgr.vbs -a--- 4/16/2026 9:14 AM 204072 winrm.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-a..nagement-appvclient_31bf3856ad364e35_10.0.29574.1000_none_0895f7c27f109b8a Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 1720 SyncAppvPublishingServer.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.29574.1000_none_ba69ed912e209e30 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 98133 adsutil.vbs -a--- 4/16/2026 9:14 AM 41401 IIsExt.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.29574.1000_en-us_ 4ad0e09e0339f1ef Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 10:43 AM 98756 prncnfg.vbs -a--- 4/16/2026 10:43 AM 66172 prndrvr.vbs -a--- 4/16/2026 10:43 AM 62698 prnjobs.vbs -a--- 4/16/2026 10:43 AM 95908 prnmngr.vbs -a--- 4/16/2026 10:43 AM 71616 prnport.vbs -a--- 4/16/2026 10:43 AM 44278 prnqctl.vbs -a--- 4/16/2026 10:43 AM 22612 pubprn.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-s..r-core-mgmtprovider_31bf3856ad364e35_10.0.29574.1000_none_62cec50667f8da2a Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 4119 CallUxxProvider.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.29574.1000_none_81bcc6c67609fdb9 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 145712 slmgr.vbs Directory: C:\Windows\WinSxS\amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.29574.1000_none_0688f60763f16bc8 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 204072 winrm.vbs Directory: C:\Windows\WinSxS\amd64_updateservices-services_31bf3856ad364e35_10.0.29574.1000_none_bae89f3176313538 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 8332 DynamicCompression.vbs -a--- 4/16/2026 9:14 AM 4289 SetAppPool.vbs -a--- 4/16/2026 9:14 AM 5813 SetMimeMap.vbs Directory: C:\Windows\WinSxS\wow64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_10.0.29574.1000_none_c4be97e36281602b Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 41401 IIsExt.vbs Directory: C:\Windows\WinSxS\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_10.0.29574.1000_en-us_ 55258af0379ab3ea Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 10:43 AM 98756 prncnfg.vbs -a--- 4/16/2026 10:43 AM 66172 prndrvr.vbs -a--- 4/16/2026 10:43 AM 62698 prnjobs.vbs -a--- 4/16/2026 10:43 AM 95908 prnmngr.vbs -a--- 4/16/2026 10:43 AM 71616 prnport.vbs -a--- 4/16/2026 10:43 AM 44278 prnqctl.vbs -a--- 4/16/2026 10:43 AM 22612 pubprn.vbs Directory: C:\Windows\WinSxS\wow64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.29574.1000_none_8c117118aa6abfb4 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 145712 slmgr.vbs Directory: C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.29574.1000_none_10dda05998522dc3 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 4/16/2026 9:14 AM 204072 winrm.vbs

related announcements:

https://techcommunity.microsoft.com/blog/Windows-ITPro-blog/vbscript-deprecation-timelines-and-next-steps/4148301

Windows Server vNext cannot be activated

Karl-WE — Mon, 22 Jun 2026 18:46:46 GMT

Error Code 0xC004F012 when trying to activate WS vNext Datacenter with Key 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67.

vbscript is removed, implying the future removal of this component from the OS.

It appears that Windows Activation relies on vbscript.

I would wish for a native PowerShell support / module instead of vbscript.
Is this something that is on the roadmap?

Windows Server Datacenter: Azure Edition preview build 29595 now available in Azure

StaceyCL_RM — Wed, 27 May 2026 19:16:12 GMT

Hello Windows Server Insiders!

We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 29595 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 29595 | Microsoft Community Hub.

Announcing Windows Server vNext Preview Build 29595

StaceyCL_RM — Tue, 26 May 2026 17:02:07 GMT

Hello Windows Server Insiders!

Build 29531 established a new Server preview baseline build. Please perform a clean install of Build 29531 (or later) using the installation media linked below.

While upgrades from earlier Windows Server previews (Build 26525 and older) are not technically blocked by setup.exe, a number of known issues have been identified related to upgrades necessitating the establishment of a new baseline build for our Server vNext Preview Program.
The new baseline build (29531) will not be Flighted due to upgrade issues. Flighting support resumed with preview build 29550 or later.

What's New

Quick Machine Recovery available in Windows Server vNext Insider Previews.

To simulate the quick machine recovery experience, use the following commands from an elevated command prompt:

1. Enable test mode:

reagentc.exe /SetRecoveryTestmode

2. Configure Windows to boot to Windows Recovery Environment on the next boot:

reagentc.exe /BootToRe

3. Reboot your device. The system goes through autoremediation of a simulated crash safely and reboots back to Windows Server.

NVMe-oF over TCP (NVMe/TCP), allowing NVMe-oF to run over standard Ethernet networks without specialized hardware.
NVMe-oF over RDMA (NVMe/RDMA), enabling low-latency, high-throughput NVMe access over RDMA-capable networks (for example, RoCE or iWARP) using supported RDMA NICs.

For more information, please visit: Introducing the Windows NVMe-oF Initiator Preview in Windows Server Insiders Builds | Microsoft Community Hub

ReFS Boot is enabled for Windows Server vNext preview builds.

Known Limitations

ReFS Boot systems create a minimum 2GB WinRE partition.
When WinRE cannot be updated due to space constraints, the system may disable WinRE. Disabling WinRE does not remove the partition.
If the WinRE partition is deleted and the boot volume is extended over it, this operation is unrecoverable without a clean install.

For more information, please visit: Resilient File System (ReFS) overview | Microsoft Learn

Known Issues

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

We value your feedback!

     [Server #####] Title of my feedback

See Give Feedback on Windows Server via Feedback Hub for specifics.

Diagnostic and Usage Information

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

Windows Server Datacenter: Azure Edition preview build 29585 now available in Azure

StaceyCL_RM — Fri, 15 May 2026 20:38:42 GMT

Hello Windows Server Insiders!

We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 29585 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 29585 | Microsoft Community Hub.

Announcing Windows Server vNext Preview Build 29585

StaceyCL_RM — Mon, 11 May 2026 17:06:03 GMT

Hello Windows Server Insiders!

Build 29531 established a new Server preview baseline build. Please perform a clean install of Build 29531 (or later) using the installation media linked below.

While upgrades from earlier Windows Server previews (Build 26525 and older) are not technically blocked by setup.exe, a number of known issues have been identified related to upgrades necessitating the establishment of a new baseline build for our Server vNext Preview Program.
The new baseline build (29531) will not be Flighted due to upgrade issues. Flighting support resumed with preview build 29550 or later.

Please join us this week for Windows Server Summit 2026

Windows Server Summit 2026 is happening this week (May 11 - May 13). Please join us for this online event to learn about the latest updates in Windows Server 2025 and what's coming in vNext. For more information and to register, please visit Windows Server Summit - May 11-13, 2026 - Microsoft Event page.

What's New

Quick Machine Recovery available in Windows Server vNext Insider Previews.

This feature is currently enabled in the latest Server vNext Insider builds for customers to experience test mode. A Group Policy option to enable or disable the feature will be introduced in upcoming builds to provide additional administrative control.

To simulate the quick machine recovery experience, use the following commands from an elevated command prompt:

1. Enable test mode:

reagentc.exe /SetRecoveryTestmode

2. Configure Windows to boot to Windows Recovery Environment on the next boot:

reagentc.exe /BootToRe

3. Reboot your device. The system goes through autoremediation of a simulated crash safely and reboots back to Windows Server.

NVMe-oF over TCP (NVMe/TCP), allowing NVMe-oF to run over standard Ethernet networks without specialized hardware.
NVMe-oF over RDMA (NVMe/RDMA), enabling low-latency, high-throughput NVMe access over RDMA-capable networks (for example, RoCE or iWARP) using supported RDMA NICs.

For more information, please visit: Introducing the Windows NVMe-oF Initiator Preview in Windows Server Insiders Builds | Microsoft Community Hub

ReFS Boot is enabled for Windows Server vNext preview builds.

Known Limitations

ReFS Boot systems create a minimum 2GB WinRE partition.
When WinRE cannot be updated due to space constraints, the system may disable WinRE. Disabling WinRE does not remove the partition.
If the WinRE partition is deleted and the boot volume is extended over it, this operation is unrecoverable without a clean install.

For more information, please visit: Resilient File System (ReFS) overview | Microsoft Learn

Known Issues

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

We value your feedback!

     [Server #####] Title of my feedback

See Give Feedback on Windows Server via Feedback Hub for specifics.

Diagnostic and Usage Information

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

CXL Memory Expansion on WinServer 2025

isheaffer — Fri, 01 May 2026 15:45:04 GMT

I'm looking to find out if on window server 2025 is CXL Type 3 in memory expansion mode is validated "GA" and if so which cxl devices. I'm having issues finding this information. Anyone know and able to share?

Windows Server Datacenter: Azure Edition preview build 29574 now available in Azure

StaceyCL_RM — Wed, 29 Apr 2026 17:16:00 GMT

Hello Windows Server Insiders!

We welcome you to try Windows Server vNext Datacenter: Azure Edition preview build 29574 in both Desktop experience and Core version on the Microsoft Server Operating Systems Preview offer in Azure. Azure Edition is optimized for operation in the Azure environment. For additional information, see Preview: Windows Server VNext Datacenter (Azure Edition) for Azure Automanage on Microsoft Docs. For more information about this build, see Announcing Windows Server vNext Preview Build 29574 | Microsoft Community Hub.

Announcing Windows Server vNext Preview Build 29574

StaceyCL_RM — Mon, 27 Apr 2026 17:07:00 GMT

Hello Windows Server Insiders!

Build 29531 established a new Server preview baseline build. Please perform a clean install of Build 29531 (or later) using the installation media linked below.

While upgrades from earlier Windows Server previews (Build 26525 and older) are not technically blocked by setup.exe, a number of known issues have been identified related to upgrades necessitating the establishment of a new baseline build for our Server vNext Preview Program.
The new baseline build (29531) will not be Flighted due to upgrade issues. Flighting support resumed with preview build 29550 or later.

What's New

[NEW] Introducing Quick Machine Recovery in Windows Server vNext Insider Previews.

To simulate the quick machine recovery experience, use the following commands from an elevated command prompt:

1. Enable test mode:

reagentc.exe /SetRecoveryTestmode

2. Configure Windows to boot to Windows Recovery Environment on the next boot:

reagentc.exe /BootToRe

3. Reboot your device. The system goes through autoremediation of a simulated crash safely and reboots back to Windows Server.

NVMe-oF over TCP (NVMe/TCP), allowing NVMe-oF to run over standard Ethernet networks without specialized hardware.
NVMe-oF over RDMA (NVMe/RDMA), enabling low-latency, high-throughput NVMe access over RDMA-capable networks (for example, RoCE or iWARP) using supported RDMA NICs.

For more information, please visit: Introducing the Windows NVMe-oF Initiator Preview in Windows Server Insiders Builds | Microsoft Community Hub

ReFS Boot is enabled for Windows Server vNext preview builds.

Known Limitations

ReFS Boot systems create a minimum 2GB WinRE partition.
When WinRE cannot be updated due to space constraints, the system may disable WinRE. Disabling WinRE does not remove the partition.
If the WinRE partition is deleted and the boot volume is extended over it, this operation is unrecoverable without a clean install.

For more information, please visit: Resilient File System (ReFS) overview | Microsoft Learn

Known Issues

Upgrading from earlier builds of Windows Server vNext previews (26525 or older) are not supported. Please perform a clean install of build 29531 or later. Users may experience failures when attempting to upgrade from earlier previews (build 26525 and older). VMs may fail to upgrade or start after upgrade from older preview builds impacting live migration and failover cluster scenarios.

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

We value your feedback!

     [Server #####] Title of my feedback

See Give Feedback on Windows Server via Feedback Hub for specifics.

Diagnostic and Usage Information

Administrators can change the level of information collection through Settings. For details, see http://aka.ms/winserverdata. Also see the Microsoft Privacy Statement.