Windows Server

Winsage
March 25, 2026
Microsoft has removed a registry hack that allowed users to unlock faster speeds for NVMe SSDs, following the introduction of native NVMe SSD support in Windows Server 2025. This change aims to enhance SSD performance by eliminating the need for the previous method that translated NVMe commands into SCSI commands, which caused latency and reduced speeds. Currently, Windows 11 does not support native NVMe SSD processing and continues to use the older command conversion method. Although the registry hack is now obsolete, third-party tools like ViVeTool can still enable this feature through specific commands, but using such tools carries risks.
Winsage
March 24, 2026
The short-term effects of Windows 11 on Azure's performance are muted due to many Azure customers operating in mixed environments that often include Linux-based systems and cross-platform tools. This shift reflects a move away from the idea of "run Windows everywhere" to "meet customers where they are." The introduction of Windows 11 could damage Microsoft's credibility and influence purchasing decisions, leading to skepticism from CIOs and architects regarding broader Microsoft platform investments. Historically, Microsoft's strength has been in stack continuity, with seamless integration across its products, but the company now faces the challenge of maintaining ecosystem cohesion while adapting to diverse customer needs.
Winsage
March 23, 2026
Microsoft has disabled a registry modification that allowed Windows 11 users to activate native NVMe support. This change was noted in the latest Insider builds of Windows 11. The registry trick had previously improved random write performance by up to 85% and enhanced random I/O across various drives and CPUs. However, it caused compatibility issues with third-party SSD management tools and could trigger recovery prompts from BitLocker. Users can still enable native NVMe support using a third-party utility called ViVeTool, which requires an elevated command prompt and a system reboot. The timeline for official native NVMe support in Windows 11 versions 25H2 and 26H2 is uncertain.
Winsage
March 17, 2026
Microsoft is implementing a two-phase initiative to disable the hands-free deployment feature in Windows Deployment Services (WDS) due to a critical remote code execution vulnerability (CVE-2026-0386) identified on January 13, 2026. This vulnerability arises from improper access control related to the Unattend.xml file, which is transmitted over an unauthenticated RPC channel, allowing attackers on the same network segment to exploit it. Successful exploitation could grant SYSTEM-level privileges and compromise OS deployment images. The initiative includes: - Phase 1 (January 13, 2026): The hands-free deployment feature will remain operational but can be disabled. New Event Log alerts and registry key controls will be introduced to enforce secure practices. - Phase 2 (April 2026): The hands-free deployment feature will be completely disabled by default for administrators who have not modified registry settings. Administrators can temporarily re-enable the feature by setting AllowHandsFreeFunctionality = 1, but this is not secure. Recommendations include reviewing WDS configurations, applying security updates, setting registry keys for secure behavior, monitoring Event Viewer for alerts, and considering alternative deployment methods. Microsoft’s KB article 5074952 provides further guidance for impacted organizations.
Winsage
March 11, 2026
Microsoft's native NVMe driver, initially released for Windows Server 2025, is now available for Windows 11, enhancing SSD performance. Users can achieve performance gains through registry tweaks. Benchmark tests showed significant improvements in random read bandwidth and input/output operations per second (IOPS). In a test with AMD EPYC 9754 processors and Solidigm P5316 SSDs, the following results were observed: - 4K Random Read: Non-Native Driver 6.1 GiB/s, Native Driver 10.058 GiB/s (+64.89%) - 64K Random Read: Non-Native Driver 74.291 GiB/s, Native Driver 91.165 GiB/s (+22.71%) - 64K Sequential Read: Non-Native Driver 35.596 GiB/s, Native Driver 35.623 GiB/s (+0.08%) - 128K Sequential Read: Non-Native Driver 86.791 GiB/s, Native Driver 92.562 GiB/s (+6.65%) - 64K Sequential Write: Non-Native Driver 44.67 GiB/s, Native Driver 50.087 GiB/s (+12.13%) - 128K Sequential Write: Non-Native Driver 50.477 GiB/s, Native Driver 50.079 GiB/s (-0.79%) Random read latency decreased significantly, with 4K and 64K read times dropping by 38.46% and 13.39%, respectively. However, 64K sequential write latency increased by 39.85%, while 128K sequential write latency rose by 12.43%. The NVMe driver also showed favorable CPU usage results during sequential read and write operations. It is not enabled by default in Windows 11, requiring users to make registry changes to activate it.
Winsage
March 11, 2026
Microsoft's Hyper-V is a hardware virtualization platform integrated into Windows 11 Professional, Enterprise, and Education editions, allowing users to host multiple virtual machines (VMs) on a single computer. It operates using a type 1 hypervisor directly on hardware, enabling VMs to share resources like CPU, memory, and storage. Hyper-V includes features such as dynamic memory allocation, software-defined networking, and saved checkpoints. IT administrators may need to disable Hyper-V due to compatibility issues with third-party virtualization software, high-precision applications, or driver conflicts. Disabling Hyper-V can also affect security features reliant on it, such as virtualization-based security (VBS) and Device Guard. Methods to disable Hyper-V include: 1. Using the Windows Features dialog. 2. Executing a PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All, HypervisorPlatform, VirtualMachinePlatform. 3. Running a DISM command: dism /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-All /FeatureName:HypervisorPlatform /FeatureName:VirtualMachinePlatform. 4. Using the bcdedit command: bcdedit /set hypervisorlaunchtype off. 5. Modifying Group Policy to disable VBS. 6. Editing the Windows Registry to disable VBS or Credential Guard. For multiple managed computers, administrators can create and execute a PowerShell script or use Group Policy Objects to streamline the process. Testing in a controlled environment is recommended to ensure desired outcomes without compromising security or functionality.
Winsage
March 11, 2026
Microsoft Corp. has released security updates addressing at least 77 vulnerabilities across its Windows operating systems and various software applications. Key vulnerabilities include: - CVE-2026-21262: Allows an attacker to elevate privileges on SQL Server 2016 and later, with a CVSS v3 base score of 8.8. - CVE-2026-26127: Affects applications running on .NET, potentially leading to denial of service. - CVE-2026-26113 and CVE-2026-26110: Remote code execution flaws in Microsoft Office exploitable by viewing malicious messages in the Preview Pane. - CVE-2026-24291, CVE-2026-24294, CVE-2026-24289, and CVE-2026-25187: Privilege escalation vulnerabilities rated CVSS 7.8. - CVE-2026-21536: A critical remote code execution bug identified by an AI agent, marking a shift toward AI-driven vulnerability discovery. Additionally, Microsoft previously addressed nine browser vulnerabilities and issued an out-of-band update on March 2 for Windows Server 2022. Adobe has released updates for 80 vulnerabilities across its products, and Mozilla Firefox version 148.0.2 has resolved three high-severity CVEs.
Winsage
March 6, 2026
Microsoft is transitioning to a universal printer driver system to address issues related to legacy printer drivers in Windows. Starting with Windows 10 version 21H2, a universal printer driver compatible with Mopria standards has been integrated and is being enhanced through updates. A phased approach to legacy printer drivers will begin in January 2026, when Windows Update will stop allowing new legacy drivers for Windows 11 and Windows Server 2005. Existing drivers for older printers will continue to function. In July 2026, Windows 11 will prioritize the universal driver over legacy drivers, and by July 2027, updates for legacy drivers will be limited to security fixes. There is no set timeline for the complete discontinuation of old printers and their drivers.
Winsage
March 6, 2026
On December 15, 2025, Microsoft announced native NVMe support in Windows Server 2025, marking a significant evolution in data management and access. The new architecture replaces Disk.sys with NVMeDisk.sys, allowing direct communication from the filesystem to hardware via StorMQ, eliminating latency and enhancing performance. Testing revealed increased read speeds, particularly in random 4K and 64K benchmarks, with significant reductions in average read latency and lower CPU usage during sequential operations. Write operations showed modest improvements. A registry modification is required to enable this feature, and caution is advised due to potential complications with NVMe drives when deduplication is enabled.
Search