Windows NT Archives

Winsage

May 29, 2026

IBM ThinkPad T43 enthusiast installs ‘almost’ every version of Windows on the single-core laptop without using virtual machine — 26 years of Windows running bare metal, from 1996 Windows NT 4.0 to Windows 10 22H2 working on legendary hardware

An enthusiastic user of the IBM ThinkPad T43 has successfully installed nearly all versions of Windows from NT 4 to 10 22H2 on the device, complete with driver support, without using virtual machines. The ThinkPad T43, released in 2005, was IBM's last laptop model before the company was acquired by Lenovo. The user documented their process on Reddit, showcasing a gallery of screenshots of various Windows versions. The T43 originally came with Windows XP and has key components including an Intel Pentium M processor, ATi Mobility Radeon X300 or X300SE graphics, a 14.1-inch screen, support for up to 2GB of DDR2 RAM, and storage options from 40GB to 100GB HDD. It also features connectivity options such as Wi-Fi, Bluetooth, Ethernet, and various ports. The laptop is noted for its robust build quality and exceptional keyboard, weighing approximately 2.3 kg (5.1 pounds).

Winsage

May 28, 2026

ReactOS brings its Windows NT tribute act to ARM64

ReactOS has successfully booted on ARM64 architecture, marking a significant milestone for the project aimed at recreating Windows NT. This experimental build has been demonstrated running on ARM64 via QEMU and on the Raspberry Pi 5. The ARM64 port is currently a proof of concept with limited functionality, and users need a UEFI ARM64 system with GICv2 or v3 enabled to run it. The ReactOS team has emphasized the experimental nature of this development, and the project is still focused on compatibility with Windows Server 2003. ReactOS is described as "an alpha-quality operating system," intended for users willing to experiment on less critical devices.

Winsage

May 28, 2026

Windows Server 2016 Update: Disastrous Bug Breaks AD

Microsoft released a mandatory patch (KB5087537) for Windows Server 2016 to enhance cryptographic layers and address critical vulnerabilities. This update is essential for organizations using legacy workloads, as mainstream support ended in January 2022, but extended support continues until January 12, 2027. The patch aims to prepare systems for the expiration of Windows Secure Boot certificates in June 2026, which, if not updated, could compromise security and expose systems to malware. The update uses a phased deployment model and includes a new SecureBoot folder to assist IT professionals in managing certificate status. It also addresses various quality-of-life issues, including bugs affecting Remote Desktop Connection and authentication errors with Microsoft services. However, a significant issue arises when the host server name is exactly 15 characters long, causing failures in the domain controller discovery process and obstructing critical operations. This bug is linked to the historical 15-character limit of NetBIOS, which affects the Active Directory lookup mechanism. Microsoft has acknowledged the issue but has not provided a timeline for a fix, leaving administrators to either rename servers or uninstall the update. As the Secure Boot deadline approaches, IT departments must carefully assess their environments to avoid disruptions while ensuring security compliance.

Winsage

May 27, 2026

Nvidia kills Windows XP-era Control Panel “after 20 years of dedicated service”

Users of RTX Pro, RTX, and Quadro GPUs still rely on the Nvidia Control Panel, as essential professional features have not yet been transferred to the newer Nvidia app. The Nvidia Control Panel was introduced in February 2006 with the ForceWare 83.60 driver package and remains compatible with graphics cards dating back to the GeForce 2 MX from 2000. Its aesthetic has changed little over the years, maintaining a Windows NT-style dialog box. Users express frustrations about feature regressions and difficulties with the new Control Panel, often preferring the old version.

Winsage

May 18, 2026

Windows CE Ported to Nintendo 64

Throaty Mumbo successfully ran Windows CE 2.11 on the Nintendo 64 by leveraging the shared architecture of both systems, which are based on the MIPS R4000 processor family. The project involved a month of reverse engineering, using Microsoft toolchains, custom hardware modifications, and debugging techniques. An EverDrive flash cartridge was used to load custom ROMs, and a USB connection facilitated uploads from a PC. Challenges included crashes with the initial EverDrive cartridge, which were resolved by upgrading to the EverDrive-64 X7. A custom kernel clone was created to troubleshoot issues with the stock Windows CE kernel, ultimately allowing the project to revert to the unmodified version. The Nintendo 64 controller was repurposed as a mouse, and standard Windows CE applications could be launched from the desktop. Comprehensive build details are available on GitHub.

Winsage

May 7, 2026

Windows 11 still runs on code from the 1990s, Microsoft admits

Windows 11 relies on the Win32 API, a legacy system dating back to Windows 95, for core functionalities like right-clicking and launching applications. Microsoft’s Chief Technology Officer, Mark Russinovich, noted that the continued relevance of Win32 was unexpected, as few anticipated it would still be a primary interface in 2026. Despite attempts to modernize the Windows API with initiatives like WinRT, Win32 remains integral to many Windows operations. The separation between Win32 applications and web technologies has complicated the transition to a new API framework. Additionally, tools from Microsoft's past, such as Sysinternals, Sysmon, and ZoomIt, continue to play important roles in Windows management.

Winsage

April 24, 2026

WSL9x: Add An Entire Windows 9x Subsystem To Your Linux

The Linux Subsystem for Windows 9x, led by Hailey Somerville, allows Linux to run within the Windows 9x framework by modifying the Linux kernel to interface with Windows 9x kernel APIs. Users need to create a specially modified Linux kernel (version 6.19) and a disk image with Windows 9x installed. The subsystem can be initiated with the wsl command, enabling both kernels to operate together. This initiative is reminiscent of Cooperative Linux and parallels the Windows Subsystem for Linux (WSL2) on Windows 10 and later. Contributions from the community have been vital to the project's development.

Winsage

April 20, 2026

Original Task Manager creator explains why it lies to you about CPU usage — former Microsoft engineer shows unique solution to a seemingly simple, but actually complicated, task

Dave Plummer, a former Microsoft engineer and architect of the original Task Manager, explained the complexities of measuring CPU usage. He noted that the process is not as simple as it seems, as CPU activity can vary across different cores and the timing of measurements can influence results. The Task Manager accounts for various states of CPU activity, including user mode, kernel mode, interrupt time, deferred procedure calls, and idle loops, making the measurement of CPU utilization a complex task rather than a straightforward one.

Winsage

April 2, 2026

Wine has been translating Windows games to Linux since 1993, but Proton is what made it effortless

Wine is a compatibility layer, not an emulator, that translates Windows API calls into POSIX equivalents, allowing Windows applications to run on Linux. Proton, developed by Valve, builds on Wine and includes additional components like DXVK and VKD3D-Proton to enhance performance for Windows games on Linux through Steam. For Steam users, Proton is recommended for a streamlined gaming experience, while Lutris is suggested for those outside the Steam ecosystem. Wine has been in development since 1993, focusing on recreating the Windows API, but faced challenges with gaming compatibility. Cedega was an early attempt to improve gaming support over Wine but ultimately declined. Valve's development of Proton was motivated by the need for better compatibility for Windows games on Linux, especially highlighted by the launch of the Steam Deck. Wine struggled with synchronization issues and handling direct kernel access by Windows applications, which Proton addressed with seccomp-bpf filters and syscall user dispatch. Both Wine and Proton are crucial to the current state of Linux gaming.

Winsage

April 1, 2026

Local vs. Microsoft account in Windows 11: How to decide and set up your preference

Setting up a Windows 11 PC requires creating a user account, with the Windows Setup program encouraging the use of a Microsoft account. A local account can still be established, though it is less promoted. Local accounts store credentials on the device, while Microsoft accounts use an email and password managed on Microsoft's servers. Local accounts are straightforward but can lead to frustration if passwords are forgotten. Microsoft accounts offer benefits like automatic encryption, easy restoration of activation, and synchronization of settings across devices. Privacy concerns regarding Microsoft accounts are often overstated, as data collection is tied to machine ID rather than account type. In Windows 11 Home edition, a temporary Microsoft account can be created during setup to later switch to a local account. In Windows 11 Pro edition, selecting the work option allows bypassing the Microsoft account requirement, with options to create a local account through domain joining. Third-party tools can assist in setting up a local account.