Microsoft has finally solved one of the biggest pain points of Windows with the rollout of Cloud Rebuild. The new recovery feature can reinstall Windows 11 even when an existing Windows installation is corrupt or refuses to boot. Available as a beta through the newly released Windows 11 Insider Beta Preview Build 26220.9343, the feature is essentially a hassle-free alternative to creating a Windows installation USB drive when a PC needs to be recovered.

According to Microsoft, Cloud Rebuild is designed to restore a Windows 11 PC to a “clean, known-good state” by downloading a fresh image of Windows along with the required drivers directly through Windows Update. Unlike the existing Reset this PC functionality, it does not depend on the health of your existing Windows installation, nor does it require users to have a USB drive or custom recovery image available.

Available via the Windows Recovery Environment (WinRE), users can access it by selecting Troubleshoot > Recovery and uninstall > Cloud rebuild from WinRE. Speaking of which, Microsoft has also improved networking support in WinRE. The recovery environment can now reuse eligible Wi-Fi profiles saved within an existing Windows installation, allowing a PC to connect during recovery without requiring administrators to separately configure Wi-Fi credentials in WinRE. Once the PC is connected, Cloud Rebuild checks Windows Update for the target Windows build and downloads the required files. Users can then confirm the Windows edition, language, and build before starting the reinstall.

The only catch here is that Cloud Rebuild completely wipes the system drive, meaning that the process removes all data stored in your main installation or C: drive, including locally stored files, accounts, applications, and settings, before reinstalling Windows. Thus, it is recommended to back up all your important files either locally or using a cloud-based service before starting the process. Once the installation is complete, the PC boots into the Windows out-of-box experience, similar to a fresh installation of Windows. For admin-managed PCs using Windows Autopilot and Microsoft Intune, the system can automatically reconnect to the organization's management infrastructure and restore assigned applications, policies, and backed-up settings.

Cloud Rebuild could particularly be useful when Windows becomes too corrupted to boot normally. Instead of finding another PC, creating installation media, and manually reinstalling Windows, users can potentially perform the entire recovery process directly from WinRE. The feature is still in preview; however, we can expect a wider release later this year.

If you are yearning for a quick-shot retro Windows experience on your modern Windows 11 or macOS system, then there’s a new vibe-coded clone of the Windows 3.1 Program Manager that may interest you. Developer Mayuki has released a neat little nostalgia project dubbed ReProgman – named after the ancient Windows 3.1 ‘progman.exe ’, which was the primary shell of the era – until Windows 95 swept it away three decades ago.

ReProgman looks pretty authentic to my eyes, and it brought back memories of why I wasn’t sad to see it shrivel away from Windows machines. In a social media post about the release of ReProgman, Mayuki seems to agree with my sentiments. “I asked Claude to create a clone of the Windows 3.1 Program Manager,” wrote the developer (machine translation). “I think you'll enjoy reminiscing with it for about 30 seconds.”

Claude Code worked pretty swiftly to churn out this clone of the Windows 3.1 shell. The first version that was precipitated in about an hour was “pretty decent” but needed some effort to iron out the wrinkles. Then Mayuki complains again that actually using ReProgman induced boredom after about half a minute of usage.

The end-user-ready releases of ReProgman weigh in at between 12 and 16MB, so they are quite a trivial download and don’t need installing. Thus, it isn’t very taxing to give them a try for a spot of nostalgia-tinted navigation around your present system’s programs and files. Mayuki says that building and running this application needs the .NET SDK 10.0+. The code has been released on GitHub under the MIT license.

In conclusion, Miyuki’s ReProgman provides an easy trip down personal computing's memory lane, specifically to the Windows 3.X era of the early to mid-1990s. However, some will prefer to get their retro computing kicks by running the actual MS-DOS/Windows 3.1 combo on real hardware. As we discovered recently, that doesn’t limit users to dusting off an old i486 or similar. Back in April, an enthusiast demoed Windows 3.1X on ultra-modern bare metal with a system using a Ryzen 9 9900X and RTX 5060 Ti.

Microsoft just released another version of Windows 11 designed for developers, dubbed Project Zenith. According to the Windows Blogs, this operating system is optimized for developer workflows and will first become available on the AMD Ryzen AI Halo, Team Red’s direct answer to the Nvidia DGX Spark, although it will also arrive on more devices from Microsoft’s OEM and other silicon partners soon. Redmond calls Project Zenith “a ready-to-code distraction-free Windows experience on developer-class devices with 64 GB+ unified memory and 250+ GB/s memory bandwidth,” claiming that “developers can jump right in.”

It comes with pre-installed tools like Visual Studio Code, GitHub Copilot, PowerToys, WinAppCLI, Windows Dev Skills, Intelligent Terminal, PowerShell 7, Git, GitHub CLI, AzureCLI, Core Utils, Oh My Posh, Python 3.14+, uv, NVM, Node 24+, WSL 2+ Ubuntu, and .NET 10. Aside from that, Microsoft said it pre-configures Windows 11 so developers don’t have to dig through the settings menus of various apps to configure them for their needs.

It’s primarily designed for AI developers, especially since the devices it’s installed on are designed to run 30B+ parameter models locally and without meters. The company also made it more secure for developing and running agents, deploying features such as OS-enforced identity, containment through Microsoft Execution Containers (MXC), and enterprise-grade manageability for agents.

Project Zenith is Microsoft’s response to the AI token crisis, which has caused costs to spiral out of control, especially as agents use 1000x more tokens compared to standard AI. While frontier models would still be available on the cloud, AI developers could run everything else locally through devices like this, powered by this version of Windows 11. This should help AI developers keep using their agents without feeling the bite of tokenized billing, which is especially crucial for those working in smaller organizations or experimenting at home.

One big tradeoff with Project Zenith, though, is that it’s only available on expensive devices, at least for the moment. The AMD Ryzen AI Halo, with its AMD Ryzen AI Max+ 395 processor, 128GB LPDDR5x-8000 RAM, 2TB SSD, and integrated Radeon 8060S graphics, costs $3,999.99 on Micro Center. Even if Microsoft eventually makes Project Zenith available for separate purchase and installable on other mini-PCs, the 64 GB+ unified memory requirement will be a major roadblock, especially with skyrocketing RAM prices driven by the AI boom.

Microsoft will begin automatically enabling its Memory Integrity security feature on a broader range of eligible Windows PCs through quality updates starting in October 2026, extending the kernel-level protection to more existing devices by default. In a September 1 blog post, Microsoft said the rollout will provide stronger protection for more devices against attacks targeting the Windows kernel, while PCs that already have Memory Integrity deliberately disabled will retain their existing configuration.

“Windows quality updates will begin enabling memory integrity protection on eligible devices,” Microsoft said. The updates will also enable Virtualization-based Security (VBS) where required, which provides the isolated environment underlying Memory Integrity. Before making the change, Windows will automatically assess each device using what Microsoft describes as readiness signals covering its hardware capabilities, compatibility, and performance.

The October rollout is basically an expansion of Microsoft’s existing default-enablement policy. Memory Integrity is already switched on by default on clean Windows 11 installations that meet Microsoft’s hardware requirements, as well as on Secured-core PCs. Current requirements include an 8th Gen or newer Intel processor for Windows 11 22H2, an AMD Zen 2 or newer processor, at least 8GB of RAM on x64 systems, an SSD of at least 64GB, compatible drivers, and enabled hardware virtualization. Automatic activation under that policy applies to clean installations and not upgrades of existing devices.

Memory Integrity — also known as Hypervisor-Protected Code Integrity (HVCI) — has existed since the Windows 10 era and was originally released as part of Microsoft’s Device Guard security technology. It uses VBS and the Windows hypervisor to move kernel-mode code-integrity checks into an isolated environment, helping prevent malicious or untrusted code and drivers from executing in the Windows kernel. Windows 10 generally left the protection optional outside configurations such as S mode, while Windows 11 made it more of a default security feature on compatible new installations.

The feature comes with a performance wrinkle familiar to PC gamers, leading many gamers to disable it. Microsoft acknowledged in 2022 that Memory Integrity and Virtual Machine Platform could affect gaming performance on some Windows 11 configurations, and advised gamers prioritizing performance that they could temporarily disable these protections while playing, warning that doing so reduces security. The company’s own gaming guidance subsequently continued to recommend temporarily disabling Memory Integrity and VMP where they interfere with gaming performance.

The security feature’s impact on performance depends on the hardware. Microsoft says Memory Integrity performs better on newer processors with hardware features designed to accelerate the required isolation, while older CPUs relying on software emulation can experience a larger performance hit. Driver compatibility can also prevent activation, with Microsoft documenting issues ranging from malfunctioning software to incompatible gaming anti-cheat solutions.

For most users, the October change requires no action. Eligible PCs will be evaluated and updated automatically, while administrator policies and previous user choices remain in place. Microsoft specifically says systems where Memory Integrity has already been disabled “won’t be automatically changed by this rollout,” leaving gamers and other users who previously opted out in control of the setting.

The Linux kernel is approaching a staggering 2,000 CVEs fixed per release, up from roughly 500 through much of the Linux 6.x era, as AI and large language models increasingly scour the operating system’s enormous codebase for vulnerabilities. According to an August 28 Phoronix report, Linux stable maintainer Greg Kroah-Hartman revealed the trend in a slide teasing an upcoming presentation at Kernel Recipes 2026, showing CVE counts jumping above 1,000 with Linux 7.0 and exceeding 1,500 with Linux 7.2. If the current trajectory continues, Linux 7.3 could push the figure beyond 2,000.

Rather than a change in Linux’s security or a rise in vulnerabilities, the spike is mainly due to “detectives” using AI tools to scour the Linux kernel source tree, which has grown to over 40 million lines over 35 years of Linux’s existence. These tools can examine countless obscure sections humans may rarely revisit, occasionally finding genuine defects; Linux CVE records this year already explicitly credit AI-assisted static analysis with finding vulnerabilities subsequently confirmed by Intel Product Security. However, many of the findings have been low-priority vulnerabilities — often within obscure driver code — questionable patches, and outright hallucinations, leaving human maintainers to separate useful work from noise.

This problem already constitutes a nuisance for kernel teams that have to fix these issues. In the Linux 7.3 networking pull request, maintainer Jakub Kicinski estimated that between one-third and one-half of the 648 net-next patches handled during the cycle appeared to be low-priority fixes, clean-ups, or clarifications driven by AI. "We are completely overwhelmed,” Kicinski wrote.

The issue has also led Linux maintainers to question whether decades-old drivers are worth keeping alive. In April, developer Andrew Lunn proposed removing nearly 28,000 lines of legacy networking code covering old ISA and PCMCIA-era hardware. While these drivers historically required little attention because they barely had any users, the AI and fuzzing tools started finding defects that maintainers were obligated to investigate and fix, regardless of whether anyone actually runs the hardware.

Linux 7.3 is removing old SGI and IBM driver code, while other ancient components have also been retired as maintainers reassess whether their compatibility value justifies their new maintenance cost. The FreeVxFS filesystem driver, for example, was removed after its maintainer said the decades-old compatibility code now largely served as fodder for automated bug checkers.

Now, the kernel community is not simply rejecting AI; Kroah-Hartman himself has successfully used locally-running AI-assisted fuzzing tools to uncover kernel bugs. The bone of contention is unverified AI output dumped onto humans for validation. Kroah-Hartman recently barred LLM-generated patches from the kernel’s staging subsystem except for legitimate security fixes, while updated kernel guidance warns that AI-generated reports submitted without human verification can waste maintainer time.

The team has also increasingly had to fight AI with AI. It has now secured access to multiple frontier models to help review patches and filter out hallucinated results, and is considering pushing more routine administrative work onto LLMs in subsequent development cycles. Kroah-Hartman is expected to discuss the trend further at Kernel Recipes, which is slated to run from September 21 to 23 in Paris. Linux 7.3 itself has already entered testing, with Linus Torvalds releasing Linux 7.3-rc1 on August 30 after closing its two-week merge window.

California’s legislature has passed Assembly Bill 1856, exempting open-source operating systems from the State’s Digital Age Assurance Act months before the law is due to take effect on January 1, 2027. The Senate amended the Bill on August 21 before passing it on the 26th in a 39-0 vote, with the Assembly then accepting these changes in a concurrence vote the following day. The amendment ends almost a year of uncertainty surrounding whether Linux distributions and SteamOS would be forced to collect user age data during account setup alongside Windows, macOS, iOS, and Android. AB 1856 has now been sent to Governor Gavin Newsom, who signed the original act into law last October.

These amendments redefine the term “operating system provider” to exclude any person or entity that distributes an OS or application “under license terms that permit a recipient to copy, redistribute, and modify the software.” Any software distributed under the GPL, MIT, BSD, and Apache licenses satisfies that test, which removes the likes of Debian, Fedora, Ubuntu, Arch, and the BSD family from AB 1856’s scope.

A second exclusion removes software components that aren’t “offered to consumers as a stand-alone executable application through a covered application store” from the law’s definition of an application, covering libraries and dependencies distributed through package managers like apt and pacman. AB 1856 doesn’t explicitly say that repos aren’t app stores, but a store’s main obligation under the law is to request an age signal from the user’s OS provider and pass it to developers; an exempt open-source OS produces no signal. A third carve-out excludes storefronts distributing extensions or add-ons that run exclusively inside a host application, which takes browser extension stores out of scope.

The amendments to AB 1856 also remove the original definition of “user,” which read, “a child that is the primary user of a device,” and technically classified every device owner in California as a child. The law’s signaling framework depends on adults declaring their age on account setup, so their devices get flagged as 18 and over, but under that definition nobody could ever be flagged as an adult.

In addition, lawmakers inserted a new provision prohibiting anyone from requesting an age signal from an OS provider or app store unless required by law. That closes off potential abuse of the age API that could have led to it being used as a general-purpose data collection channel even when age verification wasn’t required. Platforms and developers also gain a good-faith safe harbor against erroneous signals, protecting them from liability when age-gating signals are inaccurate.

Windows, macOS, iOS, and Android remain fully in scope, with age collection required at account setup from January 1, 2027. A later July 1, 2027, deadline applies to devices set up before January 1. Whether SteamOS is in scope isn’t yet clear: its Arch-based system components are open source, but Valve distributes the image alongside the proprietary Steam client. GrapheneOS, which in March said it would refuse to comply with age-verification mandates, is distributed under open-source MIT and Apache licenses and now falls outside the law’s scope entirely, though Brazil’s Digital ECA still applies to it.

Assemblymember Buffy Wicks, who wrote both the Digital Age Assurance Act and the AB 1856 amendment, introduced the exemption back in February following criticism from Linux developers and the Electronic Frontier Foundation.

The majority of PCs are sold with Windows 11 licensed, paid-for, and pre-installed. This fact irks many folks, especially Linux aficionados who intend to wipe all traces of Microsoft’s OS while their shiny new machine is box fresh. The Refund4Freedom site was put together by the Italian Linux Society and the Free Software Foundation Europe to help address this unfairness. “Consumers should be able to buy laptops without any specific operating system, and should not have to pay the license price if they don't want to,” asserts the site, and they have information and forms to help you get your cash back.

Refund4Freedom doesn't just help PC buyers in the quest to get Windows refunds; they have three key demands. Prevention is better than cure, right? The first demand is that “Device manufacturers and vendors should not impose an operating system or software on consumers, and should not force them to pay for software that they don't want.” This is central to the site’s message and purpose. However, it also wants to promote the idea that consumers should have the right to buy hardware without pre-installed software and see the price of the product with and without Windows, etc. Refund4Freedom also urges manufacturers and vendors to clearly outline the steps for requesting and obtaining a refund for pre-installed OSes and software. Of course, the process for consumers should be as friction-free as possible.

“Not all manufacturers and vendors are equal.”

“Not all manufacturers and vendors are equal,” notes Refund4Freedom on its website. Some are more helpful than others when it comes to refunds. You can read more on the website about each brand surveyed, but it looks like Acer and Lenovo both operate reimbursement procedures for Windows. Asus has a hidden reimbursement procedure, but we only get told of the Italy-centric way to reach out to Asus about it. Dell and HP don’t have any reimbursement procedure for Windows, according to the site.

Whichever brand of PC you buy, and the above list is far from exhaustive, you should follow a deliberate rejection procedure. If you intend to shun Windows, Refund4Freedom tells users to start up the PC and take pictures showing the contract clauses addressing reimbursement. Do not format or erase the computer at this stage. The next step is to contact the manufacturer's customer service. Do this in a recordable way, and so email/messaging is encouraged for records.

If the above two steps aren’t working out for you, the Refund4Freedom site has a pre-made form you can fill in and forward. However, this is again Italy-centric. For example, towards the end it mentions the Autorità Garante della Concorrenza e del Mercato (AGCM), as well as a ruling by Judge Dr. Mirko Buratti of the Court of Monza… So, perhaps you can swap in some rulings appropriate to your country for this part of the form? Get your favorite LLM to hallucinate some local court rulings for you.

Finally, and whatever the outcome, Refund4Freedom asks its readers to report their experience, good or bad, to the aforementioned AGCM. To inspire you, the site includes several user reports of success, and I note one user getting back as much as €150 from Acer (~$175). That was a combination of Windows license reimbursement and a larger legal fee refund. A more typical reimbursement level is roughly $60.

The development of Linux, a free ‘hobby’ operating system, was announced by Linus Torvalds 35 years ago today. On August 25, 1991, the unknown computer science student noted that the budding OS had been “brewing since April, and is starting to get ready.” The first public release of this ‘Minix-like’ OS came the following month, and in a last-minute change by the co-worker who uploaded it, was distributed with the name Linux instead of Freax. In 2026, Linux powers everything from smartphones to supercomputers and oodles of products, like the Steam Deck, in between.

The above commemorative post celebrates Torvalds’ stewardship over the Linux project. However, it is also quick to make clear that “hundreds of maintainers and thousands of contributors” have been instrumental to making this free open source OS a competitive, capable alternative to corporate/paid software, which can “move computing forward for humanity.”

Since 1991, Linux has come a long way on its journey from its humble ‘hobby’ OS beginnings. What started as a kernel with roughly 10,000 lines of code has exploded into 40 million or more lines today. Torvalds was humble about the first release yet proud of features like its multi-threaded filesystem, and the first release being clear of any borrowed Minix code. But the countless contributors over the last 35 years have helped forge an enviable OS, which boasts capabilities and features that must make it a worrying foe for commercial rivals.

There are areas, outside our PC and gaming core, where Linux is actually the biggest fish by far. Industry stats suggest that nearly 80% of web servers, and virtually all of the world’s Top500 supercomputers run a flavor of Linux. It dominates mobile too, with nearly 4 billion Android devices running Linux-derived kernels. Then there are all those embedded systems, encompassing things such as routers to automotive MCUs – so many run Linux.

I feel that Linux has made significant progress towards the fabled ‘year of Linux’ over the last couple of years. Microsoft’s Windows has been its own worst enemy in some respects, pushing people away due to a multitude of concerns. Meanwhile, consumers can see that content creation, productivity, and gaming on Linux PCs are continuously improving.

There was a recent collective sigh of relief in the Linux world, too. Earlier today, we reported on news that the decades-long Linux ownership dispute was effectively killed after Xinuos’ appeal was rejected by the U.S. Court of Appeals. That ruling means much lingering uncertainty over Linux devices facing future licensing claims, maker settlements, audits, and/or forced software rewrites has been banished.

Legendary Windows developer Dave W. Plummer has been busy finessing his revamped Task Manager. His latest release, dubbed TMOG (Task Manager OG), was vibe coded by feeding Claude “a 107-page spec,” says the mind behind the original 80KB Task Manager, which debuted publicly in Windows NT 4.0 (1996). TMOG doesn’t just work natively on modern Windows 11 systems though; it struts its neon stuff on macOS and Linux, too.

Above you can read Plummer give some background regarding the latest TMOG release, interspersed with details about his son’s emergency appendectomy. Cutting a long story short, Plummer found he had lots of spare time waiting around the hospital and thought he'd put it to good use by doing some coding.

With a new MacBook Air M5 under his arm, Plummer decided not to follow his original plan of vibe coding a new version of Microsoft Word, sticking to a project he knows intimately – Task Manager. After constructing “a 107-page spec” and feeding it to Claude Code, he got a rough app working by the time his son left the hospital, having completed the first procedure. A spell of internal bleeding meant readmission and more portable M5 dev time for Dave.

The result of all this extra hospital waiting room time is that Plummer had abundant TMOG tinker time. For example, TMOG can “animate everything at 60 Hz, instead of once a second.” Moreover, there are oodles of visual customization options, plus some interesting retro-flavored presets.

The first versions of TMOG were generated on the portable M5 in about four and a half hours. They worked the first time, asserts the veteran dev, and then work on fine-tuning started from there. Reading through the social media interactions following the new TMOG announcement, it looks like there are still a few vibe-coding flaws to paper over, and Plummer seems busy responding to many individual comments. There are also plenty of positive messages about the responsiveness and capabilities of the TMOG beta versions available.

At the time of writing, the latest version of TMOG beta available is version 0.1.1 on all supported platforms.

A decades-long dispute over the ownership of Linux looks like it is over. Earlier this month, the United States Court of Appeals for the Second Circuit rejected Xinuos’ continued claims that IBM and Red Hat improperly contributed jointly‑developed Project Monterey UNIX code to Linux, reports The Register. Despite this deathly blow to its chances of extracting potential damages from IBM and Red Hat, and oodles of Linux royalties and licensing fees, Xinuos intends to seek a full‑bench rehearing. This appeal is a very long shot for Xinuos, with only 0.03% of such hearings granted, according to IBM’s legal representatives in the dispute.

This is a complicated case that spans decades. So, to make sense of what has happened over the years, we’ve constructed a timeline of key events, spanning from way back in 1998 to the present day.

• 1998 Project Monterey. IBM partnered with a firm called Santa Cruz Operation (SCO), Intel, and Sequent to build a unified UNIX running on multiple processor architectures. SCO’s contribution was largely related to Intel x86 code.
• 1998-2001. Linux enjoyed rapid growth, so the importance of Project Monterey waned. IBM saw the shifting sands and moved its focus to Linux.
• Early 2000s. SCO first complained that IBM contributed jointly‑developed UNIX code to Linux without having proper rights to do so. Litigation began.
• 2003. SCO’s first major lawsuit was filed against IBM. It asked for billions of dollars due to the aforementioned complaint of IBM’s unauthorized use of UNIX code in Linux.
• 2011. Xinuos bought SCO’s UNIX business and IP.
• 2021. The SCO heir settled with IBM for $14.25 million. That’s a far smaller sum than it asked for in 2003, which kind of reflects SCO’s failure to produce convincing legal evidence.
• 2021. Xinuos sued IBM and Red Hat, claiming that IBM knowingly breached its non‑exclusive license by contributing Monterey code to Linux.
• 2022-2025. Xinuos argued that IBM’s actions amounted to licensing violations, but the U.S. District Court (SDNY) rejected this claim.
• August 10, 2026. Xinuos’ appeals are rejected. The U.S. Court of Appeals for the Second Circuit ruled that the case was too old to relitigate, and Xinuos framed it as licensing but was really arguing ownership, which is time‑barred. Thus the District Court dismissal stood.
• Now, August 2026. Xinuos has announced that it will petition for a full‑bench rehearing of its case. However, this is a long shot with a 0.03% chance of a rehearing being granted. According to IBM’s defense law firm.

While Xinuos looks like it has run out of road on its Linux code ownership claims, that’s probably good for the computing community. IBM, Red Hat, and the open-source world can probably now rest a little easier, with the shadow cast in 2003 now nearly entirely removed. Lingering uncertainty over Linux’s legitimacy is evaporating with the Second Circuit’s affirmation that the case is time-barred, and rather hollow, legally.

Other companies contributing code to open source projects can also rest a little easier as this distracting, resource-draining litigation grinds to a halt. Success for Xinuous may have also meant billions of Linux devices facing licensing uncertainty, maker settlements, audits, and/or forced software rewrites.

Like clockwork, it's a new month and a new OS-breaking bug has been discovered in Windows 11's latest monthly update, KB5121003. Users reported random system instability, with games freezing or outright crashing, and even BSODs in worst-case scenarios. Microsoft investigated the issue and reached a vindicating conclusion — RGB software installed on affected PCs was interfering with core system components, causing Windows 11 to become unstable.

Online multiplayer titles such as Arc Raiders, Marvel Tokon: Fighting Souls, and The Finals were most affected by this issue. Reports mentioned these games exhibiting a pretty classic crash pattern. They'd suddenly hang and become unresponsive, show an "EXCEPTION_ACCESS_VIOLATION" blue screen, and force your computer to restart automatically.

An official update posted on Microsoft's Windows 11 25H2 health status page says, "this issue is related to peripherals or internal device components which have RGB lighting features." The software governing these devices would install drivers or code components with file names similar to "inpoutx64" to control the RGB. When you'd launch a certain game, inpoutx64 would trigger the issue and cause a crash.

Microsoft didn't explain the underlying cause, but it's likely tied to anti-cheat not appreciating a kernel-mode driver in user space. RGB software, like other apps, should be limited to user space, but the driver it uses to interface with peripheral controllers runs in kernel space. For anti-cheat software, this is essentially an exploit waiting to happen, so it tries to block the driver to make sure it doesn't inject malicious code.

If the driver is blocked upon startup and the RGB software unknowingly tries to push a lighting change or monitor a temp sensor, for instance, it hits a wall, and Windows throws up the EXCEPTION_ACCESS_VIOLATION error. If the driver is terminated mid-use while executing assembly instructions at the Ring 0 level, it causes a critical kernel fault. Kernel space typically can't recover from unhandled errors like these, so Windows triggers a blue screen as a precaution to protect your hardware.

Microsoft says it's "presently working to understand the relationship between these RGB components and the games which trigger this issue." The company will provide more info later, but for now, you can use the Registry Editor to manually disable the driver as a temporary solution. Embark Studios, developers of Arc Raiders and The Finals, also shared this method to fix crashes for now.

This could break some RGB software functionality, but you can use universal programs like SignalRGB or OpenRGB to control your devices as long as they're supported. Their specialized drivers have strictly defined whitelists that don't scare anti-cheat software. Still, if you're facing this issue, Microsoft suggests reporting it via Feedback Hub—that's how issues like this get prioritized in the first place.

Linux kernel 7.3 is set to bring an oddly nostalgic update for 3dfx's Voodoo 3, one of the most recognizable graphics cards of the late 1990s. Don't get too excited; the venerable PCI-and-AGP accelerator isn't suddenly getting a modern Linux graphics stack, but the kernel's existing tdfxfb framebuffer driver is being updated so that it can initialize a Voodoo 3 itself rather than relying on the system firmware to have already run the card's video BIOS. It's a small change with a surprisingly specific purpose, and one that illustrates why ancient hardware occasionally gets attention in contemporary Linux.

The problem is that the tdfxfb driver historically assumed that the Voodoo card had already been initialized by the PC's firmware. That's because, at the time it was written, that was a reasonable assumption on a conventional x86 PC. The system firmware would execute the card's video BIOS during boot, configure the hardware, and then hand Linux something that is already capable of displaying an image. That assumption breaks down on newer and unusual platforms where the firmware cannot or does not execute the VGABIOS. The creator's patch description specifically calls out non-x86 computers, systems where another graphics card is primary, and newer BIOSes that can't run the old video BIOS.

The developer behind the patches, Daniel Palmer, was using a Voodoo 3 in an Amiga 4000 equipped with a PCI bridge when the problem cropped up. Linux could detect the card, but the Voodoo was still completely uninitialized, leaving him staring at "no signal detected." The new code uses configuration information from the card's own video BIOS to perform the initialization from Linux instead, allowing the driver to bring the VGA core up and establish a working display without depending on the system firmware. For now, the new manual initialization code is specifically aimed at the Voodoo 3; he had initially noted support for the VSA-100-based Voodoo 4 and 5 cards, but their BIOS layouts are different, so that support was removed from the current patch series. The code has been tested on both a modern x86-64 system and an Amiga 4000 with a Mediator PCI bridge.

On a conventional modern-ish x86-64 PC with a Voodoo 3 installed, the practical result is fairly modest. Load tdfxfb and you can get a working Linux framebuffer device, typically exposed as /dev/fb0, with the Voodoo driving a display that can host the Linux virtual console. In other words, this is enough to turn the Voodoo from "a PCI device that Linux can identify" into an actual display adapter capable of putting pixels on the screen even when firmware didn't initialize it first. Applications that know how to use the Linux framebuffer interface can also draw to it, just as they could with other old framebuffer devices.

The thing is, that's also where the limits of this work become apparent. Linux fbdev is a legacy graphics interface and has long been superseded by Linux's DRM/KMS graphics infrastructure, so this ain't a resurrection of the Voodoo 3 as a contemporary Linux GPU. Loading tdfxfb does not give you a Mesa stack, modern OpenGL, Wayland acceleration, or the sort of 3D functionality you would expect. It is essentially a very old-fashioned "squirt pixels at the display" arrangement, but that's useful enough for a Linux console, embedded-style framebuffer applications, and, apparently, people putting exotic PCI graphics cards into even more exotic old computers, but it's not exactly a compelling reason to install a Voodoo 3 in a modern desktop.

The more interesting part is that Palmer is working on a separate 3D path for the Voodoo 3, and that effort is already much further along than the framebuffer work alone might suggest. The experimental interface exposes the Voodoo's register space to userspace through a new /dev/tdfx3d misc device, whose mmap() interface allows software to program the card's 3D hardware directly. On top of that sits smoltdfx, a tiny userspace library for driving the Voodoo 3, and smolminigl, a small OpenGL 1.x implementation built on top of it. Palmer says he has tested the project on real Voodoo 3 hardware and that it can render directly through the card's registers without X, Mesa, or Glide.

Palmer is developing that work alongside a QEMU emulation of the Voodoo 3. The developer says Claude helped build the emulator in the first place to debug the issue of getting the card working on his Amiga. Now, test programs can be run against both the emulated card and the real hardware, with differences fed back into the emulator until the behavior matches. The smoltdfx project now uses the same rendering tests against QEMU and physical Voodoo 3 hardware, comparing frame digests to catch differences. According to Palmer, the resulting MiniGL implementation can already run Quake on the real card, although performance isn't great, and some issues with the Voodoo 3's multitexturing capabilities remain to be worked out.

Obviously, that's a lot more interesting than simply putting a Linux console on a Voodoo 3. The sum total is a highly experimental 3dfx graphics stack built from the bottom up: Linux provides the framebuffer and low-level device access, userspace programs the Voodoo directly, and a lightweight OpenGL implementation sits above that to provide enough functionality for classic 3D software to command the card.

Indeed, things could get particularly fun for retro-computing and virtualization. A PCI Voodoo 3 is the sort of device that, at least conceptually, could be assigned to a virtual machine using PCI passthrough, letting a guest operating system talk directly to the real accelerator with its period-accurate 3dfx driver. In the fantasy version of that setup, you could have a modern Linux host hand an actual Voodoo 3 to a Windows 98 or DOS-era guest and then let the guest use the very same hardware that the old software expected. The engineering details are much nastier than the concept suggests (particularly around resetting and exposing such old hardware cleanly), but the new ability to initialize an otherwise-dormant Voodoo from Linux is at least a useful piece of that puzzle.

For now, though, the headline is more significant than the immediate feature set. Linux 7.3 isn't suddenly turning a 25-year-old Voodoo 3 into a usable GPU; it's making an existing framebuffer driver capable of bringing the card to life on systems where firmware cannot do the job, which is a very small but very real hole in hardware support. More remarkably, the same effort has already spilled into experimental 3D acceleration on real hardware, with a userspace Voodoo 3 library and an OpenGL implementation capable of running Quake. Voodoo 3 may be over 25 years old by now, but somebody is still teaching Linux new tricks with it in 2026.

China's Ministry of State Security has told some state-linked organizations to remove a customized version of Windows 10 from their machines, Bloomberg reports, citing people familiar with the matter. The order reportedly accelerates a planned retirement that the software's developer had scheduled for February 2027, and it sent Chinese OS vendors' shares surging, with Hunan Kylinsec and Archermind both hitting Shanghai's 20% daily limit and China National Software climbing 10%. Bloomberg's sources attributed the directive to data security concerns but didn't specify what vulnerabilities Beijing is worried about.

The affected software is the government edition developed by C&M Information Technologies (CMIT), a joint venture set up in 2016 between Microsoft and state-owned China Electronics Technology Group, with the Chinese side holding the majority stake. The build is based on Windows 10 Enterprise but strips out OneDrive and other consumer-facing components, disables certain native functions, keeps updates and activation inside China, and lets government users substitute Chinese encryption algorithms for Microsoft's standard cryptography. China Customs and Shanghai's Commission of Economy and Informatization were among the first pilot customers when the edition launched in 2017.

Microsoft ended mainstream Windows 10 support globally in October 2025, which left CMIT's edition as the only Windows still officially sanctioned for Chinese government use. "Microsoft is not aware of a security incident affecting this product," a company spokesperson told Bloomberg, adding that it continues to receive regular security updates.

Beijing banned Windows 8 from government procurement in 2014, ordered a three-year replacement of foreign PCs in government offices starting in 2019, and in 2022 told central agencies and state firms to scrap foreign-branded computers entirely. The domestic stack built to absorb that demand now includes Kylin V10, UnionTech's UOS, and Huawei's HarmonyOS 5 laptops, and it reaches down to the silicon in systems like Huawei's Qingyun desktops running the homegrown Kirin 9000X.

StatCounter's traffic data shows how little of that campaign has reached the consumer market. Windows accounted for 87.64% of Chinese desktop web traffic in July 2026, and Windows 10 alone still made up 43.56% of Chinese Windows usage, compared with 50.01% for Windows 11, ten months after mainstream support ended. Roughly two in five Chinese desktops are currently running an unsupported Microsoft OS, the gap that CMIT's edition was meant to close for government users.

It's not clear what the scope of the new directive is, with Bloomberg's reporting covering “some” state-linked entities. CMIT didn't respond to the outlet's request for comment.

Popular open-source media player VLC has run into an unusual issue on Windows 11 that causes it to take as long as 33 seconds to start playing a simple MP3 file, the side effect of a recent unexplained change to Windows. The issue was publicized after game developer Jonathan Blow said he had stopped using VLC in favor of Microsoft's Media Player because of the delay. He also used the incident to criticize the state of open-source software running on Windows.

Responding to Blow's complaint, the developers behind VLC player fired back and claimed that the media player itself was not responsible. According to the VLC team, the bug is primarily due to a Microsoft Defender issue introduced through a Windows 11 update that conflicts with VLC's plugin cache.

"This is because of a « bug » from Microsoft Defender in one update of Windows 11, who magically made VLC plugins cache quarantined by Windows. Reinstalling VLC or regeneration of the plugin cache will fix this. Calling open source software embarrassing when it is a Windows update that broke it is quite disrespectful," the account responded.

The cache is an important part of how the media player works, as it relies on plugins for codecs, demuxers, and input/output modules. Instead of putting everything into a single executable, VLC loads these components as and when required and uses a cache to avoid having to scan the entire plugin directory every time it loads. The issue seems to occur when Microsoft Defender quarantines or blocks VLC's plugins.dat cache file. As a result, VLC can take a noticeable amount of time to process its plugin system before finally beginning playback. We also tried to replicate the issue on a Windows 11 machine; however, VLC launched normally, and we did not experience any noticeable delay when playing an MP3 file.

The easiest way to fix this is to reinstall VLC or regenerate the plugin cache. The VLC Windows installer includes a dedicated executable file to reset the cache files. This can be accessed by either heading to the VLC installation folder and running vlc-cache-gen.exe or its shortcut within the Start menu called "VLC media player - reset preferences and cache files." Do note that this also removes any customized preferences, such as audio settings like equalizers, keyboard shortcuts, subtitles, etc.

A more reliable solution is to add an exception for the VLC installation folder in Microsoft Defender itself. This should prevent Microsoft Defender from interfering with VLC's cache files and avoid the same issue from recurring. While the workaround seems relatively simple, it is still far from being ideal. One should not have to jump through hoops just to play an MP3 file. While Microsoft is yet to comment on the issue, it remains to be seen whether a future Windows Defender update will address the underlying cause.

Windows is in a tough spot right now, with years of neglect and stagnation reaching a boiling point with customers. Lack of optimization, bloat, ads, forced AI slop, and persistent tracking have forced Microsoft to admit its missteps and commit to fixing the OS at large. Windows Latest's new testing shows that the built-in weather app is a perfect representation of the state of Windows. The "app" consumes up to 1.2GB of RAM while idling, and it serves up a bunch of ads while you check the temperature.

MSN Weather is the default weather app that ships with Windows, which explains why it's filled with promotions throughout, despite being part of a paid OS. To be clear, the app looks very modern and has all the data you could ask for, such as live radar overlays, hourly wind and precipitation breakdowns, air quality index, and moon phases. It's also accurate because the data is sourced from a bunch of different providers across the world, but mostly Foreca.

The author explains that getting accurate forecasts is not a cheap endeavor, so it's not like Microsoft is running a charity. But the comparison falls apart when you look at what the competition is offering. Apple's native weather app on macOS is just as beautiful, detailed, and accurate, yet it's free of ads. It also only consumes about 250MB of memory to show all that data, so 5x less than Windows. This is because MSN Weather is technically not even an app to begin with; it's a web wrapper that's pinging a bunch of browser tabs in real-time.

When the author clicked on the Task Manager entry for MSN Weather, they saw 8 Chromium-based subprocesses, confirming that they're just looking at a website being rendered via WebView 2. For context, native Windows apps are supposed to adhere to the WinUI framework, which the company is slowly adopting over Win32 and UWP. Microsoft is committed to updating all the native apps Windows ships with to Win32, which should significantly improve their optimization, but we don't know if the ads will suddenly disappear as well.

The author saw Adobe Acrobat ads while checking the forecast, and we saw two ads — one for LendingTree and another for Spotify. Apart from that, scrolling around the app and clicking on the different menus and boxes was fast enough. We have to emphasize that the app really is granular and well-built from an aesthetic point of view; Microsoft gets full points for that, or is it MSN? That distinction is another issue that makes the weather app conundrum a bit more confusing.

When Microsoft promised to rebuild all native Windows 11 apps, it didn't explicitly say those would include MSN-branded services too, like MSN Weather and MSN News. Seeing as though they're simply called by their utilitarian names in the OS, there's a strong chance that these memory hoggers will also be eventually upgraded. For now, just stick to your phone, especially if you were among those who immediately Googled how to remove the weather widget from your taskbar that fateful day.

Last month, we covered a federal criminal case in which Microsoft's Global Device Identifier (GDID) helped the FBI catch an alleged hacker. Despite the noble cause, the implications of a persistent tracker built into Windows became difficult to ignore, and it was enough of a tipping point to convince Windscribe to do something about it. The VPN company has created an open-source project and script called "deGDID" that aims to strip GDID off your PC — but does so at the cost of breaking some Microsoft cloud services.

You can find the script on GitHub and run it via PowerShell with admin privileges. It's completely free and works in a very straightforward manner. There are three main execution flags that dictate how deGDID operates: –Status, which is read-only and tells you if a GDID is active on your rig; –Status –Redact, which generates logs with the GDID redacted so users can share diagnostic data more confidently; and –Protect, which completely wipes the GDID and prevents the creation of new ones.

A fourth flag, –Unprotect, allows you to reverse the script in case you need to revert back to the default state. But –Protect is the one worth discussing. First, the script looks for server-issued GDID keys in the registry, where they remain cached, and purges them all. This is something you can do manually as well. In fact, Windscribe tried it on a virtual machine, but the GDID keys are silently re-minted in the background upon a reboot or whenever Windows contacts Microsoft servers again.

To close this loop, the script then modifies the ACLs (Access Control Lists) and registry permissions to prevent the OS from fetching and subsequently trying to remint the GDID keys. It puts up a firewall against the internal DeviceAdd endpoint, which completely cuts off Microsoft identity services from even seeing this as a registered Windows PC. This one-two punch completes the process, and the existing GDID keys are not only wiped, but the possibility of new ones being created is put to bed as well.

Keep in mind that old keys that are already server-side cannot be removed; Microsoft has access to them indefinitely. This script also only works on unmanaged systems with admin accounts. If you're part of an organization or domain, deGDID will refuse to run. More importantly, though, since it blocks Microsoft's DeviceAdd pipeline, some core Windows services will break because they'll fail to authenticate your Microsoft account.

The reason deGDID is even needed in the first place is that Windows has no native toggle to turn off GDID. It exists as a permanent device ID that can track you without your consent. It works across IP addresses since it sits beneath the layer where VPNs operate, so no amount of network tunneling can obfuscate it. This can explain why Windscribe was compelled to create deGDID — to combat a potentially invasive system that has the power to wreak havoc in the wrong hands.

We tried the script on a Windows 11 computer, and it worked as intended. Running the –Status flag showed multiple cached GDIDs that were then removed by the –Protect flag, and a new GDID didn't show up even after restarting. As expected, some Microsoft apps freaked out and returned connection errors. Account verification through login.live.com was also blocked across all browsers, though login.microsoftonline.com still worked. Online games and other apps continued to behave normally as well.

Windscribe says deGDID is a research project, and it will continue to evolve as more information about how GDID works is uncovered. For now, the fact that it can make core Microsoft services and features fail might be too much of a tradeoff for some. The script also doesn't promise to kill every GDID instance, and Microsoft already has your previous keys, so this is certainly not an ideal solution — but it's a good start to the fight against hidden trackers.

In May of this year, Microsoft said that 32GB of RAM is now the future-proof “no worries” configuration if you’re a gaming enthusiast, and that 16GB of RAM is now the new “practical starting point” if you want to have a smooth experience with Windows 11. However, it seems that the company is backtracking on this announcement as it removes all references to the post on the Windows Learning Center website, according to Windows Latest.

Microsoft previously posted a blog titled “How to optimize your gaming PC setup” in November 2025, where it said that 32GB is the ideal capacity for hardcore gamers who demand the best possible quality for AAA games or use mods a lot. However, this page is no longer available, and people who attempt to visit the link are automatically redirected to the Learning Center Homepage.

Many manufacturers are once again releasing laptops that just have 8GB of RAM. Microsoft is part of this move, as it dropped its budget Surface Go and Surface Laptop Go models and introduced 8GB base versions of its Surface Pro 12, Surface Laptop 13, and Surface Laptop for Business. Thankfully, Redmond is not leaving users who cannot afford expensive RAM out to dry, as it recently promised to optimize the operating system and reduce its footprint by this year.

Even though Windows 11’s minimum specifications just require 4GB, the prevalence of many web-based apps and interfaces on the OS use up a lot of memory on many systems. While using web-based React and WebView2 is easier for developers, they’re not as efficient as apps that are built to run natively on Windows. This wasn’t a problem when memory was cheap and plentiful, as people could just spend a few dollars to upgrade their Windows PCs. However, now that memory modules are expensive and it’s hard to find the best prices for DDR5 and DDR4 kits, developers are going to be forced to optimize their software to use as little memory as possible.

This was actually what Windows programmers had to do in the 1980s and 1990s, when every Microsoft engineer had a stopwatch to ensure that their work remained fast, even on the limited hardware of the time. Even the original Task Manager, which was built by the same person who integrated ZIP file support into Windows, was only 80KB big so that it could run smoothly on “potato” hardware.

Hopefully, both Microsoft and app developers will rise to the challenge brought about by the memory shortage and make Windows efficient once more. This is especially true as Microsoft is now facing some competition from macOS and Linux (although Windows is, by far, still the most popular operating system today).

Microsoft said that it’s planning to optimize Windows 11 for systems with 8GB of RAM and above as part of its promise to improve Windows 11 in March 2026. The company said in its latest update that the optimization is part of expanding its focus on operating system upgrades, which include a faster out-of-the-box experience, easier parental controls, and improved voice interactions.

While the official minimum specifications for Windows 11 sit at just 4GB of RAM, most PC builders advise getting at least 16GB if you want to have a smooth experience. In fact, Microsoft has previously recommended 32GB of RAM for Windows 11 for gamers, especially if they want a system that can handle games in the near future. Unfortunately, the RAMpocalypse has forced both users and manufacturers to stick with slower DDR4 memory and lower capacities. Some experts predict that the entry-level PC will disappear by 2028, and we’ve even seen some manufacturers, including Apple, reintroduce 8GB laptops just to hit a specific price point.

The resurgence of 8GB systems will likely deliver a bad experience for users who stick with Windows 11, which is the likely reason why Microsoft is pushing for the optimization of its operating system. If Windows 11 performs poorly on these systems, it could draw users towards macOS or Linux alternatives as they blame the operating system for underperforming on limited hardware. In fact, we’ve already seen this happen before — after Microsoft ended support for Windows 10, MacBooks saw an uptick in sales as users migrated towards macOS instead of going for Windows 11. SteamOS is also encouraging some gamers to ditch Windows, and Valve is working on a general release for the OS, which many say contains less bloat and is a bit snappier than what Microsoft offers.

The RAM shortage crisis, alongside increasing competition, is forcing Microsoft to do better with Windows 11. Hopefully, these optimizations arrive sooner and don’t introduce new bugs, allowing both new and existing users to get more out of their systems.

The Windows blog post also gave an update on what improvements the company has made to Windows 11 so far. This includes a better Windows Search experience, more Taskbar and Start customizations, a more responsive and reliable File Explorer, among others. Many of these changes are still in preview, though, so unless you’re part of the Windows Insider Program, you’ll have to wait a few more weeks to months before you can start enjoying these changes.

The Steam Machine helped grow the popularity of Linux gaming, including installations of Bazzite and other gaming-oriented Linux distributions. Valve seemingly doesn't want to stop its open-source development efforts anytime soon, and is now working on a port of the Mesa Radeon Vulkan driver (RADV) to Windows; It's already running Counter-Strike 2, according to developers at Collabora.

As cross-platform development is rather tricky, Valve opted to get a port of RADV to Windows going by way of sponsoring contractors at Collabora. In its blog post, Collabora explained the several hoops it had to jump through to accomplish this task.

With Windows 10 and WDDM 2.0, Microsoft improved the split between graphics drivers' userspace code (the vast majority of the driver itself) and the kernel-level portion that actually talks to the graphics card. This presented the opportunity to hook RADV to the AMD kernel card driver. That's easier said than done, however, as communication between those parts often carries non-standardized data that RADV needs to understand. And to understand the "conversation," it needs to be recorded and analyzed.

An earlier 2024 effort by Faith Ekstrand yielded a basic-but-valuable utility for logging WDDM 2.0 calls and reverse-engineering them to produce a basic RADV implementation. Out of both debugging necessity and as a development tool, Collabora built and expanded upon Ekstrand's work, improving the logger to the point where it can now fully analyze any Vulkan application that runs with AMD's official driver and dump all the data passing to the kernel.

After a lot of work getting to grips with how the AMD driver interacts with the kernel driver, including but not limited to reverse-engineering obscure data structures, the team made progress, and Windows RADV is now able to run some games, including Counter-Strike 2.

Despite the ongoing effort, Collabora explains that since user- and kernel-space driver are a matched pair, changes to those aren't guaranteed to be backwards-compatible, meaning that even a fully functional RADV could break at any point. For that reason, Collobora is requesting that AMD, Microsoft, or both provide a documented interface to the kernel driver or an intermediary compatibility layer.

AMD graphics driver development on Linux has coalesced around the Mesa Vulkan stack, with both company and community devs contributing to the RADV project. Over in the Windows world, the only option is AMD's proprietary driver, which can cause a lot of headaches when developing cross-platform games and applications.

AMD's Vulkan driver for Windows has developed a reputation for instability. Meanwhile, Linux RADV is generally praised for its stability and performance, sometimes running faster than the AMD Windows driver, especially on older cards. With a rapid development schedule, it also generally sees fixes and speed upticks often.

If at some point using RADV on Windows becomes viable, you'd be getting an arguably more stable, mature driver with active development. Games' graphical issues could become far easier to debug and patch thanks to the open nature of RADV, and studios developing with Linux in mind can target the one platform instead of two with different behaviors. Any developer or company can contribute to the project, too.

Furthermore, this lets Valve improve Windows compatibility layers, and any optimizations can be carried over to both operating systems. All told, this is likely one of the several moving parts to improve Linux — thus the Steam Deck, Steam Machine, and upcoming hardware — as a viable gaming platform. Even a future notion of gamers installing RADV on Windows to get a performance or stability boost isn't too far-fetched.

Additionally, RADV on Windows would also help keep discontinued cards usable, and given pricing right now, that certainly would be a good thing.

Microsoft released Windows NT 4.0 to manufacturing partners on July 31, 1996. Codename Cairo marked an important milestone in the history of Microsoft’s original server OS and would far outlive Microsoft’s original plans as enthusiasts and administrators clung to it, as older readers will be aware. Headlining features of NT 4.0, which made it a winner, include the melding of the intuitive new Windows 95 UI into the fully 32-bit enterprise OS. It was also notable for being the last version of NT to support Alpha, MIPS, or PowerPC CPU architectures.

Historical Windows NT timeline:

• Windows NT Server 3.1 – in 1993, the first version of Windows NT also introduced NTFS
• Windows NT Server 3.5 – in 1994, this update provided integrated support for Winsock and TCP/IP
• Windows NT Server 3.51 - client/server support added in 1995
• Windows NT 4.0 – in 1996, NT got the Windows 95 UI and the familiar My Computer, My Documents, and so on
• Windows 2000 Server – the 5^th NT release started a new naming scheme, introduced Active Directory, plus NTFS 3.0 with file system encryption
• Followed by the more modern Server releases…

After the initial Windows NT 4.0 release, Microsoft followed up with a version for embedded systems and its Terminal Server edition.

The Windows NT line was critical to Microsoft as it led the charge against dominant Unix server software ecosystems. Its first public release was in 1993, with version 3.1, but NT 4.0 coupled the underlying data server and personal workstation tooling with Win95 UI elements such as the Start Menu, Taskbar, Task Manager, and so on. It would also support new components like the cryptography API, DCOM, TAPI 2.0, and some DirectX (v2) features.

Despite all the new technology under the hood and the frills of the latest UI, Microsoft’s Windows NT 4.0 launched with remarkably low minimum requirements. Would-be users were recommended to install it on a PC with a CPU that ran at 33 MHz or better, had 32MB of RAM, SVGA graphics, and a hard disk with 256 MB capacity. This was in the Pentium / Pentium Pro era. NT 4.0 would become “the server for the masses,” boasted Microsoft on the OS’s 20^th anniversary.

Another reason that NT 4.0 was so important is that it formed the foundation for the Windows XP release (2001), leaving the DOS-based 95, 98/SE, and Me versions of the consumer OS behind as archaic hybrids. In the half-decade between the release of NT 4.0 and XP, Microsoft had a lot of work to do, such as implementing Plug and Play, building out gaming tech, adding WDM drivers, and so on. Thankfully, PCs also grew in muscle, specs, and multimedia capabilities to make the larger and more demanding XP a big hit.

Windows XP landed with a core marketing line that it was “Built on NT technology,” which felt uncomfortable to read if you were from the camp that believed ‘NT’ was short for ‘New Technology.’

It is pretty easy to find an old Cairo release online for retro machine tinkering. Those interested in a more casual poke around in NT 4.0 out of interest, curiosity, or nostalgia will find there are some online installs you can play with via a web browser.

Legendary Windows developer Dave W. Plummer has shared details and screenshots of a version of Task Manager for Apple Mac computers. Apple computer users currently have Activity Monitor for peeking at CPU activity, memory usage, as well as closing apps and processes, by default. However, “Activity Monitor blows,” asserts Plummer, in response to people asking why he would port the classic Windows utility to the fruity computer.

Preempting questions from his social media followers, Plummer mused over the optics of releasing Task Manager for Mac, due to his Microsoft development history. In case you missed it, Plummer was the original dev behind Windows Task Manager when it debuted as a lean and mean 80KB accessory. He’s also recently reimagined this essential Windows system tool in a retro-futuristic Atari Tempest remix.

Back in the world of Macs, and looking to the side from the world of PCs, there is indeed a case for a better task manager or activity monitor for Apple computers. The Windows utility has more features under the hood, giving it a far greater scope and utility value (task priorities, startup management, services control, and more). We haven’t tried the new Mac version of Task Manager; it hasn’t been released at the time of writing, but if it can decant some of the Windows features over to the Apple computing platform, it may be an attractive addition.

Plummer says the utility is currently in beta, and he intends to “throw it up on the App Store… (for free in Beta, because the first taste is always free).” There’s also, admittedly, a chance he will get bored with tinkering with it and release the source for others to continue with.

We already mentioned the optics over a seasoned Windows dev coding / porting staple Microsoft OS code to Apple Macs, but Plummer has addressed queries about this in further posts today. In this Tweet, the dev asserts that “Microsoft very graciously sent me the source code to XP Task Manager along with permission to share/demo it.” Moreover, the project is written in Swift and uses no original code, and Plummer says he has no post-Windows XP code to tap into, either.

Meanwhile, development continues apace, with Plummer providing insight into some drive meter activity coding he’s currently working on. The dev is finessing drive activity for Task Manager for the Mac right now and pondering over the flickery visuals resulting from “drawing instantaneous drive activity at 60fps.”

AI-generated slop code has been a plague for some open-source projects, namely but not only Gentoo Linux, Curl, and Ghostty, limiting or outright banning LLM-created contributions. And yet, just like both the models themselves get better and the people using them become more considerate, the landscape may be changing. Linus Torvalds, Linux's creator and kernel manager, has seemingly taken an accepting stance of AI-assisted tooling.

In a long comment on the Linux kernel mailing list, Torvalds spelled it out fairly clearly: "I realize that some people really dislike AI, but this is an area where I'm willing to absolutely put my foot down [...] Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away."

This discussion came regarding the usage of Sashiko, an opt-in (per-mailing-list) and apparently quite effective multi-stage code review tool that analyzes kernel patches. The project page says the tool can find 53.6% of bugs on proposed patches, and argues that that metric already puts it above human level, as the patches in question already supposedly went through human review. The false positive rate "is harder to measure," being pinned "within 20%." Crucially, Sashiko only comments on patches, and does not take action by itself.

Developer Laurent Pinchart suggested that Sashiko's output be triaged before comments were sent out to patch authors, basing the notion on the Software Freedom Conservancy's guidelines on AI-generated code. Google's Roman Gushchin, one of Sashiko's creators, pointed out that doing that would undermine the utility of the tool, and that Pinchart's position was quite anti-LLM — a sentiment echoed by Linus Torvalds in his reply.

Torvalds put it clearly: "AI is a tool, just like other tools we use. And it's clearly a useful one. It may not have been that 'clearly' even just a year ago, but it's no longer in question today," a statement that reflects his changing stance on the matter since he initially dismissed AI tools as overhyped back in 2024. He also noted that Linux is not a "social warrior" project, and that it's always been about improving technology.

To drive the point home, he remarked that the tool "keeps finding embarrassing bugs," adding that he "will very loudly ignore people who try to argue against other people from using it," while highlighting the software's rapid evolution.

Perhaps quite poignantly, Torvalds remarked that resistant developers could use some self-awareness, as "it's not like natural intelligence is always all that great either," underscoring the fact that while AI tools may not be perfect, they generally only need to be good enough for their respective use cases. The fact that Sashiko seemingly finds errors in code that underwent human review is quite illustrative.

The adventurous developer who recently released Linux for the Atari Jaguar (1993) has brewed up a version of the open-source OS for the Sega 32X (1994). If you can’t remember the 32X, it was Sega’s mid-gen answer to early fifth-generation challengers like the Jaguar, 3DO, and Amiga CD32. Sega’s solution added some potent processing power to a mushroom-like slot in an expansion to its popular Mega Drive/Genesis. Now cakehonolulu has got it running Linux, despite facing several major hurdles.

Compared to its Genesis host, the Sega 32X was incredibly muscular. The Genesis had relied on the capable but long-in-the-tooth Motorola 68000 (7 MHz) for years, but the 32X add-on boosted that with a pair of Hitachi SuperH SH2s (SH7604) CPUs (23 MHz). It also ramped up system RAM from the base 64KB by adding 256KB of its own. Sega’s expansion offered more than just speed; the console’s color palette was ramped up from 64 to 32,000 simultaneous colors on screen, and it was powerful enough to introduce hitherto unachievable 3D graphics elements to mainstream console gaming.

As with cakehonolulu’s tale of Linux wrangling on the old Jag, the above-linked blog talks through a long list of hurdles that needed to be leapt to get the Linux kernel booted and running BusyBox. This time around, particularly steely roadblocks included: the even more constrained RAM situation, the lack of hardware synchronization primitives, the desire to get SMP working across the pair of SH2 CPUs, no direct UART access from the 32X, and scheduler bugs, among other things.

On the positive side, smoothing the development process along were access to Chilly Willy’s 32X devkit, the linuxmd project, the Krikzz FPGA-based flash cart with ROM – RAM mapping tools, and existing SH2 documentation and sample projects. Please check through the linked blog for far more technical details from cakehonolulu.

As you can see, cakehonolulu was successful again. So, what’s the next stop for this adventurous dev – the Sega Saturn? Whatever the project may be, it was interesting to read that works like this are basically forming a portfolio for the Spanish dev, which they hope will help them with job hunting.

A set of updates for Sega Dreamcast hardware has been merged into the Linux 7.2-rc3 kernel this weekend. Dmitry Torokhov submitted updates addressing the legendary console’s input subsystem and Linus Torvalds merged them on Saturday. The updates even surprised Linux-focused site Phoronix, That’s probably due to context: the Dreamcast continues to enjoy support while admittedly older but real computing hardware like the i486, PowerPC 40x chips, DEC Alpha, and Itanium / IA‑64, have all been sidelined in recent times.

In brief, the updates should mean new versions of Linux will come with more stable mouse, keyboard, and joystick drivers for Dreamcast stalwarts. If you are one of the Dreamcast faithful, still satisfying your computing (and gaming) needs on the final original consumer gaming hardware from Sega, this is good news.

Reading the pull request we can see some details about the new drivers for the Dreamcast’s Maple‑bus peripherals (mouse, keyboard, controller). Specifically, there’s a “fix for a crash in Sega Dreamcast (Maple) mouse driver when opening the device, caused by missing driver data,” as well as “Fixes for Maple drivers (keyboard, mouse, joystick) to properly order setting driver data and device registration to avoid races.” In this context races refers to things happening in the wrong order to result in crashes: it’s a timing bug that’s now been quashed.

Dreamcast hangers-on will now be able to craft specialized Linux builds on CD-R for their machines. The maplemouse driver has had the now-fixed crash-inducing bug since 2017.

Phoronix also comments that Linux kernel fixes for the GD-ROM driver used by the Dreamcast and a proposal for the VMUFAT file-system driver were also seen this year.

The Sega Dreamcast launched at the end of 1998 (in Japan, and the following year in the U.S.). So, in some ways it isn’t that surprising that it is still getting Linux kernel updates when the Intel i486 (1989) has been retired from mainline support. But one might have expected stronger demand for supported Linux distributions among i486 desktop and laptop users.

Windows 95 worked out whether a setup program had run by reading the executable's name and checking it against a short list of hard-coded words, according to Microsoft engineer and semi-official Windows historian Raymond Chen, sharing the details via his Old New Thing blog. A filename containing "setup," "install," or "inst" flagged the program as an installer, which triggered the operating system's routine for repairing system files that installers had damaged. Three non-English entries appeared on the same list, which Chen identified as his own guesses at Italian, Turkish, and Hungarian.

The full match list ran to six terms: setup, install, inst, imposta, ayarla, and felrak. Chen wrote that "install" was redundant, because any name containing it already contains "inst," and speculated that the shorter entry was added later to catch installers named along the lines of "blahinst" without anyone deleting the original. A program whose own name produced no match got a second test, with Windows 95 checking whether the word "Setup" appeared anywhere in the path to the executable. A separate live check ran after any multimedia driver was installed through an INF file, added because those drivers frequently overwrote system DLLs.

This heuristic gated a recovery mechanism Chen described in March. Installers of the period overwrote system files without checking versions, disregarding Microsoft's rule that a file should only ever be replaced by a newer one. An installer carrying Windows 3.1 copies of shared DLLs, for example, would bury the newer Windows 95 versions underneath them, and every program that relied on the current files would break.

Windows 95 kept backup copies of commonly clobbered files in a hidden C:\Windows\SYSBCKUP directory. It would then let each installer finish, check its work, and restore the correct versions where the installer had downgraded them. This safety net depended entirely on correctly guessing that an installer had run, so a setup routine with an unusual name slipped past it, while an ordinary program named something like instant.exe tripped it for nothing.

The file check was often deferred until the next boot rather than run immediately, with Chen explaining that some installers, unable to replace a file already in use, would drop back to MS-DOS, run a batch file to swap the file, and restart Windows, so the cleanup pass had to wait for the reboot to catch anything the batch file had altered.

Windows 2000 debuted a new approach

Microsoft dropped this approach in Windows 2000, which introduced Windows File Protection. That system registers for file-change notifications through Winlogon restores protected files from a cache at %WinDir%\System32\dllcache, with no filename guessing and no waiting for a setup program to complete.

Then, Windows ME shipped a comparable System File Protection, and Vista onward moved to Windows Resource Protection, which guards files using access-control lists instead. The sfc /scannow command that Windows 11 users still run to repair system files descends directly from that work, having replaced a 1995 mechanism that decided when to act by scanning filenames for the word "setup."

Unwanted ads can be one of the most infuriating parts of the modern tech experience, where hardware you already paid for is insistent on advertising even more slop to you. LG has a bit of a reputation in this regard, and it seems like the company is expanding its repertoire to even more invasive promos now. A user on the r/pcmasterrace subreddit shared that their brand-new LG monitor is showing them ads for McAfee.

Most of us are already aware of the euphoric feeling associated with getting McAfee shoved into your face. Usually, though, it's limited to laptops and prebuilt PCs that come with bloatware, freemium software, or just outright premium software that you somehow acquired for free. It would sensibly drive a person insane if a new monitor that has no other job than displaying your GPU's output starts participating in these activities.

In this case, u/t40r just bought this monitor and plugged it into their computer for the first time. That's when they noticed a small pop-up in the corner right away. It was from the "LG Monitor App Installer," and the first thing it showed the OP was an ad for McAfee. That's right — it was something entirely unrelated to the monitor. But how did this app show up on u/t40r's PC when they didn't even set anything up yet?

The answer is apparently the great evil known as the Microsoft Store. Checking the startup apps in Task Manager confirmed that it added the LG Monitor App Installer to the PC automatically. It's similar to how motherboard software magically enters itself into your system when you reinstall Windows. That one makes a bit more sense, though, since it's supposed to help control or manage your computer.

Sure, the LG Monitor app could serve the same purpose for the monitor, but it wasted its precious first impressions on a McAfee ad instead of showing something useful to the customer. Persuasion be damned. Anyhow, we were able to confirm that this was not an isolated incident either, as another Redditor posted about the same issue just a week ago, along with the steps for the removal process via local group policy.

Scouring through the comments also reveals other instances where users reported other manufacturers engaging in similar ghost installs. It seems like a standard Microsoft policy of auto-downloading related monitor software, but it's then up to the manufacturer what they actually show in said app. Regardless, these apps don't seem to respect your preferences and just show up uninvited, even if you're already running a debloated version of Windows.

With recent discussions on just how granular Microsoft's telemetry can be, this openness starts to feel like an oversight just waiting to be exploited. Even if Microsoft thinks it's "helpful" to install utilities without consent, it should at least try to make sure those tools aren't throwing up ads. LG makes some of the best monitors on the market; otherwise, it's a shame that deeper software integration can sometimes undermine great hardware.

A Spanish systems software developer has ported Linux to the Atari Jaguar console. To succeed at the task, cakehonolulu had to overcome severe memory limits, the lack of a memory management unit (MMU), and face off against a handful of unusual hardware quirks. A blog post from the dev tells us about the work to port Linux to this ill-fated 1993-launched flop, and happily ends in evidence that a working Linux kernel and BusyBox command line shell can be booted on the old Jag. Now Linux runs on both your cherished real hardware via cartridge, or in a Jaguar emulator.

Anyone wishing to port Linux to the Atari Jaguar would face numerous constraints due to the hardware. One of the first hurdles successfully leaped by cakehonolulu was the CPU used. Atari’s system designers architected the Jag using a Motorola 68000 CPU, which was already pretty old at the time, but a moderately fast 13.3 MHz version was selected. Though the gaming prowess of the console was lifted by custom co-processors dubbed Tom & Jerry, some games didn’t make much use of this graphics and DSP acceleration, as it was notoriously difficult to tap into.

For this Linux port, the general CPU capabilities of the M68000 would also be targeted to run the OS. With that in mind, and knowing that the CPU lacked an MMU, cakehonolulu was lucky to find that classic Motorola 68k processors are still supported by Linux, and also the uClinux project, which allows Linux to run on MMU‑less systems like the Jaguar.

While these prior works were helpful, it wasn’t long until the linux_jag developer needed to battle with other Atari Jaguar constraints. The console comes with just 2MB of RAM and up to 6MB of ROM, which is incredibly miserly compared to even the cheapest microcontrollers and SBCs nowadays. Much RAM and storage optimization later, cakehonolulu tripped over a few issues getting Linux to boot on the Jaguar, and ended up implementing a console driver for Tom so the OS would work on real hardware.

A brief Atari Jaguar history

Atari’s Jaguar was released with great pride by the iconic video game company in 1993. It was controversially claimed to be the world’s first 64-bit console, but it still never managed to push aside incumbent previous-gen machines from Sega (Genesis / Mega Drive) or Nintendo (Super NES).

The mass market had enough patience to largely ignore the first wave of ‘early fifth-generation consoles’ like this, the 3DO, and the Amiga CD32. They were rewarded handsomely with the launch of the true accelerated 3D gaming next-gen wave, led by the Sega Saturn (which also used an M68000 CPU, alongside co-processors), Sony’s first PlayStation, and the Nintendo 64.

History can be a little unfair to the Atari, though, as it did have some eye-popping for the time original games and ports. I owned the original console with Alien vs. Predator (1994), and it was quite a stunning, tense, and scary game. Others thought the Jag’s Tempest 2000 was a killer app. In addition, there were strong Doom and Wolfenstein 3D FPS ports from the PC.

No need to pinch yourself — it is, in fact, 2026, and there was a court hearing last June 22 about IBM allegedly using copyrighted source code in Unix-like products, yet again for the umpteenth time since 2003, a saga that's part of the Unix wars.

For historical context, Xinuos (formerly SCO) and IBM have been embroiled in legal battles for decades, as the companies cooperated between 1998 and 2001 on developing an Itanium variant of Unix. Since then, SCO has repeatedly and dramatically taken IBM to court, claiming the defendant misused SCO-owned source code from the collaborative effort in its AIX and z/OS products, as well as Linux. Many battles have been fought over who owns the "Unix" name, what code IBM put in Linux, and even FreeBSD.

The latest hearing pertains to a 2021 lawsuit by Xinuos, the company that acquired the remnants of Santa Cruz Operations, more commonly known as SCO. Xinuos' CEO reportedly once stated the group didn't purchase SCO just to acquire the right to sue IBM, but the company eventually changed its mind in 2021 and dragged IBM back to court on claims that its conduct and copyright infringement resulted in great damage to Xinuos' market position.

Xinuos picking a fight with a team of lawyers colloquially known as the Nazgûl is questionable on its own — yet, in the aforementioned 2021 lawsuit, Xinuos added bold claims, such as stating that IBM's purchase of Red Hat should be reversed under antitrust law, and that the company's strategy in said acquisition was to destroy FreeBSD — the variant underpinning Xinuos' wares.

How, exactly, an MIT-licensed operating system would be "destroyed" is an interesting matter. Xinuos stated at the time that "IBM and Red Hat have abused their control over the Unix/Linux operating system market for far too long." One wonders if Linux users with hundreds of distributions at their disposal would agree that IBM has been pulling their strings all along.

The lawsuit dragged on until 2025, when Xinuos voluntarily chose to drop the antitrust claim (presumably after finding little purchase from the court). It also found itself disabused of the merits behind the copyright complaint, as the New York judge in question framed the claim as time-barred: too long had passed for Xinuos to file a complaint, and original ownership of the code is murky at best. Darl McBride, the SCO executive who launched the original lawsuit, passed away from ALS in 2024.

Xinuos did, however, press on with the copyright issue and requested a hearing for an appeal. And on June 22, 2026, the firm argued in front of a three-judge Second Circuit panel that the previous judge miscast a copyright infringement claim as an ownership claim.

Say whaaaat? Hannah Montana Linux is back. The distro made as a tribute to the noughties Disney Channel sitcom for tweens and teens, featuring the eponymous secret pop star, was basically abandoned in 2009. Now it's back, with a modern kernel and about 18 years of patches, with the release of the Hannah Montana Linux v26.0 remaster by developer Noah Cagle.

Little is known about why the original Hannah Montana Linux was developed, released, and almost immediately abandoned. The version available via Archive.org is the only known release, identified as Hannah Montana Linux x86 basic edition 202201. It is still available if you’d like to test out a frozen-in-time HM-themed version of Kubuntu. You can grab it as a 691.7MB download via the link provided. Be warned that it is now “basically unusable,” though, according to Cagle, due to being insecure and for its poor software support.

Fast forward to the present day, and Cagle’s HML26 release solves all the issues with the old distro. Browsing the modern web is possible and safe, finding and installing software is easy, and the dev has even made the terminal look pretty.

In the video feature about the release of Hannah Montana Linux v26.0, Cagle provides some insight into how this version of the OS was customized, built, and released. After initially considering the Cubic GUI wizard for creating customized live ISO images of Ubuntu and Debian-based platforms, the developer decided to go with Live Build, an official tool for Debian-based distros.

We then get a walkthrough of using this tool to make a Pretty in Pink version of Debian Linux. Briefly, a lot of the work required to make a distro like HML26 is adding various files and references into a set folder structure, and then building the Linux ISO. Most of the custom imagery and iconography sit in an includes.chroot directory.

Key customized elements would include an icon pack, color scheme, and wallpapers, and they were largely built by cloning and then editing existing theme resources. The main wallpaper looks a lot like the original, and that’s because it uses the original PNG as a source, updated by Cagle to 16:9. The cherry on the cake, though, might be the stylized ‘H’ start button.

When Cagle was happy with his customizations, he sought out a way to transform the ISO from being a live-CD only so it could offer an install option. This final step in creating HML26 was done with a tool called Calamares. This app is strong in applying branding, so it was a great choice for a professional revival of Hannah Montana Linux.

You can download and try out Hannah Montana Linux v26.0 now, with the ISO available at the above-linked GitLab page under GPL 3.0. You’ll want a system with at least 8GB of RAM to enjoy this OS. Those with older machines might want to look at HML26 Lite, which switches KDE Plasma 6 for the lightweight LXQt.

The RAMpocalypse is hitting enthusiasts hard. We recently reported on the crisis seeping down to affect supplies of the decades-old DDR2 gen RAM. So it comes as no huge surprise that a well-known tech tinkerer has been inspired to look at the viability of Windows 11 on an even more ancient DDR1 platform. Step forward Omores, who demonstrates Microsoft’s newest OS running on a Core 2 Quad Q6600, using a DDR1 motherboard, supported by an ATI Radeon HD 4650 AGP graphics card. “The best part,” says our hacky hero. “It’s completely stable.”

DDR1 first became available to PC builders and DIYers at the turn of the century, replacing the aging SDR SDRAM. The DDR1 rollout began with data rates like DDR-200 and DDR-266, being the preferred choice over older platforms featuring PC100 or PC133 SDRAM. We don’t know the rated speed of the DDR1 sticks Omores used, as it isn’t shown, but DDR-400 was the best official non-overclocked standard (a couple of years later). It would make sense to use the best memory on a cherry-picked older system like this.

Other key components of this age-defying Windows 11 PC build include an ASRock ConRoe 865PE motherboard. This is regarded as something of a legendary board as it bridged generations and allowed folks to use the latest Core 2 Duo and Core 2 Quad chips from Intel while keeping their DDR1 RAM and AGP graphics cards. It isn’t only today that PC DIYers have cared deeply about component longevity.

The last significant component in this DDR1 system that we were told about was the ATI Radeon HD 4650 AGP graphics card. This seems to have required the most wrangling to make it work with Windows 11 / modern software. However, Omores reveals that “With some 'hacking' ... AGP 8X is fully functional and H.264 hardware decoding is active.” The key was finding, then crowbarring, ATI’s Windows 7 64-bit drivers from 2012 onto the system.

Once some details of the setup were confirmed in the video using tools like CPU-Z and GPU-Z, Omores showed the ‘fresh’ Windows 11 DDR1 system running modern browsers, with embedded video and hardware decoding. A handful of games and 3D benchmarks were also shown running without glitches. Last but not least, the system did indeed run Crysis.

In a later comment on the Reddit post, Omores elaborates on how to install the ATi driver on Windows 11 and shares a more detailed video link. “I like that Windows 11 is rock stable on these older systems with no UEFI whatsoever and only ACPI 1.1,” adds the adventurer in older PC tech. “A lesser-known fact is that Windows 11 actually officially supports BIOS systems via Windows 11 IoT, so it's kind of expected to run smoothly.”

Microsoft has extended its free consumer Windows 10 Extended Security Updates (ESU) program by a year, pushing the cutoff for critical security patches to October 14th, 2027. The change came without any actual announcement, appearing instead in an edit to Microsoft's Windows 10 ESU support page. Devices already enrolled roll over to the new date automatically, with no action required from users. The program was originally set to expire on October 12th, 2026, one year after Windows 10 reached end of support on October 14th, 2025. With the extension, however, users who can’t or won’t move to Windows 11 now have a second free year of patches.

Speaking to BleepingComputer, Microsoft said that the change reflects “our ongoing commitment to helping customers stay secure during the transition,” adding that the extra year gives users “more time and flexibility to find the best PC for their needs while keeping them protected.”

In terms of enrollment, nothing has changed: users can enroll for free by syncing their PC settings to a Microsoft account through Windows Backup, by redeeming 1,000 Microsoft Rewards points, or with a one-time payment of $30. Users in Europe can enroll at no cost simply by signing in with a Microsoft account, a concession Microsoft made after pushback from consumer advocacy groups over its original requirements. A single ESU license covers up to 10 devices tied to the same account.

Microsoft's consumer program is limited to personal devices, however. Systems joined to an Active Directory domain or to Microsoft Entra, or managed through Mobile Device Management, are corporate-controlled and therefore not eligible. Personally owned machines that are only Entra-registered — e.g., a work account added to a personal device, rather than the device itself being organization-owned — still qualify.

Windows 11 has surged to roughly 73% of desktop share against Windows 10’s 26%, so it’s clear that the broader migration is working. Those users still on Windows 10 are increasingly the difficult edge cases, with around 400 million active PCs unable to officially upgrade to Windows 11 because their hardware fails its TPM 2.0, Secure Boot, or supported-processor requirements.

Users of those machines face a choice of remaining on unsupported Windows 10 or upgrading their hardware outright. But thanks to the AI-driven memory shortage, doing so has never been more expensive: DRAM contract prices have roughly doubled since early last year (and are expected to double again) as Samsung, SK Hynix, and Micron divert wafer capacity toward high-bandwidth memory for AI accelerators.

IDC expects PCs, tablets, and smartphone prices to rise 10% to 20% through the end of 2026, with memory now accounting for a far larger share of a system's bill of materials than it did two years ago.

For users unwilling to buy new hardware at current prices, some third-party options remain. The security firm 0patch has pledged to provide unofficial Windows 10 micropatches through 2030, and Linux migration efforts such as the End of 10 initiative continue to court holdouts whose machines can’t run Windows 11.

A Reddit user has demonstrated that SteamOS, Valve's Arch-based gaming operating system built around AMD silicon, can boot and run on an Intel Arc B580 discrete graphics card. Posting in the r/SteamOS subreddit as SaperPL, they documented the feat this week, pairing the Arc B580 with a Ryzen 5 5600 processor and getting Valve's full gaming-mode interface running on the card. The catch is that reaching that point took a Radeon card, a workaround for a broken installer, and a motherboard setting that nearly sank performance along the way.

The opening exists because recent SteamOS beta builds quietly widened hardware coverage. Valve's changelog for the beta cites improved compatibility with recent Intel and AMD platforms, language clearly aimed at the wave of Intel-powered handhelds rather than desktop Arc cards. However, because the underlying Linux graphics driver is shared, the same Mesa stack that targets Intel handheld chips also recognizes a desktop Arc GPU. SaperPL's system reported the card as Mesa Intel Arc B580 Graphics (BMG G21) on Mesa 26.1.2, running SteamOS 3.9.

Getting there was not exactly plug-and-play. According to the post, newer SteamOS images that supposedly already include Intel Arc support failed during setup. These images did not boot into the older live desktop-style installer with install, update, and recovery options. Instead, they started installing directly to the drive, then failed when the system tried to connect to the network and pull its first update. SaperPL says the same problem occurred even when testing with a Radeon RX 9060 XT, suggesting the issue was not limited to the Arc B580 itself.

The workaround was suitably PC-gaming messy. SaperPL installed an older “repair-main” SteamOS build using the Radeon card, pulled the required updates, and then swapped in the Intel Arc B580. After that, SteamOS booted on the Intel GPU and ran from the Main channel. The poster also noted that users without a spare Radeon card may be able to follow a Steam Community workaround to bypass the installer’s update failure directly, although that still leaves the process firmly in enthusiast territory.

The first performance results were mixed. SaperPL tested 14 games, including Cyberpunk 2077, Helldivers 2, Marvel’s Spider-Man: Miles Morales, Indiana Jones and the Great Circle, Toxic Commando, Hades, Rocket League, and others shown in the SteamOS library screenshot. The interface itself appeared to behave well, with the poster saying the Steam library and store navigation worked smoothly, even while downloads continued in the background. Gamescope also reportedly worked similarly to Radeon, apart from a VRR bug on FreeSync displays with HDR that caused occasional flickering.

Frame rates were another story. Indiana Jones and Toxic Commando were initially barely above 20 FPS at 1080p on the lowest settings, while Helldivers 2, Cyberpunk 2077, and Spider-Man: Miles Morales fell far below comparable Windows benchmark videos. The poster’s monitoring suggested the CPU was not the main problem, with the GPU often sitting around 80% to 90% usage while the Ryzen 5 5600 hovered between roughly 30% and 50%.

The biggest culprit turned out to be a familiar one for Intel Arc users: Resizable BAR. SaperPL later updated the post to say that ReBAR had been disabled on the Asus B450 Strix motherboard after a CPU change. Once enabled, Cyberpunk 2077 and Spider-Man appeared to perform as expected, while Indiana Jones and Toxic Commando improved significantly, though still not fully matching Windows reference results.

That detail matters because Intel Arc GPUs are unusually sensitive to Resizable BAR. Without it, the CPU cannot efficiently access the GPU’s full memory space, which can lead to severe performance drops. In this case, it made the difference between “SteamOS on Arc is broken” and “SteamOS on Arc is early, but actually running.” Even on Windows, leaving ReBAR off will severely impact Arc performance.

Commenters also pointed to another likely limitation: kernel support. Intel’s Arc drivers on Linux have improved considerably, but the newest performance work often depends on recent kernel and Mesa versions. If SteamOS’ Main channel is still behind the very latest Linux graphics stack, Arc performance may remain below what the same card can do under Windows or faster-moving Linux distributions.

For now, this is more proof of concept than a consumer-ready feature. Valve has not turned SteamOS into a general desktop gaming OS with clean support for every GPU, and the install path shown here is still too awkward for normal users. But the result is interesting. SteamOS running on an Intel Arc B580 suggests Valve's hardware net is widening, whether intentionally for desktop GPUs or indirectly through work on Intel-powered handhelds.

That could matter for future SteamOS machines. AMD remains the obvious fit for Valve’s gaming hardware today, but Intel has been pushing harder on Linux graphics support, and low-profile Arc cards could become attractive for small living-room builds if the driver stack matures.

Copilot PCs have been around for a couple of years since Microsoft launched them in 2024, and while the company tried to push NPU-equipped laptops towards users to take advantage of these new features, it seems that it’s planning to reverse course. According to Windows Latest, an experimental Windows App SDK available on GitHub now lets you run Language Model APIs on supported GPUs, starting with the Nvidia GeForce RTX 30-series cards with at least 6GB of VRAM. However, it also requires a Windows Insider Experimental Channel and Developer Mode switched on. Hence, you need to go through some hoops to turn on local AI inferencing on Windows, even if you don’t have an NPU-equipped device.

You still won’t get all the features found in a Copilot+ PC even if you went through all the hoops to activate this feature, but it’s a sign of things to come for local AI on Windows PCs, in general. It’s still not clear why Microsoft is seemingly abandoning the Copilot+ PC advantage it has heavily marketed in recent years, though RAM pricing might play a role, but this is good news for the millions of users who were locked out of Copilot features simply because their processors don’t have a built-in NPU (neural processing unit). This also opens Windows’ AI features to desktop users, who typically don’t have processors that support NPUs.

What’s interesting is that NPUs aren’t necessarily more powerful than GPUs for AI processing — it’s just that they’re more efficient, making them crucial for laptops with limited battery life. And because not all laptops come with a discrete GPU (which are mostly found on gaming and high-end laptops), it also allowed Microsoft to include AI features on more affordable Windows 11 PCs. Another reason Microsoft could be looking to expand Copilot+ features to non-NPU-powered devices is that AI didn’t actually take off the way it had hoped. A research firm in 2024 said that people didn’t purchase AI PCs because of their features — instead, they bought them because they’re what’s available if they need to upgrade.

The situation is worsening in 2026, as the AI data center-driven shortage of memory and storage chips is pushing computer prices to unprecedented highs. This has resulted in a collapse in sales for PCs and their components, with entry-level laptops expected to disappear by 2028. People not buying new NPU-equipped PCs would limit the adoption of Copilot+ PCs and the AI features they offer. By expanding the availability of AI features to non-Copilot+ PCs, Microsoft will increase its user base and help differentiate Windows 11 from the competition, especially as Windows is slowly bleeding users to macOS and Linux.

AI-assisted coding (or vibe coding) has infiltrated Linux driver maintenance, with Linux developers now using LLMs to help maintain old drivers in the Linux kernel. Phoronix reports that GitHub Copilot was used to clean up code pertaining to vintage AMD R6000 Linux graphics drivers, helping keep the driver relevant for people still using these late 2000s-era GPUs.

Specifically, the R600 Gallium3D driver saw 59 commits by Gert Wollny, all aimed at cleaning up shader compiler code in the driver. The refactoring process was done with Copilot, with notes in each commit citing Copilot in auto mode being used to help build the code.

This method of driver maintenance will inevitably become a staple of Linux driver maintainers moving forward, as the world adopts AI over human programmers for writing the vast majority of code written today. The Linux community often only has a handful or a single person updating these older drivers, making AI a very incentivizing tool to compensate for a lack of manpower and help keep these older drivers alive. The R600 Linux driver is designed to run the AMD/ATI HD 2000 through HD 6000 series of graphics cards. The HD 2000 series debuted in 2007, and the HD 6000 debuted in 2010, making some of these graphics cards nearly 20 years old.

Rather than rejecting AI, Linus Torvalds has opted to embrace the adoption of AI and allow Linux developers to use AI, but only when appropriate. A new policy enforces proper tagging if Linux kernel developers use AI to assist in code creation. Critically, this system puts the blame for any buggy code on the person publishing kernel driver changes, requiring the person to test their work before publishing.

Despite the use of AI, Linux developers are, regardless, discussing branching off the R600 drivers into a legacy branch dubbed “Amber2”. This would free up the main Mesa codebase and prevent legacy drivers from accidentally breaking as new features are added to Mesa.

Apple introduced its next major macOS release, macOS 27 Golden Gate, at its WWDC event. The new operating system update, coming this fall, includes a series of new artificial intelligence gestures, as well as iterations to the "liquid glass" design introduced in last year's release, macOS 26 Tahoe.

Craig Federighi, Apple's senior vice president of software engineering, said that the 27 releases were focused on more polished and intuitive operating systems, trust and safety (including for children), and updates to Apple Intelligence and Siri. Unlike previous years, Apple spent most of its time highlighting changes that affect the entirety of its platforms, meaning that many of the improvements on Mac are also available in some form on the iPhone or iPad, and vice versa, reflecting the continuing deep integration in Apple's ecosystem of products, including iPhone (iOS 27), iPad (iOS 27), and watchOS (watchOS 27).

macOS will include some specific upgrades, including ultrawide display support with higher resolutions, and an updated video podcast player, while many others, like updates to iCloud shared albums and changes to Maps, are across multiple platforms. In many ways, the focus on fixes is reminiscent of 2009's OS X Snow Leopard, which was famous for fixing problems rather than introducing tons of new features.

Liquid Glass

Apple is making changes to Liquid Glass across its platforms to make content more readable and decrease distractions. Glass will now better diffuse content behind it.

A new slider in settings will let you move from from ultra-clear to fully tinted, letting you customize how much it affects readability.

Specifically on the Mac, Apple is adding a uniform tool bar across the top of apps, which harkens back to more traditional Mac design. Expanded sidebars will move to the edge of windows, and sidebar icons will regain their colors. Additionally, every window will have tighter corner radii, even if they're not updated, for improved consistency across the OS. These were all complaints from Mac diehards over the last year.

In app icons across platforms, there will be additional layers of glass in icons to make them sharper and more defined.

Improvements

Apple said that it is bringing a massive amount of improvements under the hood of macOS and other platforms, with focus on CPU usage, memory usage, display rendering, and more. Apple claims apps can launch 30% faster on the iPhone and iPad, while new photos will show up in the library up to 70% faster. The advanced CPU scheduler on the iPhone is being optimized and brought all the way back to the iPhone 11, which will be the oldest iPhone supporting iOS 27.

Network transitions — especially between cellular and Wi-Fi — were also highlighted, so you don't have to toggle as often.

The company also highlighted a new content index across Spotlight, photos, mail and more, which will index your existing files immediately and continue to do so as new content comes in. Apple demonstrated a new ranking system for mail on Mac, showing more relevant results, even if it's years old.

AI and Siri

Federighi claimed that the mission is to turn AI into helpful and intuitive products, rather than AI for the sake of AI.

"Truly helpful AI must be centered around you and your needs," Federighi said, saying it needs to be designed for devices, apps, and with privacy in mind. Surprisingly, Federighi briefly mentioned that its foundation models are integrated with Gemini and will be used "on-device and in servers" with private cloud compute. Additionally, Apple has a more powerful on-device model.

Apple SVP for Siri engineering Mike Rockwell showed off a revamped Siri. The new Siri grows out of the dynamic island with "Hey Siri" or when you hold the buttons. It retains context between interactions.

A new voice experience includes a more conversational tone. Voice can now be customized for expressivity and pace, with sliders to adjust them in a new Siri app.

Rockwell asked about a Suki Waterhouse concert, and Siri told him when the concert will be. You can even inquire about tickets, which in this case were part of a lottery. Rockwell asked to be added to the lottery and to play her newest single in separate requests, as it remembered context.

He also demonstrated finding photos from a recent trip, asking Siri to pick out photos that include just specific people, and then share them with family members via text – without even having to go into the Photos app.

On iOS, you can swipe down, use the side button, or say "Hey Siri." On the Mac, Siri is integrated into Spotlight, or you can use Siri requests in system menus. One demonstration included using Siri on a Mac to help build a Maker Space at a child's school. When "How should I think about building a maker space in a shed” was typed into Spotlight, macOS realized it was a question specifically for the assistant. Siri was able to search through texts from the demonstrator's son, to address lingering electrical issues and find a fix.

Siri AI is also coming to iPadOS, where you can use the dedicated Siri App. You'll be able to see a conversational history synced with iCloud across devices, including Mac, Apple Watch, and iPhone. On visionOS, you can simply look at Siri and initiate your query.

Visual Intelligence will be integrated into the iPhone camera app. You can tap the shutter button for Siri AI to “see what you see” and provide contextual information, powered by Apple Foundation models. Pointing your iPhone at a plate of food can give you nutritional information, while showing the camera an image of a restaurant bill will let you split it among friends. You can also use visual intelligence to ask about items presented on your screen.

You'll also be able to write with Siri anywhere you type. Siri can generate drafts, including emails, and will provide suggestions and automatic proofreading, available systemwide, even in third-party apps.

Siri AI won't be available in the European Union and China initially, as Apple deals with international regulation and privacy laws. Siri AI will first be available in English.

Apple Intelligence in apps

Apple also demonstrated how Intelligence can be used within and across applications, including Safari, Passwords, Photos, and Home.

In Safari, Apple has introduced tab management features, which can organize tabs into topics. Another option lets you monitor a page and asks you to "Notify me" for changes on a page, like a product coming back in stock or a ticket becoming available. You can then close the tab, but Siri will notify you when the page has changed. Perhaps the most impressive change is one to Shortcuts. You can describe what you want a Shortcut to do in natural language, and it brings together the steps automatically. One example: “When I’m leaving home, message Pedro” brings together a shortcut using Maps and Messages, which should open up Shortcuts to a much wider variety of people who may have been put off by its complicated nature.

Other demos included custom Safari extensions to adapt web pages for you, a Password app that can automatically fix compromised passwords for you on "eligible" accounts. In messages, you can get one-tap suggestions, and the phone app can find flight information when calling an airline.

For Home, Apple Intelligence can understand how a number of unrelated notifications work together to create fewer notifications and provide images from multiple security cameras. It can even track package deliveries across multiple cameras. 4K resolution will work on supported cameras.

In the Image Playground, you can create high-quality images in any style, with the image generation model running on private cloud compute. You can use natural language to adjust existing images and use it across the device, such as on your lock screen. The Photos app may have the most controversial aspects, as you can extend photos to change photo borders without cropping. There's also an option to reframe the entire scene with a spatial camera, as if you were moving the lens in the original shot. This feature works on any image in your library, even if you've taken the photos on other cameras or phones.

These features will support all languages Apple Intelligence works with. Some features will have usage limits that will adjust based on iCloud+ subscriptions.

Developers will have access to improved models, including server models, through a new API that will support natural language and images.

Lastly, Apple highlighted updates to XCode, including agentic coding, choosing the model and agent of your choice (including the newly added Google Gemini). It can connect to Figma and GitHub for design, and a new Device Hub will let developers simulate devices, including touch screens, alongside real-world testing devices.

Trust and Safety

Apple also demonstrated new child safety tools, with new child accounts and parental controls. Child accounts will automatically block adult websites and implement app store age restrictions.

Children will be able to ask parents for permission to buy or download apps in messages, as well as browse new websites in Safari for children under 13. There will be similar permissions for contacting new people outside of your family.

A new safety communication warns about nude images and intervenes, but will also be expanded to gore or violent content. Parents will have Time Allowances across entertainment, games, and social media, with shared allowances across all three, or you can set them individually. A redesigned Screen Time will let parents see how devices are being used. Developer tools are being made more capable for third-party apps to take advantage of the new features.

Golden Gate will be the first version of macOS to exclusively support Apple Silicon Macs. Last year, Apple announced that Tahoe would be the final major release to support Intel-based systems. (Intel-based Macs will still receive three years of security updates.) This is the last macOS release to support Rosetta 2, the tool that lets Apple Silicon computers run Intel applications through an emulation layer (though parts may stick around to keep legacy games running). Without Intel processors to support, Apple is urging developers to make native applications for its own silicon.

Support and Release Dates

Developer betas for the 27-suite of OS releases are available today, with public betas starting in July. Final releases are expected in the fall.

macOS 27 Golden Gate will be supported on devices with Apple Silicon. Apple's website specifies:

• MacBook Neo
• MacBook Air (2020 and later with Apple Silicon)
• MacBook Pro (2020 and later with Apple Silicon)
• iMac (2021 and later with Apple Silicon)
• Mac mini (2020 and later with Apple Silicon)
• Mac Studio (2022 and later with Apple Silicon)
• Mac Pro with Apple Silicon (2023)

However, adjustments to Siri's voice and advanced dictation will require newer chips on the Mac, iPad and iPhone. On the Mac, that means "an M3 and later and at least 12GB of unified memory." Otherwise, you need an iPhone 17 Pro, iPhone 17 Pro Max, iPhone Air, iPad models with M4 and later and at least 12GB of unified memory, or Apple Vision Pro with M5.

A “full-feature-parity version of Notepad” has been written in x86 assembly and it weighs in at just 2,749 bytes. Windows legend Dave W. Plummer is (inevitably) the coder behind this efficiency tour de force, and he’s made RetroPad available (code and exe) on his GitHub under the Apache 2.0 license.

Plummer announced this latest release of RetroPad on Thursday, describing it as a feature-for-feature match of the version of Notepad that shipped with Windows XP. That’s impressive enough in 2.7KB, rather than an app of about 65KB. However, Plummer’s work rate is such that he’s since added optional line numbers and a dark mode. He also decided to add “all of the Notepad keyboard shortcuts” on Saturday which added a few bytes. It won’t be long until there’s an accompanying YouTube video for a deeper dive into RetroPad, but for now we have the GitHub notes.

A few hours ago Plummer also added the trpad.exe to GitHub, so folks who don’t want to run the code through MASM/Crinkler can just download and run this little utility. The version of trpad.exe available on GitHub wouldn’t run on my Windows 11 laptop, though.

Windows app bloat

Windows bloat has become so bad that even Microsoft noticed. Earlier this year, Microsoft promised to go back and get the basics right, things like File Explorer, the Taskbar, and other Windows staples were going to get some tuning and polish. This was a much-needed initiative, but was precipitated by a tone-deaf exec post about the operating system “evolving into an agentic OS.”

The puffing up of Notepad is a fascinating case study in Windows bloat. As mentioned previously, the Windows XP era Notepad was approximately 65KB, not much more than Windows 9X releases (~50KB). According to a web search notepad.exe would grow to around 190KB to 200KB for the Windows 7 to 10 eras.

Windows 11 is a bit different, though. The notepad.exe in my current Windows 11 install appears to weigh in at 352KB but according to the Windows Control Panel, the install size is 808KB. Looking even deeper at this, and it seems like the moderately sized .exe file is just a ‘stub’ or ‘bootstrapper’ app to point to a UWP/WinUI app that is about 5MB in size. That’s where Microsoft has stuffed all the recently added features like spell check, autosave, multiple tabs, and Copilot writing tools.

A short video has resurfaced in which Bill Gates promotes Windows 95 with DirectX as a gaming platform set to eclipse DOS. The video is part of footage from an internal Microsoft ‘Judgment Day’ developer/gaming event. So far, so ordinary, but the typically meek Gates appears dressed in a trench coat and holding a shotgun, standing inside a Doom-style environment littered with demon carcasses. You can watch the video by expanding the tweet below.

The Doom franchise began in 1993, well before Windows was widely used for games beyond the likes of Minesweeper and Solitaire desktop distractions. Throughout much of the 1990s, PC users would run games through DOS, with Windows seen as something to use for multitasking productivity tasks. With Windows 95, Microsoft wanted to change that; hence, this promotional video to developers, starring Gates himself.

Though there were (and are) DOS gaming devotees, Windows 95 was promoted as delivering improved multimedia, Plug and Play hardware support, and, with DirectX, even better gaming performance.

Gates begins his in-Doom spiel by saying that “these games are getting really realistic” before boasting that “Windows 95 is THE BEST game platform, whether it’s the best performance, the best setup, the best integration.” He then admitted that DOS can be hard work for end users, developers, and tech support. But the key improvement being dangled in front of developers was the new DirectX API.

During this brief presentation intro, Gates touted 75 new games coming for Windows 95 in the coming year. He reckoned with this push and collaboration between Microsoft and game developers, “we’ll be able to clean up this DOS mess, and get everything focused on Windows.”

This unusual video isn’t just Bill Gates standing and spouting about Windows 95 gaming, thankfully. Halfway through this clip, he is interrupted by an enemy grunt, and quickly turns to give it both barrels, “Don’t interrupt me.” But when delivering this punchline, Bill sounds more like Kermit the Frog than Arnie.

The video closes with Microsoft’s logo, some sinister laughing soundtrack, and the tagline “Who do you want to execute today?”

Key to the background collaboration between Microsoft and a host of game developers was the work of Gabe Newell. The future Valve co-founder initiated and led the Microsoft team responsible for porting id Software’s Doom to Windows 95, which would result in the release of Doom95 in 1996. Some sources say that Doom was installed on more computers worldwide than Windows 95 was at this time (late 1995).

Linux developers are looking into retiring the x32 ABI that was introduced into the Linux kernel in 2012. Phoronix reports that Sebastian Andrezj Siewior of Lintronix has proposed removing the x32 ABI from the Linux kernel due to its obsolescence and lack of serious adoption since its debut. If no objections are raised, the x32 ABI will likely be removed from the Linux kernel by 2027.

x32 ABI was introduced to Linux in an effort to optimize the memory consumption of 64-bit programs. The application binary interface was designed to allow 64-bit processors and applications to operate in semi “64-bit/32-bit” hybrid mode. With x32 ABI, software is allowed access to the full 64-bit register file and data path but is restricted to using 32-bit pointers. For the uninitiated, a pointer is a binary number that keeps track of data that is held in system memory.

This ability allows the OS to use more than 4GB of RAM while keeping pointer sizes at just 4 bytes instead of 8 bytes (for 64-bit). This size difference is x32 ABI’s main selling point, as cutting the pointer size in half improved the amount of data that can fit in a CPU’s multiple caches and improved performance.

Despite its potential, x32 ABI also had several disadvantages. Using x32 ABI adds additional complexity for developers to deal with and requires compilers to support the feature. Arguably, its biggest technical problem relates to the fact that individual processes running with x32 ABI cannot take advantage of more than 4GB of memory due to the pointer sizes being limited to 32 bits.

That said, the nail in the coffin for x32 ABI is its lack of mainstream adoption by software developers as a whole. This was likely helped by the fact that x32 ABI was ever only implemented on Linux and was not ported to Windows or Mac. Sebastian Andrezj Siewior highlighted further issues in his proposal, noting that the better performance x32 ABI realized was not great enough for certain workloads to move to it and use it exclusively.

An IBM ThinkPad user boasts that they can install “(almost) all versions of Windows from NT 4 to 10 22H2,” with driver support, without resorting to virtual machine (VM) technology. The ThinkPad T43 from 2005, used by Redditor MatiHalek, was already a firm favorite among retro tech enthusiasts and well known for being IBM’s final design prior to the Lenovo acquisition. The confirmation that it can run 26 years of Windows OSes certainly adds to the T43’s considerable charms.

So, what did Mati actually do? In the post embedded above, you can see they posted a gallery with 10 Windows screenshots, most of which show an iteration of the System > About control panel as evidence of the version of Windows installed and running. This gallery will take many readers on a journey down memory lane as the Windows UI evolves through the eras.

Mati says that they didn’t use VMs to install any of these Windows versions. They were all real software-to-metal installs on the single-core Pentium M CPU, though it wasn’t always an entirely straightforward process getting Windows to behave. We’d assume most difficulties would be due to support and drivers for graphics and storage interface hardware.

The Redditor didn’t install the 26 years of OSes sequentially in a strictly experimental fashion. “When I got this laptop, XP was installed, so I decided to dual-boot Vista with that XP. Then I did the upgrade path Vista-7-8-8.1-10RTM,” they explained. Subsequently, Windows 22H2 wrinkles forced them into doing a clean install for this pretty recent OS from Microsoft. However, modern OSes don’t appear to be Mati’s passion as “after that, I wiped the hard drive and multi-booted 98, NT 4, and 2000.” They end their post by indicating they will be keeping this 20th-century OS trio on the IBM ThinkPad T43, simply out of preference. It's probably the most responsive choice, given the hardware.

IBM ThinkPad T43 hardware

As we mentioned in the intro, the ThinkPad T43 was the final laptop from IBM’s stables, before Lenovo took the reins. Mati was correct to assert that it originally shipped with Windows XP, and it launched just a few months before Vista hit the scene.

Key components of the T43 were as follows:

• Intel Pentium M processor
• ATi Mobility Radeon X300 or X300SE graphics
• 14.1-inch screen in resolutions up to 1,400 x 1,050 pixels
• Support for up to 2GB of DDR2
• Storage config between 40GB and 100GB HDD
• Wi-Fi, Bluetooth, Ethernet, and modem connectivity options
• Ports included 2x USB 2.0 ports, a parallel port, VGA, S-Video, a PC Card slot, and a docking station port

Beyond the hardware tech specs, the IBM ThinkPad T43 earned a lot of praise due to its durable, perhaps legendary, build and keyboard quality. It isn’t light for a 14-incher in 2026 terms, of course, weighing in at approximately 2.3 kg (5.1 pounds).

Do any readers still cherish an IBM ThinkPad T43? If so, do you still run an older version of Windows like Mati does, or have you moved to an alternative OS like Linux?

AMD has been accused of 'bait-and-switch' tactics following changes to the licensing of Vivado on Linux. As reported by It's Foss, AMD has decided that Linux users of the Vivado chip design environment need to pay up or stick with an older version that will become unsupported soon.

For the uninitiated, Vivado is AMD's proprietary design suite used to program Field Programmable Gate Arrays (FPGAs). These special chips can be rewired via software to mimic nearly any kind of computer hardware. This makes them invaluable for simulations and design testing. If you are designing, simulating, or testing custom circuits for AI, aerospace, or advanced electronics, Vivado is the gateway to making that hardware actually work.

The core of the outrage stems from a change in Vivado's upcoming 2026.1 update. Previously, the free "Standard" tier supported both Windows and Linux. Under the new tiered model, the free "Basic" tier is restricted entirely to Windows. If you want to use Vivado natively on Linux, you'll be forced to step up to the "Core" tier, which demands an eye-watering $1,200 to $1,800 annual subscription.

AMD's defense on its community forums has also not landed well. The company claimed that 70% of Vivado users are on Windows anyway, alienating the academic researchers, engineering students, and open-source hobbyists who heavily favor Linux-native environments and rely on free tools to learn the trade.

A forum representative for the company stated, "No one is stopping users (students, etc.) to continue using the current versions of Vivado (any Vivado version prior 2026.1)," and developing using the free Vivado ML Standard Edition, arguing that it was only if users decided to update that they'd need the license.

"I guess no one involved in this decision thought about the millions of hobbyists and amateurs like myself using Vivado for their hobby projects," one disgruntled user replied. Another noted that many users are already discussing moving to alternate platforms like Lattice and Altera due to these changes.

AMD's forum representative confirmed they were "collecting all the feedback received and passing on to the relevant team/marketing" at AMD, leaving the door ajar for a possible change to this policy down the line.

California lawmakers may be backing away from a controversial age-verification requirement bill that alarmed Linux and open-source developers earlier this year, after a new amendment bill proposed exempting most open-source operating systems from the state’s upcoming Digital Age Assurance Act. In practice, that would likely exempt most mainstream Linux distributions — including Debian, Fedora, Ubuntu, Arch Linux, and Mint — from compliance requirements scheduled to take effect on January 1, 2027.

Assembly Bill 1856 (AB 1856), currently moving through California’s legislature ahead of committee reviews in June, would amend the state’s earlier age-assurance law by excluding software distributed under licenses that allow users to “copy, redistribute, and modify the software.”

The proposed amendment specifically states: “Operating system provider” does not mean a person or entity that distributes an operating system or application under license terms that permit a recipient to copy, redistribute, and modify the software.

The amendment follows months of backlash after California passed the original Assembly Bill 1043 (AB 1043), formally known as the Digital Age Assurance Act, in late 2025. The law sought to shift online age verification away from individual websites and apps and down to the operating-system level instead.

Under the original law, operating systems would be required to request a user’s age or birth date during device setup, then expose an “age bracket signal” to apps and app stores. The law, which defined brackets such as “under 13,” “13–15,” “16–17,” and “18+,” immediately raised questions about how such requirements would apply to decentralized, open-source software ecosystems.

Unlike Apple’s iOS or Google’s Android, most Linux distributions are not centrally controlled commercial platforms. Many are community-run projects maintained by volunteers, often without user accounts, telemetry systems, or even formal corporate ownership structures. Critics argued the law’s wording was so broad that it could technically force open-source operating systems to become age-verification platforms.

Privacy advocates, including the Electronic Frontier Foundation, criticized the legislation as invasive and warned it could create infrastructure for broader identity tracking online. Linux developers also questioned how California could realistically enforce such requirements on infinitely forkable open-source software projects.

The controversy became particularly heated after reports suggested platforms like SteamOS could still fall under the law due to their ties to proprietary application ecosystems. Valve’s Linux-based gaming platform ships with the proprietary Steam storefront and client, potentially placing it closer to Apple’s App Store or Google Play from a regulatory standpoint.

AB 1856 does not repeal the original Digital Age Assurance Act. Instead, it narrows the definition of who qualifies as an “operating system provider” under the law. Commercial platforms with proprietary app ecosystems could remain subject to California’s age-assurance requirements even if most open-source Linux distributions are ultimately exempted.

California Assembly Member Buffy Wicks introduced the amendment on February 11, 2026. However, the open-source exemption language appeared in later revisions that began drawing attention across Linux and privacy communities. The latest version is dated May 18, 2026, and as of May 19, 2026, the bill was read a second time and ordered to third reading.

Linus Torvalds declared the Linux kernel's private security mailing list "almost entirely unmanageable" on Sunday in his weekly post to the Linux Kernel Mailing List (LKML), blaming a flood of duplicate vulnerability reports generated by researchers running the same AI tools against the same code. The complaint accompanied the release of Linux 7.1-rc4 and a pointer to newly merged documentation that formalizes how AI-assisted bug reports should be handled.

The problem, according to Torvalds, is the combination of volume and redundancy: multiple researchers are independently discovering identical bugs using automated tools and filing them separately on a private mailing list, where nobody can see what has already been submitted. Maintainers end up spending their time triaging duplicates and directing reporters to fixes that were merged weeks earlier.

"AI detected bugs are pretty much by definition not secret, and treating them on some private list is a waste of time for everybody involved," Torvalds wrote on LKML.

Torvalds pointed developers to the project's security bug documentation, which states that vulnerabilities found using AI tools should be treated as public disclosures and submitted directly to the relevant maintainers, not routed through the private security list. Reports must be concise, formatted in plain text, and include a verified reproducer.

In March, Willy Tarreau, the creator of HAProxy and a longtime Linux kernel stable maintainer, said in comments posted to LWN that the kernel security mailing list, which received roughly two to three reports per week two years ago, now receives five to 10 reports per day. Most are solid finds, but the duplication across researchers using similar tooling has overwhelmed the existing triage process.

Torvalds urged researchers to go further than filing raw findings. "If you actually want to add value, read the documentation, create a patch too, and add some real value on top of what the AI did," he wrote. "Don't be the drive-by 'send a random report with no real understanding' kind of person."

This Torvalds-endorsed approach is exactly what fellow maintainer Greg Kroah-Hartman has been doing with his “Clanker T1000” system, a Framework Desktop-powered bug-finding tool: discover the issue, write the fix, take responsibility for the patch, and submit it publicly.

The Linux kernel project formalized its broader stance on AI-assisted contributions last month, establishing a project-wide policy that permits AI-generated code provided developers follow strict disclosure rules.

Under that policy, AI agents cannot use the legally binding "Signed-off-by" tag, and contributors must use a new "Assisted-by" tag for transparency. Every line of AI-generated code, and any resulting bugs, remains the legal responsibility of the human who submits it.

Microsoft is finally looking into fixing automatic GPU driver downgrades on Windows 11 that have plagued users since the OS's launch in 2021. Windows Latest reports that Microsoft has finally acknowledged the issue and is preparing a partial fix that will be released by Q4 of 2026.

Specifically, Microsoft is looking to start applying this fix to Windows 11 PCs in April 2026. Only by Q4 will the update be applied to everyone.

The fix Microsoft is cooking up narrows down how many devices Windows Update can target with specific GPU driver updates. GPU drivers that are published to the Windows Update catalog using this system incorporate a two-part hardware ID (HWID) in conjunction with computer hardware IDs (CHIDs). The latter is an ID designation designed to identify a specific PC model or hardware configuration.

This two-pronged approach gives Windows Update better information on when to expose GPU drivers to Windows 11 machines. The outgoing system Microsoft is using only considers a four-part hardware ID as part of a ranking system. The worst part about this system is that it will not take into consideration the GPU driver model specifically, which is what allows Windows Update to downgrade GPU drivers in the first place. Whichever driver is ranked highest in the Windows Update catalog for systems with a specified hardware ID, Windows Update will push even if the driver itself is outdated.

However, there is a caveat with this system — only device display drivers that target new devices can get the update. Existing drivers in the Windows Update catalog may still get forcibly applied on older systems.

Windows Update has long had a problem where the service will automatically downgrade GPU drivers in the right circumstances. This is specifically problematic with OEM machines when the OEM has uploaded a GPU driver to the Windows Update catalog. One issue I've run into personally is the inability to clean install Intel Xe drivers on my Windows 11 laptop. Doing so automatically triggers Windows Update to install several older Intel graphics driver revisions.

Unfortunately, Microsoft's update won't fix the issue entirely, but it is at least a start. To clarify, this specific fix is different from the Cloud-Initiated Driver Recovery feature Microsoft rolled out recently.

Microsoft has outlined a new feature of Windows called Cloud-Initiated Driver Recovery (CIDR). This newly introduced capability lets Microsoft remotely roll back a bad driver to a previously known good version on affected PCs. Moreover, it can work without user action or OEM intervention. It sounds like a magic bullet for a long history of Windows Update woes, but we’ll have to see if it works when the rubber hits the road. CIDR will only work with drivers distributed via Windows Update.

Windows Update can cause plenty of problems when a bad driver gets through testing and gets pushed to users. Indeed, buggy drivers have caused many a lost hour, gray hair, wrinkle, high blood pressure, and so on, among Windows veterans. Microsoft also notes that a bad driver often means a user has to manually intervene and roll back to “a low-quality driver for an extended period.” So, the new CIDR is cautiously welcomed.

Microsoft spells out the CIDR process in its Tech Community blog, and there we learn that recovery starts by the Windows developer triggering "a recovery action directly from the Hardware Dev Center (HDC) Driver Shiproom." Once a problematic driver is flagged, the system recovers the previously known-good version of a driver via the Windows Update pipeline. “This is handled through coordinated updates to the PnP driver stack and the driver flighting and publishing services,” says Microsoft.

Importantly, Microsoft notes that “recovery is delivered through the existing Windows Update infrastructure — no new client agent or partner tooling is required.” That should help CIDR work well with what we’ve already got and for it to become an established standard. Likewise, partners don’t need to get involved in CIDR, Microsoft will manage it. However, Microsoft asks that these partners “continue monitoring their driver quality metrics in the Hardware Dev Center dashboard and to respond promptly to any shiproom feedback on rejected submissions.”

CIDR is rolling out now for validation and testing, and it is expected to automatically support the Hardware Dev Center publishing process from September onwards.

Last week, news of Microsoft working on a new "Low Latency Profile" for Windows 11 was leaked by Windows Central. When enabled, it would increase CPU clock speeds momentarily to improve app opening times. This was met with widespread backlash, with the community thrashing Microsoft for essentially putting on a Band-Aid instead of addressing underlying Windows performance issues. Since then, the company has stood firmly by the decision on social media, reminding users that it's simply catching up to industry practice.

Senior developer and VP Scott Hanselman replied to a lot of concerned users on X and compared other operating systems to Windows 11, highlighting that this boosting functionality isn't anything new. That's true; every modern OS, including the bastion of efficiency, Linux, and even smartphones, already have this implemented. He went on to claim that "this isn't cheating" and implies that such a solution works in tandem with optimizing apps and code in further replies.

The Low Latency Profile (LLP) is part of Microsoft's broader "Windows K2" efforts to make Windows 11 smoother, more stable, and more efficient after years of sluggishness. As such, LLP works by boosting CPU frequencies for a quick assist in things like flyout delays for the Start Menu. Your CPU usage and clocks will spike for a fraction of a second to ensure the OS feels fast and responsive during those moments.

For all this to work on a technical level, though, you do require pretty aggressive clock parking so the CPU's prepared to shift into gear the moment it's needed to speed up an OS interaction. This is also important for mobile devices with batteries, such as laptops or handhelds that might consume more power when their cores are being utilized at a minimum for longer, compared to just idling in C-state after a quick burst at max speeds.

People across social media continue to dunk on Scott's replies, asking why Microsoft needed to wait until Windows 11 was in an intolerable state to think of this solution. That's entirely fair, too, considering just how long users have been complaining about the general reliability of the OS. Even devs who formerly worked on Windows have called out Windows 11 for its underwhelming navigation performance.

There's also the argument that perhaps Microsoft needs to optimize the operating system on a much deeper level before applying superficial patches like this, given complaints about the amount of bloatware a stock copy of Windows 11 comes with. Microsoft has even resorted to making an Xbox Mode just so games can bypass the bloat and run better.

It seems like the company is slowly realizing that the AI push it's been hiding behind for a few years at this point just isn't working out the way it was expected. Just look at Xbox — even with a new CEO that literally comes from Microsoft's AI department, it's making community-first changes like never before.

A recent update to Dell's pre-installed SupportAssist Remediation software is causing persistent blue screen of death errors and reboot loops on multiple Dell laptop models, according to user reports on Dell's community forum (spotted by Neowin).

The update, version 5.5.16.0 of Dell SupportAssist Remediation and the accompanying OS Recovery Plugin, was released on April 30th. Affected users report their PCs crash and reboot roughly every 30 minutes, with the cycle continuing indefinitely until the software is removed.

SupportAssist Remediation is a background service that Dell bundles on its Windows PCs to automate system recovery and repair tasks. Dell hasn’t acknowledged the issue or released a fix, but the problem has been confirmed across at least two Dell product lines so far: the XPS 15 9530 and the Dell Pro Plus 14.

Multiple users have independently analyzed their Windows crash dump files using WinDbg, Microsoft's debugging tool, and arrived at the same conclusion: The crash dumps show a bugcheck code of 0xEF (CRITICAL_PROCESS_DIED), with the faulting process identified as DellSupportAssistRemedationService.exe, part of the SupportAssist Remediation package installed at C:\Program Files\Dell\SARemediation\agent\.

Forum user Sygent, who owns an XPS 15 9530 running Windows 11 with BIOS version 1.29.0, posted a detailed dump analysis on Sunday, showing the failure pointing directly to the Dell process. A second user, MartinHBS2026, reported the same findings on a Dell Precision 3571 and confirmed the crashes stopped after removing all SupportAssist components. A third user, Waddo, confirmed identical crash dump results on a Dell Pro Plus 14 the following day.

Users in the Dell forum thread have identified two workarounds. The first and less disruptive option is to disable only the Dell SupportAssist Remediation service by running sc.exe config "Dell SupportAssist Remediation" start= disabled from an elevated command prompt, then restarting the PC, thereby preserving the rest of Dell's update and diagnostic tools.

The second option is to uninstall SupportAssist Remediation and the Dell SupportAssist OS Recovery Plugin for Dell Update entirely. Both approaches have stopped the crashes for users who have tried them.

This isn’t the first time that SupportAssist Remediation has caused similar crashes. A Dell forum thread from January last year described the same BSOD pattern on both Windows 10 and Windows 11 machines after a SupportAssist Remediation update, with WinDbg analysis again identifying the Dell software as the cause. That earlier thread went unresolved by Dell support.

Aside from causing blue screen crashouts, Dell’s SupportAssist suite has previously been found to contain significant vulnerabilities, allowing remote attackers to gain administrative privileges on Dell PCs.

AMD’s landmark K5 processor family will no longer be supported by Linux when kernel version 7.2 arrives. The Linux-watchers at Phoronix noticed the forced retirement of the venerable K5 in a recent patch designed to “remove support for TSC-less Pentium variants.” The lack of TSC (Time Stamp Counter) in the K5 apparently makes it a burden for developers to support in the kernel.

The K5 holds a special place in AMD history as the firm’s first independently designed x86 processor. However, it wasn’t a very popular processor as it arrived late, then offered lackluster performance in the competitive environment it joined.

AMD’s shiny homegrown 4.3M transistor chip featured a “RISC-based internal architecture that decoded x86 instructions into micro-instructions before executing them,” we noted in a 2008 retrospective. However, launch SKUs in 1996 were limited to clocks from 75 MHz to 133 MHz, and, due to being late, Intel’s Pentium line was already faster. AMD still managed to get an edge on the Cyrix 6x86, though.

As was de rigueur at the time, these AMD K5 chips were sold with a ‘performance rating’ (PR) figure, suggesting an integer performance comparison with an Intel Pentium with the indicated clock speed. For example, a second revision K5 with a 116 MHz clock was marketed as a K5 PR166. Enthusiasts don’t like this kind of obfuscation, even when it is clearly on the surface. We also note that this era marked the introduction of the heatsink and fan as a CPU-partnering necessity.

Intel i486, AMD Elan SoCs, and AMD Geode CPUs also put out to pasture

We reported a month ago that Linux devs had started to remove support for the 37-year-old Intel i486 CPU in patches destined for the Linux 7.1 kernel. That was probably a bigger deal than today’s AMD K5 news, as many more of these processors were sold.

Other lesser-known processor lines have also been retired from Linux support, but are still worth a mention for the sake of completeness. Specifically, the AMD Elan (i486‑class, TSC‑less) SoC for embedded systems which first launched in 1995, looks set to be retired in Linux 7.2. Similarly the AMD Geode x86 embedded processors (early 2000s Elan replacements) will be cut off from Linux support from Linux kernel 7.2.

With no end in sight for the RAMpocalypse, it is a little sad to see older hardware getting dropped from support. However, machines packing these retired processors can still be used in fun projects where a fully up-to-date security-hardened internet-connected patched OS isn’t essential.

Linux mascot Tux the penguin was first conceptualized on this day in 1996. In an email to a mailing list 30 years ago, Linus Torvalds informed the unwashed masses of his vision for a Linux logo prototype. It should be a contented, cute, and cuddly, slightly overweight penguin, he argued.

Dialing down the details, pivoting from a world map

Torvalds’ contextual sketching of Tux came in response to another developer who was talking about using a clipart concoction involving a map of the world to represent the open-source OS.

The Linux supremo was open to holding a logo competition, but instead of a complex encapsulation of the world as a logo, he proposed a penguin. Penguins embodied three positives, thought Torvalds, being universally considered cute, cuddly, and contented. The Linux founder wanted the penguin to be highly stylized, “not a lot of detail - just a black brush-type outline,” as per the logotype rule of thumb. He also basically dismissed any complex penguin + world map fabrication.

A contented, but definitely not randy, penguin

First impressions count with logos. With penguins, the designer would have to be careful in their artwork to prevent any unintentional conclusions regarding its contented state, reasoned Torvalds at some length.

“Now, with penguins, (cuddly such), 'contented' means it has either just gotten laid, or it's stuffed on herring,” explained the lead Linux dev to mailing list subscribers. “Take it from me, I'm an expert on penguins, those are really the only two options.”

To give this overfed and content impression, Torvalds explained that Tux should be “sitting down after having gorged itself, and having just burped,” and overweight without going into fat territory.

Happy 30th, but is it time to mature?

Though we reckon Torvalds was correct in pushing for a penguin expressed in a simple brushstroke, the Tux mascot is still pretty detailed/ornate compared to a typical tech company logo. In 2026, even the fox from Firefox is on the way out, being reduced all the way to a circular spot, if we are reading the official teaser video correctly.

Other companies have vastly simplified and minimized their logos, so it seems inevitable that Tux will become a shadow of his or her former self in due course. It is true that a simpler logo for Linux would be good for branding, and a reduced detail/color identity could be a boon for merchandise and makers, too.

A top Microsoft exec has admitted that Windows 11 still relies on a bunch of old code from the 1990s. It is refreshing for Microsoft Azure Chief Technical Officer Mark Russinovich to highlight this fact on social media, but it might not surprise as many folks as he thinks.

As Russinovich eloquently puts it, those of us invested in the computer scene in the 90s “were thinking flying cars and moon stations by the year 2026, not Win32.” The admission that such old software tech is still the "bedrock" of Windows today may be the CTO strategically sharing a cold, hard truth, providing a 'let's be real' moment as part of Microsoft’s latest charm offensive. Sharing a candid confession indicates that the corporation is actually aware of the issues in its OS.

Remember, the firm is currently in the midst of a major transformation, targeting enthusiast hot button areas like Windows performance, overhead, and reliability. This drastic pivot was cautiously welcomed in contrast to Microsoft being widely slammed for boasting about Windows “evolving into an agentic OS” last November. Currently, Microsoft seems to be flailing around, trying to stop folks straying to pastures greener like Mac and Linux.

However, Win32 isn’t inherently labeled as ‘bad’ by the Microsoft CTO. Though it is ancient, it has probably stuck around for good reason. “I think one of the reasons it’s got this staying power is just a fundamental layer inside of Windows that so many apps have built on,” notes Russinovich. “So many technologies and ecosystems have been built on top of it that it’s kind of a bedrock.”

The CTO explains that Win32 has persisted even when facing targeted existential threats from within Microsoft, particularly in the Windows 8 era. “There’s been various times in Microsoft’s history where we thought we’d reboot the Windows API surface, like WinRT, that actually didn’t play out the way a lot of people expected it to.”

In closing, Russinovich highlights that Win32 was also the bedrock for tools like Sysmon and ZoomIt, which he actually wrote back in 1996. These tools are now “more relevant than ever in 2026,” as parts of Windows 11 and PowerToys, respectively, reckons the CTO.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added a newly disclosed Linux vulnerability, dubbed “Copy Fail,” to its Known Exploited Vulnerabilities catalog on May 1st, warning that the flaw, tracked as CVE-2026-31431, is already being used in active attacks and urging rapid patching across affected systems.

The vulnerability resides in the Linux kernel‘s “algif_aead” cryptographic interface and allows unprivileged local users to escalate privileges to root. In practice, this means an attacker with limited access to a system can gain full administrative control.

Security researchers at Theori disclosed the flaw publicly last week, releasing a working proof-of-concept exploit alongside their findings. According to the team, the exploit is “100% reliable” and functions without modification across multiple major Linux distributions, including Ubuntu 24.04 LTS, Amazon Linux 2023, RHEL 10.1, and SUSE 16. That level of portability is unusual and lowers the barrier for attackers seeking to weaponize the bug.

At a technical level, the bug enables attackers to write controlled data into the kernel‘s page cache, a low-level memory structure, ultimately allowing privilege escalation. While the exploit requires local access, it still allows attackers to break out of standard user restrictions and gain full control of the system.

Compounding the risk, a discussion on the Openwall oss-security mailing list suggests that the vulnerability and the working exploit were publicly disclosed without prior coordination with Linux distribution maintainers. In typical responsible disclosure processes, vendors are given advance notice to prepare and distribute patches before technical details are made public.

In this case, however, maintainers indicated that no such heads-up was provided, leaving some distributions without fixes ready at the time of disclosure. One contributor noted that older long-term support kernel branches had yet to receive backported patches, forcing developers to rely on temporary mitigations, including disabling affected cryptographic modules.

The result is a compressed response window in which defenders must scramble to deploy updates while attackers can immediately leverage publicly available exploit code.

That dynamic is reflected in CISA‘s unusually swift inclusion of the flaw in its exploited vulnerabilities list, signaling that the issue poses a significant and immediate risk. CISA has given U.S. federal agencies two weeks to apply patches, in line with Binding Operational Directive 22-01, and has also urged all organizations to prioritize remediation.

Linux vendors have begun rolling out kernel updates to address the flaw. However, with exploit code already in the wild, users running older or unpatched systems may remain vulnerable until the fixes are applied.