Author: Martin Brinkmann

The main future of PC that Microsoft envisions is giving Windows users more flexibility when it comes to interacting with the PC. Instead of using mouse and keyboard, Microsoft is betting big on AI and the recently announced Copilot Voice feature.

In simple terms, it allows anyone, Microsoft says even users with no-Copilot+ PCs, to talk to the AI using a connected microphone. This allows Windows users to use their voice for searching, getting help, or automating tasks, according to Microsoft.

Many news outlet made it appear that Microsoft wants Windows users to use their voice exclusively when they use the PC. This is not the case, but Microsoft believes that voice will play a much larger role in the future.

There are several uncertainties here, largely because Microsoft did not provide many details on the functionality. Tests have to show how well, or not, the voice feature works and what you can do with it.

• Is it just for communicating with the AI via voice?
• Can you use it for other purposes, e.g., dictation?
• What are the privacy implications? Where is the voice data processed? Is it stored? If so, for how long? Who has access to the data?

Who is going to talk to their PC?

Assuming that the feature works well, the question about who is going to use it needs to be answered as well.

Voice interactions can be beneficial in some contexts, for instance if you need to use your hands for something else, or use a fullscreen app and do not want to switch to the text-based prompt.

However, voice does not work well in some contexts. Imagine talking to your Windows PC during your commute, or in an office with other workers sitting nearby.

The idea of a Star Trek-like communication with a computer system works well, if there is only one person talking to it. Now imagine the whole Enterprise-crew talking to the computer at the same time in the command room. That is utter chaos.

So, this voice feature will be used in private for the most part, which excludes some business use. Still, Microsoft says it is another option that Windows users have, and that is fine, provided that you want to communicate with the AI.

What is your take on this? Do you see yourself talking to an AI in the coming years?

It did not take long for Microsoft to confirm the first few issues after the official release of this year’s feature update, Windows 11 version 25H2.

The latest issue affects the Windows Recovery Environment. It is an essential recovery option of Windows that includes features such as repairing startup, resetting the PC, or uninstalling updates.

The confirmed bug renders USB mice and keyboards inoperable. Means, if the input devices are connected via USB, they won’t function in the Windows Recovery Environment.

For some, it can mean that no selection can be made, unless a non-USB mouse or keyboard is connected to the PC.

The issue affects the following platforms:

• Windows 11, version 25H2
• Windows 11, version 24H2
• Windows Server 2025

Microsoft writes:

After installing the Windows security update released on October 14, 2025 (KB5066835), USB devices, such as keyboards and mice, do not function in the Windows Recovery Environment (WinRE). This issue prevents navigation of any of the recovery options within WinRE.

Microsoft notes that the issue does not impact normal operations. In Windows itself, USB mice and keyboards continue to work.

The company revealed that it plans to release a fix for the issue in the coming days. This was on October 17th, which suggests that a fix should be released very soon.

Until then, you better cross fingers that you won’t need the Recovery Environment or have a non-USB keyboard or mouse ready for accessing it even with the bug present.

The second issue that Microsoft confirmed affected IIS websites. They would fail to load if affected. Microsoft admitted that it fixed the issue using a Known Issues Rollback. This rollback restores previous functionality to resolve bugs.

Note that it is necessary on managed PCs to configure special policies to allow the rollback to take place, as explained here.

If you still run a device with the Home or Pro editions of Windows 11, version 23H2, then you may want to consider upgrading it to a newer version of Windows 11. Microsoft published a reminder that the particular version of the operating system is reaching end of life in November 2025 for consumer devices.

The details:

• Affects Windows 11, version 23H2 Home and Pro editions.
• Support ends after November 11, 2025.

Microsoft writes on its website:

Windows 11 Home and Pro, version 23H2 will reach the end of updates on November 11, 2025. This version was released in October of 2023.

This edition will no longer receive security updates after November 11, 2025. Customers who contact Microsoft Support after this date will be directed to update their device to the latest version of Windows 11 to remain supported.

Microsoft released the operating system in 2023. It is supporting specific consumer versions of its Windows 11 operating system for 24 months. Business customers get an additional 12 months worth of support for specific versions of the operating system.

Tip: use the two keys Windows-key and R to open the runbox. Type winver and hit the Enter-key. This displays the version that is installed on a device currently.

The solution

Most home devices should support Windows 11, version 24H2 or this month’s Windows 11, version 25H2. Both upgrades won’t install too quickly, unlike the upgrade from 24H2 to 25H2. Expect multiple reboots during the upgrade process.

Should you upgrade to 24H2 or 25H2? New Windows versions are better to be avoided in the first months after release. While 25H2 is a smallish release, it should not be a problem to upgrade to Windows 11, version 24H2 first. The upgrade to 25H2 should not take long once you feel ready to install it.

Most devices should upgrade fine via Windows Update in the Settings app. Just open it, maybe hit the check for updates button, and you should see a new version offered to you.

This may not be the case if you bypassed system requirement checks during installation of Windows 11, or if a safeguard hold is in place. You can check out my guide on upgrading Windows 11 on systems that do not meet all requirements.

While Microsoft has its own tool for checking if a PC meets the system requirements of its Windows 11 operating system, it is generally considered rather heavy and not overly useful.

If you have come to the same conclusion, you may prefer an open source alternative that is both free and lightweight.

WhyNotWin11 is developed by serial developer Roby C. Mahel, whom you may know for his work on MSEdgeRedirect and other open source apps already.

The main purpose of WhyNotWin11 is simple: check, if your PC meets the system requirements to find out if you can upgrade without hassles.

All you need to do is download the app and run it. No installation, no ads, nothing that is considered bloat.

The app runs its checks on start automatically and presents its findings to you in its interface after a short moment.

Note that you can run the app on Windows 11 as well. Handy, if you installed the operating system and used bypasses for certain requirements.

The program color codes results. Green checkmark tell you that everything is fine, but you will also known if a component does not meet Windows 11’s minimum requirements.

WhyNotWin11 does not prioritize certain components over others, which could improve usability. Arguably, some checks are more important than others. For instance, the CPU or TPM version checks, while others, like CPU frequency, may not be as important, at least not for making upgrade decisions.

Still, it is easy enough and you see at a glance if your system fails to meet requirements. You can hover over the i-icon next to an entry to find out more about it.

WhyNotWin11 does not provide suggestions or tips to resolve compatibility issues. You find a few help guides in settings though. These explain how to enable secure boot or the TPM. There is also a link to the official Windows 11 requirements and to skipping some of the checks.

All guides open websites though.

Closing Words

WhyNotWin11 is a handy open source tool to quickly check the Windows 11 compatibility of a PC. It is a portable app, which means that you can run it without installation. Ideal for placing it on a USB tools collection and carrying it around whenever you do some troubleshooting work.

Now You: do you use lightweight open source tools like WhyNotWin11 regularly? Feel free to highlight apps that you recommend in the comments below.

It is clear that Microsoft is pushing Windows 11 users towards using a Microsoft account. While using one has advantages, part of the user base prefers local accounts because they are not tied to a Microsoft account, offer more privacy, and there is no risk of accounts being banned by Microsoft.

Up until now, workarounds existed to create local accounts in Windows 11. These required a bit of magic during setup, but they let users create a local account immediately.

Going forward, it appears that Microsoft is tinkering with Windows setup to make these bypasses go away.

In a recent Insider build, it posted the following announcement:

We are removing known mechanisms for creating a local account in the Windows Setup experience (OOBE). While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens, potentially causing users to exit OOBE with a device that is not fully configured for use. 

The consequence, according to Microsoft? “Users will need to complete OOBE with internet and a Microsoft account, to ensure device is setup correctly.”

In other words, Microsoft is forcing users to go through the process of setting up their device and system with a Microsoft account. Even users who have no interest in using one are required to use one during setup.

They can still create a local account after setup ended and remove the Microsoft account, but this requires even more work on their part to set up the operating system.

Microsoft says that it is doing so because setting up using local accounts bypasses “critical setup screens”. The company does not reveal which, but if your first thought is upsells, you are probably not too far off the mark here.

Using a Microsoft account is the first step towards signing up for Microsoft 365 — you need Office and more online space right — or a Game Pass — you play games, right — or towards using Copilot, Edge or other company products.

Bypasses continue to exist, but they require tweaking Windows installation media, something that most users may not be willing to do. It may also lead to more downloads of installation media from third-party sources, which is also increasing the risk of malware infections.

Another option, at least for now, is to set up Windows 11 using an older image. This should work but may require extended upgrades to make sure the system is supported.

Now You: what is your take on this? Should Microsoft give users clear options to use local accounts or a Microsoft account? Feel free to leave a comment down below.