Windows Archive
This blog post is intended to notify all Windows Hardware program partners that Microsoft has taken a strategic initiative to clean up legacy drivers published on Windows Update to reduce security and compatibility risks. The rationale behind this initiative is to ensure that we have the optimal set of drivers on Windows Update that cater to a variety of hardware devices across the windows ecosystem, while making sure that Microsoft Windows security posture is not compromised. This initiative involves periodic cleanup of drivers from Windows Update, thereby resulting in some drivers not being offered to any systems in the ecosystem. ↫ Microsoft’s Hardware Dev Center The general gist is that Microsoft is going to remove all drivers from Windows Update for which newer versions exist – or, to put it in a different way, only the latest versions of a driver are going to remain available on Windows Update. It’s effectively a clean-up of Windows Update, and the only way older versions of drivers will remain available on Windows Update is if the manufacturer in question can make a “business justification” to keep them around. Some of this may sound surprising, since many people assume Windows Update only offers the latest versions of drivers – annoyingly so, sometimes – but this isn’t the case. Corporations with fleets of devices can actually determine exactly which drivers get sent to their devices, including opting for older versions in case newer versions have regressions or otherwise cause issues. Sometimes you just don’t have a choice. According to Adam Demasi, the creator and maintainer of the amazing Legacy Update service, Microsoft hasn’t deleted a single driver or update from Windows Update since 2001 (save for problematic updates). This results in a truly massive collection of updates and drivers, and that’s causing real problems for Microsoft. Windows Update has a pretty cool system of describing whether an update is necessary to be installed on the current system, or if it is already installed. It also builds a relationship graph between updates, to indicate when they have been replaced by a newer update that includes all changes from the previous update. That system is also its downfall, causing the Windows Update service to be incredibly slow in checking for updates, possibly never completing the check at all. This issue also applies to WSUS, which despite being based on the very robust SQL Server, struggles with the number of drivers Microsoft hosts on Windows Update. As of April, we know that Windows Update hosts 1,799,339 drivers, and this creates a 138 GB database that requires almost 16 days to synchronise down from the main servers. The WSUS server is brought to its knees, with frequent timeouts while it furiously tries to complete database queries. (The PC used is a Ryzen 5700G with 32 GB of 3600 MHz RAM and 500 GB of NVMe, running Windows Server 2025 and SQL Server 2022.) ↫ Adam Demasi From this, it’s easy to understand why Microsoft would want to perform some housekeeping, followed by a new set of rules around only keeping the latest versions of drivers around in Windows Update. Demasi also notes that these plans by Microsoft won’t affect drivers for old devices, since they will still be served their “newest” driver version, and it won’t affect Legacy Update either.
The blue screen of death has been such a core part of Windows that’s it’s become part of humanity’s collective consciousness. They’re not nearly as common anymore as they used to be back in the Windows 9x and early Windows XP days, but they do still occasionally when dealing with broken hardware, shoddy drivers, or other such faults. Well, the blue screen of death is losing its eponymous blue colour, and will now clearly mention the stop code and where – in which driver – the kernel panic occurred. The Windows 11 24H2 release included improvements to crash dump collection which reduced downtime during an unexpected restart to about two seconds for most users. We’re introducing a simplified user interface (UI) that pairs with the shortened experience. The updated UI improves readability and aligns better with Windows 11 design principles, while preserving the technical information on the screen for when it is needed. ↫ David Weston at the Windows Blogs This is part of a new feature in Windows 11 called quick machine recovery, or QMR. If a Windows PC gets stuck in a boot loop, ending up in the Windows Recovery Environment, Microsoft can now deploy fixes and remediations through WinRE. This feature will become available later this year by default on Windows 11 Home, while on Windows 11 Pro and Enterprise, administrators can control how this feature works. So far, it seems QMR is only intended to be used for widespread outages, but I wonder if it would be possible to eventually use QMR locally. It would be pretty neat if Microsoft released the server-side component of QMR so individuals can run and (ab)use it locally for their own machines.
It’s been nearly a year since a faulty CrowdStrike update took down 8.5 million Windows-based machines around the world, and Microsoft wants to ensure such a problem never happens again. After holding a summit with security vendors last year, Microsoft is poised to release a private preview of Windows changes that will move antivirus (AV) and endpoint detection and response (EDR) apps out of the Windows kernel. ↫ Tom Warren at The Verge After the CrowdStrike incident, one of the first things Microsoft hinted as was moving antivirus and EDR applications out of the kernel, building an entirely new framework for these applications instead. The company has been working together with several large security vendors on these new frameworks and APIs, and it’s now finally ready to show off this new work to the outside world. Instead of designing the new frameworks and APIs in-house and just dumping them on the security vendors, Microsoft requested the security vendors send them detailed documentation on how they want the new frameworks and APIs to work. This first preview of the new implementation will be private, and will allow security vendors to request changes and additional features. Microsoft states it will take a few iterations before it’s ready for general availability, and on top of that, security software is only the first focus of this new effort. It turns out Microsoft wants to move more stuff out of the kernel, with anti-cheat software – more accurately described as rootkits, like Riot’s Vanguard – being an obvious next target. Perhaps this effort could have some beneficial side effects for gaming on Linux, which you should be doing anyway if you want better performance, because Windows games seem to perform better on Linux than they do on Windows.
For a while now I’ve been wondering if Microsoft would blink when it comes to Windows 10’s rapidly approaching end of support date. Only a few weeks ago, Microsoft at the very least twitched by extending support for Microsoft Office on Windows 10, which should’ve been an indication of what was to come. Today, Microsoft actually blinked: regular consumers wishing to keep using Windows 10 after support ends in October will now be able to sign up for an additional year of security updates. Microsoft is making this possible by allowing Windows 10 users to sign up for the Windows 10 Extended Security Update program for one year of extended updates, for free. This program is normally only available to paying enterprise customers, and this marks the first time the company is letting regular consumers make use of it. The “for free” requires some serious caveats, though, as depending on how you look at it, it’s not free at all. You options are to either pay around $30, pay 1000 Microsoft points, or to sign up for the Windows Backup application to synchronise your settings to Microsoft’s computers (the “cloud”). This last option is technically free, but not only does the free tier include just 5GB of online storage, it also makes use of OneDrive, so if you’re using OneDrive to store your documents and other files you may need to pay for additional storage. On top of that, anything that requires the use of OneDrive is simply not “free”, and only allows Microsoft to further get its claws in you. If Sartre was alive today, Huis clos would’ve declared “L’enfer, c’est OneDrive” instead. Regardless, it’s the stay of execution many Windows 10 users have been waiting for, even if it isn’t entirely perfect. Sure, choosing between an unmaintained Windows 10, Windows 11, and using OneDrive is about as pleasant as shoving shards of glass underneath your fingernails, and I have a feeling quite a few people are about to find out.
Quite often, I wonder how much nostalgia plays part in our perception of past events. Luckily, with software, you can go “back” and retest it, and so there’s no need for any illusions and misconceptions. To wit, I decided to reinstall and try Windows 7 again (as a virtual machine, but still), to see whether my impressions of the dross we call “modern” software today are justified. ↫ Igor Ljubuncic The conclusion is that, yes, you can still get quite far today with Windows 7, and I honestly don’t fault anyone for longing for those days. Windows 7 sits dead smack in the middle between the dreadfulness of Windows XP and pre-patches Vista on one extreme, and the ad-infested, “AI”-slop that are Windows 10 and 11. Its Aero look also happens to be experiencing somewhat of a revival, with both Apple and Google borrowing heavily from it for their latest software releases. Transparent blurred glass is making a comeback, but I doubt the current crop of designers at Apple and Google will be able to top just how nice Aero Glass looked in Windows 7. Still, I don’t think you should be using an out-of-support version of Windows for anything more than retrocomputing and as a curiosity, for obvious reasons we’re all aware of. With the end of support for Windows 10 – still used by two-thirds of Window users – approaching quickly, a lot of people are going to have to make the same choice that fans of Windows 7 made years ago: keep using what I like, risks and all, or move on to what I don’t like, but is at least maintained and supported? That is, assuming you can even make that choice in the first place, since in the current economic uncertainty, most definitely cannot. Maybe the Windows world will dodge a bullet, and the circumstances force Microsoft to extend support for Windows 10, like they did with Office applications. Let’s see if they blink, again.
As part of Microsoft’s ongoing commitment to compliance with the Digital Markets Act, we are making the following changes to Windows 10, Windows 11, and Microsoft apps in the European Economic Area (EEA). We’ll update this post as these changes are shipped, first in Windows Insider builds and then in retail builds. ↫ Windows Insider Program Team It’s time for more changes to make Windows suck just a little bit less, but only for those of us who live in the European Economic Area (the EU plus Iceland, Liechtenstein, and Norway), courtesy of basic consumer protection laws like the Digital Markets Act. Windows users in other parts of the world will not get these changes, so if you don’t live in the EU/EEA, feel free to look away to remain blissfully ignorant. In the EU/EEA, Edge will no longer bug you to be set as the default browser, unless you actually open Edge. In addition, other Microsoft applications won’t bug you to install Edge if you’ve removed it from your system. Setting a browser as default will now also register more filetypes. Whereas in other parts of the world setting, say, Firefox as your default browser in Windows will only register it as the default for http, https, .htm, and .html, it will register the following additional defaults: ftp, read, .mht, .mhtml, .shtml, .svg, .xht, .xhtml, and .xml. Users in the EU/EEA can now also remove the Microsoft Store, without affecting updates or the ability for developers to the Microsoft Store Web Installer for their applications. You can now also have multiple online search providers in Windows Search, and countless Microsoft applications and Windows components will no longer default to opening Edge for web content, opting to use your default browser instead. These are all very welcome improvements for European Windows users. It’s almost like consumer protection laws work.
One of the ways in which Windows (and macOS) trails behind the Linux and BSD world is the complete lack of centralised, standardised application management. Windows users still have to scour the web to download sketchy installers straight from the Windows 95 days, amassing a veritable collection updaters in the process, which either continuously run in the background, or annoy you with update pop-ups when you launch an application. It’s an archaic nightmare users of supposedly modern computers should not have to be dealing with. Microsoft has tried to remedy this, but in true Microsoft fashion, it did so halfheartedly, for instance with the Windows Package Manager, better known as winget. Instead of building an actual package manager, Microsoft basically just created a glorified script that downloads the same installers you download manually, and runs them in unattended mode in the background – it’s a download manager masquerading as a proper application management framework. To complicate matters, winget is only available as a command-line tool, meaning 99% of Windows users won’t be using it. There’s no graphical frontend in Windows, and it’s not integrated into Windows Update, so even if you strictly use winget to install your applications – which will be hard, as there’s only about 1400 applications that use it – you still don’t have a centralised place to upgrade your entire operating system and all of its applications. It’s a mess, and Microsoft intends to address it. Again. This time, they’re finally doing what should have been the goal from the start: allowing applications to be updated through Windows Update. Built on the Windows Update stack, the orchestration platform aims to provide developers and product teams building apps and management tools with an API for onboarding their update(s) that supports the needs of their installers. The orchestrator will coordinate across all onboarded products that are updated on Windows 11, in addition to Windows Update, to provide IT admins and users with a consistent management plane and experience, respectively. ↫ Angie Chen on the Windows IT Pro Blog Sounds good, but hold on a minute – “orchestration platform”? So this isn’t the existing winget, but integrated into Windows Update, where it should’ve been all along? No, what we’re looking at here is Microsoft’s competitor to Microsoft’s winget inside Microsoft’s Windows Update, oh and there’s also the Windows Store. In other words, once this rolls out, it’ll be yet another way to manage applications, existing inside Windows Update, and alongside winget (and the Windows Store). They way it works is surprisingly similar to winget: application developers can register an update executable with the orchestrator, and the orchestrator will periodically run this update executable to check for updates. In other words, this looks a hell of a lot like a mere download manager for existing updaters. What it’s definitively not, however, is winget – so if you’re a Windows application developer, you now not only have to register your application to work with winget, but also register it with this new orchestrator to work with Windows Update. This thing is so incredibly Microsoft.
Windows NT 4 doesn’t virtualise well. This guide shows how to do it with Proxmox with a minimal amount of pain. ↫ Chris Jones Nothing to add, other than I love the linked website’s design.
Jwno is a highly customizable tiling window manager for Windows 10/11, built with Janet and ❤️. It brings to your desktop magical parentheses power, which, I assure you, is not suspicious at all, and totally controllable. ↫ Jwno documentation Yes, it’s a Lisp system, so open your bag of spare parentheses and start configuring and customising it, because you’re going to need it if you want to use Jwno to its fullest. In general, Jwno works as a keyboard driven tiling window manager. When a new window shows up, it tries to transform the window so it fits in the layout you defined. You can then use customized key bindings to modify the layout or manipulate your windows, rather than drag things around using the mouse. But, since a powerful generic scripting engine is built-in, you can literally do anything with it. ↫ Jwno documentation It’s incredibly lightweight, comes as a single executable, integrates perfectly with Windows’ native virtual desktop and window management features, has support for REPL, and much more.
Today we’re very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo: Will this be Open Source? · Issue #1 · microsoft/WSL. That means that the code that powers WSL is now available on GitHub at Microsoft/WSL and open sourced to the community! You can download WSL and build it from source, add new fixes and features and participate in WSL’s active development. ↫ Pierre Boulay at the Windows Blogs Windows Subsystem for Linux seems like a relatively popular choice for people who want a modern, Linux-based development environment but are stuck using Windows. I’m happy to see Microsoft releasing it as open source, which is no longer something to be surprised by at this point in time. It leaves one to wonder how long it’s going to be before more parts of Windows will be released as open source, since it could allow Microsoft’s leadership to justify some serious job cuts. I honestly have no idea how close to the real thing Windows Subsystem for Linux is, and if it can actually fully replace a proper Linux installation, with all the functionality and performance that entails. I’m no developer, have no interest in Windows, so I’ve never actually tried it. I’d love to hear some experiences from all of you. Aside from releasing WSL as open source, Microsoft also released a new command-line text editor – simply called Edit. It’s also open source, in its early stages, and is basically the equivalent of Nano. It turns out 32bit versions of Windows up until Windows 10 still shipped with the MS-DOS Editor, but obviously that one needed a replacement. It already has support for multiple documents, mouse support, and a few more basic features.
Last time, we looked at the legacy icons in progman.exe. But what about moricons.dll? Here’s a table of the icons that were present in the original Windows 3.1 moricons.dll file (in file order) and the programs that Windows used the icons for. As with the icons in progman.exe, these icons are mapped from executables according to the information in the APPS.INF file. ↫ Raymond Chen These icons age like a fine wine. They’re clear, well-designed, easy to read, and make extraordinary good use of the limited amount of available pixels. Icons from Mac OS, BeOS, OS/2, and a few others from the same era also look timeless, and I wish modern designers learned a thing or two from these.
I think one of the more controversial parts of Windows 11 – aside from its system requirements, privacy issues, crapware, and “AI” nonsense – is its Start menu. I’ve heard so many complaints about how it’s organised, its performance, the lack of customisation, and so on. Microsoft heard those complaints, and has unveiled the new Start menu that’ll be shipping to Windows 11 soon – and I have to say, there’s a ton of genuine improvements here that I think many of you will be happy with. First and foremost, the “all applications” view, that until now has been hidden behind a button, will be at the top level, and you can choose between a category view, a grid view, and a list view. This alone makes the Windows 11 Start menu so much more usable, and will be more than enough to make a lot of users want to upgrade, I’m sure. Second, customisation is taken a lot more seriously in this new incarnation of the Start menu. You can actually shrink or remove completely sections you’re not using. If you’re not interested in those recommendations, you can just remove that section. Don’t want to use the feature where you pin applications to the Start menu? Remove that section. This, too, seems to address common complaints, and I’m glad Microsoft is fixing this. Then there’s the rest. Microsoft is promising this new Start menu will perform better, which better be true because I’ve seen some serious lag and delays on incredibly powerful hardware. The recommendations have been improved as well, in case you care about those, and there’s a new optional mobile panel that you can slide out, which contains everything related to your phone. Personally, I’m a classic Start menu kind of person – on all my machines (which all run Fedora KDE), I use a classic, very traditional cascading menu that contains nothing but application categories and their respective applications, and nothing more. Still, were I forced to use Windows, these improvements are welcome, and they seem genuine.
As the headline suggests, we’re going to be talking about some very dry Windows stuff that only affects a relatively small number of people, but for those people this is a big deal they need to address. If you’re working on pre-production drivers that need to be signed, this is important to you. The Windows Hardware Program supports partners signing drivers for use in pre-production environments. The CA that is used to sign the binaries for use in pre-production environments on the Windows Hardware Program is set to expire in July 2025, following which a new CA will be used to sign the preproduction content starting June 9, 2025. ↫ Hardware Dev Center Alongside the new CA come a bunch of changes to the rules. First and foremost, expiry of signed drivers will no longer be tied to the expiry of the underlying CA, so any driver signed with the new CA will not expire, regardless of what happens to the CA. In addition, on April 22, May 13, and June 10, 2025, Windows servicing releases (4D/5B/6B) will be shipped to Windows versions (down to Windows Server 2008) to replace the old CAs with the new ones. As such, if you’re working on pre-production drivers, you need to install those Latest Cumulative updates. On a very much related note, Microsoft has announced it’s retiring device metadata and the Windows Metadata and Internet Services (WMIS). This is what allowed OEMs and device makers to include things like device names, custom device icons, and other information in the form of an XML file. While OEMs can no longer create new device metadata this way, existing metadata already installed on Windows clients will remain functional. As a replacement for this functionality, Microsoft points to the driver’s INF files, where such information and icons can also be included. Riveting stuff.
Back in the late ’90s and early 2000s, if you installed a comprehensive office suite on Windows, such as Microsoft’s own Office or something like WordPerfect Office or IBM Lotus SmartSuite, it would often come with a little icon in the system tray or a floating toolbar to ensure the applications were preloaded upon logging into Windows. The idea was that this preloading would ensure that the applications would start faster. It’s 2025, and Microsoft is bring it back. In a message in the Microsoft 365 Message Center Archive, which is a real thing I didn’t make up, the company announced a new Startup Boost task that will preload Office applications on Windows to reduce loading times for the individual Office applications. We are introducing a new Startup Boost task from the Microsoft Office installer to optimize performance and load-time of experiences within Office applications. After the system performs the task, the app remains in a paused state until the app launches and the sequence resumes, or the system removes the app from memory to reclaim resources. The system can perform this task for an app after a device reboot and periodically as system conditions allow. ↫ MC1041470 – New Startup Boost task from Microsoft Office installer for Office applications This new task will automatically be added to the Task Scheduler, but only on PCs with 8GB of RAM or more and at least 5GB of available disk space. The task will run 10 minutes after logging into Windows, will be disabled if the Energy Saves feature is enabled, and will be removed if you haven’t used Office in a while. The initial rollout of this task will take place in May, and will cover Word only for now. The task can be disabled manually through Task Scheduler or in Word’s settings. Since this is Microsoft, every time Office is updated, the task will be re-enabled, which means that users who disable the feature will have to disable it again after each update. This particular behaviour can be disabled using Group Policy. Yes, the sound you’re hearing are all the “AI” text generators whirring into motion as they barf SEO spam onto the web about how to disable this feature to speed up your computer. I’m honestly rather curious who this is for. I have never found the current crop of Office applications to start up particularly slowly, but perhaps corporate PCs are so full of corpo-junkware they become slow again?
Time for another story from Raymond Chen, about why, in Windows 7, logging in took 30 seconds if you had set a solid colour as your background. Windows 7’s logon system needs to wait for a number of tasks to be completed, like creating the taskbar, populating the desktop with icons, and setting the background. If all of those tasks are completed or 30 seconds have passed, the welcome screen goes away. As you can guess by the initial report mentioning having to wait for 30 seconds, one of the tasks that need to be completed isn’t reporting in, so the welcome screen is displayed for the full 30 seconds. In the case of this bug, that task is obviously setting the background. The code to report that the wallpaper is ready was inside the wallpaper bitmap code, which means that if you don’t have a wallpaper bitmap, the report is never made, and the logon system waits in vain for a report that will never arrive. ↫ Raymond Chen It turns out that people who enabled the setting the hide desktop icons were experiencing the same delay, and that, too, was caused by the lack of a report from, in this case, the desktop icons. Interestingly, it seems especially settings changed through group policies can cause issues like this. Group policies are susceptible to this problem because they tend to be bolted on after the main code is written. When you have to add a group policy, you find the code that does the thing, and you put a giant “if policy allows” around it. Oops, the scope of the “if” block extended past the report call, so if the policy is enabled, the icons are never reported as ready, and the logon system stays on the Welcome screen for the full 30 seconds. ↫ Raymond Chen These issues were fixed very quickly after the release of Windows 7, and they disappear from the radar within a few months after the release of everyone’s favourite Windows version.
Remember the odd inetpub folder that seemingly randomly appeared on people’s root drives after installing a Windows 11 update? Everybody assumed it was something left over from an update script, and that the folder was safe to remove. Well, it turns out that’s not the case, as the empty folder is actually a crucial part of a security fix for a serious vulnerability. Initially undocumented in the official release notes, the empty and seemingly inactive inetpub folder led to user speculation about whether it was a leftover artifact from development or a bug. Microsoft has since clarified that the folder is intentional and part of a critical security improvement. The change addresses CVE-2025-21204, a vulnerability that allowed local attackers to exploit symbolic link (symlink) attacks via Windows Update, potentially granting unauthorized access to protected system files or directories. As part of the fix, the system pre-creates certain directories — including C:\inetpub — to harden the update process and mitigate such attacks. ↫ Cyberdom If you’ve already removed the folder, you can reinstall the April 2025 cumulative update to restore the folder, or you can wait for next month’s update roll-up, which will also restore the folder. This lone, empty folder at your Windows PC’s root is apparently a crucial part of the security of your computer, but since it took Microsoft a while to publish release notes, nobody knew where it was coming from. The idea that a random, empty folder usually associated with IIS could be part of a vulnerability mitigation didn’t cross anybody’s mind at the time, especially since random folders appearing at a Windows PC’s root aren’t exactly uncommon or out of the ordinary. The consensus seems to be that creating this folder is a pretty clever form of mitigation, despite feeling so hacky. I’m assuming Microsoft’s engineers are capable, and that making the folder in question impossible to delete or somehow hidden is simply not an option and would break the vulnerability mitigation, but that doesn’t change the fact that this looks like a really crude hack that should be solved in a more elegant way.
Ars Technica took a look at how the current version of Windows Recall works, including the improvements Microsoft made since the initial security nightmare of a rollout, and concludes: Recall continues to demand an extraordinary level of trust that Microsoft hasn’t earned. However secure and private it is—and, again, the version people will actually get is much better than the version that caused the original controversy—it just feels creepy to open up the app and see confidential work materials and pictures of your kid. You’re already trusting Microsoft with those things any time you use your PC, but there’s something viscerally unsettling about actually seeing evidence that your computer is tracking you, even if you’re not doing anything you’re worried about hiding, even if you’ve excluded certain apps or sites, and even if you “know” that part of the reason why Recall requires a Copilot+ PC is because it’s processing everything locally rather than on a server somewhere. ↫ Andrew Cunningham at Ars Technica Way back in 1996, Mercedes-Benz unveiled the A-Class, a small, practical car that purported to be more premium than cheaper, similarly-sized cars from other brands. The car had a big problem, though – it was unusually narrow and tall, and because of it, it famously failed spectacularly at the “moose test”, in which a car has to suddenly swerve around a “moose” on the road. The car simply toppled over, and after initially denying the problem, Mercedes recalled every single A-Class sold and added a variety of mitigations like electronic stability control and suspension changes. As far as I can recall, it fixed the issue. To this day, however, I cannot look at an A-Class, even the modern ones which look like normal hatchbacks and bear effectively zero resemblance to the original, quirky A-Class from 1996, and not think of the failed moose test and the recall. I know the modern A-Class won’t fail that test, and I know it’s an infinitely safer car than the original one, but my brain still makes that connection every time I see one. A lot of people my age, whether they’re into cars or not, seem to remember this recall, because the original A-Class was such a unique and recognisable vehicle at the time, especially coming from Mercedes. My point is – Recall will face this same issue. No matter how secure Microsoft makes it, no matter how much they claim and prove it only runs locally, no matter how hard they try and hammer on the fact data never leaves your PC, people will always think of that initial botched rollout, and all the accurate reporting that Recall was a nightmare. And it just so happens that the skepticism is warranted, and hopefully keeps people from using this corporate Trojan horse.
Remember Windows Recall, the Windows feature that would take a screenshot of your desktop every three seconds, stored them in a database, and then let you search through them at later dates? The feature has been hobbled by implementation problems, security issues, and privacy troubles, and has been released in preview and pulled since its original unveiling. Well, it’s back in testing now for users of the Release Preview Channel. As you use your Copilot+ PC throughout the day working on documents or presentations, taking video calls, and context switching across activities, Recall will take regular snapshots and help you find things faster and easier. When you need to find or get back to something you’ve done previously, open Recall and authenticate with Windows Hello. ↫ Windows Insider blog The “AI” magic (meaning, OCR and image recognition, but with ✨sparkles✨) runs locally, on device, and supposedly, the collected screenshots and data extracted from them never leave your device – at least, for now. The tech industry has a long history of relegating its promises, so excuse me if I don’t have a ton of faith in this data remaining on a Windows PC for too long into the future. Case in point, a related Windows Copilot feature: Copilot Vision. This is very similar to Windows Recall, but instead of taking automating screenshots every few seconds, you can invoke it manually so that Copilot will “read” the current contents of your desktop, applications, and so on, allowing you to ask questions, get help, and so on. The kicker, however, is that while the screenshots and resulting data from Recall supposedly remains on your machine, whatever Copilot Vision does is done on Microsoft’s servers. In other words, a feature very similar to Windows Recall is already sending your personal, private data to Microsoft. I’m sorry, but I just don’t think Windows Recall will remain “on-device” for very long. The temptation to hoover that data up into the giant advertising machine is too great, and there’s no way in hell Microsoft will be able to resist it.
This month’s security updates for Windows 11 create a new empty folder on drive C. It is called “inetpub,” and it does not contain any extra folders or files. Its properties window shows 0 bytes in size and that it was created by the system itself. Neowin checked a bunch of Windows 11 PCs with the April 2025 security updates installed, and all of them had inetpub on drive C. ↫ Taras Buria at Neowin So this folder, inetpub, is most likely coming from Microsoft’s Internet Information Services, the company’s web server. IIS is part of Windows, but inactive by default, and it seems some buggy update script somewhere forgot to remove the folder or created it by accident. Regardless, it seems you can remove it without any issue, so if you see it on your Windows’ root drive, just delete it any be on your merry way. Still though, something about this seems odd, right? Internet Information Services as a core product hasn’t been updated since 2018 when version 10 came out, which doesn’t necessarily mean specific Windows updates might not have changed it since then, but it doesn’t exactly inspire confidence. The Internet Information Services’ website also hasn’t been updated in ages, and is broken in places, further adding to the feeling IIS seems to be mostly abandoned, only kept going as part of Windows updates because it’s, well, part of Windows. I’m not trying to insinuate there’s anything nefarious or dangerous going on with this silly folder glitch or anything; I was just surprised to see such an outdated, seemingly abandoned web server suite still being a default part of Windows today.
Good news for Windows users, and for once there’s not a hint of sarcasm here: Microsoft has started rolling out Windows Hotpatch to the client versions of Windows. This feature, which comes from the server versions of Windows, allows the operating system to install patches to in-memory processes, removing the need for a number of restarts. Obviously, this is hugely beneficial for users, as they won’t have to deal with constant reboots whenever a new bunch of Windows updates are pushed. There are some limitations and other things you should know. First, the way the system works is that every quarter, installations with Hotpatch enabled will receive a quarterly baseline update that requires a reboot, followed by two months of hotpatches which do not require a reboot. Hotpatches can only be security updates; new features and enhancements are rolled up into the quarterly baseline updates. In other words, while this will not completely eliminate reboots, it will cut the number of reboots per year down from twelve to just four, which is substantial, and very welcome in especially corporate environments. The biggest limitation, however, is that Windows Hotpatch will only make it to one client version of Windows, Enterprise version 24H2, so users of the Home or Professional version are out of luck for now. On top of that, you’re going to need a Microsoft subscription, use Microsoft Intune, and an Intel/AMD-based system (Hotpatch will come to ARM later). I hope it’ll make its way to Windows 11 Home and Professional, too, because I’m fairly sure quite a few of you using Windows would love to set this up on your own machines.
