Tag: windows 11

How is the last supported Windows operating system doing after Microsoft ended support for its predecessor Windows 10 a month ago? Not so good, at least according to Dell CEO Jeffrey Clarke.

Clarke revealed several information during the company’s latest earnings call. One of them being that Dell believes that there are 500 million Windows 10 PCs out there in the world that can’t be upgraded to Windows 11 officially. While most could be upgraded by bypassing Microsoft’s artificially introduced system requirements, only a small fraction will because of the technical process that is involved and the consequences.

Another 500 million PCs that run Windows 10 can be upgraded, but have not yet. That leaves about 500 million PCs that run Windows 11 already, according to Dell.

However, this is not the only bombshell that Clarke dropped during the call. He also revealed that the transition from Windows 10 to Windows 11 is much slower than the transition from Windows 8 to Windows 10.

The transition is lagging behind, which affects Dell’s growth in the sector. Dell reported a revenue of $12.1 billion for its Client Solutions Group, which bundles commercial client and consumer PC sales. Here, Dell reported a slight uptick in commercial client revenue to $10.1 billion and a declining revenue of $2 billion in consumer PCs.

The Infrastructure Solutions Group made more than up for that though. Its revenue was $14.1 billion, which is a 24 percent increase compared to the last year and the sevenths consecutive quarter with double-digit growth. AI is the main driver of the revenue increase of this group.

To sum it up: Windows 10 users seem to hold on to their PCs, even if they could upgrade them to Windows 10. For now, PCs remain supported with security updates if ESU is enabled for the device.

Now You: Windows 10 or Windows 11, what is your preference? Or something else? Maybe you made the switch to Linux already?

You may have heard that Microsoft is working on a new restore feature for Windows 11 called Point-in-time Restore.

The backup feature in a sentence: It allows Windows admins to restore the exact previous state of a Windows PC.

The main focus is to offer fast restores to a previous system state to allow the quickest recovery possible using integrated options.

The biggest different to System Restore, therefore, is that it creates a snapshot of the entire Windows system and not just some files and setting, like System Restore.

While that sounds like a great addition to Windows and could make some backup apps unnecessary, this is not the case entirely, as there are downsides to this as well.

Probably the biggest letdown is that it is capped to 72 hours. Means, it won’t help if the issue occurred before that period and was not noticed until then. Microsoft says that this is the maximum and that restore states will be deleted after being kept for the maximum.

The restore points may also be deleted in other circumstances, mostly when storage that is reserved for the restoration feature is reaching the set maximum size or when the device itself is running low on disk space.

Windows 11 creates a restore point every 24 hours by default. Here is a table that shows the main differences between Point-in-time Restore and System Restore, according to Microsoft.

Criteria	Point-in-time restore	System Restore
Configuration	System settings	Control panel
Restore point trigger	Scheduled frequency (automatic only)	Event-triggered or manual
Retention	Max 72 hours per restore point	Indefinite (subject to disk usage/cleanup)
Target scope	Full system state	System files and settings; app/user data coverage varies
Management	Will support remote management*	No modern management

Good news is that Point-in-time restore runs locally and while you do need to make sure that enough storage space is available, it could finally be a Windows feature that most Windows 11 users have nothing against.

However, it won’t replace traditional backup software, as these allow you to keep copies indefinitely, something that Point-in-time Restore does not seem to support and probably won’t ever.

Windows users who use BitLocker to encrypt their data either willingly or unknowingly may have run into a BitLocker related issue several times in the past.

It is unclear when it all started, but the essence of the bug was always the same: affected Windows PCs would boot into BitLocker Recovery Mode after installation of an update that caused the issue.

The problem here is that to get out of the mode, users needed the recovery key, which many probably did not really know. While it is easy to look it up online, at least when a user uses a Microsoft account to sign in, it still was a hassle in the best case.

Microsoft confirmed another BitLocker Recovery issue on the Microsoft 365 admin center, but not yet as a known issue for regular users who do not have access to the admin portal.

The issue affects the following Windows versions:

• Windows 10, version 22H2
• Windows 11, version 24H2
• Windows 11, version 25H2

The systems are affected, if the October 2025 security updates are installed on the machines.

Microsoft says that the issue affects Windows PCs with Intel processors and Modern Standby mostly. Still, other systems may also be affected.

As usually, Windows users may resolve the issue by entering the BitLocker recovery key when prompted for it.

Closing Words

Microsoft seems to have a hard time fixing the BitLocker bug for good, as it reappeared several times, including in May of 2025 when Microsoft issued another warning about the problem.

The integration of Microsoft Bing, or any other online search tool for that matter, in Windows Search is an abomination. The main idea is to run a search online if Windows can’t find anything locally or at least give you the option to run the search.

I’d argue that the vast majority of Windows users does not want this. When you run a search locally, you expect local results. Also, a web browser is just a click away and the more appropriate vessel for running searches online.

Recently I noticed that if you are too fast when the system boots, your searches may end up opening Bing in Microsoft Edge, even if there is a local match. It happens only when you open Start right after the system has booted, start typing and press the Enter-key.

Anyway, it is highly recommended to block Bing entirely in Windows Search, unless you are one of the few users who finds this useful actually (I have yet to meet a single user who does though, let me know..).

Here is how you can end Bing in Windows Search in a matter of seconds (thanks Henk):

1. Open the Start menu on the Windows machine.
2. Type Powershell.
3. Select “run as administrator” to open an elevated PowerShell window.
4. Paste the following code: Set-ItemProperty -Path “HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Search” -Name “BingSearchEnabled” -Value 0 -Type DWord
5. Press the Enter-key to run it.

That is all there is to it. In case you wonder, this adds the Dword BingSearchEnabled to the Registry. Note that you can add the information manually as well using the Registry Editor, or create a Registry file if you prefer that way.

You can undo the change at any time by setting the value to 1 or deleting the key. I doubt anyone would, but it may happen that Microsoft accidentally resets this. You will notice right away though, as searches may include online content in that case again.

Now You: Do you use the online search feature of Windows Search? Or do you disable it / ignore it instead? Feel free to leave a comment down below.

There is certainly no shortage of options when it comes to capturing screenshots or videos on computer systems. From built-in solutions like Microsoft’s Snipping Tool to excellent third-party apps like my favorite PicPick.

Greenshot is another household name. The open source application has been around for a long time and it is well maintained. It supports various types of screenshot captures, from full screen over windowed to region captures.

While it does lack some of the advanced options, like capturing video or scrolling windows in most programs, it does support a few extras like excellent support for integrating third-party services like Flickr or Dropbox. Other features that it supports include adding annotations and highlights, obfuscating parts of the screenshot, and more.

The developer of Greenshot Christian Schulz released a new version of the application just a few days ago. It includes a single fix for file associations not working when the app is running already and a new feature: a portable version.

Good news is that you can run Greenshot now from any location using the portable version. You can put it on a USB flash drive or stick and carry it with you around to use it on any Windows machine you plug the USB device in.

So, if you are using Greenshot already you might switch to the portable version, if you prefer it. You can download the portable version, or the setup version, of Greenshot from its GitHub repository.

Now You: which screenshot tool or tools do you use and why? Feel free to leave your recommendation in the comment section below.

Microsoft announced an upcoming change regarding the titles of Windows Update. Going forward, Microsoft wants to simplify the name of updates so that they are “more intuitive, consistent, and informative”.

The company hopes that this change will make it easier for regular users to understand what an update does that is installing or was installed on the Windows device. Original equipment manufacturers and partners should benefit from this as well, according to Microsoft.

The updated titles follow a simple structure and will focus on the name of the update. Most updates, the exception is a driver update, include the KB ID as before. Windows Updates include the build number furthermore, while drivers the version of the driver.

Microsoft posted several examples of how driver updates will be named in the future:

• Monthly or out-of-band security updates: Security Update (KB5034123) (26100.4747)
• Monthly preview non-security updates: Preview Update (KB5062660) (26100.4770)
• .NET Framework security updates: .NET Framework Security Update (KB5056579)
• .NET Framework non-security updates: .NET Framework Preview Update (KB5056579)
• Driver updates: Logitech Driver Update (123.331.1.0)
• AI component updates: Phi Silica AI Component Update (KB5064650) (1.2507.793.0)

Generally speaking, the new titles apply to Windows operating system updates, such as monthly cumulative updates, .NET Framework updates, driver updates, AI component updates, and Visual Studio updates.

Windows users will find the new titles under Settings > Windows Update and also in the update history, which can be accessed from the Windows Update page of the Settings. Lastly, it is also shown on the Windows release health website.

Microsoft says that updates that do get deployed via WSUS (Windows Server Update Services) or the Microsoft Update Catalog, won’t reflect the changed titles for the most part. Windows feature update titles will also keep the traditional title.

The new titles may omit the version of Windows the update is for. While that may not affect regular users who install the update on their devices, it could affect users who want a quick overview of the released updates on Microsoft’s website or elsewhere.

Now You: What is your take on this change? Is it for the better?

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.