A technology enthusiast claims that the oldest GUI application that still runs on Windows 11 is CDPLAYER.EXE from November 1992. The app had to run on Microsoft’s newest consumer OS without modifications or emulation involved to be chosen as the ‘winner’ of their experiment. Blogger Enlyth expected something from the early NT era, as Windows 11 doesn’t support 16-bit apps, despite its strong backward compatibility. Finding an app that is almost 34 years old that still works with a simple double-click is a remarkable result.

At the beginning of their journey to find the oldest Windows UI app that just works on Microsoft’s newest OS, Enlyth confirmed FREECELL.EXE from February 1993 would still run without issues. This game was distributed alongside the Win32s environment, designed to allow some 32-bit applications to run on the 16-bit operating systems like Windows 3.1 and 3.11. Win32s was made available in beta in October 1992, but went mainstream in July 1993.

A tip Enlyth received via a tech forum suggested that FREECELL.EXE was a candidate for the oldest GUI app remaining compatible with Windows 11. However, the blogger wasn’t satisfied with this easy win and dug through “some early NT 3.1 pre-release versions that seemed promising.” Build 347 caught the detective’s eye, specifically CDPLAYER.EXE, linked on Nov 16, 1992. That indeed seems to be the earliest GUI app that works without modification or emulation on Windows 11. But this knowledge almost defied Enlyth’s eye as their system is, like many modern systems, optical-drive-less. Luckily, adding a small DLL (cdemu.dll) allowed Enlyth to emulate a CD drive and demonstrate that the 1992-era application still functions as intended.

I wanted to verify that CDPLAYER.EXE was still usable on the latest Windows 11 release. Unfortunately, the multi-part.ARJ archive of Windows NT 3.1 that I found on Archive.org threw up errors when I tried to pick through its contents. I have a USB-attached optical drive that plays CD audio in Windows 11, so I thought I could get CDPLAYER.EXE to run without any extra DLL.

Lastly, Enlyth wanted to push the envelope a little and see what even more ancient Windows apps might work if they got some help from the Winevdm project on 64-bit Windows. “Using otvdm does feel like cheating,” admitted the digital sleuth, and we’d agree. However, being able to run 16-bit apps in Windows 11 ratcheted back the wheels of time. The result was that Enlyth managed to enjoy “a fully playable version of REVERSI.EXE dated 15-Nov-1985.” That’s a GUI-driven game distributed as part of Windows 1.01 and is roughly 41 years old.

A new "Advanced Performance Extensions (APX)" option has been spotted in a version of Windows 11 made available to Windows Insiders on October 23, with the feature set to enable a boost in application performance on compatible chips. At the moment, those chips don't exist. But when they do, this feature is the one that you'll want to flick on if you're using one of them. The new toggle was reported by Neowin after it was first spotted by a poster on the X social network. The feature debuted in build 29295 as an Experimental build, so it's unlikely that it will make its way to the version of publicly available Windows 11 anytime soon.

Intel announced APX back in 2023, confirming that it features 16 additional general-purpose registers and three-operand instruction formats with a new data destination register for many integer instructions. Doubling the number of general-purpose registers from 16 to 32 will allow code compiled with APX to run with 10% fewer loads and 20% fewer stores than Intel 64's baseline, says Intel. APX has been available in the GCC compiler since version 14, with subsequent versions up to GCC 17, which is targeting a 2027 code freeze, adding additional support. LLVM and MSVC have preliminary support, as well. Although enablement has been going steady for the past two years, developers will still need to recompile their applications with the proper flags for APX-capable CPUs to leverage those instructions.

Not that there's any real need to rush just yet. The fact that no APX-capable chips are on sale yet means that enabling the feature in Windows 11 build 29295 does nothing currently. But it's clear that Microsoft is getting its ducks in a row ahead of time. Intel's Nova Lake Core Ultra 400-series chips are expected to be the first to feature APX support, but they won't break cover until early 2027. Even then, it's likely that the 28-core version will debut first, with the 52-core model made to wait until later in the year. These are consumer chips, of course, with Intel's Xeon 7 'Diamond Rapids' bringing APX support and up to 256 cores to the data center, also in 2027.

The good news is that you might not have to buy a new chip to enjoy improved Windows 11 performance. Five years after Windows 11's debut, Microsoft has already said that it's working to make its operating system play more nicely with machines with just 8GB of RAM. But what Microsoft gives with one hand, it soon takes away: an expansion of the Windows 11 Memory Integrity feature will reduce gaming performance on some systems.

Professional Windows crusher NTDEV has showcased their next-generation tool for compressing Windows 11 into the tiniest of tiny installs. Based on their newest and unreleased Pico11, they managed to create a “proof of concept I put together to see how small I could make a Windows 11 ISO while keeping a working desktop and a few familiar apps.” Moreover, it’s a perfect installer to shove on a 700MB CD-ROM without wasting space, with this demo version weighing in at 699,811,840 bytes.

The test system (a VM with 4GB allocated) used around 883MB of RAM.

In the above video, NTDEV demos a freshly installed Windows 11 ISO that had been processed with Pico11. The desktop looks familiar to anyone currently using Windows 11. “Calculator and Settings still open, Notepad saves files, and Paint still lets me draw questionable logos,” highlights the dev. However, it is also pointed out that “Task Manager might look a little older than you remember.” The older Task Manager seems to be a lightweight legacy version. It may have been possibly swiped from Windows 7, but its exact origin isn’t divulged by NTDEV.

At this time, NTDEV admits what you see is “an experiment, not a replacement for a normal Windows installation,” and that’s mainly because Windows Update and general servicing have been removed to fit inside the constraints of CDR capacity. If you are interested in creating Windows installs like this, the good news is that NTDEV says they are working on adding what they describe as Pico11 capabilities to the Tiny11 builder tool, which you can find on GitHub.

Tiny11 has already demonstrated impressive Windows 11 ISO building capabilities with its Tiny11 mode, Tiny11 Core mode, and Custom mode. Pico11 sounds most closely related to Tiny11 Core as it eschews servicing and recovery support. However, there appears to be some more under-the-hood tweaking, which may have been evidenced in this new showcase by the presence of the older version of Task Manager.

Tiny11 has historically been responsible for even smaller Windows 11 installs, but the extreme 100MB distillation of the OS, for example, came without any Windows 11 UI. Builds could also be remarkable for using tiny amounts of RAM – as little as 176MB. More typical and useful were custom builds powered by Tiny11 where 'bloatware' was removed and that weighed in at around the 2GB mark.

Hopefully we will learn more about Pico11 and get greater insight into its capabilities soon.

Windows XP became available at retailers for the first time on this day back in 2001. It was ushered in with Microsoft's largest and glitziest launch event since Windows 95, but the bigger news was its delivery of an OS with modern underpinnings and features. Thankfully, it lived up to the hype and would ensure nearly 13 years of favor among enthusiasts, but that might be partly due to the failure of the unloved Vista.

The NYC launch event for Windows XP in 2001 was the centerpiece of a lavish $500 million campaign Microsoft had planned for the new OS. However, celebrations were somewhat muted due to the aftermath of 9/11. Microsoft actually dumped its intended ‘Prepare to Fly’ launch slogan for ‘Yes You Can’ for this obvious reason.

Nevertheless, the launch was still a significant event and featured NYC Mayor Rudy Giuliani joining Bill Gates on stage. Gates framed the big launch as evidence that “New York is back and open for business.” There was also a free lunchtime concert in Bryant Park featuring Sting, followed by a Times Square NYC takeover. Meanwhile, retail stores like CompUSA, Circuit City, and Best Buy opened at midnight for eager tech beavers to grab a copy of Windows XP at its freshest.

At the launch presentation, Gates said that the debut of Windows XP represented the end of the era of MS-DOS, which had underpinned a UI or shell known as Windows for many years. For consumers, that stretched all the way up to the much maligned Windows Me.

As we mentioned in our 40-year retrospective of Windows last year, Windows XP was the real ‘Start Me Up’ moment. That’s because it brought the Windows NT core to consumer PCs – replacing the archaic DOS and its restrictions and drivers. Thus, Windows XP would become well regarded for reliability, performance, and security (after a few teething troubles), and its new UI was claimed to make tasks 25% easier to complete, too.

Some of the technical features that would be widely welcomed in XP included USB plug-and-play support that worked, built-in CD burning software, and ClearType support as new LCDs started to usurp bulky CRTs on desks.

During Windows XP’s supported life (October 2001 to April 2014), there would be three major Service Pack (SP) releases. It also saw DirectX 8.1 to 9.0c arrive for gamers. In the meantime, Windows Vista made something of an unwanted splash, launched to consumers in January 2007. Windows XP’s lengthy extended support meant that folks could skip Vista entirely and move straight to Windows 7 when it hit retail and new-build systems in October 2009.

Overall, it is interesting to observe that Windows XP’s lifespan was actually over two years longer than Windows 10, which was (in)famously launched as “the last version of Windows.”

While Windows overclockers have spent years lazily sliding UI controls to adjust frequency curves and tweak voltages inside Ryzen Master, Linux users have largely had to treat their CPU tuning like an archaeological dig into the opaque veil of UEFI/BIOS firmware. Well, rejoice, Linux users, as AMD has officially published a fresh set of patches for the Linux kernel introducing AOD (AMD Overclocking Driver) support for Ryzen processors, Phoronix reports.

Instead of forcing developers to reverse-engineer closed-source firmware hooks or rely on messy, machine-specific ACPI workarounds, this new kernel driver is a direct pipeline to AMD's platform adjustments. By exposing core tuning capabilities straight through the standard sysfs interface, AMD is laying down an official, upstreamed foundation for software-level CPU management.

Right out of the gate, the driver handles platform-level SMT toggling, memory clock visibility, and power tunables. That's right: you can now toggle Simultaneous Multithreading (SMT) dynamically through this driver interface. That works through the CPU hotplugging mechanism and acts as a clean alternative to passing the old 'nosmt' boot parameter to the kernel. The new driver also allows real-time monitoring of memory clocks, and initial power controls are being wired up, too.

Now, if you're expecting a polished, one-click official AMD application equivalent to Ryzen Master for Linux, just pump the brakes. AMD is following its open-source amdgpu graphics driver playbook here, building the kernel plumbing and then leaving the user-space presentation layer entirely up to the community. That means you're going to have to wait for utilities like CoreCtrl to build out interfaces for this new driver, but it shouldn't be long now before that work gets underway in earnest.

This approach is arguably a better fit for the Linux philosophy anyway. Because the controls are being exposed via clean kernel sysfs nodes, it won't be long before independent developers integrate these knobs into powerhouse open-source monitoring and tuning suites, or even write dedicated desktop environment extensions specifically for the purpose of tweaking Ryzen processors.

The new patches are currently winding their way through review on the mailing lists, meaning mainstream kernel integration is on the horizon. For a DIY enthusiast who loves squeezing every last MHz out of silicon while maintaining a fully open-source software stack, this is easily the most exciting hardware-enablement milestone I've seen in a long time.

After a few revisions of his position on AI-assisted contributions to the Linux kernel, Linus Torvalds has posted his own first LLM-assisted patch. The development branch purports to fix an old issue with massive cache contention when many CPUs are reading the same file — a scenario potentially encountered when using shared libraries, databases, and web servers. Several developers had already made attempts over the years at fixing the issue, all with varied results, none quite ideal as an all-encompassing solution.

Torvalds posted his own draft for solving the problem in early 2024, and has used it on his own laptop since that time. However, he recently took the plunge and decided to "try to actually solve this thing using an LLM." He's now posted his solution in a development branch, and claims that he's seen a 23x performance improvement in a dedicated synthetic benchmark, though he notes that actual real-world impact will be far less significant, as "no real load" will witness those figures. If we had to guess, this improvement would benefit server workloads far more than desktop machines.

Over time, Torvalds has broadly taken a pro-AI stance on LLM tooling, at least within the purview of the tightly controlled, review-heavy environment of the Linux kernel code. Last July, he stated he's "willing to absolutely put [his] foot down" on AI haters, pointing out that an automated code review tool the kernel team uses outperforms humans, and that it caught basic programming mistakes that shouldn't have been submitted in the first place.

The team is even changing its policy to no longer require that patch authors disclose they used an AI tool when generating their code. Torvalds once again took an assertive stance, reiterating that users should treat LLMs as yet another tool, likening it to compilers or editors. In his view, he simply expects that "people do their best and [...] understand what they are doing."

Some might say that few people in the world are better-suited to properly employ an LLM than Torvalds, and by extension, kernel maintainers. There's an entire universe of difference between a senior master programmer using the LLM to speed up the boring parts of his work, and some newbie with a credit card going "claude make linux faster plz no mistakes."

However, It's not all roses. Thanks to how adept AI agents have become at recognizing common security flaw patterns, the Linux security mailing list became "unmanageable" earlier in the year. Linux has been fixing CVEs at an astonishingly rapid pace of around 2,000 per release. Still, the team's hand is being forced into dropping older hardware drivers, as they're often the target of numerous security reports, despite their negligible install base.

After the rough reception of Windows Vista, Windows 7 launched in 2009 to largely positive reviews. Even 17 years later, it remains one of the most beloved versions of Windows ever released. But how does this nearly two-decade-old operating system hold up on modern hardware? We managed to install Windows 7 on a modern PC and put it to the test across eight DirectX 11 games and two DirectX 9 titles to see how its gaming performance compares to Windows 11 today. Surprisingly, Windows 7 still carves out many notable wins over its successor.

At launch, Windows 7 was very similar to Windows Vista in many respects. Vista had introduced significant changes under the hood compared to Windows XP, including technologies such as SuperFetch, ReadyBoost, ReadyDrive, new asynchronous APIs, and other I/O improvements. It also introduced native processor power management and various memory-management enhancements. On the visual side, Vista was the first version of Windows to feature Windows Aero, with its distinctive glass-like window borders.

Windows 7 retained many of these underlying technologies while addressing several of Vista’s biggest criticisms. One notable improvement was greater control over User Account Control (UAC), allowing users to adjust how frequently they received UAC prompts. In Vista, these prompts could appear far too often, becoming a major source of frustration for many users.

Windows 7 also benefited from something that had nothing to do with the operating system itself: more powerful hardware. When Vista launched, many mid-range and budget PCs struggled to deliver smooth performance, particularly when using more demanding visual features such as Windows Aero. By 2009, however, PC hardware had advanced considerably, and the performance required to run these features smoothly was no longer a significant concern for most users.

The Challenge of Running Windows 7 on a Modern PC

Getting Windows 7 running on modern hardware is not as straightforward as installing a current version of Windows. At 17 years old, the operating system predates many of the technologies used by modern PCs, meaning driver support is extremely limited. For example, Windows 7 does not include native NVMe or USB 3.0 support, so the necessary drivers have to be slipstreamed into the installation ISO. Microsoft did eventually release patches that added NVMe support, but without injecting the appropriate drivers into the ISO, the Windows 7 installer will not recognize an NVMe drive.

Our system is based on AMD’s AM5 platform (with the full system specifications detailed later in the article), which presents another limitation: there are no official Windows 7 chipset drivers for the platform.

Fortunately, we are using an RDNA 2 GPU, which does have Windows 7 driver support, allowing us to use a relatively modern graphics card for our testing.

The motherboard is also an important consideration. Modern motherboards that have dropped CSM (Compatibility Support Module) and legacy boot support can make installing Windows 7 considerably more difficult, and in some cases may prevent the operating system from booting altogether. Fortunately, our motherboard still supports CSM, so this was not an issue for our setup.

Test System

Windows 7 system specs

• AMD Radeon RX 6950 XT
• Ryzen 7 9800X3D
• 64GB (2x32GB) G.SKILL Flare X5 DDR5 @6000 MHz CL30
• Seagate Lightsaber FireCuda (530) NVMe SSD
• ASUS ROG STRIX B850-F Gaming WiFi
• Corsair Nautilus 360 RS AIO Cooler
• HAGS not supported by driver
• Windows 7 Ultimate 64-bit Service Pack 1 (Build 7601)
• AMD Adrenalin 22.6.1 for Windows 7 (2022)

Windows 11 system specs

• AMD Radeon RX 6950 XT
• Ryzen 7 9800X3D
• 64GB (2x32GB) G.SKILL Flare X5 DDR5 @6000 MHz CL30
• Seagate Lightsaber FireCuda (530) NVMe SSD
• ASUS ROG STRIX B850-F Gaming WiFi
• Corsair Nautilus 360 RS AIO Cooler
• HAGS not supported by driver
• Windows 11 25H2 (Build 26200.9278)
• AMD Adrenalin 22.6.1 for Windows 11 (2022)

For Windows 7, we disabled Secure Boot, enabled CSM, and set Boot Device Control to Legacy OPROM Only. Enabling CSM means that we no longer have access to Resizable BAR (it's not supported anyway). For Windows 11, we disabled VBS (Virtualization-Based Security) and HVCI (Hypervisor-Protected Code Integrity).

It is important to note that while we used Adrenalin 22.6.1 for both Windows 11 and Windows 7 testing, the two packages contain different internal driver versions. Although both packages were released in June 2022, the Windows 11 driver is based on a more advanced codebase than the Windows 7 driver.

In both cases, we performed a clean install of each operating system and filled the SSD to about 50-60%.

Performance Testing

We tested ten games in total: eight using DirectX 11 and two using DirectX 9. The DirectX 11 titles are the primary focus, as both systems support them natively. By comparison, our Windows 11 system will run DirectX 9 games through the D3D9On12 mapping layer, while our Windows 7 system will run them natively. There are ways to get around the use of D3D9On12 on Windows 11, but we want to evaluate the out-of-the-box experience that most gamers would encounter. As a result, we expect Windows 7 to have an advantage in the DirectX 9 titles.

It will become apparent in the results below that the advantages of each operating system will vary depending on whether we are CPU-limited or GPU-limited.

Metro 2033 Redux (DX11)

Metro 2033 Redux was released in 2014 and features a new lighting engine, higher visual fidelity, and new locations for certain levels. The game is predominantly GPU-bound, but there are moments when GPU utilization drops sharply as you traverse the game world. At these points, the CPU becomes the limiting factor, resulting in a corresponding drop in performance.

Although Windows 11 delivers a higher average frame rate, Windows 7 handles the CPU-related performance drops much better, resulting in significantly stronger 1% lows. Installing the AMD chipset drivers and enabling Resizable BAR improves 1% lows on Windows 11 slightly, but it still falls well behind Windows 7.

Windows 11’s more advanced graphics driver appears to provide an advantage in GPU-limited scenarios, while Windows 7’s lower CPU overhead offers more consistent frame pacing, though with lower peak performance.

Batman: Arkham Origins (DX11)

Batman: Arkham Origins runs on a modified version of Unreal Engine 3 and uses several DX11 enhancements such as Tessellation, Ambient Occlusion HBAO+, Percentage Closer Soft Shadows (PCSS), and Depth of Field (DoF).

When CPU-limited at 1080p, Windows 7 once again puts in a strong showing, outperforming Windows 11 in both average frame rate and 1% lows. Surprisingly, Windows 7 also comes out ahead at 4K in Origins, though with a far smaller advantage. As we will see throughout the remainder of our testing, however, this is a rare occurrence. Even so, Windows 7 maintains a slight performance advantage over Windows 11 at 4K in this title.

Batman: Arkham Knight (DX11)

Batman: Arkham Knight was both a critical and commercial success, despite a notoriously troubled PC launch plagued by severe bugs and major performance issues. Visually, however, the game still holds up remarkably well, and modern hardware is more than capable of brute-forcing this demanding PC port.

Windows 7 again delivers higher performance at 1080p when we are CPU-limited. Windows 11 jumps ahead when we become GPU-limited at 1440p and 4K.

Batman: Arkham City (DX11)

Batman: Arkham City was the second entry in the series, following Arkham Asylum, and the first to support DirectX 11. This introduced features such as tessellation, which adds greater geometric detail to characters and environments.

In Arkham City, our system is GPU-bound at every resolution tested, giving Windows 11 the advantage across the board.

The Witcher 3: Wild Hunt (DX11)

The Witcher 3 faced some controversy at launch over reductions in image quality compared to its initial reveal. CD Projekt Red quickly released a patch addressing these concerns and improving the game’s visuals. From a performance perspective, however, the game was extremely demanding at launch.

While the game is very GPU bound in general, at 1080p we did encounter a slight CPU bottleneck, which gave Windows 7 an advantage in 1% lows. At 1440p and 4K, Windows 11 takes a slight lead.

Control (DX11)

Control is the newest title we tested for this comparison, having launched in 2019. While the game introduced several ray tracing features, these were exclusive to the DirectX 12 API. Since Windows 7 does not support DirectX 12, we tested Control using DirectX 11 on both operating systems. Even without ray tracing, Control remains the most graphically advanced title in our Windows 11 vs Windows 7 comparison.

Windows 11 wins across the board. This is not a surprise, as we are GPU-limited across all resolutions tested.

Hitman: Absolution (DX11)

Hitman: Absolution was released in 2012 and was the first game to use the Glacier 2 engine. The updated engine could handle crowds of up to 1200 characters, which was unprecedented at the time. The game also featured several DirectX 11 enhancements, including global illumination and tessellation.

This is another game that pushes the GPU hard, regardless of resolution. Our test system was GPU-limited even at 1080p.

Hitman 2 (DX11)

Hitman 2 was released in 2018, making it the second-newest game in our operating system comparison. It features detailed environments, dense crowds, and full reflections across many surfaces, making it an impressive-looking title overall.

Hitman 2 is another example where our test system is GPU-limited at every resolution, giving Windows 11 a clean sweep across the board.

Batman: Arkham Asylum (DX9)

We now move to our first DirectX 9 game. As previously mentioned, Windows 7 should have an advantage here because our Windows 11 system must use the D3D9On12 mapping layer for DirectX 11 games. But just how much of an advantage?

Significant advantages for Windows 7 in average frame rate and 1% lows, especially at 1080p and 1440p. The advantage is reduced at 4K, but the performance is still smoother overall in Windows 7. Another translation layer, such as DXVK, may close the gap.

Borderlands 2 (DX9)

Borderlands 2 is our second DirectX 9 game and the final overall game tested.

Once again, another massive win for Windows 7 at the lower resolutions. The performance at 4K is virtually identical.

Bottom Line

Windows 11 is optimized for GPU-hungry games

The results are interesting, but perhaps not entirely surprising. The DirectX 9 results are largely in line with our expectations, given that Windows 11 must run these games through the D3D9On12 mapping layer, yielding substantial advantages for Windows 7.

The DirectX 11 results are more nuanced, but a clear trend emerges: Windows 7 has the advantage when we are CPU-limited, while Windows 11 performs better when we are GPU-limited. This makes sense given that Windows 11 uses graphics drivers built on a more advanced codebase, while Windows 7 is a leaner operating system with fewer background processes and, consequently, lower CPU overhead.

Microsoft has recently detailed its K2 plan, which aims to improve the performance and reliability of Windows 11. We hope these continued efforts to improve Windows 11 pay off.

The lower CPU performance we observed in Windows 11 cannot be attributed to its most notable security features, such as VBS (Virtualization-Based Security) and HVCI (Hypervisor-Protected Code Integrity), as we disabled both during testing. Notably, Windows 7 does not support VBS or HVCI at the software level, while Windows 11 supports hardware virtualization extensions (such as Intel VT-x or AMD-V) and Second Level Address Translation (SLAT). Additionally, fixed-function hardware can reduce the impact of virtualization to varying degrees, based on the CPU architecture's capabilities. However, additional telemetry and other background services still pop up and use precious CPU cycles.

Using the latest chipset drivers and enabling features such as Resizable BAR does not help Windows 11 close the gap in CPU-limited scenarios by any significant margin. Ultimately, we would like to see Windows 11 become leaner and more efficient, as our results suggest there is still some performance left on the table, particularly on the CPU side.

A new compression model, called CRAM, offers a different path to compression that avoids swap entirely by keeping the compressed data in memory, and it offers up to 452x the performance of ZRAM. I was a kid in the 1990s when the idea seemed so simple to me: I can use PKZIP to compress my files, so why can't we do that with RAM? Indeed, I am not a singular genius, and many other people had the same idea, so memory compression has been a feature of most operating systems for a long time. In Linux, the most popular options are zswap and ZRAM, but both of these options are fundamentally swap-layer features. CRAM is a new take that claims to boost performance tremendously.

CRAM was conceptualized by Gregory Price and his team at Meta. The central realization that seems to have spurred the development of CRAM is that the largest portion of the performance hit from compressed memory isn't the compression; that's tiny. No, the largest hit apparently stems mostly from the fault itself and the swap behavior. So the thinking seems to have been "what if we just do zram, but completely in memory instead of as swap?"

That's a gross simplification of an enormously complex project, but what CRAM seems to be doing is making use of mechanisms Linux already has to enable radically higher-performance compressed memory, particularly on reads. It uses a private NUMA node (essentially, a ghost CPU) instead of pretending to be a block device, and this lets Linux continue using all of its memory semantics, including migration and ballooning, to manage CRAM.

A critical part is the "Chicken Bit," which tells Linux that it has to stop trying to use CRAM while it is busy managing allocations. See, compressed memory seems straightforward until you start actually thinking about it. Compressibility of data varies tremendously based on what you're compressing, all the way from big piles of zeroes (perfectly compressible) up to already-compressed data (non-compressible). Given that, how do you know how much "logical" RAM you have when some of it is compressed? And how do you know when you're going to run out?

CRAM hasn't actually solved that problem yet, it seems; the slides I'm working from seem to establish this as an unsolved problem and an area of ongoing research. But the Chicken Bit is one way it can at least stop cascading failures (colorfully called a "poison storm" in the presentation) from happening when writes outpace CRAM's ability to allocate them.

Because CRAM is stored in RAM and treated as RAM, with full cacheline/byte access, it can be accessed in a read-only fashion with little delay; just the cost of hardware-offloaded compression. As a result, CRAM "runs at DRAM speed," as the creator says in the slide above. While the graph already looks impressive, it's a logarithmic scale; CRAM, in the worst case, is doing 489 million operations per second versus ZRAM's 1.1 million. It's barely comparable.

Even when you enable writes, CRAM is still much faster than ZRAM; 5.4x in the worst tested case of 20% writes. That's a huge drop from the 452x read-only case, but keep your context; a 5.4x speedup is still titanic. The massive performance cliff when writes are involved comes down to the need to page fault and migrate folios back to the original NUMA domain, as you can't write directly to compressed data; you'd corrupt everything.

My explanation of CRAM might not be completely correct; I wasn't at the Linux Plumbers' Conference in Prague to hear the presentation directly, so I'm working off of the slides available from the session information site (h/t to Phoronix for the spot) I think I've managed to grasp the gist of what Price is getting at, though.

While the obvious target of the work here (given its origin at Meta Platforms) is big Linux servers, ZRAM and Zswap are used all over the Linux ecosystem, even on machines as constrained as the Steam Deck. Many distributions enable one or the other by default. CRAM seems like it could offer a considerable speed-up for some of these machines, so hopefully it finds its way into the kernel once the remaining implementation questions are answered.

Windows 11 was released five years ago, on October 5, 2021. It feels like it's been around longer, as Microsoft’s latest OS has generated numerous headlines, mostly concerning the pain it put users through. We’ve all aged with it. Things might be settling down, at last, though, as the 26H2 update started to roll out just a few days ago, and it is not promising a revolution, simply a “predictable and low-disruption” update.

After the crowd-pleasing Windows 10’s return to form, it was all too predictable that Windows 11 would misstep in some unexpected way, or actually in several ways. Microsoft is pretty creative with its misreading of the market. At release, the biggest issue with the new OS was that it sought to force lots of capable hardware into retirement. This issue churned for months, with folks wrangling system files to bypass minimum system requirements, and Microsoft seemingly shifting the goalposts around at the same time.

Another early controversy was Microsoft continuing to push users into setting up Windows using an online Microsoft account, and cutting off avenues of avoidance. Again, communities had to fight the OS to make it work the way they wanted, often with a simple local account. This struggle continues to this day. Microsoft paints the requirement as good for users, providing OneDrive backups, syncing across devices, and providing extra recovery and security features. However, forced online accounts are also a commercial vehicle for selling digital goods and services.

Things had settled down in Windows land by 2024, but Microsoft spoiled the broth again with the introduction of the Copilot+ PC era. In some ways, it showed some foresight in sensing that AI was going to be big. Nevertheless, this was another clear misstep, with gaffes/scares like the AI-centerpiece Windows Recall app.

Copilot+ PC’s failure was confirmed by Microsoft and its OEM partners when they quietly killed off all Copilot+ PC branding earlier this year. For now, built-in AI is being de-emphasized, and Microsoft is looking at a cross-platform agentic model.

A change of direction

This year has also seen Microsoft publicly realize that people need Windows 11 as a foundation for their productivity tasks and gaming fun. The OS isn’t the destination. Thus, in spring, execs promised to clean up and optimize Windows 11 for its basic everyday use. Going forward, Microsoft has dangled the carrot of faster built-in apps, lower memory/resource use, and other foundational OS optimizations.

Windows 11 26H2 was released to consumers last week. As a battle-scarred Windows veteran, I’ve not clicked the update button yet on any of my machines, but there are reasons to be optimistic that it doesn’t deliver new nightmares. Version 26H2 is being distributed with the promise to deliver a “predictable and low-disruption” update. Boring is good.

Despite the aforementioned controversies, as well as the usual collection of silly/scary bugs that needed ironing out, people are still using Windows 11. It is widely adopted and dominates the PC landscape. MacOS and Linux have made inroads in terms of users, but Windows still looks mostly unassailable on roughly 76% of all desktop/laptop computers. Among Windows versions, it holds nearly 72% of the market, with Windows 10 rapidly declining and dipping under 28% at the most recent count.

It won’t be long until Linux enthusiasts will be able to complete a clean kernel build in under 10 seconds. Linux expert and Phoronix head honcho Michael Larabel said that “the coffee window is closing” in recent commentary that weighs computer processor advances and human / AI optimizations of the Kbuild code. What once used to be a computer processing task that provided a decent excuse for a coffee break now only allows enough time for a measured sip.

The source site’s determined Linux focus has meant that OS kernel compilation times have become a signature benchmark over the last two decades. Larabel notes that this once time-consuming process “can be done in now roughly 15 seconds.” It isn’t just advances in hardware and core counts pushing the envelope; compiling a defconfig x86-64 Linux kernel build has had many bottlenecks removed thanks to the work of Linux MM developer Lorenzo Stoakes and the assistance of AI/LLMs recently. Even modest processors have seen their compile times cut dramatically thanks to this work.

Larabel went hands-on with the latest v4 kernel patches from Lorenzo, and armed with his very powerful EPYC workstation, achieved “a 15-second kernel build!” Before the latest patches, the same system took over 22 seconds for the same compilation task.

The test system is extremely potent, though. Your home PC or laptop might still let you have enough time to go brew some coffee, as Larabel’s test rig features the following components:

• 2x AMD EPYC 9575F 64-core processors (so, 128 cores / 256 threads)
• 24 x 64GB DDR5-6400 memory modules
• Samsung PM1743 3.84TB PCIe Gen 5.0 NVMe SSD storage
• Stock Ubuntu 26.04 LTS

It is noted that the code compilation benchmarking didn’t employ a RAMdisk to aggressively tune the compile times

All the above timings mentioned are for the minimal default kernel compilation for x86-64 systems. The Phoronix chief also timed the compilation of a Linux kernel with ‘allmodconfig’ with thousands of drivers and subsystems enabled. This precipitates far longer compile times. On the above beefy system, though, the latest Lorenzo patches drove the time down from 169 seconds to 134 seconds. So, this other milestone is approaching the two-minute mark.

Phoronix is now taking bets on AMD (Zen 6) EPYC 9686F systems, with MRDIMMs and PCIe Gen6 storage pushing defconfig x86-64 Linux kernel compilation times under the 10-second mark.

Russian president Vladimir Putin voted online in the State Duma elections on Friday. That’s a pretty ordinary-sounding thing for any president to do, but this filmed-for-the-press event has been widely shared outside of Russia. Why? The official video appears to show Putin voting on a PC using an unlicensed copy of Windows on a Dell PC. The president then comments, “You can’t go wrong,” as he clicks on his choice of candidate. Moreover, folks are throwing scorn at the aging Russian president’s mouse skills. If this were an audition for an eSports team, it would have been a clear fail.

The above embed comes via the nonprofit Central European news aggregator Visegrad24. The magnified section of the video shows a screen effect that looks very similar to the Windows activation reminder watermark. However, the other overlay on the screen is obviously from a different computer, and it’s dated 2018. We found some established Russian media sources with the video recording, like Komsomolskaya Pravda, and there does indeed appear to be a watermark present shown on Putin's computer screen at the end of the voting clip.

Russian state media source TASS explains that the vote was to elect deputies to the 9^th State Duma. It says that over recent years “Putin has preferred to cast his vote remotely.” It also reveals that some former Ukrainian territories will get to participate in this vote. “For the first time ever, residents of the recently incorporated Donetsk and Lugansk People’s Republics, as well as the Kherson and Zaporozhye Regions, will participate in legislative elections for the lower house of the Russian parliament,” says the official Russian news agency.

Returning to the social media bubbling up over the Kremlin clip, some valid points seem to be raised. Putin’s comment about “you can’t go wrong” is almost a reverse Vranyo. There is hardly going to be uncertainty about the result of any vote in Russia. Hot tip: We think that United Russia, the ruling pro-Kremlin party backed by Vladimir Putin, is going to do well this year.

We also note that the president seems to be voting on a foreign (Dell brand) computer. By law, Russian officials must use computers with certain levels of localization, so it might be reasonable to assume this machine was set up entirely for Putin’s voting publicity clip. That would also go some way to explain an unactivated, unregistered copy of Windows being used. It’s likely a fresh, clean copy of Microsoft’s OS run separate from any government network.

As for Putin’s computer skills, it looks like his interactions with the online voting forms are largely being hampered because he can’t see properly, rather than a hand-eye-coordination issue. There are uncomfortably pregnant pauses between the 73-year-old squinting and leaning into the screen and clicking the mouse. Either Putin should wear his glasses, or the Kremlin administrators are going to need to code a Big Picture Mode for his nuclear launch computer.

Anyone old enough to be messing with PCs in the early to mid-2000s probably has the following burned into their mind: FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8. That's neither a magic spell nor a password for a cabal — it's the best-known Windows XP key, letting anyone install and run the operating system with its incantation and just the one CD. Ever wondered how or why Microsoft let such an apparent gaping hole in its copy protection? Former engineer Dave Plummer explained in an X post.

First off, there were actually two versions of the original Windows XP media: Retail and Volume. The former was for anyone who just bought the OS off the shelf, while the latter was reserved for Microsoft partners and OEMs that needed to easily install it on thousands of machines without needing to individually activate every single one at install time.

Retail and Volume media had different keys, too, and the installer would validate the key you input against specific data on the disc, "encrypted so hard that even today it hasn't been decrypted [...]" (Someone will take those words as a challenge). The magical piece of cryptic data was nothing other than the whole 10 MB of... Microsoft Bob. The short-lived assistant was technically the antecessor of the much-maligned and memed-upon Clippy, and did its best in 1995 to introduce newbies to basic computing tasks.

Regular Joes and Janes weren't supposed to be anywhere within a stone's throw of a Volume disc, though, as those were strictly enterprise-only. The final version of the CD, called Release to Manufacturing, or RTM, was complete in August 24, 2001 — two months before the official launch on October 25. The discs were available to OEMs and partners before the release date so those companies could have their wares ready with Windows XP on them.

Plummer notes that "very few" organizations had access to the Volume image and the corresponding Volume License Key (VLK) and believes that someone at a major OEM, potentially Dell or Intel, leaked the Volume media and the key together before the official release. The pirate group Devils0wn then quickly spread it online for everyone to enjoy

Later on, when Service Pack 1 arrived, the FCKGW key was among the 640 blacklisted from the operating system due to leakage. Service Pack 2 and its Windows Genuine Advantage checks went a couple steps further and blocked updates entirely on machines with a blacklisted VLK. Plummer states that Microsoft didn't want to cause unnecessary trouble for customers, hence its laissez-faire attitude and choice to stick to just blacklisting affected keys.

Many theories over the years proposed that the FCKGW key worked because Microsoft's key generation algorithm was very basic, a notion outright dismissed by Plummer. He plainly states that algorithm was written by "ACTUALLY smart guys with heads so big that they bumped the doorjamb on the way into your office."

The truth of the situation was far simpler: as is usual with computing, ultimately the problem was between the keyboard and the chair. It's a good a time as any to reminisce about that compact disc you totally don't have on a bookshelf somewhere with the FCKGW key written on it with a Sharpie.

Microsoft has issued an out-of-band update for its recent Windows 11 patch, which has caused a number of bugs and issues. The September 2026 update was just released last Tuesday, and although it packs a number of new features and fixes nearly 1000 security flaws (commonplace in this day and age), there are also a few unfortunate regressions.

The 25H2 update finally reintroduces a movable taskbar, just like we've had since Windows 95, with an option to make the height smaller for compact displays. Likewise, the Start menu now has multiple configurable layouts, and you can toggle each main section on or off. Microsoft also revamped Windows Search — perhaps to finally be useful — and users can now choose to only have it display local results. Explorer got a handy tweak in the form of using KB, MB, GB size indicators, as well.

The update has also surfaced some serious bugs. First off, PCs with AMD Radeon GPUs are crashing, apparently due to the update provoking driver instability. Reinstalling the driver doesn't appear to help, and the reports unfortunately cover most contemporary AMD graphics cards. Microsoft did not mention AMD GPUs specifically in its latest update.

Microsoft noted that it has fixed an issue with Remote Desktop Services where RDS might become unstable, causing connection and sign-in failures.

Microsoft is also aware of an issue with audio output and microphone input going dead. Additionally, there are seemingly reports of audio devices starting up with a botched configuration, like tweaked 3D audio settings or speaker setups. The apparent workaround seems to be putting audio in a standard 2.0 configuration, but Microsoft has now addressed this issue in the emergency patch.

Explorer may display a black screen after logging in, leaving you with a perfectly functioning operating system but no visible UI. The File History backup feature is reportedly not detecting external drives, effectively making it useless. Of particular concern to enterprises, systems administrators, and homelabs, the Remote Desktop Service is also experiencing issues. Last but not least, Microsoft says it has addressed an issue where Claude Cowork is nonfunctional due to the update breaking HC-managed Linux VMs with Plan9 shared folders

Owners of HP and Lenovo systems are also advised to consider holding off on this update. Ever since the August 2026 patch (and now, cumulatively, with the September update), there are reportedly serious issues on both camps. On the HP side, there are instances of the update triggering BIOS corruption, leading to a failed install with no ability to recover the OS — though seemingly the OEM has published a new BIOS revision, so it's hard to say which side is to blame. Meanwhile, Lenovo users might have their machines black-screen or shut down out of the blue, seemingly due to power mismanagement.

While it's heartening to see that Microsoft has significantly increased its Windows development speed and is seemingly listening to customer feedback, a string of bugs after a major feature update are still common.

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).