Windows Archive
Developing for Windows seems to be a bit of a nightmare, at least according to Microsoft, so they’re trying to make the lives of developers easier with a new tool called winapp. The winapp CLI is specifically tailored for cross-platform frameworks and developers working outside of Visual Studio or MSBuild. Whether you are a web developer building with Electron, a C++ veteran using CMake, or a .NET, Rust or Dart developer building apps for Windows, the CLI can streamline the complexities of Windows development – from setting up your environment to packaging for distribution. This makes it significantly easier to access modern APIs – including Windows AI APIs, security features and shell integrations – directly from any toolchain. Windows development often involves managing multiple SDKs, creating and editing multiple manifests, generating certificates and navigating intricate packaging requirements. The goal of this project is to unify these tasks into a single CLI, letting you focus on building great apps rather than fighting with configuration. While the CLI is still in its early days, and there are many Windows development scenarios still in the works, we’re sharing this public preview now to learn from real usage, gather feedback and feature requests, and focus our investments on the areas that matter most to developers. ↫ Nikola Metulev at the Windows Blogs For instance, run the command winapp init at the root of your project, and winapp will download the proper SDKs, create manifest files, etc., all automatically. You can also generate the correct certificates, easily create MSIX packages, and more. The tool is available through winget and npm (for Electron projects), but is still in preview, with the code available on GitHub.
I totally forgot you could do this, but back in the Windows 9x days, you could hold down shift while clicking restart, and it would perform a sort-of “soft” restart without going through a complete reboot cycle. What’s going on here? The behavior you’re seeing is the result of passing the EW_RESTARTWINDOWS flag to the old 16-bit ExitWindows function. What happens is that the 16-bit Windows kernel shuts down, and then the 32-bit virtual memory manager shuts down, and the CPU is put back into real mode, and control returns to win.com with a special signal that means “Can you start protected mode Windows again for me?” The code in win.com prints the “Please wait while Windows restarts…” message, and then tries to get the system back into the same state that it was in back when win.com had been freshly-launched. ↫ Raymond Chen There’s a whole lot more involved behind the curtains, of course, and if conditions aren’t right, the system will still perform a full reboot cycle. Chen further notes that because WIN.COM was written in assembly, getting back to that “freshly-launched” state wasn’t always easy to achieve. I only vaguely remember you could hold down shift and get a faster “reboot”, but I don’t remember ever really using it. I’ve been digging around in my memories since I saw this story yesterday, and I just can’t think of a scenario where I would’ve realised in time that I could do this.
It’s no secret that the Windows 95 installer uses a heavily stripped-down Windows 3.10 runtime, but what can you actually do with it? How far can you take this runtime? Can it run Photoshop? It is a long-standing tradition for Microsoft to use a runtime copy of Windows as a part of Windows Setup. But the copy is so stripped-down, it cannot run anything but the setup program (winsetup.bin). OR IS IT? A mini-challenge for myself: create a semi-working desktop only based on runtime Windows 3.10 shipped with Windows 95 installer but not using any other Microsoft products. ↫ Nina Kalinina A crucial limitation here is that Kalinina is not allowing herself to use any additional Microsoft products, so the easy route of just copying missing DLLs and other files from a Windows 95 disk or whatever is not available to her; she has to source any needed files from other sources. This may seem impossible, but during those days, tons of Windows (and even DOS) applications would ship with various Microsoft DLLs included, so there are definitely places to get Windows DLLs that aren’t coming directly from Microsoft. As an example, since there’s no shell of any kind included in the stripped-down Windows 3.10 runtime, Kalinina tried Calmira and WinBar, which won’t work without a few DLLs. Where to get them if you can’t get them straight from Microsoft? Well, it turns out programs compiled with later version of MSVC would include several of these needed DLLs, and AutoCad R12 was one of them. WinBar would now start and work, and while Calmira would install, it didn’t work because it needs the Windows Multimedia Subsystem, which don’t seem to be included in anything non-Microsoft. It turns out you can take this approach remarkably far. Things like Calculator and Notepad will work, but Pain or Paintbrush will not. Larger, more complex applications work too – Photoshop 2.5.1 works, as does Netscape, but without any networking stack, it’s a little bit moot. Even Calmira XP eventually runs, as some needed DLLs are found inside “Mom For Windows 2.0”, at which point the installation starts to look and feel a lot like a regular Windows 3.x installation, minus things like settings panels and a bunch of default applications. Is this useful? Probably not, but who cares – it’s an awesome trick, and that alone makes it a worthwhile effort.
We all knew this was going to happen, so let’s just get it over with. Microsoft is testing a new feature that integrates Copilot into the File Explorer, but it’s not going to be another ‘Ask Copilot’ button in the right-click menu. This time, Copilot will live inside File Explorer, likely in a sidebar or Details/Preview-pane-like interface, according to new references in Windows 11 preview builds. ↫ Mayank Parmar at Windows Latest What am I even supposed to say at this point? Who wants this? Why utterly destroy what little reputation and goodwill Windows has left? Has the hype bubble become this clouded and intoxicating? Even system administrators who want to turn off Copilot in their organisations or device fleets in an official, supported way are getting punched in the face by Microsoft. The company rolled out a new Group Policy to disable Copilot, but it’s such a useless mess it might as well not be there at all. This essentially means that IT admins will only be able to uninstall the Copilot app for customers where their device has both Copilot apps installed by either a clean install or by the IT team itself, as long as the Copilot app has not been opened in a month. So, even if you accidentally open the Copilot app for a second because it’s there in your Windows taskbar, the Copilot app won’t be uninstalled. ↫ Usama Jawad at Neowin You shouldn’t be using Windows.
Ever noticed your computer acting sluggish or warning you about low storage? Temporary files could be the sneaky culprit. Windows creates these files while installing apps, loading web pages, or running updates. Left unchecked, they pile up and hog valuable space. Luckily, clearing them out is easier than cleaning your kitchen junk drawer. Let’s explore Storage Sense, Disk Cleanup, manual deletion, and a few bonus performance tips to keep your PC running like new. ↫ Microsoft Windows Learning Center You may think this is one of those junk SEO articles generated by “AI” to trap Google searches, but no, this is published by Microsoft on Microsoft’s website. Instead of fixing the long-standing and well-known problems around Windows being absolutely terrible at keeping itself clean and functional over longer periods of time, the company figured it’d be a better idea to just keep shoving that responsibility unto users instead. None of the tools mentioned in this article should need to be run or set up by users manually. A computer is supposed to make life less tedious, not more so, and I already have enough cleaning up and laundry to do out here in the real world, and I don’t want to be bothered with it on my computer. Why on earth am I supposed to manually remove unnecessary Windows Update files? Why did Adobe installers leave about 15GB of old installers in some directory inside C:/Windows on my wife’s computer that I had to remove using a third party tool? In what universe is this okay? Sometimes I wonder how much of our collective time is wasted just by dealing with Windows on a day-to-day basis in our society. Imagine the time we could reclaim and spend on our loved ones, families, and hobbies instead, if only Windows was developed by people with even a modicum of competency.
Up until now, it’s always remained possible to activate Windows offline, by calling a phone number, going through a lengthy phase of entering digits on your phone dialpad, and carefully listening to and entering a string of numbers on the device you’re trying to activate. For a while, even, this was, as far as I can tell, one of the easiest ways to fix activation issues caused by replacing one component too many, causing Windows activation to think you had a new machine. Phone activation was always remarkably more lenient and forgiving than online activation. Well, as part of Microsoft’s crusade to make Windows progressively more shit, it seems phone activation is going away. However, that seems to no longer work on Windows 11 or 10 or Windows 7 either, as another user Ben Kleinberg has documented on his YouTube channel. Now when trying to activate the OS by attempting to call the phone number for Microsoft Product Activation, an automated voice response says the following: “Support for product activation has moved online. For the fastest and most convenient way to activate your product, please visit our online product activation portal at aka.ms/aoh” ↫ Sayan Sen at Neowin They’re going after your local, non-online account, they’re going after offline activation – what’s next in line on the chopping block? Are they going to actively start blocking the various debloat tools that make Windows 11 at least slightly less of a block of concrete chained around your neck? Please switch to a real operating system.
Nina Kalinina has been on an absolute roll lately, diving deep into VisiOn, uncovering Bellcore MGR, installing Linux on a PC-98 machine, and much more. This time, she’s ported Windows 2 to run on a machine it was never supposed to run on. I bought my first Apricot PC about three years ago, when I realised I wanted an 8086-based computer. At the time, I knew nothing about it and simply bought it because it looked rad and the price was low. I had no idea that it was not IBM PC-compatible, and that there were very few programs available for it. I have been on a quest to get a modern-ish word processor and spreadsheet program for it ever since. Which eventually made me “port” Windows 2 on it. In this post, I will tell you the story of this port. ↫ Nina Kalinina To get Windows 2 working on the Apricot, Kalinina had to create basic video, keyboard, and mouse drivers, allowing Windows 2 to boot into text mode. I wasn’t aware of this, but Windows 2 in text mode is funky: it’s rendering all the text you would see in a full Windows 2 user interface, just without any of the user interface elements. Further developing the video driver from scratch turned out to be too big of an undertaking for now, so she opted to extract the video driver from Windows 1 instead – which required a whole other unique approach. The keyboard and mouse drivers were extracted from Windows 1 in the same way. The end result is a fully working copy of Windows 2, including things like Word and Excel, which was the original goal in the first place. There aren’t many people around doing stuff like this, and it’s great to see such very peculiar, unique itches being scratched. Even if this is only relevant for exactly one person, it’s still been worth it.
I’m sure most of us here are aware of the bright red-and-yellow colour scheme called “Hot Dog Stand”, included in Windows 3.1. While it’s not the only truly garish colour scheme included in Windows 3.1, its name probably did a lot to make it stand out from the others. There’s been a ton of speculation about the origins of the colour scheme, and why it was included in Windows 3.1, but it seems nobody ever bothered to look for someone who actually worked on the Windows 3.1 user interface – until now. PC Gamer’s Wes Fenlon contacted Virginia Howlett, Microsoft’s first user interface designer who joined the company in 1985, and asked her about the infamous colour scheme. It turns out that the origin story for the infamous colour scheme is rather mundane. In Howlett’s own words: I do remember some discussion about whether we should include it, and some snarky laughter. But it was not intended as a joke. It was not inspired by any hot dog stands, and it was not included as an example of a bad interface—although it was one. It was just a garish choice, in case somebody out there liked ugly bright red and yellow. ↫ Virginia Howlett, quoted by Wes Fenlon in PC Gamer Howlett then lists a few other included colour schemes that were just as garish, or even more so, as examples to underline her point. Personally, I’m a huge proponent of allowing users to make their interfaces as ugly and garish as they want, as the only arbiter on what’s on your screen is you, and nobody else. Hot Dog Stand and similar garish themes need to make a comeback, because there’s bound to be some people out there whose vibes align with it.
With the current, rapidly deteriorating state of the Windows operating system, you have to take the small wins you can get: Microsoft is now offering the option of removing “AI” actions from Windows 11’s context menus. buried deep in the Windows 11 Insider Preview Build 26220.7344 release notes, there’s this nugget: If there are no available or enabled AI Actions, this section will no longer show in the context menu. ↫ Windows Insider Preview release notes If you then go to Settings > Apps > Actions and uncheck all the “AI” actions, the entire submenu in Windows 11’s context menus will vanish. While this is great news for those Windows users who don’t want to be bothered by all the “AI” nonsense, I wish Microsoft would just give users a proper way to edit the context menu that doesn’t involve third party hackery. KDE’s Dolphin file manager gives me full control over what does and does not appear in its context menu, and I can’t imagine living without this functionality – there’s so many file-related operations I never use, and having them clutter up the context menu is annoying and just slows me down. There’s more substantial and important changes in this Insider Preview Build too, most notably the rollout of the Update Orchestration Platform, which should make downloading and installing application updates less cumbersome, but since it’s a new feature, application won’t support it right away. This release also brings the new Windows MIDI Services, and Microsoft hopes this will improve the experience for musicians using MIDI 1.0 or MIDI 2.0 on Windows. There’s a slew of smaller changes, too, of course. I’m not exactly sure when these new features will make their way to production installations – who does, honestly, with Microsoft’s convoluted release processes – but I hope it’s sooner rather than later.
On its own, the title of this post is just a true piece of trivia, verifiable with the built-in subst tool (among other methods). Here’s an example creating the drive +:\ as an alias for a directory at C:\foo: The +:\ drive then works as normal (at least in cmd.exe, this will be discussed more later): However, understanding why it’s true elucidates a lot about how Windows works under the hood, and turns up a few curious behaviors. ↫ Ryan Liptak Fascinating doesn’t even begin to describe this article, but at the same time, it also makes me wonder at what point maintaining this drive letter charade becomes too burdensome, clunky, and complex. Internally, Windows NT does not use drive letters at all, but for the sake of backwards compatibility and to give the user what they expect, a whole set of abstractions has been crafted to create the illusion that modern versions of Windows still use the same basic drive letter conventions as DOS did 40 years ago. I wonder if we’ll ever reach a point where Windows no longer uses drive letters, or if it’s possible today to somehow remove or disable these abstractions entirely, and run Windows NT without drive letters, as Cutler surely intended. Vast swaths of Windows programs would surely curl up in fetal position and die, including many core components of the operating system itself – as this article demonstrates, very few parts of Windows can handle even something as mundane as a drive letter outside of A-Z – but it’d make for a great experiment. Someone with just the right set of Windows NT skills must’ve tried something like this at some point, either publicly or inside of Microsoft.
During a Dell earnings call, the company mentioned some staggering numbers regarding the amount of PCs that will not or cannot be upgraded to Windows 11. “We have about 500 million of them capable of running Windows 11 that haven’t been upgraded,” said Dell COO Jeffrey Clarke on a Q3 earnings call earlier this week, referring to the overall PC market, not just Dell’s slice of machines. “And we have another 500 million that are four years old that can’t run Windows 11.” He sees this as an opportunity to guide customers towards the latest Windows 11 machines and AI PCs, but warns that the PC market is going to be relatively flat next year. ↫ Tom Warren at The Verge The monumental scale of the Windows 10 install base that simply won’t or cannot upgrade to Windows 11 is massive, and it’s absolutely bonkers to me that we’re mostly just letting them get away with leaving at least a billion users out in the cold when it comes to security updates and bug fixes. The US government (in better times) and the EU should’ve 100% forced Microsoft’s hand, as leaving this many people on outdated, unsupported operating system installations is several disasters waiting to happen. Aside from the dangerous position Microsoft is forcing its Windows 10 users into, there’s also the massive environmental and public health impact of huge swaths of machines, especially in enterprise environments, becoming obsolete overnight. Many of these will end up in landfills, often shipped to third-world countries so we in the west don’t have to deal with our e-waste and its dangerous consequences directly. I can get fined for littering – rightfully so – but when a company like Microsoft makes sweeping decisions which cause untold amounts of dangerous chemicals to be dumped in countless locations all over the globe, governments shrug it off and move on. At least we will get some cheap eBay hardware out of it, I guess.
With all the problems Windows is facing, I think one area where Microsoft can make some easy, quick gains is by drastically improving Explorer, Windows’ file manager. It seems that in the latest developer releases, they’re doing just that. The most impactful change – possibly – is that Microsoft is going to preload Explorer. We’re exploring preloading File Explorer in the background to help improve File Explorer launch performance. This shouldn’t be visible to you, outside of File Explorer hopefully launching faster when you need to use it. If you have the change, if needed there is an option you can uncheck to disable this called “Enable window preloading for faster launch times” in File Explorer’s Folder Options, under View. ↫ Windows Insider Program Team Microsoft is also reordering the context menu in Explorer, and while this may seem like a small set of changes, the new context menu does look much tidier and less busy. They achieve this by moving a few top-level items to a submenu, and reordering some other elements. Sadly, the context menu still retains its own context menu (“Show more options”), which is a traditional Win32 menu – which I still think is one of the most Windows of Windows things of all time. Regardless, I hope these small changes make Explorer more bearable to use for those of you still using Windows, because we all know you need it.
You may have noticed a sharp increase in problems and issues in Windows recently – following the rise of the “AI” hype cycle, entirely coincidentally, I’m sure – and it seems Microsoft is finally starting to acknowledge just how bad Windows has become. On the positive side though, following all that backlash, Microsoft acknowledged Windows has issues, and as if on cue, the company in a new support article has admitted that there are problems on almost every major Windows 11 core feature. The issues are related to XAML and this impacts all the Shell components like the Start Menu, Taskbar, Explorer, and Windows Settings. ↫ Sayan Sen at Neowin It’s wild how many core components like this have apparently been broken due to these problems since July of this year. This means countless Windows users have been experiencing weird issues on a daily basis in multiple components for four months now, which is absolutely wild. On top of all the more structural problems in Windows, I wonder how people can get anything done at all – only a few days ago, I had to manually clean out the Installer folder in the Windows folder on my wife’s gaming PC, because for some inexplicable reason, Windows decided to permanently store 18GB’s worth (!) of past Adobe Acrobat updates and installers in there. It’s impossible to reliably say that Microsoft’s incessant focus on crypto NFTs “AI” lies at the root of all of these problems, but if 30% of “new” code in Microsoft is indeed regurgitated by “AI”, it’s hard not to conclude as such.
Blasts from the pasts are often fun, and in the case of feature removals from Windows, it’s often accompanied by surprise that the feature in question still existed. Case in point: This article provides essential information about the deprecation and planned removal of Windows Internet Name Service (WINS) from future Windows Server releases. Microsoft has announced that WINS will be removed from all Windows Server releases after Windows Server 2025 and will remain under the standard support lifecycle through November 2034. Organizations using WINS are strongly encouraged to migrate to modern DNS-based name resolution solutions. ↫ Microsoft knowledge base article WINS was introduced with Windows NT 3.5 back in 1994, and maps NetBIOS to IP addresses in much the same way DNS maps domains names to IP addresses. Nobody should be using WINS anymore, and Microsoft has been discouraging its use for a long time now. With the ubiquity of DNS, WINS serves very little purpose, so it makes sense Microsoft is removing it from Windows.
Microsoft has just announced a whole slew of new “AI” features for Windows, and this time, they’ll be living in your taskbar. Microsoft is trying to transform Windows into a “canvas for AI,” with new AI agents integrated into the Windows 11 taskbar. These new taskbar capabilities are designed to make AI agents feel like an assistant in Windows that can go off and control your PC and do tasks for you at the click of a button. It’s part of a broader overhaul of Windows to turn the operating system into an “agentic OS.” Microsoft is integrating a variety of AI agents directly into the Windows 11 taskbar, including its own Microsoft 365 Copilot and third-party options. “This integration isn’t just about adding agents; it’s about making them part of the OS experience,” says Windows chief Pavan Davuluri. ↫ Tom Warren at The Verge These “AI” agents will control your computer, applications, and files for you, which may make some of you a little apprehensive, and for good reason. “AI” tools don’t have a great track record when it comes to privacy – Windows Recall comes to mind – and as such, Microsoft claims this time, it’ll be different. These new “AI” agents will run in what are essentially dedicated Windows accounts acting as sandboxes, to ensure they can only access certain resources. While I find the addition of these “AI” tools to Windows insufferable and dumb, I’m at least glad Microsoft is taking privacy and security seriously this time, and I doubt Microsoft would repeat the same mistakes they made with the entirely botched rollout of Windows Recall. in addition, after the Cloudstrike fiasco, Microsoft made clear commitments to improve its security practices, which further adds to the confidence we should all have these new “AI” tools are safe, secure, and private. But wait, what’s this? Additionally, agentic AI applications introduce novel security risks, such as cross-prompt injection (XPIA), where malicious content embedded in UI elements or documents can override agent instructions, leading to unintended actions like data exfiltration or malware installation. ↫ Microsoft support document about the new “AI” features Microsoft’s new “AI” features can go out and install malware without your consent, because these features possess the access and privileges to do so. The mere idea that some application – which is essentially what these “AI” features really are – can go out onto the web and download and install whatever it wants, including malware, “on your behalf”, in the background, is so utterly dystopian to me I just can’t imagine any serious developer looking at this and thinking “yeah, ship it”. I’m living in an insane asylum.
Let’s take a look at how things are going at Microsoft, whose CEO claimed a few months ago that 30% of their code was generated by “AI”. After installing Windows Updates released on or after October 28, 2025 (KB5067036), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process. When you reopen Task Manager, the previous instance continues running in the background even though no window is visible. This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance. Additional instances appear as “Task Manager” in the Processes tab and as “Taskmgr.exe” in the Details tab. Although the impact is less if Task Manager is opened and closed a few times, many instances accumulated over time can cause noticeable slowdowns in other applications. ↫ The Windows Health Dashboard Well okay then.
After the release of Windows 95, with its brand new and incredibly influential graphical user interface, it was only a matter of time before this new taskbar, Start menu, and everything else would make its way to Microsoft’s other operating system line, Windows NT. The development of Windows 95 more or less lined up with that of Windows NT 3.5, but it wouldn’t be until Windows NT 4.0, released a little less than a year after Windows 95, that NT, too, would have the brand new user interface. Raymond Chen has published a blog post detailing the cooperation and interplay between the Windows 95 and Windows NT teams, and, as always with Chen, it’s a joy to read. Members of the Windows 95 user interface team met regularly with members of the Windows NT user interface team to keep them aware of what was going on and even get their input on some ideas that the Windows 95 team were considering. The Windows NT user interface team were focused on shipping Windows NT, but they appreciated being kept in the loop. During the late phases of the development of Windows 95, the Windows NT side of the house took a more active role in bringing the Windows 95 user interface to Windows NT. ↫ Raymond Chen at The Old New Thing Chen details there was a lot of code-sharing, to the point where the Windows 95 version of the GUI contained NT-specific code, and vice versa. This code-sharing was quite a lot less elegant than today with tools like git, since Microsoft’s own internal source code system called SLM (pronounced ‘slime’) did not support branches, so they had to regularly perform three-way merges manually. It was a different time, for sure. Anyway, it’s amazing how much of this ancient Microsoft lore could’ve been lost to time, or shrouded in mystery, if it wasn’t for someone like Raymond Chen regularly sharing the stories from Microsoft’s past.
Microsoft is introducing a new feature in Windows to better deal with blue screens of death. In the release notes for Windows 11 Insider Preview Build 26220.6982 (Dev Channel), the company detailed that after a user experiences a blue screen, Windows will automatically perform a memory scan. We’re introducing a new feature that helps improve system reliability. If your PC experiences a bugcheck (unexpected restart), you may see a notification when signing in suggesting a quick memory scan. If you choose to run it, the system will schedule a Windows Memory Diagnostic scan to run during your next reboot (taking 5 minutes or less on average) and then continue to Windows. If a memory issue is found and mitigated, you will see a notification post-reboot. ↫ Amanda Langowski at the Windows Blogs In its current iteration, this memory scan will trigger after every single error code to collect as much data as possible, but Microsoft states it will refine and narrow the number of error codes in the future. In addition, this feature will not be available on Arm64 and systems with Administrator Protection and/or BitLocker without Secure Boot. Let’s hope this feature won’t be a nuisance, but an actually useful feature that helps people uncover memory problems that otherwise remain undiagnosed.
Raymond Chen has another great post about some of the classic icons from Windows 95, this time focusing on pifmgr.dll. In this file, there are a variety of random-seeming icons, and it turns out they’re random for a reason: they were just a bunch a fun, generic icons intended for people to use when creating PIF files. The icons in pifmgr.dll were created just for fun. They were not created with any particular programs in mind, with one obvious exception. They were just a fun mix of icons for people to use for their own homemade shortcut files. ↫ Raymond Chen at The Old New Thing For those of us who didn’t grow up with Windows, or who, god forbid, are too young to know, PIF or personal information files are effectively shortcuts to DOS programs for use in a multitasking environment. A PIF file would not only point to the relevant DOS executable, but also contain information about the environment in which said executable was supposed to run. Their history goes back to IBM’s TopView, and Microsoft later embraced and adapted them for use in Windows.
Microsoft has published a set of short questions and answers about driver updates through Windows Update, and there’s one tidbit in there I found interesting. Driver dates might look old, but that is not true. The driver date is descriptive info set by the driver provider and can be any date they choose. When determining which driver to install, Windows Update uses targeting information set by the provider inside the driver files to determine the best driver. This lets the device provider promote the best driver, regardless of the chosen date. ↫ Microsoft knowledge base article Whenever I do have to fiddle with Windows machines, I always wondered about why some drivers in Windows Update would show some seriously old dates. It turns out the answer is as obvious as it always tends to be: OEMs.
Submitted by