Windows 11 has other system requirements, though they weren’t the focus of this TPM-centric blog post. Windows 11 systems must have Secure Boot enabled, and they have to use a supported processor—an 8th-gen Intel Core CPU, an AMD Ryzen 2000 CPU, or a Qualcomm Snapdragon 850 CPU or newer. In fact, these CPU requirements exclude a couple of generations’ worth of Intel and AMD chips with built-in TPM 2.0 support.
Windows 11 also has nominal requirements for RAM and processor speed, but any system that meets the CPU or TPM requirements will easily clear those bars. If you have a supported CPU and your PC doesn’t appear to support TPM 2.0, you should be able to enable it in your system’s BIOS, either manually or by installing a BIOS update for your motherboard.
Windows 11 can be installed on unsupported systems, either those with an older TPM 1.2 module or no TPM enabled at all. It’s more annoying to install major updates on those systems, and Microsoft reserves the right to pull updates from those systems at any time, but aside from that, Windows 11 usually runs about as well on these PCs as Windows 10 did.
Windows 10’s free, guaranteed security updates stop in October 2025, less than a year from now. Windows 10 users with supported PCs have been offered the Windows 11 upgrade plenty of times before. But now Microsoft is apparently making a fresh push to get users to upgrade, sending them full-screen reminders recommending they buy new computers.
The reminders, which users have seen within the last few days, all mention the end of Windows 10 support but otherwise seem to differ from computer to computer. My Ars colleague Kyle Orland got one focused on Windows 11’s gaming features, while posters on X (formerly Twitter) got screens that emphasized the ease of migrating from old PCs to new ones and other Windows 11 features. One specifically recommended upgrading to a Copilot+ PC, which supports a handful of extra AI features that other Windows 11 PCs don’t, but other messages didn’t mention Copilot+ specifically.
None of the messages mention upgrading to Windows 11 directly, though Kyle said his PC meets Windows 11’s requirements. These messages may be intended mostly for people using older PCs that can’t officially install the Windows 11 update.
But this is more than just a theoretical exercise; I’ve been using Windows 11 on some kind of “unsupported” system practically since it launched to stay abreast of what the experience is actually like and to keep tabs on whether Microsoft would make good on its threats to pull support from these systems at any time.
Now that we’re three years in, and since I’ve been using Windows 11 24H2 on a 2012-era desktop and laptop as my primary work machines on and off for a few months now, I can paint a pretty complete picture of what Windows 11 is like on these PCs. As the Windows 10 update cliff approaches, it’s worth asking: Is running “unsupported” Windows 11 a good way to keep an older but still functional machine running, especially for non-technical users?
My hardware
I’ve run Windows 11 on a fair amount of old hardware, including PCs as old as a late XP-era Core 2 Duo Dell Inspiron desktop. For the first couple of years, I ran it most commonly on an old Dell XPS 13 9333 with a Core i5-4250U and 8GB of RAM and a Dell Latitude 3379 2-in-1 that just barely falls short of the official requirements (both systems are also pressed into service for ChromeOS Flex testing periodically).
But I’ve been running the 24H2 update as my main work OS on two machines. The first is a Dell Optiplex 3010 desktop with a 3rd-generation Core i5-3xxx CPU, which had been my mother’s main desktop until I upgraded it a year or so ago. The second is a Lenovo ThinkPad X230 with a i5-3320M inside, a little brick of a machine that I picked up for next to nothing on Goodwill’s online auction site.
Both systems, and the desktop in particular, have been upgraded quite a bit; the laptop has 8GB of RAM while the desktop has 16GB, both are running SATA SSDs, and the desktop has a low-profile AMD Radeon Pro WX2100 in it, a cheap way to get support for running multiple 4K monitors. The desktop also has USB Wi-Fi and Bluetooth dongles and an internal expansion card that provides a pair of USB 3.0 Type-A ports and a single USB-C port. Systems of this vintage are pretty easy to refurbish since components are old enough that they’ve gone way down in price but not so old that they’ve become rare collectors’ items. It’s another way to get a usable computer for $100—or for free if you know where to look.
And these systems were meant to be maintained and upgraded. It’s one of the beautiful things about a standardized PC platform, though these days we’ve given a lot of that flexibility up in favor of smaller, thinner devices and larger batteries. It is possible to upgrade and refurbish these 12-year-old computers to the point that they run modern operating systems well because they were designed to leave room for that possibility.
But no matter how much you upgrade any of these PCs or how well you maintain them, they will never meet Windows 11’s official requirements. That’s the problem.
Using it feels pretty normal
Depending on how you do it, it can be a minor pain to get Windows 11 up and running on a computer that doesn’t natively support it. But once the OS is installed, Microsoft’s early warnings about instability and the possible ending of updates have proven to be mostly unfounded.
A Windows 11 PC will still grab all of the same drivers from Windows Update as a Windows 10 PC would, and any post-Vista drivers have at least a chance of working in Windows 11 as long as they’re 64-bit. But Windows 10 was widely supported on hardware going back to the turn of the 2010s. If it shipped with Windows 8 or even Windows 7, your hardware should mostly work, give or take the occasional edge case. I’ve yet to have a catastrophic crash or software failure on any of the systems I’m using, and they’re all from the 2012–2016 era.
Once Windows 11 is installed, routine software updates and app updates from the Microsoft Store are downloaded and installed on my “unsupported” systems the same way they are on my “supported” ones. You don’t have to think about how you’re running an unsupported operating system; Windows remains Windows. That’s the big takeaway here—if you’re happy with the performance of your unsupported PC under Windows 10, nothing about the way Windows 11 runs will give you problems.
…Until you want to install a big update
There’s one exception for the PCs I’ve had running unsupported Windows 11 installs in the long term: They don’t want to automatically download and install the yearly feature updates for Windows. So a 22H2 install will keep downloading and installing updates for as long as they’re offered, but it won’t offer to update itself to versions 23H2 or 24H2.
This behavior may be targeted specifically at unsupported PCs, or it may just be a byproduct of how Microsoft rolls out these yearly updates (if you have a supported system with a known hardware or driver issue, for example, Microsoft will withhold these updates until the issues are resolved). Either way, it’s an irritating thing to have to deal with every year or every other year—Microsoft supports most of its annual updates for two years after they’re released to the public. So 23H2 and 24H2 are currently supported, while 22H2 and 21H2 (the first release of Windows 11) are at the end of the line.
This essentially means you’ll need to repeat the steps for doing a new unsupported Windows 11 install every time you want to upgrade. As we detail in our guide, that’s relatively simple if your PC has Secure Boot and a TPM but doesn’t have a supported processor. Make a simple registry tweak, download the Installation Assistant or an ISO file to run Setup from, and the Windows 11 installer will let you off with a warning and then proceed normally, leaving your files and apps in place.
Without Secure Boot or a TPM, though, installing these upgrades in place is more difficult. Trying to run an upgrade install from within Windows just means the system will yell at you about the things your PC is missing. Booting from a USB drive that has been doctored to overlook the requirements will help you do a clean install, but it will delete all your existing files and apps.
If you’re running into this problem and still want to try an upgrade install, there’s one more workaround you can try.
Download an ISO for the version of Windows 11 you want to install, and then either make a USB install drive or simply mount the ISO file in Windows by double-clicking it.
Open a Command Prompt window as Administrator and navigate to whatever drive letter the Windows install media is using. Usually that will be D: or E:, depending on what drives you have installed in your system; type the drive letter and colon into the command prompt window and press Enter.
Type setup.exe /product server
You’ll notice that the subsequent setup screens all say they’re “installing Windows Server” rather than the regular version of Windows, but that’s not actually true—the Windows image that comes with these ISO files is still regular old Windows 11, and that’s what the installer is using to upgrade your system. It’s just running a Windows Server-branded version of the installer that apparently isn’t making the same stringent hardware checks that the normal Windows 11 installer is.
This workaround allowed me to do an in-place upgrade of Windows 11 24H2 onto a Windows 10 22H2 PC with no TPM enabled. It should also work for upgrading an older version of Windows 11 to 24H2.
Older PCs are still very useful!
Having to go out of your way to keep Windows 11 up to date on an unsupported PC is a fairly major pain. But unless your hardware is exceptionally wretched (I wouldn’t recommend trying to get by with less than 4GB of RAM at an absolute bare minimum, or with a spinning hard drive, or with an aging low-end N-series Pentium or Celeron chip), you’ll find that decade-old laptops and desktops can still hold up pretty well when you’re sticking to light or medium-sized workloads.
I haven’t found this surprising. Major high-end CPU performance improvements have come in fits and starts over the last decade, and today’s (Windows 11-supported) barebones bargain basement Intel N100 PCs perform a lot like decade-old mainstream quad-core desktop processors.
With its RAM and GPU updates, my Optiplex 3010 and its Core i5 worked pretty well with my normal dual-4K desktop monitor setup (it couldn’t drive my Gigabyte M28U at higher than 60 Hz, but that’s a GPU limitation). Yes, I could feel the difference between an aging Core i5-3475S and the Core i7-12700 in my regular Windows desktop, and it didn’t take much at all for CPU usage to spike to 100 percent and stay there, always a sign that your CPU is holding you back. But once apps were loaded, they felt responsive, and I had absolutely no issues writing, recording and editing audio, and working in Affinity Photo on the odd image or two.
I wouldn’t recommend using this system to play games, nor would I recommend overpaying for a brand-new GPU to pair with an older quad-core CPU like this one (I chose the GPU I did specifically for its display outputs, not its gaming prowess). If you wanted to, you could still probably get respectable midrange gaming performance out of a 4th-, 6th-, or 7th-gen Intel Core i5 or i7 or a first-generation AMD Ryzen CPU paired with a GeForce RTX 4060 or 3060, or a Radeon RX 7600. Resist the urge to overspend, consider used cards as a way to keep costs down, and check your power supply before you install anything—the years-old 300 W power supply in a cheap Dell office desktop will need to be replaced before you can use it with any GPU that has an external power connector.
My experience with the old Goodwill-sourced ThinkPad was also mostly pretty good. It had both Secure Boot and a TPM, making installation and upgrades easier. The old fingerprint sensor (a slow and finicky swipe-to-scan sensor) and its 2013-era driver even support Windows Hello. I certainly minded the cramped, low-resolution screen—display quality and screen-to-bezel ratio being the most noticeable changes between a 12-year-old system and a modern one—but it worked reliably with a new battery in it. It even helped me focus a bit at work; a 1366×768 screen just doesn’t invite heavy multitasking.
But the mid-2010s are a dividing line, and new laptops are better than old laptops
That brings me to my biggest word of warning.
If you want to run Windows 11 on an older desktop, one where the computer is just a box that you plug stuff into, the age of the hardware isn’t all that much of a concern. Upgrading components is easier whether you’re talking about a filthy keyboard, a failing monitor, or a stick of RAM. And you don’t need to be concerned as much with power use or battery life.
But for laptops? Let me tell you, there are things about using a laptop from 2012 that you don’t want to remember.
Three important dividing lines: In 2013, Intel’s 4th-generation Haswell processors gave huge battery life boosts to laptops thanks to lower power use when idle and the ability to switch more quickly between active and idle states. In 2015, Dell introduced the first with a slim-bezeled design (though it would be some years before it would fix the bottom-mounted up-your-nose webcam), which is probably the single most influential laptop design change since the MacBook Air. And around the same time (though it’s hard to pinpoint an exact date), more laptops began adopting Microsoft’s Precision Touchpad specification rather than using finicky, inconsistent third-party drivers, making PC laptop touchpads considerably less annoying than they had been up until that point.
And those aren’t the only niceties that have become standard or near-standard on midrange and high-end laptops these days. We also have high-resolution, high-density displays; the adoption of taller screen aspect ratios like 16: 10 and 3:2, giving us more vertical screen space to use; USB-C charging, replacing the need for proprietary power bricks; and backlit keyboards!
The ThinkPad X230 I bought doesn’t have a backlit keyboard, but it does have a bizarre little booklight next to the webcam that shines down onto the keyboard to illuminate it. This is sort of neat if you’re already the kind of person inclined to describe janky old laptops as “neat,” but it’s not as practical.
Even if you set aside degraded, swollen, or otherwise broken batteries and the extra wear and tear that comes with portability, a laptop from the last three or four years will have a ton of useful upgrades and amenities aside from extra speed. That’s not to say that older laptops can’t be useful because they obviously can be. But it’s also a place where an upgrade can make a bigger difference than just getting you Windows 11 support.
Some security concerns
Windows 11’s system requirements were controversial in part because they were focused mostly on previously obscure security features like TPM 2.0 modules, hypervisor-protected code integrity (HVCI), and mode-based execution control (MBEC). A TPM module makes it possible to seamlessly encrypt your PC’s local storage, among other things, while HVCI helps to isolate data in memory from the rest of the operating system to make it harder for malicious software to steal things (MBEC is just a CPU technology that speeds up HVCI, which can come with a hefty performance penalty on older systems).
Aside from those specific security features, there are other concerns when using old PCs, some of the same ones we’ve discussed in macOS as Apple has wound down support for Intel Macs. Microsoft’s patches can protect against software security vulnerabilities in Windows, and they can provide some partial mitigations for firmware-based vulnerabilities since even fully patched and fully supported systems won’t always have all the latest BIOS fixes installed.
But software can’t patch everything, and even the best-supported laptops with 5th- or 6th-generation Core CPUs in them will be a year or two past the days when they could expect new BIOS updates or driver fixes.
The PC companies and motherboard makers make some of these determinations; cheap consumer laptops tend to get less firmware and software support regardless of whether Intel or AMD are fixing problems on their ends. But Intel (for example) stops supporting its CPUs altogether after seven or eight years (support ended for 7th-generation CPUs in March). For any vulnerabilities discovered after that, you’re on your own, or you have to trust in software-based mitigations.
I don’t want to overplay the severity or the riskiness of these kinds of security vulnerabilities. Lots of firmware-level security bugs are the kinds of things that are exploited by sophisticated hackers targeting corporate or government systems—not necessarily everyday people who are just using an old laptop to check their email or do their banking. If you’re using good everyday security hygiene otherwise—using strong passwords or passkeys, two-factor authentication, and disk encryption (all things you should already be doing in Windows 10)—an old PC will still be reasonably safe and secure.
A viable, if imperfect, option for keeping an old PC alive
If you have a Windows 10 PC that is still working well or that you can easily upgrade to give it a new lease on life, and you don’t want to pay whatever Microsoft is planning to charge for continued Windows 10 update support, installing Windows 11 may be the path of least resistance for you despite the installation and update hurdles.
Especially for PCs that only miss the Windows 11 support cutoff by a year or two, you’ll get an operating system that still runs reasonably well on your PC, should still support all of your hardware, and will continue to run the software you’re comfortable with. Yes, the installation process for Windows’ annual feature updates is more annoying than it should be. But if you’re just trying to squeeze a handful of years out of an older PC, it might not be an issue you have to deal with very often. And though Windows 11 is different from Windows 10, it doesn’t come with the same learning curve that switching to an alternate operating system like ChromeOS Flex or Linux would.
Eventually, these PCs will age out of circulation, and the point will be moot. But even three years into Windows 11’s life cycle, I can’t help but feel that the system requirements could stand to be relaxed a bit. That ship sailed a long time ago, but given how many PCs are still running Windows 10 less than a year from the end of guaranteed security updates, expanding compatibility is a move Microsoft could consider to close the adoption gap and bring more PCs along.
Even if that doesn’t happen, try running Windows 11 on an older but still functional PC sometime. Once you clean it up a bit to rein in some of modern Microsoft’s worst design impulses, I think you’ll be pleasantly surprised.
Andrew is a Senior Technology Reporter at Ars Technica, with a focus on consumer tech including computer hardware and in-depth reviews of operating systems like Windows and macOS. Andrew lives in Philadelphia and co-hosts a weekly book podcast called Overdue.
On Thursday, OpenAI released an early Windows version of its first ChatGPT app for Windows, following a Mac version that launched in May. Currently, it’s only available to subscribers of Plus, Team, Enterprise, and Edu versions of ChatGPT, and users can download it for free in the Microsoft Store for Windows.
OpenAI is positioning the release as a beta test. “This is an early version, and we plan to bring the full experience to all users later this year,” OpenAI writes on the Microsoft Store entry for the app. (Interestingly, ChatGPT shows up as being rated “T for Teen” by the ESRB in the Windows store, despite not being a video game.)
Upon opening the app, OpenAI requires users to log into a paying ChatGPT account, and from there, the app is basically identical to the web browser version of ChatGPT. You can currently use it to access several models: GPT-4o, GPT-4o with Canvas, 01-preview, 01-mini, GPT-4o mini, and GPT-4. Also, it can generate images using DALL-E 3 or analyze uploaded files and images.
If you’re running Windows 11, you can instantly call up a small ChatGPT window when the app is open using an Alt+Space shortcut (it did not work in Windows 10 when we tried). That could be handy for asking ChatGPT a quick question at any time.
And just like the web version, all the AI processing takes place in the cloud on OpenAI’s servers, which means an Internet connection is required.
So as usual, chat like somebody’s watching, and don’t rely on ChatGPT as a factual reference for important decisions—GPT-4o in particular is great at telling you what you want to hear, whether it’s correct or not. As OpenAI says in a small disclaimer at the bottom of the app window: “ChatGPT can make mistakes.”
Microsoft announced today that it’s releasing a new app called Windows App as an app for Windows that allows users to run Windows and also Windows apps (it’s also coming to macOS, iOS, web browsers, and is in public preview for Android).
On most of those platforms, Windows App is a replacement for the Microsoft Remote Desktop app, which was used for connecting to a copy of Windows running on a remote computer or server—for some users and IT organizations, a relatively straightforward way to run Windows software on devices that aren’t running Windows or can’t run Windows natively.
The new name, though potentially confusing, attempts to sum up the app’s purpose: It’s a unified way to access your own Windows PCs with Remote Desktop access turned on, cloud-hosted Windows 365 and Microsoft Dev Box systems, and individual remotely hosted apps that have been provisioned by your work or school.
“This unified app serves as your secure gateway to connect to Windows across Windows 365, Azure Virtual Desktop, Remote Desktop, Remote Desktop Services, Microsoft Dev Box, and more,” reads the post from Microsoft’s Windows 365 Senior Product Manager Hilary Braun.
Microsoft says that aside from unifying multiple services into a single app, Windows App’s enhancements include easier account switching, better device management for IT administrators, support for the version of Windows 365 for frontline workers, and support for Microsoft’s “Relayed RDP Shortpath,” which can enable Remote Desktop on networks that normally wouldn’t allow it.
On macOS, iOS, and Android, the Windows App is a complete replacement for the Remote Desktop Connection app—if you have Remote Desktop installed, an update will change it to the Windows App. On Windows, the Remote Desktop Connection remains available, and Windows App is only used for Microsoft’s other services; it also requires some kind of account sign-in on Windows, while it works without a user account on other platforms.
For connections to your own Remote Desktop-equipped PCs, Windows App has most of the same features and requirements as the Remote Desktop Connection app did before, including support for multiple monitors, device redirection for devices like webcams and audio input/output, and dynamic resolution support (so that your Windows desktop resizes as you resize the app window).
In October of 2017, Microsoft released a version of Windows 10 called the “Fall Creators Update,” back when the company tried to give brand names to these things rather than just sticking to version numbering. One of the new apps included in that update was called Paint 3D, and while it shared a name with the old two-dimensional MS Paint app, it was entirely new software that supported creating 3D shapes and a whole bunch of other editing and transform options that the old Paint app didn’t have.
But the old Paint app’s renaissance is coming at the expense of Paint 3D, which Microsoft says is formally being deprecated and removed from the Microsoft Store on November 4. Windows Central reports that users of the app will be notified via a banner message, just in case they aren’t regularly checking Microsoft’s documentation page for the list of deprecated and removed Windows features.
Microsoft recommends the Paint and Photos apps for viewing and editing 2D images and the 3D Viewer app for viewing 3D models. Creating and editing 3D images will be left to third-party software.
When it was introduced, Paint 3D was also pitched as a way to create and manipulate three-dimensional objects that could then be dropped into real environments using the Windows Mixed Reality platform. It’s probably not a coincidence that Windows Mixed Reality is being removed in this fall’s Windows 11 24H2 release, right around the same time Paint 3D will be removed from Windows and from the Microsoft Store.
Many Windows 8- and 10-era apps have either been axed or renamed in the Windows 11 era as Microsoft has refocused on built-in Windows apps with decadeslong histories. The Mail and Calendar apps are being replaced with a version of Outlook, and though it isn’t calledOutlook Express there are certainly parallels. The Groove app was renamed “Windows Media Player” and picked up a few legacy Media Player capabilities, like the ability to play and rip audio CDs. Voice Recorder became Sound Recorder. Snip & Sketch had its capabilities rolled back into the Snipping Tool.
CrowdStrike CEO George Kurtz said Thursday that 97 percent of all Windows systems running its Falcon sensor software were back online, a week after an update-related outage to the corporate security software delayed flights and took down emergency response systems, among many other disruptions. The update, which caused Windows PCs to throw the dreaded Blue Screen of Death and reboot, affected about 8.5 million systems by Microsoft’s count, leaving roughly 250,000 that still need to be brought back online.
Microsoft VP John Cable said in a blog post that the company has “engaged over 5,000 support engineers working 24×7” to help clean up the mess created by CrowdStrike’s update and hinted at Windows changes that could help—if they don’t run afoul of regulators, anyway.
“This incident shows clearly that Windows must prioritize change and innovation in the area of end-to-end resilience,” wrote Cable. “These improvements must go hand in hand with ongoing improvements in security and be in close cooperation with our many partners, who also care deeply about the security of the Windows ecosystem.”
Cable pointed to VBS enclaves and Azure Attestation as examples of products that could keep Windows secure without requiring kernel-level access, as most Windows-based security products (including CrowdStrike’s Falcon sensor) do now. But he stopped short of outlining what specific changes might be made to Windows, saying only that Microsoft would continue to “harden our platform, and do even more to improve the resiliency of the Windows ecosystem, working openly and collaboratively with the broad security community.”
When running in kernel mode rather than user mode, security software has full access to a system’s hardware and software, which makes it more powerful and flexible; this also means that a bad update like CrowdStrike’s can cause a lot more problems.
Recent versions of macOS have deprecated third-party kernel extensions for exactly this reason, one explanation for why Macs weren’t taken down by the CrowdStrike update. But past efforts by Microsoft to lock third-party security companies out of the Windows kernel—most recently in the Windows Vista era—have been met with pushback from European Commission regulators. That level of skepticism is warranted, given Microsoft’s past (and continuing) record of using Windows’ market position to push its own products and services. Any present-day attempt to restrict third-party vendors’ access to the Windows kernel would be likely to draw similar scrutiny.
Microsoft has also had plenty of its own security problems to deal with recently, to the point that it has promised to restructure the company to make security more of a focus.
CrowdStrike’s aftermath
CrowdStrike has made its own promises in the wake of the outage, including more thorough testing of updates and a phased-rollout system that could prevent a bad update file from causing quite as much trouble as the one last week did. The company’s initial incident report pointed to a lapse in its testing procedures as the cause of the problem.
Meanwhile, recovery continues. Some systems could be fixed simply by rebooting, though they had to do it as many as 15 times—this could give systems a chance to grab a new update file before they could crash. For the rest, IT admins were left to either restore them from backups or delete the bad update file manually. Microsoft published a bootable tool that could help automate the process of deleting that file, but it still required laying hands on every single affected Windows install, whether on a virtual machine or a physical system.
And not all of CrowdStrike’s remediation solutions have been well-received. The company sent out $10 UberEats promo codes to cover some of its partners’ “next cup of coffee or late night snack,” which occasioned some eye-rolling on social media sites (the code was also briefly unusable because Uber flagged it as fraudulent, according to a CrowdStrike representative). For context, analytics company Parametrix Insurance estimated the cost of the outage to Fortune 500 companies somewhere in the realm of $5.4 billion.
The detailed post explains exactly what happened: At just after midnight Eastern time, CrowdStrike deployed “a content configuration update” to allow its software to “gather telemetry on possible novel threat techniques.” CrowdStrike says that these Rapid Response Content updates are tested before being deployed, and one of the steps involves checking updates using something called the Content Validator. In this case, “a bug in the Content Validator” failed to detect “problematic content data” in the update responsible for the crashing systems.
CrowdStrike says it is making changes to its testing and deployment processes to prevent something like this from happening again. The company is specifically including “additional validation checks to the Content Validator” and adding more layers of testing to its process.
The biggest change will probably be “a staggered deployment strategy for Rapid Response Content” going forward. In a staggered deployment system, updates are initially released to a small group of PCs, and then availability is slowly expanded once it becomes clear that the update isn’t causing major problems. Microsoft uses a phased rollout for Windows security and feature updates after a couple of major hiccups during the Windows 10 era. To this end, CrowdStrike will “improve monitoring for both sensor and system performance” to help “guide a phased rollout.”
CrowdStrike says it will also give its customers more control over when Rapid Response Content updates are deployed so that updates that take down millions of systems aren’t deployed at (say) midnight when fewer people are around to notice or fix things. Customers will also be able to subscribe to release notes about these updates.
Recovery of affected systems is ongoing. Rebooting systems multiple times (as many as 15, according to Microsoft) can give them enough time to grab a new, non-broken update file before they crash, resolving the issue. Microsoft has also created tools that can boot systems via USB or a network so that the bad update file can be deleted, allowing systems to restart normally.
In addition to this preliminary incident report, CrowdStrike says it will release “the full Root Cause Analysis” once it has finished investigating the issue.
One of Windows 11’s more contentious changes is that, by default, both the Home and Pro editions of the operating system require users to sign in with a Microsoft account during setup. Signing in with an account does get you some benefits, at least if you’re a regular user of other Microsoft products like OneDrive, GamePass, or Microsoft 365 (aka Office). But if you don’t use those services, a lot of what a Microsoft account gets you in Windows 11 is repeated ads and reminders about signing up for those services. Using Windows with a traditional local account is still extremely possible, but it does require a small amount of know-how beyond just clicking the right buttons.
On the know-how front, Microsoft has taken one more minor, but nevertheless irritating, step away from allowing users to sign in with local accounts. This official Microsoft support page walks users with local accounts through the process of signing in to a Microsoft account. As recently as June 12, that page also included instructions for converting a Microsoft account into a local account. But according to Tom’s Hardware and the Internet Wayback Machine, those instructions disappeared on or around June 17 and haven’t been seen since.
Despite the documentation change, most of the workarounds for creating a local account still work in both Windows 11 23H2 (the publicly available version of Windows 11 for most PCs) and 24H2 (available now on Copilot+ PCs, later this fall for everyone else). The easiest way to do it on a PC you just took out of the box is to press Shift+F10 during the setup process to bring up a command prompt window, typing OOBEBYPASSNRO, rebooting, and then clicking the “I don’t have Internet” button when asked to connect to a Wi-Fi network.
Other workarounds include using the Rufus tool to create a USB installer that will automatically bypass the Microsoft account sign-in requirement, or (for Windows 11 Pro users) indicating that you want to join the PC to a corporate domain and then not actually joining it to a domain. Setting the PC up with a Microsoft account and then signing out afterward is also still an option.
There is one workaround that has allegedly stopped working—it used to be that trying to “sign in” with a nonexistent email account would get you a local sign-in option. But as of earlier this month, according to Windows Central editor Zac Bowden, it looks like the Windows 11 setup screen will just ask you to try another email address instead.
To be fair to Microsoft, all the big tech companies want you to sign in with an account before you can use all the features of the software, but neither Apple nor Google goes as far as to mandate account sign-in to access basic functionality. Macs, iPhones, and iPads will all let you complete the setup process without signing in, though you do have to know which buttons to click. Google will allow you to use Chromebooks in guest mode, and Android phones and tablets are still usable without signing in (though this does make it more difficult to find and install apps). Microsoft’s pushiness remains unique; there’s definitely a difference between a company that would really prefer that you sign in, and one that forces you to.
Microsoft is all-in on its Copilot+ PC push right now, but the fact is that they’ll be an extremely small minority among the PC install base for the foreseeable future. The program’s stringent hardware requirements—16GB of RAM, at least 256GB of storage, and a fast neural processing unit (NPU)—disqualify all but new PCs, keeping features like Recall from running on all current Windows 11 PCs.
But the Copilot chatbot remains supported on all Windows 11 PCs (and most Windows 10 PCs), and a change Microsoft has made to recent Windows 11 Insider Preview builds is actually making the feature less useful and accessible than it is in the current publicly available versions of Windows. Copilot is being changed from a persistent sidebar into an app window that can be resized, minimized, and pinned and unpinned from the taskbar, just like any other app. But at least as of this writing, this version of Copilot can no longer adjust Windows’ settings, and it’s no longer possible to call it up with the Windows+C keyboard shortcut. Only newer keyboards with the dedicated Copilot key will have an easy built-in keyboard shortcut for summoning Copilot.
If Microsoft keeps these changes intact, they’ll hit Windows 11 PCs when the 24H2 update is released to the general public later this year; the changes are already present on Copilot+ PCs, which are running a version of Window 11 24H2 out of the box.
Changing how Copilot works is all well and good—despite how quickly Microsoft has pushed it out to every Windows PC in existence, it has been labeled a “preview” up until the 24H2 update, and some amount of change is to be expected. But discontinuing the just-introduced Win+C keyboard shortcut to launch Copilot feels pointless, especially since the Win+C shortcut isn’t being reassigned.
The Copilot assistant exists on the taskbar, so it’s not as though it’s difficult to access, but the feature is apparently important enough to merit the first major change to Windows keyboards in three decades. Surely it also justifies retaining a keyboard shortcut for the vast majority of PC keyboards without a dedicated Copilot key.
People who want to continue to use Win+C as a launch key for Copilot can do so with custom keyboard remappers like Microsoft’s own Keyboard Manager PowerToy. Simply set Win+C as a shortcut for the obscure Win+Shift+F23 shortcut that the hardware Copilot key is already mapped to and you’ll be back in business.
Win+C has a complicated history
The Win+C keyboard shortcut actually has a bit of a checkered history, having been reassigned over the years to multiple less-than-successful Windows initiatives. In Windows 8, it made its debut as a shortcut for the “Charms” menu, part of the operating system’s tablet-oriented user interface that was designed to partially replace the old Start menu. But Windows 10 retreated from this new tablet UI, and the Charms bar was discontinued.
In Windows 10, Win+C was assigned to the Cortana voice assistant instead, Microsoft’s contribution to the early-2010s voice assistant boom kicked off by Apple’s Siri and refined by competitors like Amazon’s Alexa. But Cortana, like the Charms bar, never really took off, and Microsoft switched the voice assistant off in 2023 after a few years of steadily deprioritizing it in Windows 10 (and mostly hiding it in Windows 11).
Most older versions of Windows didn’t do anything with the Win+C, but if you go all the way back to the Windows 95 era, users of Microsoft Natural Keyboards who installed Microsoft’s IntelliType software could use Win+C to open the Control Panel. This shortcut apparently never made it into Windows itself, even as the Windows key became standard equipment on PCs in the late ’90s and early 2000s.
So pour one out for Win+C, the keyboard shortcut that is always trying to do something new and not quite catching on. We can’t wait to see what it does next.
In October 2025, Microsoft will stop supporting Windows 10 for most PC users, which means no more technical support and (crucially) no more security updates unless you decide to pay for them. To encourage adoption, the vast majority of new Windows development is happening in Windows 11, which will get one of its biggest updates since release sometime this fall.
But Windows 10 is casting a long shadow. It remains the most-used version of Windows by all publicly available metrics, including Statcounter (where Windows 11’s growth has been largely stagnant all year) and the Steam Hardware Survey. And last November, Microsoft decided to release a fairly major batch of Windows 10 updates that introduced the Copilot chatbot and other changes to the aging operating system.
That may not be the end of the road. Microsoft has announced that it is reopening a Windows Insider Beta Channel for PCs still running Windows 10, which will be used to test “new features and more improvements to Windows 10 as needed.” Users can opt into the Windows 10 Beta Channel regardless of whether their PC meets the requirements for Windows 11; if your PC is compatible, signing up for the less-stable Dev or Canary channels will still upgrade your PC to Windows 11.
Any new Windows 10 features that are released will be added to Windows 10 22H2, the operating system’s last major yearly update. Per usual for Windows Insider builds, Microsoft may choose not to release all new features that it tests, and new features will be released for the public version of Windows 10 “when they’re ready.”
One thing this new beta program doesn’t change is the end-of-support date for Windows 10, which Microsoft says is still October 14, 2025. Microsoft says that joining the beta program doesn’t extend support. The only way to continue getting Windows 10 security updates past 2025 is to pay for the Extended Security Updates (ESU) program; Microsoft plans to offer these updates to individual users but still hasn’t announced pricing for individuals. Businesses will pay as much as $61 per PC for the first year of updates, while schools will pay as little as $1 per PC.
Beta program or no, we still wouldn’t expect Windows 10 to change dramatically between now and its end-of-support date. We’d guess that most changes will relate to the Copilot assistant, given how aggressively Microsoft has moved to add generative AI to all of its products. For example, the Windows 11 version of Copilot is shedding its “preview” tag and becoming an app that runs in a regular window rather than a persistent sidebar, changes Microsoft could also choose to implement in Windows 10.
The Copilot key will, predictably, open up the Copilot generative AI assistant within Windows 10 and Windows 11. On an up-to-date Windows PC with Copilot enabled, you can currently do the same thing by pressing Windows + C. For PCs without Copilot enabled, including those that aren’t signed into Microsoft accounts, the Copilot key will open Windows Search instead (though this is sort of redundant, since pressing the Windows key and then typing directly into the Start menu also activates the Search function).
A quick Microsoft demo video shows the Copilot key in between the cluster of arrow keys and the right Alt button, a place where many keyboards usually put a menu button, a right Ctrl key, another Windows key, or something similar. The exact positioning, and the key being replaced, may vary depending on the size and layout of the keyboard.
We asked Microsoft if a Copilot key would be required on OEM PCs going forward; the company told us that the key isn’t mandatory now, but that it expects Copilot keys to be required on Windows 11 keyboards “over time.” Microsoft often imposes some additional hardware requirements on major PC makers that sell Windows on their devices, beyond what is strictly necessary to run Windows itself.
If nothing else, this new key is a sign of how much Microsoft wants people to use Copilot and its other generative AI products. Plenty of past company initiatives—Bing, Edge, Cortana, and the Microsoft Store, to name a few—never managed to become baked into the hardware like this. In the Windows 8 epoch, Microsoft required OEMs to build a Windows button into the display bezel of devices with touchscreens, but that requirement eventually disappeared. If Copilot fizzles or is deemphasized the way Cortana was, the Copilot key could become a way to quickly date a Windows PC from the mid-2020s, the way that changes to the Windows logo date keyboards from earlier eras.
We’ll definitely see more AI features from Microsoft this year, too—Microsoft Chief Marketing Officer Yusuf Medhi called 2024 “the year of the AI PC” in today’s announcement.
Chipmakers like Intel, AMD, and Qualcomm are all building neural processing units (NPUs) into their latest silicon, and we’ll likely see more updates for Windows apps and features that can take advantage of this new on-device processing capability. Rumors also indicate that we could see a “Windows 12” release as soon as this year; while Windows 11 has mostly had AI features stacked on top of it, a new OS could launch with AI features more deeply integrated into the UI and apps, as well as additional hardware requirements for some features.
Microsoft says the Copilot key will debut in some PCs that will be announced at the Consumer Electronics Show this month. Surface devices with the revised keyboard layout are “upcoming.”