kernel Archives

Winsage

July 20, 2026

Enable BitLocker on Windows 11: 11 Steps, 45 Min [2026]

A stolen laptop can lead to a significant data breach, particularly when taken from public places. Windows 11 has introduced BitLocker, a full-disk encryption feature that became mandatory for Australian businesses in 2026. The Office of the Australian Information Commissioner reported 766 notifiable data breaches in the latter half of 2024, with unauthorized access to devices being a major cause. Full-disk encryption is crucial for compliance with the Essential Eight framework, which mandates data protection on portable devices. BitLocker ensures that data on an encrypted drive becomes unreadable if the drive is removed and connected to another computer. It aligns with the Essential Eight framework, requiring evidence of encryption rather than just claims of protection. There are three types of encryption on Windows 11: Device Encryption, BitLocker Drive Encryption, and File-Level Encryption. BitLocker is available only on Windows 11 Pro and higher editions. To use BitLocker, certain prerequisites must be met, including having Windows 11 Pro or higher, a Trusted Platform Module (TPM) 2.0, UEFI firmware with Secure Boot enabled, and local administrator rights. The process to enable BitLocker involves confirming the edition, checking TPM status, enabling BitLocker through Windows Settings or PowerShell, and backing up the recovery key. Organizations can deploy BitLocker fleet-wide using Microsoft Intune, and additional security measures like TPM+PIN can be implemented for pre-boot authentication. Common pitfalls during BitLocker rollout include skipping recovery key backup and assuming that Home edition machines are covered. Troubleshooting common BitLocker issues involves identifying symptoms and applying appropriate fixes. Advanced tips for enhancing security include suspending BitLocker before maintenance and auditing compliance at the fleet level. BitLocker is integral to protecting data on portable devices, and compliance documentation is essential for proving that every device has an active recovery key.

Winsage

July 14, 2026

Microsoft Patch Tuesday for July 2026 — Snort rules and prominent vulnerabilities

Microsoft's July 2026 security update addresses 622 vulnerabilities, with 57 classified as "critical." Two critical vulnerabilities, CVE-2026-56155 (Active Directory Federation Services) and CVE-2026-56164 (Microsoft SharePoint Server), have been exploited in the wild. The critical vulnerabilities include 48 remote code execution (RCE) vulnerabilities, seven elevation of privilege (EoP) vulnerabilities, one spoofing vulnerability, and one security feature bypass vulnerability. RCE vulnerabilities affect various Microsoft services, including Windows Media, Microsoft Office, and SQL Server, with eleven rated as "more likely" to be exploited. Additional important vulnerabilities include CVE-2026-49170, CVE-2026-49795, and CVE-2026-50325. Talos is releasing a new Snort ruleset to detect these vulnerabilities, and Cisco Security Firewall customers are advised to update their ruleset.

AppWizard

July 13, 2026

Steam Machine compatibility checks are here, though not every game on the store enjoys a rating

Steam users can now check a game's compatibility with Steam Machine and SteamOS directly from the store page. This feature was introduced after the Steam Machine's June release. Players can click 'learn more' next to the Steam Deck compatibility rating for an overview of compatibility across Valve's hardware and software. The game Black Myth: Wukong has an 'unknown' compatibility status with the Steam Machine, while it runs successfully on SteamOS. Valve is investigating compatibility for titles like Dragon’s Dogma 2 and Elden Ring Nightreign. Some games, like 007: First Light, can achieve a 'Verified' rating on the Steam Machine. Currently, the Steam store does not allow filtering by Steam Machine or SteamOS compatibility, but this feature is expected soon.

Winsage

July 10, 2026

Windows 10 is still getting Windows 11 features, but it’s only for developers

Microsoft has confirmed that WSL Containers, which allows users to create and manage Linux containers directly from Windows, is now available on Windows 10. Users must have Windows 10 version 2004 (Build 19041) or later to utilize WSL Containers. The installation process involves checking the Windows build, installing WSL, updating to the container build, confirming the version, and running a test command. WSL Containers support GPU passthrough, enabling CUDA capabilities directly from Windows 10. A text-based UI dashboard for managing WSL Containers, named lazywslc, has also been introduced.

AppWizard

July 7, 2026

How to run Linux GUI apps on Android (when it actually works)

Android 17 is progressing towards enabling a fully functional Linux desktop environment, allowing for the potential to run Linux GUI applications. The Android kernel is based on Linux, and Google has integrated Linux terminal support. Users face challenges with the implementation of the Weston app, which is intended to provide a graphical environment for Linux GUI applications. The process to enable Linux GUI apps involves several steps, including enabling Linux terminal support, installing Flatpak, and accessing the Wayland terminal. However, users encounter technical hurdles, such as insufficient memory allocation and issues with the D-bus portal, leading to a frustrating experience. Despite some successful attempts to run the Weston command, persistent errors hinder functionality, and the feature is not yet ready for widespread use.

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.