kernel Archives

Winsage

July 3, 2026

Intel’s major driver update for Windows 11 delivers performance boost, ships with Microsoft’s quality promise

Microsoft's Driver Quality Initiative (DQI) aims to enhance driver stability and predictability for Windows 11, with Intel recently releasing Bluetooth and Wi-Fi driver updates (version 24.50.0) that align with this initiative. The DQI, discussed at the Windows Hardware Engineering Conference (WinHEC) in May 2026, involves collaboration with major tech companies like Intel, AMD, and Qualcomm to improve driver reliability. Microsoft has mandated OEMs to follow strict security policies and adopt Microsoft-authored class drivers to reduce kernel interference and enhance performance and security. The initiative includes quality benchmarks focused on stability, functionality, performance, and reduced power impact. Intel is the first to adopt these changes, with AMD also committing to high-quality driver collaboration.

Winsage

July 2, 2026

Microsoft’s new Azure Linux 4.0 is here, and it could replace Windows Server in the enterprise

Microsoft has released Azure Linux 4.0, transitioning it from an internal tool to a server operating system that users can install on their own servers and virtual machines. Azure Linux 4.0 is built on Fedora Linux, allowing the use of RPMs and ensuring compatibility with Azure's cloud platform. The beta version features a hardened Linux kernel 6.18, optimized for performance on Hyper-V and Azure virtual machines, and incorporates SELinux-based security measures without a graphical user interface. In the Azure Marketplace, it is marketed as a "Microsoft-built Linux distribution for Azure," with formal support available for deployments on Azure but not for standalone hardware. The Azure Linux GitHub repository provides transparency into the distribution, encouraging community engagement while Microsoft retains control over the base image's contents. Azure Linux is positioned as a free, Azure-optimized server operating system for hybrid environments, potentially signaling a shift away from Windows Server.

Tech Optimizer

July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley and was advised to focus on analytics rather than OLTP databases, which were considered solved. This led to the creation of Apache Spark and Databricks. However, during the development of Databricks, it was found that OLTP databases were not solved problems; they were difficult to scale and fragile. This realization led to the development of Lakebase, a serverless Postgres database designed with modern technology. Lakebase architecture separates the write-ahead log (WAL) and data files into independent, scalable services. The WAL is externalized to a service called SafeKeeper, which uses Paxos-based replication for durability, while data files are managed by PageServer, which stores them in cloud object storage. This design addresses challenges such as data loss, scaling, and performance interference between transactional and analytical workloads. Lakebase maintains compatibility with Postgres, offers unlimited storage, serverless compute, durable writes, and simpler high availability. It also introduces LTAP (Lake Transactional/Analytical Processing), which allows both transactional and analytical processing to operate on a single data copy in real time, eliminating the need for separate data copies and reducing costs. LTAP utilizes a unified storage layer that allows data to be materialized in both row and columnar formats, optimizing it for both transactional and analytical workloads. The system ensures that analytics can access the most current data without affecting transactional performance by using a log sequence number (LSN) to retrieve the latest changes. Unlike traditional CDC approaches, LTAP requires no explicit table replication, as all data is stored in a single governed copy. This architecture circumvents common issues faced by hybrid transactional/analytical processing (HTAP) systems, such as incomplete feature sets, lack of ecosystem support, and performance contention. The Lakebase architecture has unlocked capabilities like unlimited storage, elastic compute, durable writes, and instant branching, with ongoing developments anticipated in the future.

Tech Optimizer

July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley, where they were advised to focus on analytics rather than OLTP databases, which were considered a solved problem. However, upon developing Databricks, they found that OLTP databases were cumbersome, challenging to scale, and fragile. This led to the creation of Lakebase, a serverless Postgres database designed to address these issues by externalizing the write-ahead log (WAL) and data files into independent services. Lakebase architecture separates the WAL into a distributed service called SafeKeeper and data files into another service called PageServer, allowing for improved durability, scalability, and performance. This architecture eliminates data loss risks associated with disk failures and misconfigurations, simplifies high availability, and allows for elastic compute resources. Lakebase also introduces LTAP (Lake Transactional/Analytical Processing), which enables transactions and analytics to operate on a single data copy in real-time, avoiding the need for separate data copies and reducing costs. The system retains Postgres's ACID semantics while storing data in open columnar formats, making it accessible to both transactional and analytical engines without the delays and complexities of traditional replication methods. The architecture allows for unlimited storage, serverless compute, and instant branching, while ensuring that analytics can read the most current transactional data without affecting transactional workloads. LTAP aims to unify transactional and analytical processing by leveraging distinct compute engines for each workload while integrating at the storage layer.

Winsage

June 29, 2026

Microsoft keeps Windows Server 2022 hotpatching alive into 2027

Microsoft has extended the availability of Windows Server 2022 hotpatching until 2027, specifically for the Windows Server 2022 Datacenter: Azure Edition. Mainstream support for Windows Server 2022 will end on October 13, 2026, while extended support will last until October 14, 2031. Hotpatching allows administrators to apply security updates without server downtime, although quarterly cumulative updates requiring a reboot will still occur. This feature is exclusive to Azure Edition users, with no similar support for on-premises users of Windows Server 2022. Additionally, hotpatch updates are being introduced for Windows 11 24H2 Enterprise clients and are now the default for Windows Autopatch.

Winsage

June 28, 2026

Microsoft denies WSL 3 exists, reveals Windows 11’s WSL Containers ship next week

Microsoft has clarified that there is no WSL 3 in development, as stated by Craig Loewen, the Product Manager for the Windows Subsystem for Linux (WSL). The confusion arose from articles discussing a new feature called WSL Containers, which will be launched soon. WSL allows users to run Linux environments on Windows without dual-booting, while WSL Containers enable the creation and management of Linux containers directly within Windows, eliminating the need for third-party tools like Docker Desktop. WSL 1, introduced in 2016, served as a translation layer for Linux system calls, and WSL 2, launched in 2019, included a full Linux kernel in a lightweight virtual machine. WSL Containers is an enhancement to WSL, allowing developers to build, run, and deploy containers directly from Windows using the wslc.exe command. This feature is part of Microsoft's strategy to make Windows a more accessible platform for running Linux workloads, helping to retain developers who might consider switching to other operating systems.

AppWizard

June 25, 2026

Riot Vanguard finally drops its controversial always-on requirement for anti-cheat — new on-demand mode requires a strict Windows 11 security stack

Riot Games has introduced a new feature for its Vanguard anti-cheat system called Vanguard On-Demand, which allows the kernel driver to load only when a Riot game is launched and unload upon exit. This change ends the previous practice of loading the driver at Windows start-up, which has been in place since 2020. The new mode is supported by Windows 11 25H2 and requires specific hardware configurations, including UEFI Secure Boot, TPM 2.0, Virtualization-Based Security (VBS), Hypervisor-Protected Code Integrity (HVCI), and IOMMU. Approximately 35% of players currently meet these hardware requirements, while around 3% are using incompatible systems. Riot has created a checklist called Vanguard Pre-Check to help players determine if their systems qualify. The percentage of fully secured machines is estimated to be around 34.33% and is increasing monthly. Players whose systems do not meet the criteria will need to make manual adjustments in their BIOS. Vanguard On-Demand mode will be available for players on Windows 11 starting later today. The feature is based on Microsoft’s Runtime Driver Attestation Report, which tracks driver activity since boot and helps ensure no vulnerable drivers have been loaded while Vanguard is inactive. Riot Games has required TPM 2.0 and Secure Boot on Windows 11 since 2020 and has faced criticism for these requirements. Enabling VBS and HVCI may affect frame rates and could disable older peripheral drivers due to Microsoft's vulnerable driver blocklist.

AppWizard

June 25, 2026

You can finally turn Riot’s Vanguard anti-cheat off when you’re not playing a game

Riot Games is updating its Vanguard anti-cheat system to an "on-demand" model, which will only activate during gameplay and stop once the game ends. This change addresses concerns over Vanguard's previous persistent background operation and kernel mode access. Players must meet specific security criteria to use the new feature, including enabling pre-boot security mechanisms and Windows' native protection features. Approximately 35% of players already meet these conditions, while 3% using older hardware will not have access to the on-demand option until they upgrade. Vanguard will continue its current operation for those unable to meet the requirements. The update is influenced by advancements in Windows and PC hardware security and aims to enhance anti-cheat measures while keeping the process optional for most players.

Winsage

June 23, 2026

Microsoft Confirms Windows 11 26H2 Update for x86-64 PCs

Microsoft has confirmed the release of the Windows 11 update version 26H2, designed for PCs with x86-64 processors from Intel and AMD. Devices with Qualcomm Snapdragon Elite and NVIDIA RTX Spark processors will receive a separate update. Earlier this year, Windows 11 26H1 was introduced for Windows-on-Arm devices. Windows 11 26H2 is a minor update that shares the same code base as version 25H2, allowing for a seamless transition without a complete system file replacement. The update process is straightforward and will consolidate security and quality updates. Microsoft will provide security updates for Windows 11 versions 24H2, 25H2, and 26H2 for two years. Windows 11 Enterprise LTSC editions will offer stability by locking onto a specific kernel code base for security updates until a future date.

Winsage

June 22, 2026

MSYS2 And The No-Fuss Way To Get More GNU Into Your Windows

The Windows desktop experience has a streamlined interface, but its command line interface (CLI) offerings, particularly the cmd.exe shell, have been criticized for lacking the features found in UNIX/BSD/Linux environments. Microsoft’s transition to PowerShell has disappointed users who prefer a more traditional CLI experience. Despite Windows NT operating systems being POSIX compliant, they have historically lacked a suitable shell. MSYS2 provides a solution by offering a Linux-like experience with a Bash shell and the pacman package manager, allowing users to run shell scripts and access various tools. However, binaries compiled in MSYS2 may depend on shared libraries not included in the Windows system path. Upon installation, users can choose from different terminal options, with the UCRT terminal recommended for its usability. MSYS2 facilitates a streamlined development workflow, enabling the use of familiar tools across multiple platforms, but it does not achieve perfect integration within Windows and has some limitations, such as issues with stdout output in Bash.