Windows Archive
Another interesting post from Raymond Chen, this time about the difficulty of dealing with a system that’s become CPU-starved. The question is simple: why not just run Task Manager and important parts of the UI like the taskbar at a higher priority? The catch with running anything at high priority is that unless you have been very careful to avoid it, you will eventually run into a shared resource that you will have to wait for, and you are now stuck. Your priority checkout pass gets you to the front of the line, but if the person at the register has a large shopping cart full of groceries, you just have to wait until they are done before you get your chance. Even if the code that protects the shared resource is careful to avoid priority inversion by transferring the priority of the waiter to the thread that owns the resource, you are still stuck waiting, and that owning thread might be doing something that takes a long time, like, say, accessing a file over the network. ↫ Raymond Chen If a system has reached a state where even accessing or using something like a task manager becomes a problem, I personally just bonk my computer over the head with a forced shutdown using the power button. Honestly though, I can’t remember the last time I’ve had to do this, as my Linux machines all seem to handle problematic applications just fine. That being said, I’m sure people managing tons of servers and/or workstations and developers debugging their own running code run into catastrophic problems like this far more often, making forced shutdowns not as practical. Have a terminal window open with top and easy access to the kill command, or make sure you can just ssh into it remotely if the UI has gone completely nuts.
Raymond Chen published another story from the Windows development trenches, this time about what happens when you hold down the power button. If you hold a PC’s power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system’s “Shut down” command isn’t working. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. ↫ Raymond Chen I’m a bit confused by these numbers, because I have never seen a PC take this long to power off when holding down the power button; usually it takes only a few seconds to do so, meaning Windows would never generate said kernel dump. I tried reading through the various ATX specification documents to find more information on this, but then I remembered I’m not an electrical engineer so I have no idea what I’m looking at. The baseline is that ATX always provides standby power to the motherboard, and pressing the power button shorts the power button pin to ground, telling the PSU to power on fully. Pressing the power button if the computer is running tells the operating system to initiate a shutdown (although you can change this behaviour), but if you hold the button down for a certain number of seconds, it forces a power-off. So far, so good; basic information. It seems that the length of time you need to hold down the power button to force a power-off is dependent on the motherboard in question, handled by a microcontroller or some other IC. Virtually every source I can find says this timing is set to about 4-5 seconds, which is quite a bit shorter than the number of seconds given by Chen. Perhaps motherboard manufacturers consider the 12 seconds to be too long, and just do their own thing, regardless what the ATX specification suggests? What further complicates matters is that Chen details how the kernel dumps created after pressing the power button for 8 seconds do, in fact, get sent to Microsoft once the computer turns on again. In fact, he is one of the people who gets to see these dumps and respond to them, so obviously they are indeed rolling in. Does this mean there’s a huge number of computers out there that require you to hold down the power button for 12 seconds to force a shutdown that nobody’s ever seen? These emergency kernel dumps are internally classified as “long power button hold” (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as “black screen LPBH”, and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.) ↫ Raymond Chen What’s going on here? Obviously, I’m not going to doubt Chen, so there must be something here I don’t quite understand or that I’m missing. The ATX specification might suggest 12 seconds, but could Windows perhaps adapt its kernel dump behaviour – dumping much sooner than 8 seconds – based on the motherboard it’s running on, maybe through information provided by the chipset drivers? I would love it if someone more knowledgeable than me can help us unravel this small mystery.
I think it’s safe to say that Windows’ Modern Standby feature isn’t exactly free from issues. The biggest problem seems to be that it’s not very good at actually determining when to transition between regular sleep and hibernation, often leaving users with an empty battery as they open their laptop’s lid. Microsoft has now released an update to hopefully address this long-standing problem. This update improves the adaptive hibernate policy to provide more instant-on resumes from Modern Standby while helping preserve battery life when the charge is low. Noticeable changes include less hibernation while the battery is above 80% and hibernating sooner when the battery is below 10%. ↫ KB5127936 Among other new features and changes this update brings are Cloud Rebuild, a way for devices to install Windows without needing a local image. Cloud Rebuild can be started form within an existing installation, remotely by administrators, or through the Windows Recovery Environment. Obviously, a working internet connection, wired or wireless, is required for this feature to work. This is the same update that introduces CLAT, which we talked about yesterday, to smooth the transition from IPv4 to IPv6.
Windows 11 25H2, starting with build 26200.9550, now comes with something called CLAT. As organizations move toward IPv6-only and IPv6-mostly networks, some applications still depend on IPv4-only applications or services. Windows CLAT helps those applications continue to work when a network does not provide native IPv4 connectivity. CLAT is the client-side component of 464XLAT. It statelessly translates IPv4 traffic from the Windows client into IPv6 for transport across the network to a provider-side translator (PLAT), which provides stateful NAT64 translation to IPv4. ↫ Jim Alumbaugh at Microsoft’s Networking Blog Yet another important component of the long, neverending transition to IPv6. Like endlessly cutting a cucumber in half, you’ll never quite run out of cucumber to cut.
What’s the oldest Windows GUI application you can still run on Windows 11 today, without any modifications? For now, the best answer Boris Popik can come up with is an innocuous application from build 347 of Windows NT 3.1, an early prerelease: CDPLAYER.EXE. You can’t go any older than that, because earlier prerelease builds had not yet finalised its PE format and calling convention. Neat find. Popik also mentions a few other contenders, but I won’t spoil those here.
Thew day ends in a Y, so Microsoft is launching a new way to build Windows applications. Get excited, Windows application developers! If you caught our session at Microsoft Build 2026 or you’ve been watching the repo, you’ve seen this one taking shape in public for a while now, and a lot has changed since Build. Here’s the longer tour: Microsoft.UI.Reactor, an experimental C# framework that brings the MVU (Model-View-Update) pattern to WinUI desktop apps. No XAML files, no code-behind, no ViewModels. Two things before the fun part. Reactor is experimental: no support policy, no API guarantees, published this early on purpose because we’d rather hear we got the design wrong now than once people have shipped on it. And it is not a replacement for XAML or MVVM, which we’ll come back to. ↫ Alexandre Zollinger Chohfi at Microsoft’s Dev Blogs At multiple points in the linked blog post, Microsoft underlines that no, Reactor is not going to replace XAML. I’m sure Windows developers who learned Win32, Silverlight, WinRT XAML, WPF, UWP, WinUI 2 and 3, and all the others, over the past two decades will feel deeply comforted by Microsoft’s insistence that Reactor will not replace XAML. Microsoft repeats: this won’t replace XAML. They swear.
Microsoft’s been claiming for a while now that they’re working on improving performance and responsiveness in Windows, with a particular focus on making more efficient use of memory. This is probably the only positive thing to come out of the RAM crisis Microsoft helped create and is currently still fueling. The company’s now claiming that Windows 11 is “up to 20% more responsive” thanks to these efforts. The result is a Windows experience that’s up to 20% more responsive, with improvements you can feel as soon as you boot into your PC and extending to Start, File Explorer, Search, Snipping Tool, Microsoft 365, Edge and more. A big part of that work is making smarter use of memory and system resources. We’ve improved memory management and efficiency across Windows to help keep more of your PC’s resources focused on what you’re actively doing. That work can make an especially meaningful difference on PCs with 8GB of memory. Windows can now keep up to 2GB more of your active data in memory instead of moving it to slower storage, helping your PC stay responsive as you open more apps or browser tabs. Windows is also making additional memory-saving improvements that reduce background memory use. For example, on PCs with 8GB of memory or less, Widgets load only when you open them, making more than 200 MB of memory available for your apps and other work. It’s one example of the broader work underway to reduce the Windows memory footprint and deliver a fast, responsive experience across the PCs people use every day, an area we’ve made an explicit focus for Windows. ↫ Navjot Virk on the Windows Blogs If, for a moment, we take these claims at face value, they’re simply good news for every Windows 11 user, and legitimately the only good thing to come out of the RAM crisis. These kind of claims are always hard to measure, especially considering just how varied the Windows software and hardware ecosystem is, but I’m sure people good at benchmarking are going to try and find some more definitive answers here. In the same blog post, Microsoft also highlights several other recent improvements it’s made to Windows 11, like the new search experience we talked about recently, a brand new Photos application, some new whiteboard-like application, and several more things. Considering how complex Windows’ versioning scheme and various branches have become, I have no idea when these features and improvements actually make their way to your machine. On a slightly related note, Microsoft also unveiled that it’s bringing Microsoft Defender to Linux, with a particular focus on desktop Linux. Even Microsoft has to face the reality of the rising popularity of Linux on the desktop.
Are you aware of ReFS, Microsoft’s next-generation file system for Windows? I’m sure the average OSNews reader is, but I really wonder how many people are using it out in the wider world, even though Microsoft keeps improving it. Since earlier this year, Windows Server and Windows 11 can boot from ReFS volumes, and it’s used by Windows’ Dev Drive feature as well. What Microsoft doesn’t seem to want, though, is people using ReFS on removable drives. Starting with Windows updates released on and after October 13, 2026, Microsoft is making hardening changes to the Resilient File System (ReFS). This article describes Windows hardening changes for ReFS volumes that are mounted from removable media. ReFS on removable media, such as a USB disk, is not a supported configuration. The changes add auditing and enforcement controls that help administrators identify these volumes and prevent them from being mounted. ↫ Microsoft Knowledge Base article I’m oddly fascinated by this. Apparently, there are enough people out there trying to use ReFS on removable media to warrant the above auditing and enforcement controls, which is fascinating in an of itself. On top of that, using ReFS on removable media is apparently also dangerous enough – which raises the question of why, exactly, it’s so dangerous in the first place. Microsoft doesn’t really explain itself here, other than saying it’s “not a supported configuration”. I wonder if and when Microsoft will move from NTFS to ReFS as the default file system for new Windows installations. It’s been around for quite a while now, and there’s no denying that competing operating systems, especially in the server space, have file systems that are far superior to NTFS (like Btrfs, ZFS, and others), and I’m assuming Microsoft would love to catch up. It’s been a long time since Microsoft changed Windows’ default file system, however, and with the massive number of people using Windows, it’s not something to take lightly. Then again, Apple migrated hundreds of millions of iPhones, iPads, and Macs to a brand new file system without anybody noticing a thing, and as far as I can recall, without any problems.
In this article. I am going to explain the different steps the I/O manager follows when initializing an I/O operation starting from determining the right target, choosing the right path and finally sending the request to be processed by the right drivers. To make it easier I choose to focus on read requests only since the major steps are common by all types of requests. ↫ Win-Ware A very in-depth look at Windows’ I/O Manager.
Whenever Microsoft starts messing with something like the search function in Windows, a lot of people are going to be holding their breath and expecting the worst. Well, get ready, because they’re redesigning the whole thing. In July, we shared how we are improving the Windows Search Box with less clutter and more control. We introduced a calmer home screen, removed promotional content from web results, and gave you more choice over whether web and Microsoft Store suggestions appear. Today, we’re carrying those investments forward with a new Windows Search experience built on WinUI 3. This modern foundation makes Windows Search faster and more efficient with resources, while delivering an even more streamlined and focused design. ↫ Anshul Rawat at the Windows Blogs The company claims this new version of search is faster and uses less memory, which, if true, are very welcome improvements. It’s also just a single column of results now, and they’re adding inline previews for things like weather and files on your machine, as well as for answers to all kinds of queries you might normally go to an online search engine for. You can now also use search to perform all kinds of tasks in Windows, like turning on dark mode, managing windows, and so on. All of this can be done using relatively natural language, and Microsoft claims they’ve implemented better detection of typing errors and synonyms, which is quite welcome. Weirdly enough, though, it’s not yet integrated into the Start menu, since it’s a preview just for testers, but that’s something they’re working on for future releases. Judging by the videos and screenshots, I’m actually kind of positively surprised. This looks quite decent and nice, and if the promised performance improvements actually materialise, this may actually be an upgrade to search worth looking forward to. Of course, this is still Microsoft, so it’s just as likely they’ll screw up somewhere between now and when this goes live to regular users. Still, I think it looks decent.
Speaking of Windows and performance, how about that RAM crisis? Microsoft is feeling the squeeze too, and is apparently doing work up and down the Windows stack to improve its memory consumption. Microsoft’s Windows chief Pavan Davuluri has admitted that the rising cost of memory is pushing the company to make Windows 11 use less RAM. Microsoft is working on the Windows memory manager, memory compression, WinUI 3 and WebView2, and has made “memory optimization for 8GB and above” an official priority for the rest of 2026. ↫ Abhijith M B at Windows Latest This might be the only positive consequence of the RAM crisis.
To this day, Windows retains full support for the old MS-DOS 8.3 filename limitation, and it does this by creating 8.3 aliases for files with longer names. Apparently, this has a measurable effect on performance, so naturally, people are going to turn it off to make their Windows installations perform better. According to the user, this resulted in noticeably smoother scrolling in Tile view. They subsequently repeated the process on several folders they regularly use and reported that searching through files became much faster. The user also claimed that external hard drives became faster and that browsing an Android directory over USB or FTP behaved more like a regular Windows folder, including when copying large numbers of music files. ↫ Sayan Sen at Neowin You can disable this legacy feature in Windows per volume or globally, but Microsoft is warning users not to do so. Even in 2026, applications and registry entries may depend on 8.3 filenames being available, so removing them can lead to unexpected outcomes. It’s just one of those things you wouldn’t expect to still be around or have a measurable impact in the days of fast SSDs, but there’s enough credibly evidence out there to suggest that yes, it actually does negatively affect performance. If you’re doing a lot of file operations in Windows, it might be worthwhile to do some testing of your own to see if you can speed things up. Or, you know, you can just not use a house of cards disguised as a serious operating system.
Microsoft has announced WSL containers for developers who aren’t already using Docker, Podman, or Rancher on their Windows workstations. WSL containers is now generally available! Check out this blog post to learn more about this overall feature enabling seamless access to Linux containers on Windows via the new “wslc.exe” command. This new Linux container platform comes with multiple architectures changes compared to WSL, which we’ll detail in this post. ↫ Pierre Boulay at the Microsoft Dev Blogs If you already have WSL installed, you can run wsl -update to get this new container feature, or you can download it straight from GitHub.
Windows 11 received its September update on the 8th of this month, and within days Microsoft had acknowledged or investigated problems involving Remote Desktop, USB audio, Linux and WSL-based apps like Claude Cowork, and enterprise domain issues. Windows Latest also found File History failures, Explorer.exe crashes, and AMD GPU instability, with an emergency update following on September 14 that still did not fix everything. This got us curious, and we looked back across the nine monthly updates released from January through September 2026 and, rather unsurprisingly, Windows 10 update history isn’t infected with nearly as many bugs as that of Windows 11. ↫ Abhijith M B at Windows Latest Of course, Windows 10 also isn’t getting nearly as much attention from Microsoft, but that’s kind of the whole point, isn’t it? Whenever Microsoft touches something, especially over the last 5 years or so, it’s one cascade of failures after the other, eroding trust in Windows’ updates even more (if that’s even possible). In that light, why would you want to use Windows 11 and all the headaches that come with it, when Windows 10 is right there, still being supported, albeit without the latest bells and whistles that only seem to break Windows 11 anyway? If you really do need or want to use Windows, consider switching back to Windows 10 whenever the usual Windows reinstallation time draws near. You won’t lose much, but will gain quite a bit in the process. Of course, this won’t be a responsible or usable choice forever, but at this point in time, I definitely think it’s the optimal choice for quite a few people.
Raymond Chen, longtime Microsoft employee and author of the very popular The Old New Thing blog, published an interesting post about the Win32 scrollbar. It turns out there’s actually quite a few interesting shortcuts and useful hidden features, like clicking inside a scrollbar while holding down shift will make the content jump to that point. Halfway through the article, though, Chen laments how nobody really uses proper Win32 scrollbars anymore. Sadly, almost nobody uses Win32 scroll bars any more. Everybody uses frameworks that provide their own custom scroll bars. ↫ Raymond Chen And as you might expect, none of these scrollbars work like the Win32 one, making even something as basic as the scrollbar a fragmented mess. He doesn’t just blame things like Electron, either, as Microsoft’s own WinUI framework, which is used for most “new” Windows UI developed by Microsoft for Windows 11, also uses custom scrollbars that do not work like the Win32 one does. Great, so by the time I learn about a shortcut for scroll bars (Shift+click), the ecosystem has fragmented so much that I can’t even rely on it working. ↫ Raymond Chen Modern computing is depressing.
When I used Windows for a month because you people paid me to do so, the utter lack of consistency in the way applications and the operating system itself looks, feels, and behaves was a major sticking point. It turns out, though, that I was only scratching the surface of just how bad things really are on Windows. Case in point: the new WinUI Notepad application that replaced the classic Win32 one. I had no idea just how bad it really is. It’s been seven weeks since I last complained about something in Windows on this blog. That feels like too long, so here’s a post about menus – specifically, the menu bar in the modern version of Notepad in Windows 11. That menu bar has, unfortunately, quite a few regressions compared to the menu bar in the old Win32 version of Notepad. ↫ Reupen Shah I’m not going to spoil any of it, because there’s no way you’d believe any of it without the videos Shah provides. I’m aghast.
Zenith is a variant of Windows for “developer-class devices”. Project Zenith comes with a set of pre-installed tools spanning languages and runtimes, source control, and productivity tools. Windows Terminal and Visual Studio Code are pinned to the Taskbar by default, putting your favorite tools within immediate reach. We’ve also pre-configured Windows Settings for coding across File Explorer, Search, Start, and the Taskbar. File Explorer shows file extensions, hidden files, the full path in the title bar, and the details pane, with long-path support enabled. Recently used files and folders and sync provider tips are turned off for a cleaner workspace. In Search and Start, Command Palette is enabled, while Start menu tips and account notifications are turned off to reduce distractions. Windows Subsystem for Linux (WSL) has become foundational for running Linux workloads on Windows. Last year we open-sourced WSL. Building on that momentum at Build 2026, we integrated WSL more deeply into Windows with WSL containers to provide a built-in way to create, run, and interact with Linux containers directly on Windows. ↫ Logan Iyer at the Windows Blogs It’s highly unlikely you’ll be using this Zenith Windows flavour any time soon, as it requires 64GB of unified RAM with 250 GB/s memory bandwidth. In 2026, that’s a serious ask. On top of that, it’s not entirely clear to me if Zenith will be available as a separate Windows variant, without having to buy a complete device. Of course, it would be trivial to set all of this up on any fresh Windows installation.
When I wrote about using Windows 11 for a month as part of the ongoing OSNews fundraiser (keep donating to get me to do the same for macOS!), one of the things I mentioned was that “the modern desktop context menu has its own classic Win32 context menu”. This is, in fact, a long-standing complaint I’ve repeatedly used as the perfect example of just how chaotic and low-quality Windows has become. Thankfully, and naturally I fully attribute this to my repeated complaints (*), Microsoft has been working on a brand new, faster, configurable context menu, and Neowin actually reviewed it. If you ask me, this revamped context menu addresses just about the biggest problem users had with the one in Windows 11, and that is the need to click through more buttons than necessary to do simple things like renaming a file or opening its properties. That problem is now basically gone. I have no issues with the new design. It looks modern, it feels more consistent with the rest of Windows, and even though all the new sections can still make it look a little busy, you now have the option to make it as simple or as button-packed as you want. That should cover most use cases and preferences well. I’d even say that when the new context menu becomes available to everyone, my guide on how to bring back the classic context menu might become obsolete. ↫ Ivan Jenic at Neowin The biggest reason I’m linking to this is not because I care about whatever monster of a context menu Windows users are having to deal with. No, I’m only linking to this because I never in my life imagined I’d be linking to a review of a context menu. I mean, at least it’s not the chess application icon. That would be embarrassing. I get a perverse sense of joy out of this.
Raymond Chen explains what, exactly, the file winstart.bat in Windows 95 is used for. In Windows 95, you could create a winstart.bat file in your Windows directory. During startup, the virtual machine manager initializes and creates the so-called “System virtual machine” (the “System VM”), which is the virtual machine that all Windows programs run in. But before running the user-mode kernel in that virtual machine, the virtual machine manager runs the winstart.bat batch file if it exists. ↫ Raymond Chen Chen needs to use several diagrams to really explain what the batch file is used for, but as a very crude summary, it allows you to load TSRs that only apply to Windows programs, while not affecting any additional DOS command prompts you may load later after Windows is already running. While many think it’s a Windows 95 feature, it was already present in Windows 3.x. A unique feature that I doubt many people made active use of.
This was bound to happen. According to a new report from Taiwanese publication United Daily News (UDC,) Microsoft is raising the cost of Windows license fees for hardware makers by a much higher amount than normal. According to the report, certain OEMs are seeing licensing price hikes of between 7% and 10%. ↫ Zac Bowden at Windows Central Like every other tech company diving head-first into “AI”, Microsoft is losing money on its gamble head-over-fist, with no profitability in sight. Since admitting betting the company on “AI” was a mistake is out of the question, Microsoft has to extract the money from somewhere else to make up for it. The cost of Windows licenses for OEMs is an obvious lever to pull, as OEMs really have nowhere else to turn to (yes, desktop Linux is making gains, but not in any meaningful numbers), so they’ll take hit and pass the cost on to consumers. The end result will be that prices for laptops will increase even more than they already have thanks to the “AI”-induced RAM and component crisis, creating a double-whammy of price increases caused by “AI”, either directly or indirectly. It’s just another category of products we can add to the cost of living crisis that’s causing untold harm and damage to hardworking people all over the world. The price of incompetence is rarely paid for by the incompetent.
Submitted by 