Tag: Windows 11 fixes

Windows 11 mouse cursor bug caused by KB5120998 update August 2026
August 31, 2026

Windows 11 Mouse Cursor Bug: KB5120998 Fix & Workarounds

Post By administrator Microsoft, Windows , , , , , No Comments

The Windows 11 mouse cursor bug introduced by the optional August 2026 cumulative update KB5120998 has caught thousands of users off guard — cursor tails growing longer, pointer personalisation reverting to defaults, and high-DPI custom cursors ballooning into oversized white blobs. If you installed this update and your cursor is now behaving strangely, you are not alone, and there are steps you can take right now without having to roll back the entire update.

What Is KB5120998 and Why Did It Cause a Mouse Cursor Bug?

Windows 11 KB5120998 update history screen showing the cursor issue entry

Released on 27 August 2026 as an optional preview update, KB5120998 targets Windows 11 versions 24H2 and 25H2, bumping the OS builds to 26100.9278 and 26200.9278 respectively. According to Microsoft’s own release notes, the update ships with 35 changes covering taskbar reliability, Start menu improvements, voice-typing settings persistence, and Windows Management Instrumentation fixes. It is a preview — meaning IT admins and enthusiastic early adopters tend to grab it before the mandatory Patch Tuesday rollout — but its reach has still been wide enough to generate a significant wave of reports.

The KB5120998 cursor issue stems from a bug in the way the update handles mouse pointer personalisation settings. Microsoft has confirmed it received reports that “mouse cursor personalisation settings are being changed or reverted to certain standard settings” after installation. In practical terms, that means custom cursors get reset, cursor shadow and trail options change without the user touching them, and on high-DPI displays the system cursor reverts to an enlarged default white pointer. A secondary bug in the same update also resets desktop wallpaper for some users.

Which Windows 11 Versions Are Affected by the Cursor Bug?

The Windows cursor problem specifically targets machines running:

  • Windows 11 24H2 — OS Build 26100.9278
  • Windows 11 25H2 — OS Build 26200.9278

Because KB5120998 is an optional preview update, only users who actively chose to install it — or whose IT departments pushed it for testing — are exposed. Machines still on the standard automatic update channel that have not yet received KB5120998 are unaffected. You can confirm your current build by pressing Win + R, typing winver, and pressing Enter.

Symptoms: How the KB5120998 Cursor Issue Appears

Users across Reddit, Microsoft’s own Answers forum, and third-party tech outlets have reported a consistent set of symptoms. If you recognise any of these after installing KB5120998, the update is likely responsible:

  • Cursor tail or shadow appears noticeably longer than before
  • Custom cursor schemes revert to the default Windows white pointer
  • High-DPI cursors display as large, blocky white shapes instead of the intended design
  • The pointer size and colour settings in Settings > Accessibility > Mouse pointer and touch appear to reset on reboot
  • Attempting to re-apply cursor personalisation in Settings has no lasting effect
  • Desktop wallpaper resets to a default image (a secondary bug in the same update)

Microsoft’s Response to the Windows 11 Mouse Cursor Bug

Windows 11 mouse cursor bug fix steps in Mouse Properties and Accessibility settings

Microsoft has publicly acknowledged the cursor fix Windows 11 situation is on its radar. In a statement reported by Windows Latest, the company confirmed: “We’re aware” — and said it is actively investigating. No patch or out-of-band fix had been released at the time of writing (late August 2026), but given that KB5120998 is a preview update and not yet a mandatory rollout, Microsoft has time to bake a resolution into the next Patch Tuesday release before it reaches the wider Windows user base.

For the full official breakdown of what KB5120998 was supposed to fix, you can review Microsoft’s official KB5120998 support page, which lists all 35 changes in detail.

How to Apply a Cursor Fix Without Rolling Back the Update

The good news is that the cursor fix for Windows 11 does not necessarily require uninstalling KB5120998. Try these steps in order before resorting to a full update rollback.

Step 1: Manually Re-Apply Your Cursor Scheme

Open Settings > Bluetooth & devices > Mouse > Additional mouse settings. In the Mouse Properties dialog, navigate to the Pointers tab and reselect your preferred cursor scheme from the drop-down. Click Apply, then OK. Reboot your PC. For many users, this temporary re-application holds between sessions once the system has completed its first full restart post-update.

Step 2: Adjust Pointer Size and Colour via Accessibility Settings

Navigate to Settings > Accessibility > Mouse pointer and touch. Reset the pointer size slider and choose your preferred colour. Some users have reported that toggling between the custom colour option and then back to white — and applying — forces the system to write the correct value to the registry, making the preference stick.

Step 3: Edit the Registry Directly

For advanced users, the cursor preferences are stored under HKEY_CURRENT_USER\Control Panel\Cursors. You can export this key before the next update so you always have a clean backup. If KB5120998 wiped your values, you can re-import the exported .reg file to restore them instantly. Always back up the registry before making changes — press Win + R, type regedit, go to File > Export, and save the Cursors key.

Step 4: Uninstall KB5120998 (Last Resort)

If the KB5120998 cursor issue persists and is severely disrupting your workflow, uninstalling the update is confirmed to restore both cursor and wallpaper settings. Go to Settings > Windows Update > Update history > Uninstall updates, find KB5120998 in the list, and select Uninstall. Because this was an optional preview update, removing it does not leave you exposed to any mandatory security patches — those will arrive via the next standard cumulative update.

Will Microsoft Release a Permanent Cursor Fix for Windows 11?

Windows 11 licence validity unaffected by cursor bug or KB5120998 update

Almost certainly yes. Microsoft has a consistent pattern of resolving preview-update regressions in the subsequent mandatory Patch Tuesday release. Given that the Windows cursor problem is highly visible — literally affecting every action a user takes — it is a high-priority fix. The next scheduled Patch Tuesday for Windows 11 falls in September 2026, which gives Microsoft a tight but workable window. Until that update arrives, the manual workarounds above should keep most users productive.

Is Your Windows 11 Licence Still Valid After the Bug?

Absolutely. A buggy update does not affect your Windows activation status in any way. Your digital licence remains tied to your motherboard’s hardware signature and is entirely independent of cumulative updates. If you are, however, running an unactivated copy of Windows 11 or considering a fresh installation while this issue unfolds, now is a good time to ensure you have a legitimate licence in place. Browse our range of Windows 11 Pro licences — from €12.90 for an OEM key — or grab a Windows 11 Home licence starting at €9.35, both with lifetime activation and instant digital delivery.

How to Avoid Being Caught Out by Future Preview Updates

The KB5120998 situation is a reminder that optional preview updates exist for early testing — not production use. Here is how to protect yourself going forward:

  • Avoid optional updates unless you are specifically testing features. In Windows Update settings, toggle off “Get the latest updates as soon as they’re available”.
  • Create a restore point before every major update via Control Panel > System > System Protection > Create.
  • Export your Cursors registry key as described above so you can restore personalisation in seconds if a future update reverts it.
  • Monitor reputable Windows news sources after any update release before installing — a 48-hour wait often reveals major bugs like this one.
  • Check Microsoft’s Known Issues tracker on the Windows 11 release health dashboard before applying preview updates to production machines.

FAQ

What exactly does KB5120998 do to cause the mouse cursor bug?

KB5120998 contains a bug that reverts mouse cursor personalisation settings to system defaults after installation. This causes custom cursor schemes to reset, cursor tails to appear longer, and high-DPI cursors to display as oversized white pointers. The underlying pointer functionality is unaffected — only the appearance and personalisation settings are impacted.

Is the Windows 11 mouse cursor bug dangerous or a security risk?

No. The KB5120998 cursor issue is purely cosmetic and affects personalisation settings only. It does not expose your system to security vulnerabilities, corrupt files, or cause data loss. It is, however, genuinely disruptive to daily workflow, particularly for users who rely on custom high-contrast or accessibility-focused cursor schemes.

Do I have to uninstall KB5120998 to fix the cursor problem?

Not necessarily. Many users report success by manually re-applying their cursor scheme via Mouse Properties or Accessibility Settings after the update. Uninstalling the update is the most reliable fix if manual steps fail, but it is a last resort rather than the first step. Microsoft is expected to release a patched version in the next cumulative update.

Which Windows 11 versions are affected by the cursor bug?

Only Windows 11 24H2 (Build 26100.9278) and 25H2 (Build 26200.9278) are affected, because KB5120998 only targets those versions. Windows 11 22H2 and older builds, as well as Windows 10, are not impacted by this specific update. Check your build via Win + R > winver to confirm.

Will the cursor fix come automatically through Windows Update?

Yes — Microsoft is expected to include the cursor fix in the next mandatory Patch Tuesday update, targeted for September 2026. Once that update installs automatically, your cursor settings should be preserved correctly going forward. In the meantime, re-applying your cursor scheme manually or uninstalling KB5120998 are your best interim options.

RGB lighting Crashing Windows shown on a gaming keyboard and blue screen monitor
August 25, 2026

RGB Lighting Crashing Windows: Microsoft’s Official Fix Explained

Post By administrator Microsoft, Windows , , , , , No Comments

RGB lighting Crashing Windows are not a myth — Microsoft has officially confirmed that RGB peripheral software is triggering blue screens, game freezes, and unexpected restarts on Windows 11. If your PC has started acting up after a recent Windows update and you own a keyboard, mouse, or fan controller with RGB effects, there is a very good chance your lighting software is the culprit. Here is everything you need to know, including the exact steps to stabilise your system today.

Why RGB Software Is Crashing Windows 11

Diagram of RGB driver blue screen conflict inside Windows 11 kernel architecture

The root cause of the Windows 11 RGB crashes is a third-party kernel driver called inpoutx64.sys. This low-level driver is bundled with a wide range of RGB control applications — from Corsair iCUE to Razer Synapse to ASUS Armoury Crate — and it is used to give those apps direct hardware access for lighting control. Under normal conditions it works quietly in the background. However, a change introduced in the August 2026 Patch Tuesday update (build 26100.9168 and 26200.9168) exposed a kernel-level conflict that causes the driver to corrupt critical system structures, triggering CRITICAL_STRUCTURE_CORRUPTION blue screens and hard game crashes.

Microsoft acknowledged the issue publicly after a flood of user reports, confirming in a support advisory that drivers or components installed by RGB devices were interfering with core Windows components on affected systems. The problem is not with the RGB hardware itself — your Corsair keyboard and your ASUS motherboard LEDs are fine. It is the companion software sitting in the Windows kernel that is causing the instability.

Which Devices and Software Are Affected

Any application that ships with or installs the inpoutx64.sys driver can potentially trigger this issue. Known affected software includes:

  • Corsair iCUE

  • Razer Synapse

  • ASUS Armoury Crate / Aura Sync

  • MSI Dragon Center / MSI Center

  • NZXT CAM

  • Logitech G Hub

  • SteelSeries GG

  • HWiNFO (some versions)

  • Various fan controller and RGB strip utilities

You do not have to own a flagship gaming peripheral to be affected. Many mid-range motherboards include onboard RGB headers and ship with software that installs the same problematic driver without any obvious prompt during setup. If you have ever clicked “install companion software” during a motherboard or peripheral driver installation, there is a reasonable chance inpoutx64.sys is sitting on your system right now.

How to Check If You Have the Problematic Driver

Windows 11 Command Prompt showing RGB lighting Windows crashes driver check command

Before diving into fixes, confirm whether the driver is present on your PC. Open Command Prompt as Administrator and run the following command:

sc query inpoutx64

If you see a service listed with a status of RUNNING or STOPPED, the driver is installed. You can also navigate to C:\Windows\System32\drivers\ in File Explorer and search for inpoutx64.sys. Its presence confirms your system is exposed to the conflict.

Microsoft’s Official RGB Software Windows Fix

Microsoft has published a support article confirming the issue and providing two workaround steps while a permanent patch is developed. These are the official steps:

  1. Stop the service: Open Command Prompt as Administrator and run sc stop inpoutx64 followed by sc delete inpoutx64. This stops and removes the service entry.

  2. Delete the driver file: Navigate to C:\Windows\System32\drivers\ and delete inpoutx64.sys. You may need to take ownership of the file first if Windows reports it is in use.

  3. Wipe the registry entry: Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64, and delete the entire key. Back up your registry first using File → Export.

  4. Restart Windows: A full reboot applies the changes and removes the driver from memory.

After completing these steps, most users report that blue screens stop and games run without freezing. Your RGB hardware will still function — keyboards and mice work fine — but the companion lighting software will lose the ability to change colour profiles until the vendor ships an updated, compatible driver. For most people, stable gaming is worth the temporary trade-off.

RGB Driver Blue Screen: The Longer-Term Solution

Removing inpoutx64.sys is a workaround, not a permanent fix. The lasting solution depends on two parties acting in parallel. Microsoft needs to ship a further Windows update that either restores compatibility for the driver or introduces tighter kernel signing controls that prevent the conflict recurring. Separately, peripheral manufacturers need to release updated versions of their RGB control software that do not rely on inpoutx64.sys for hardware access, or that ship a version of the driver that is compatible with the current kernel build.

Based on community reports across Reddit and dedicated hardware forums, several vendors including Corsair and ASUS were already working on updated software packages within days of Microsoft’s public acknowledgement. Check your RGB software’s update channel regularly — when a patched version arrives, you can reinstall it safely and your lighting profiles will come back to life. Until then, the manual removal steps above remain the most reliable path to a stable system.

Should You Roll Back the Windows Update?

Five tips to prevent Windows 11 RGB software crashes and blue screen errors

Rolling back the August 2026 Patch Tuesday update is technically possible within 10 days of installation via Settings → Windows Update → Update History → Uninstall Updates. However, this approach is not recommended as a long-term strategy. The August 2026 update patched over 80 security vulnerabilities, including several rated Critical by Microsoft’s own severity scale. Running an unpatched Windows 11 build to preserve RGB lighting is not a sensible trade-off — especially on a gaming PC that connects to online services. The inpoutx64.sys removal method lets you keep your security patches and your stable system simultaneously.

Windows 11 RGB Crashes: Keeping Your System Stable Going Forward

This incident highlights a broader tension in the Windows ecosystem: third-party software that operates at the kernel level can destabilise the entire OS when a system update shifts the rules. RGB control utilities, overclocking tools, and fan-management apps all tend to use low-level drivers for performance reasons, and every major Windows update carries a small risk of breaking one of them. A few habits can significantly reduce your exposure:

  • Delay non-critical updates by 7 days using the Windows Update pause option — by then, widespread issues like this one are usually flagged publicly.

  • Keep RGB and hardware-control software updated independently — vendor patches often arrive within days of a major Windows build drop.

  • Check the Windows Health Dashboard before applying a cumulative update — Microsoft documents known conflicts there before they appear in mainstream media.

  • Create a System Restore point before every major update so you have a clean rollback option without losing personal files.

  • Audit your installed drivers periodically using driverquery /fo list | more in Command Prompt — you may be surprised how many third-party kernel drivers are running on your machine.

For a broader look at squeezing performance and stability out of Windows, our guide on Windows performance tuning with hidden built-in tools covers the native utilities that most users overlook.

Do You Actually Need a Fresh Windows 11 Licence?

If this RGB lighting crash saga has you questioning whether your current Windows installation is properly activated — or if you are building a new gaming rig and want a clean, activated copy of Windows 11 before installing any peripheral software — Buy Now Key offers genuine Windows 11 Pro licences from €17.90, with lifetime activation on a single device and instant digital delivery. Starting with a properly licensed, clean install eliminates a whole category of activation-related instability before you even plug in your first RGB peripheral.

According to BleepingComputer’s coverage of Microsoft’s official statement, the company confirmed the gaming issues are caused specifically by drivers or components installed by RGB devices — not by Windows itself. That distinction matters: your Windows licence and core OS files are not corrupted. The fix is targeted and reversible.

FAQ

Will removing inpoutx64.sys break my RGB hardware permanently?

No. Your RGB hardware — keyboards, mice, fans, and motherboard headers — will continue to function normally for basic input and lighting after the driver is removed. What you lose temporarily is software-controlled lighting customisation: colour profiles, reactive effects, and sync across devices. Once your peripheral manufacturer ships an updated version of their RGB control software that is compatible with the current Windows kernel, you can reinstall it and your profiles will return.

How do I know if the RGB driver blue screen is causing my specific crashes?

The most reliable indicator is the stop code. If your blue screens display CRITICAL_STRUCTURE_CORRUPTION or if Windows Event Viewer logs show inpoutx64.sys as the faulting module, the RGB driver is almost certainly the cause. You can check Event Viewer under Windows Logs → System and look for Critical or Error events timestamped at the moment of each crash. If inpoutx64 appears in the log, the removal steps in this article will resolve the issue.

Is this problem limited to Windows 11, or does it affect Windows 10 too?

Microsoft’s official advisory specifically references Windows 11 builds 26100.9168 and 26200.9168, which correspond to the August 2026 Patch Tuesday cumulative updates. Windows 10 users are not currently cited as affected by this specific kernel conflict, though Windows 10 does share some driver infrastructure with Windows 11. If you are on Windows 10 and experiencing similar symptoms, the same inpoutx64.sys check and removal process applies as a diagnostic step.

Do I need to uninstall my RGB software entirely, or just delete the driver file?

You do not need to fully uninstall your RGB application. Deleting inpoutx64.sys and removing its registry entry is sufficient to resolve the crash. The RGB app itself can remain installed — it just will not be able to communicate with hardware at the kernel level until a compatible driver is available. Some users prefer a full uninstall for a cleaner result, but partial removal (driver file and registry key only) is the minimal fix and is fully reversible.

Will Windows automatically reinstall inpoutx64.sys after the next update?

Windows itself will not reinstall the driver — it belongs to third-party software, not to the OS. However, if you update or reinstall your RGB control application (Corsair iCUE, Razer Synapse, etc.) before the vendor has shipped a patched version, the installer will drop a new copy of inpoutx64.sys back onto your system. Always check that your RGB software update notes explicitly mention Windows 11 August 2026 compatibility before reinstalling.

Windows 11 August 2026 build showing redesigned AutoPlay and File Explorer menus
August 23, 2026

Windows 11 August 2026 Build: What’s New and Should You Update?

Post By administrator Microsoft, Windows , , , , , , No Comments

The Windows 11 August 2026 build is officially out, and it brings a more polished OS experience with a redesigned AutoPlay dialog, a customisable File Explorer context menu, and a wave of stability improvements. Whether you’re a daily driver user or an IT professional managing multiple machines, knowing what’s in this release — and whether to install it immediately — matters. Here’s everything you need to know.

What’s Actually in the Windows 11 August 2026 Build?

Infographic of six new features in the Windows 11 August 2026 build update

Microsoft announced the new Windows 11 builds on 21 August 2026 through its Windows Insider Blog, covering the Experimental (26H2) channel. The headline addition is Build 26340.9233 (KB5124042), which bundles several highly anticipated UI and usability changes alongside the usual security hardening.

  • Modernised AutoPlay Dialog: The AutoPlay experience has been completely rebuilt using WinUI. The refreshed panel now supports dark mode natively, aligns visually with the rest of Windows 11’s design language, and loads faster than its predecessor.
  • Customisable File Explorer Context Menu: A new “Customise menu” entry appears at the bottom of File Explorer’s context menu. Clicking it opens a dedicated Settings page where you can pin, hide, or reorder items — giving power users real control over their workflow.
  • Per-App Privacy Controls for Win32 Apps: Microsoft is extending the privacy dashboard to cover legacy Win32 applications, letting you manage microphone, camera, and location access on a per-app basis — something previously limited to UWP (Universal Windows Platform) apps.
  • Open Apps Maximised by Default: A small but quality-of-life improvement — users can now set individual apps to open in a maximised window state by default, reducing the click-and-drag routine on large monitors.
  • File Explorer Preview Enhancements: The preview pane in File Explorer now supports a wider range of file types and renders thumbnails with noticeably sharper clarity on high-DPI displays.
  • Modern File Properties Panel: The legacy file properties dialog (unchanged since Windows XP in many respects) is getting a WinUI facelift, with cleaner typography and better touch-screen usability.

These features are currently in the Experimental channel, which means they are feature-flagged — not every machine will see all of them immediately after install.

The August 11 Security Update: KB5121003 and KB5121000

Separate from the Insider builds, Microsoft’s Patch Tuesday for August 2026 (11 August) delivered two critical cumulative updates. KB5121003 covers OS Builds 26200.9168 and 26100.9168, targeting Windows 11 versions 24H2 and 25H2 respectively. KB5121000 targets the newer 26H1 release (OS Build 28000.2704), which ships exclusively on new devices with select silicon.

Key security fixes in KB5121003 include patches for Windows Secure Boot certificate expiration issues — a critical area given that Secure Boot underpins the hardware security requirements that make Windows 11 significantly more resilient than Windows 10. Microsoft’s own Windows 11 release information page on Microsoft Learn confirms the full build-to-KB mapping and general availability channel dates for all active versions.

Windows 11 New Build: Stability and Performance Improvements

Flowchart helping users decide whether to install the Windows 11 new build

Beyond features, the Windows 11 new build addresses a number of persistent reliability complaints. Users on the Windows 11 subreddit had flagged issues with Windows Insider flight certificates expiring on 11 August 2026 — Microsoft responded quickly with the 17 August builds specifically renewing those certificates, ensuring Insiders weren’t locked out of future updates. The 21 August release builds directly on that remediation.

Additional stability improvements reported across the August 2026 cycle include:

  • Reduced memory footprint for File Explorer sessions with many tabs open simultaneously
  • Fixes for intermittent freezes when connecting or disconnecting external monitors on multi-display setups
  • Improved Wi-Fi reconnection reliability after sleep/hibernate cycles
  • Resolved audio driver conflicts affecting certain Realtek and Conexant chipsets

Should You Install the August 2026 Windows Update Right Now?

The answer depends on which channel you’re on. Here’s a straightforward breakdown:

  • Stable (General Availability) channel — Yes, update now. KB5121003 and KB5121000 are security-critical patches. Leaving known vulnerabilities unpatched — especially the Secure Boot certificate fixes — creates real risk. The stable release has been tested extensively and the risk of regression is low.
  • Windows Insider Experimental (26H2) — Proceed with awareness. The 21 August build adds compelling features, but Experimental channel builds are pre-release. If you rely on your machine for daily work, wait for the Beta or Release Preview channel to receive these changes before installing on a production device.
  • Not yet on Windows 11 — Now is a great time to consider it. With Windows 10 end-of-life support ending in October 2025, remaining on an unsupported OS is a genuine security liability. The August 2026 build demonstrates that Windows 11 is maturing fast, and the upgrade path has never been smoother.

August 2026 Windows Update: What It Means for Version 26H1

Windows 11 August 2026 Windows update channels 24H2 25H2 and 26H1 compared

Windows 11 version 26H1 is a notable shift in Microsoft’s release strategy. Unlike the annual feature updates (24H2, 25H2) that rolled out to all devices, 26H1 is scoped exclusively to new devices shipping with select next-generation silicon in early 2026. If you’re on an existing machine, you won’t receive 26H1 via Windows Update — you’ll stay on the 24H2 or 25H2 servicing path, which remains fully supported and receives the same security patches.

This means the August 2026 Windows update has two very distinct audiences. Owners of new Copilot+ PCs get the 26H1 cumulative update (KB5121000) with its additional hardware-accelerated AI features. Everyone else gets KB5121003, which is still a substantial security update covering over a dozen CVEs.

How to Get Your Windows 11 License Before Updating

If you’re still running Windows 10 — or your current Windows 11 install isn’t properly activated — now is the ideal moment to sort your licence before applying updates. An unactivated Windows install limits personalisation options, can interfere with certain update flows, and leaves your security dashboard incomplete.

At Buy Now Key, you can grab a genuine Microsoft Windows 11 Pro licence from just €17.90 — a one-time purchase with lifetime activation on a single device. For home users who don’t need the advanced business features of Pro, a Windows 11 Home licence is available at an even lower price point. Both come with global language support and instant digital delivery, so you’re up and running in minutes.

Frequently Asked Questions

What is the Windows 11 August 2026 build number?

The main Insider Experimental build released on 21 August 2026 is Build 26340.9233, associated with KB5124042 for the 26H2 channel. The stable Patch Tuesday builds from 11 August are OS Build 26200.9168 / 26100.9168 (KB5121003) for 24H2/25H2, and OS Build 28000.2704 (KB5121000) for 26H1 on new devices.

Is the Windows 11 August 2026 update safe to install?

Yes, for the stable General Availability channel updates (KB5121003 and KB5121000). These have been through full QA cycles. The Experimental Insider builds (including the 21 August release) carry a higher risk of bugs and are best reserved for test machines or enthusiasts comfortable with pre-release software.

Will the new AutoPlay dialog come to all Windows 11 users?

The redesigned AutoPlay dialog is currently feature-flagged in the Experimental channel. Microsoft typically promotes well-tested features from Experimental to Beta to Release Preview to Stable over several months. Expect it to reach stable users in a future 26H2 release or a later cumulative update, assuming testing goes smoothly.

Do I need a new PC to get Windows 11 version 26H1?

Yes. Windows 11 26H1 is exclusively for new devices shipping with select next-generation silicon (announced in early 2026). If you own an existing PC — even one fully capable of running Windows 11 24H2 or 25H2 — you will not receive 26H1 through Windows Update. You’ll continue on the 24H2/25H2 servicing branch, which remains fully supported.

How do I check which Windows 11 build I’m running?

Press Win + R, type winver, and press Enter. The dialog that appears shows your exact OS build number and version (e.g., Version 24H2, Build 26100.9168). Cross-reference this with Microsoft’s Windows 11 release information page to confirm you’re on the latest available update for your channel.

Windows 11 gaming crashes caused by KB5121003 cumulative update August 2026
August 22, 2026

Windows 11 Gaming Crashes: KB5121003 Fixes and Workarounds

Post By administrator Microsoft, Windows , , , , , No Comments

Windows 11 gaming crashes are hitting millions of players in August 2026, and the culprit is a single cumulative update: KB5121003. Released on 12 August 2026 as part of Microsoft’s monthly Patch Tuesday cycle, this security update patches over 400 vulnerabilities — but it has introduced severe stability problems that are making games unplayable. Here is everything you need to know, and the fastest ways to get back in the game.

What Is KB5121003 and Why Does It Cause Game Crashes?

Diagram showing KB5121003 update conflict causing Windows 11 gaming crashes

KB5121003 is the August 2026 cumulative security update for Windows 11 versions 24H2 and 25H2 (OS Builds 26100.9168 and 26200.9168). It is one of the largest Patch Tuesday releases in recent memory, fixing over 400 documented security issues across the operating system. Unfortunately, the update also appears to have introduced a conflict with a low-level hardware input driver called inpoutx64.sys.

This driver is used by a wide range of PC games and third-party peripherals to handle hardware I/O at a kernel level. When KB5121003 modifies how Windows handles this driver, games either crash to desktop immediately on launch, freeze mid-session, or cause graphical corruption across both dedicated GPUs (dGPU) and integrated graphics (iGPU). Users on Reddit and Microsoft’s own support forums have reported crashes in titles including Valorant, Roblox, and a broad selection of other games spanning multiple genres and launchers.

Microsoft has officially acknowledged the issue on its support page for KB5121003, confirming it has received reports of games failing to run as expected following installation and that an investigation is ongoing.

Which Games Are Affected by Windows 11 Update Crashes?

The Windows 11 update crashes triggered by KB5121003 appear to affect games that rely on the inpoutx64.sys driver for input handling. Reported affected titles include, but are not limited to:

  • Valorant (and other anti-cheat–protected titles)
  • Roblox
  • Titles using older DirectInput or raw hardware I/O frameworks
  • Games with third-party overlay software that hooks into kernel drivers

Graphical corruption has been reported even on systems where the game launches successfully, with rendering artefacts appearing across both dGPU and iGPU configurations. Some players are also experiencing random forced system reboots while gaming — a secondary bug linked to the same update cycle.

Additionally, unrelated problems introduced by KB5121003 include PIN login failures and display driver errors, suggesting the update’s impact extends well beyond gaming.

KB5121003 Fix: Step-by-Step Workarounds Right Now

Step-by-step guide to fixing Windows 11 game crashes by uninstalling KB5121003

While Microsoft works on a dedicated patch, there are two main approaches to resolving the game crashes Windows 11 players are experiencing. Choose the one that best matches your situation.

Option 1: Delete the inpoutx64.sys Driver

The most targeted workaround — recommended for users who want to keep the security patches in KB5121003 — is to remove the problematic driver file without rolling back the entire update.

  1. Open Command Prompt as Administrator (right-click the Start button → Terminal (Admin)).
  2. Type the following command and press Enter: del /f /q C:\Windows\System32\drivers\inpoutx64.sys
  3. Restart your PC.
  4. Try launching your game again.

This approach removes the conflicting driver but leaves the 400+ security fixes from KB5121003 in place, which is the preferable outcome from a security standpoint.

Option 2: Uninstall KB5121003 Entirely

If deleting the driver does not resolve your game crashes Windows 11 issue, or if you are experiencing additional problems such as PIN login failures, you can uninstall the update completely. Be aware that this also removes all the security patches it delivered.

  1. Go to Start → Settings → Windows Update → Update history.
  2. Scroll down and click Uninstall updates.
  3. Find KB5121003 in the list and select Uninstall.
  4. Restart your PC when prompted.

To prevent Windows from automatically reinstalling the update before a fix is ready, you can pause updates temporarily: Settings → Windows Update → Pause updates, then choose a pause period of up to five weeks. Nvidia has also suggested this uninstall route as a temporary measure for affected users.

Option 3: Wait for Microsoft’s Official Fix

Microsoft has confirmed it is investigating the KB5121003 gaming crash issue. A fix is expected to arrive either as an out-of-band (OOB) patch or as part of the September 2026 Patch Tuesday update. If your games are mostly stable and only occasionally crashing, it may be worth simply waiting — especially if you work in a regulated environment where patching is mandatory.

KB5121003 Fix Progress: What Microsoft Has Said

According to BleepingComputer’s coverage of the issue, Microsoft has flagged the gaming problem in its Windows Health Dashboard and is actively investigating. The company has not yet released a timeline for a permanent fix, but the scale of reports — spanning gaming forums, Microsoft Answers, and mainstream tech press — suggests a rapid response is likely. Users with Sophos endpoint security software may already find the issue is resolved, as Sophos pushed a targeted remediation shortly after the problem was identified.

How to Check If KB5121003 Is Installed on Your PC

Security versus gaming stability trade-off in Windows 11 KB5121003 update fix

Not every Windows 11 machine will have received KB5121003 yet, depending on your update settings. Here is how to check:

  • Go to Settings → Windows Update → Update history.
  • Look for KB5121003 in the list of quality updates.
  • If it appears with a status of “Successfully installed”, your system has the update and could be affected.

If you have not installed the update yet and are primarily a gaming PC user, you may want to pause updates and wait for Microsoft’s corrective patch before proceeding.

Should You Sacrifice Security to Fix Game Crashes on Windows 11?

This is the core dilemma. KB5121003 addresses over 400 security vulnerabilities, making it one of the most significant Patch Tuesday releases of 2026. Uninstalling it leaves your system exposed to those vulnerabilities. For a home gaming rig that is behind a router and not storing sensitive data, the practical risk of uninstalling temporarily is relatively low — but it is not zero.

For best results, try the inpoutx64.sys driver deletion (Option 1) first, since it preserves the security patches while targeting the specific conflict causing the Windows 11 gaming crashes. Only escalate to a full uninstall if Option 1 does not resolve the problem.

Upgrade to a Stable Windows 11 Licence While You Wait

If you are still running Windows 11 Home on a gaming rig, this incident is a good reminder that Windows 11 Pro gives you more granular control over update scheduling — including the ability to defer feature and quality updates independently, giving you more breathing room when a problem patch lands. Whether you need Windows 11 Home or Pro, Buy Now Key stocks genuine licences at competitive prices, with instant digital delivery and lifetime activation.

You can explore our full range of Windows 11 licences — including Windows 11 Pro starting from €12.90 — so your next clean install or upgrade is covered the moment Microsoft ships a stable build.

Frequently Asked Questions

Which Windows 11 update is causing game crashes in August 2026?

The update responsible for widespread Windows 11 gaming crashes is KB5121003, released on 12 August 2026 as part of Patch Tuesday. It targets Windows 11 versions 24H2 and 25H2 and is confirmed by Microsoft to be causing game launch failures and mid-session crashes.

What is inpoutx64.sys and why is it involved?

inpoutx64.sys is a low-level Windows kernel driver used by many games and peripherals for direct hardware I/O access. KB5121003 appears to conflict with how this driver operates, causing games that depend on it to crash or produce graphical corruption. Deleting the driver file via Command Prompt is the fastest targeted fix available right now.

Will uninstalling KB5121003 fix my game crashes on Windows 11?

In most cases, yes — uninstalling KB5121003 resolves the game crashes Windows 11 users are experiencing. However, it also removes over 400 security patches. Try deleting the inpoutx64.sys driver first, as that fix targets only the conflict while keeping your security patches intact.

When will Microsoft release an official KB5121003 fix?

Microsoft has acknowledged the issue and an investigation is ongoing. An out-of-band patch or a fix included in the September 2026 Patch Tuesday update is the most likely timeline. Monitoring the Windows Health Dashboard or the KB5121003 support page will give you the earliest notification when a fix ships.

How do I stop Windows 11 from reinstalling the broken update?

After uninstalling KB5121003, go to Settings → Windows Update → Pause updates and set a pause of up to five weeks. This prevents Windows from automatically re-downloading and reinstalling the update before an official fix is available.

Are all Windows 11 gaming crashes caused by KB5121003?

Not necessarily. KB5121003 is the confirmed culprit for the August 2026 crash wave, but game crashes on Windows 11 can also stem from outdated GPU drivers, overheating, faulty RAM, or software conflicts. If the KB5121003 workarounds do not resolve your issue, check your GPU driver version and run a memory diagnostic as additional troubleshooting steps.

Windows 11 weather app memory usage shown in Task Manager at 1.2GB
August 18, 2026

Windows 11 Weather App Memory: Why It Eats 1.2GB and How to Fix It

Post By administrator Microsoft, Windows , , , , , No Comments

Windows 11 weather app memory usage has crossed an embarrassing milestone: Microsoft’s built-in Weather app now consumes more than 1.2 gigabytes of RAM just to display a five-day forecast. That’s not a typo, and it’s not a virus — it’s an architectural choice baked into the app itself. If your PC has ever felt sluggish after glancing at tomorrow’s rain chances, you’ve found the culprit. In this guide we’ll break down exactly why the weather app memory footprint is so outrageous, and walk you through every practical fix available right now.

What Is the Windows 11 Weather App, Really?

Diagram explaining how weather app RAM usage stems from WebView2 wrapper

Most people assume that a built-in Windows app is a lean, native application compiled specifically for Windows. The Weather app is not that. Under the hood, it is a WebView2 wrapper — essentially a stripped-down instance of Microsoft Edge’s Chromium engine loading the MSN Weather website inside a frame that looks like a desktop app. When you open Weather, Windows isn’t running a tightly optimised piece of software; it’s spinning up a near-full browser, loading a commercial web page packed with display advertising, data trackers, and JavaScript widgets, then presenting the whole thing inside a thin app shell.

This design pattern — wrapping a website in a native-looking container — has a name in the developer community: a web wrapper or Electron-style app. The difference here is that Microsoft is the OS vendor shipping it as a default system app, which raises expectations significantly. An independent developer shipping a bloated app is an inconvenience. The company that makes the operating system shipping one is a policy decision that affects hundreds of millions of machines.

Why Windows 11 Weather RAM Usage Is So High

The Windows 11 weather RAM problem stems from three compounding factors working together:

  • Chromium’s multi-process architecture: WebView2 inherits Chromium’s process model. Open Task Manager and you’ll typically see eight to nine separate Microsoft Edge WebView2 Runtime processes spawned by a single Weather app session. Each process carries its own memory overhead.
  • Advertising payload: The MSN Weather page loaded inside the wrapper is a commercial page with banner ads, sponsored content tiles, and third-party ad-tech scripts. Each ad unit triggers additional resource fetches, JavaScript execution, and GPU compositing — all of which translate directly into RAM.
  • No memory ceiling: A native Windows application typically declares its resource requirements. A Chromium-based wrapper does not. The WebView2 runtime will allocate as much RAM as the page demands, and a heavily monetised weather page demands a lot.

Independent testing reported by Tom’s Hardware confirmed peak usage reaching 1.2GB to 1.6GB, with nine separate WebView2 processes visible in Task Manager. For context, the equivalent macOS Weather app — a genuine native application — uses around 200MB. The Windows version consumes roughly five times as much for the same data.

Windows Weather Memory Fix: Step-by-Step Solutions

Windows 11 Settings screen showing how to disable weather app memory background

The good news is that you don’t have to live with this. These fixes range from a two-minute tweak to a full replacement strategy — pick what suits your comfort level.

1. Disable Background App Activity

The Weather app can run in the background even when you’re not using it, silently consuming RAM to keep forecasts up to date in the Widgets panel. Stopping this reclaims memory without losing access to the app when you actually need it.

  • Open Settings → Apps → Installed apps.
  • Search for Weather and click the three-dot menu → Advanced options.
  • Under Background apps permissions, set to Never.
  • Also toggle off Let this app run in the background if the option is present.

This alone can recover several hundred megabytes on machines that had Weather set to refresh continuously.

2. Remove the Weather Widget from the Taskbar

The Widgets button on the Windows 11 taskbar is a persistent background service that pre-loads personalised content — including Weather — whether you’ve opened the full app or not. Removing it cuts one of the main triggers for background Weather activity.

  • Right-click the taskbar → Taskbar settings.
  • Toggle Widgets off.

On some machines this step alone reduces overall system RAM usage by 200MB–400MB because the entire Widgets host process shuts down.

3. Uninstall the Weather App Entirely

Windows 11 lets you uninstall most built-in apps directly from the Start menu. Right-click the Weather tile → Uninstall. If you want to be thorough, open Windows PowerShell (Admin) and run:

Get-AppxPackage *BingWeather* | Remove-AppxPackage

This removes the app for the current user. The command is reversible — the app can be reinstalled from the Microsoft Store at any time.

4. Switch to a Lightweight Weather Alternative

Uninstalling the built-in app doesn’t mean going without weather data. These alternatives provide accurate forecasts for a fraction of the RAM cost:

  • weather.com or weather.gov in your browser: Pin a tab in your existing browser session. Since your browser is already open, there’s zero extra RAM overhead for a second Chromium instance.
  • WinWeather (Microsoft Store): A community-built lightweight weather app using native WinUI controls rather than a web wrapper.
  • Taskbar clock weather integration: Third-party tools like ElevenClock can display current conditions directly in the system clock tooltip — no separate app needed at all.
  • Search widget search: Typing a city name followed by “weather” in the Windows Search bar pulls a real-time weather card without opening any app.

5. Audit and Manage All WebView2 Processes

The Weather app isn’t the only Windows 11 application built on WebView2. The Teams, Widgets, and some Office features use the same runtime. Open Task Manager → Details tab, then sort by Memory (private working set). Any process named msedgewebview2.exe belongs to this family. Identifying and closing the parent app immediately terminates all its child WebView2 processes and returns that RAM to the pool.

For a broader look at what else might be slowing your machine down, the guide on Windows performance tuning with built-in tools covers several overlooked optimisation methods that cost nothing and take less than 30 minutes.

Should Microsoft Fix This?

The straightforward answer is yes — and the path forward already exists. Windows 11 ships with WinUI 3, a modern native UI framework that Microsoft itself uses for apps like the Settings panel and the revamped File Explorer. Building Weather as a proper WinUI 3 application would eliminate the need for a full Chromium runtime, slash memory usage by 80% or more, and still allow live data from MSN’s weather APIs. The advertising component could be retained via native ad SDKs rather than a full browser rendering engine.

Until that happens, the weather app RAM usage problem is a user-side configuration issue. Microsoft has acknowledged bloat concerns in general but has not committed to a native Weather rewrite on any public roadmap as of mid-2026.

The Bigger Picture: Web Wrappers in Windows 11

Bar chart comparing Windows 11 weather app RAM to macOS weather app usage

The Weather app is the most visible example of a broader trend. Several Windows 11 inbox apps — including the Widgets panel, parts of the Teams Chat integration that shipped in earlier builds, and certain Office companion features — rely on WebView2 rather than native code. Each one spins up its own Chromium renderer, and they don’t always share process resources efficiently.

For users on 8GB machines, this matters enormously. Microsoft’s own minimum RAM requirement for Windows 11 is just 4GB. A single Weather app session consuming 1.2GB represents 30% of the entire minimum-spec RAM budget for one background app delivering weather data you probably also have on your phone. On a 16GB machine the impact is more manageable but still measurable — particularly on devices running multiple productivity applications simultaneously.

If your Windows 11 licence is due for renewal or you’re setting up a new machine, it’s worth knowing that a properly activated, genuine Windows 11 licence starts the OS on the right foot. Buy Now Key offers Windows 11 licences starting from €9.65, covering both Home and Pro editions with instant delivery and lifetime activation.

Quick-Reference: Windows Weather Memory Fix Summary

  • Disable background permissions — Settings → Apps → Weather → Advanced options → Background: Never
  • Turn off Widgets — Taskbar settings → Widgets: Off (saves 200–400MB)
  • Uninstall via Start or PowerShell — Eliminates the issue entirely; reinstallable anytime
  • Use browser tab instead — Zero extra RAM if browser is already open
  • Audit msedgewebview2.exe in Task Manager — Identify all WebView2-based apps consuming memory

Frequently Asked Questions

Is the Windows 11 Weather app a virus or malware?

No. The high memory usage is a legitimate architectural issue, not malware. The Weather app is signed by Microsoft and ships as part of the Windows 11 default installation. Its RAM consumption is a design consequence of using a Chromium-based WebView2 wrapper rather than native code, not a sign of compromise. Running a full malware scan will confirm nothing malicious is present.

Will disabling the Weather app break anything else in Windows 11?

Uninstalling the Weather app removes it from the Start menu and the Widgets panel, but it does not affect Windows Update, system stability, or any other built-in feature. The Widgets panel itself will still function — it simply won’t show a weather card if Weather is uninstalled. You can reinstall the app from the Microsoft Store at any point with no loss of data.

How do I check current weather app RAM usage on my PC?

Press Ctrl + Shift + Esc to open Task Manager, then click the Processes tab and look for Weather or Microsoft Edge WebView2 Runtime. Sort by Memory to see the full picture. You may see multiple WebView2 entries — these are all child processes of the Weather app and should be counted together for an accurate total.

Does the Windows 11 weather app RAM usage get worse over time in a session?

Yes, typically. When the app first opens it loads the initial page, but as you interact — switching forecasts, clicking maps, scrolling through news articles embedded below the weather data — the WebView2 runtime loads additional page resources and caches them in memory. Usage can climb from 1.2GB to 1.6GB or higher in a longer session without the app releasing memory until it is closed.

What’s the best lightweight weather app for Windows 11?

The lowest-RAM option is to use a pinned browser tab pointing to a weather website like weather.gov, since your browser session is already open and no additional Chromium instance is needed. If you prefer a standalone app, community-built native WinUI alternatives from the Microsoft Store typically consume under 150MB. The Windows Search bar also provides real-time weather cards without opening any separate app at all.

VLC performance Windows 11 affected by Microsoft Defender plugin bug
August 16, 2026

Why VLC Performance on Windows 11 Is Slow — and What to Do Now

Post By administrator Microsoft, Windows , , , , , No Comments

VLC performance on Windows 11 has taken a serious hit — and for once, it genuinely isn’t VLC’s fault. A bug tied to Microsoft Defender is causing startup delays of up to 33 seconds on millions of PCs, and Microsoft has yet to ship a permanent patch. If your video playback feels sluggish, stuttery, or VLC takes an age to open an MP3, you’re not alone, and there are things you can do right now.

What Is Actually Causing the VLC Playback Issue on Windows 11?

Microsoft Defender scanning VLC plugin cache causing Windows 11 playback delays

The core problem is Microsoft Defender scanning VLC’s plugin cache file on every launch. When Defender flags or quarantines part of that cache — even as a false positive — VLC is forced to rebuild it from scratch before it can play anything. That rebuild process is the source of the infamous 33-second delay that users have been reporting since mid-2026.

VideoLAN, the non-profit behind VLC, confirmed the issue publicly via its official X (formerly Twitter) account, explicitly naming a recent Microsoft Defender update as the trigger. The Windows Latest report from August 14, 2026 adds crucial nuance: VLC’s own bug tracker reveals the situation is messier than a single Defender update, with multiple overlapping reports pointing to plugin cache corruption, Defender quarantine events, and slower I/O performance under Windows 11’s memory management in certain hardware configurations.

The 33-Second Delay: Why Does VLC Stutter So Badly?

When the plugin cache is missing or corrupted — whether because Defender nuked it or for another reason — VLC 3.0.23 and later versions can take anywhere from 5 to 33 seconds just to open an MP3 file. On HDDs the wait is worst; SSD users see shorter delays, but still noticeable pauses compared to what VLC used to deliver. The delay occurs at startup, not during playback itself, which is why it catches users off-guard: the app appears to have frozen before the UI even loads.

This is a VLC slow Windows 11 issue that disproportionately affects users who updated Windows Defender definitions in July or August 2026. On systems where Defender scanned and quarantined the plugins.dat cache file, VLC effectively has to reindex every installed codec module before it can function — a process the player was never designed to run every single session.

Why Hasn’t Microsoft Fixed This VLC Windows 11 Problem?

Windows 11 Defender exclusions settings to improve VLC performance fix

Microsoft’s position — or rather its conspicuous silence — is frustrating. Defender definition updates are pushed continuously and silently; there is no formal patch cycle for false positives the way there is for kernel vulnerabilities. The Defender team can quietly adjust a definition to stop flagging VLC’s cache, but users have no visibility into when or whether that happens.

VideoLAN’s developers have pointed out that this dynamic unfairly burdens open-source projects. A commercial vendor can open a direct support channel with Microsoft; a volunteer-driven open-source team has to rely on public bug reports and social-media callouts to get traction. It is a systemic problem that goes well beyond any single VLC playback issue.

Is This a VLC Bug or a Windows 11 Bug?

Honestly, both organisations carry some responsibility — but the weight falls on Microsoft’s side. VLC’s plugin cache architecture is long-standing and functional on every other platform. The behaviour that breaks it — Defender silently modifying or quarantining files inside an installed application’s directory — is a Windows 11 behaviour Microsoft controls entirely. VLC cannot defend against a security tool that has elevated kernel-level access to its own files.

That said, VideoLAN’s bug tracker shows VLC playback issues that predate the Defender incident, including performance regressions tied to Windows 11’s hardware-accelerated GPU scheduling (HAGS) on certain Nvidia and AMD GPU configurations. The Defender story is the most dramatic, but VLC slow Windows 11 complaints are rooted in more than one cause.

How to Fix VLC Performance on Windows 11 Right Now

Five-step VLC Windows 11 fix checklist for slow video playback issues

You don’t have to wait for Microsoft or VideoLAN to release a patch. The following steps resolve the majority of reported VLC playback issues on Windows 11 immediately.

1. Reinstall VLC or Regenerate the Plugin Cache

The fastest VLC Windows 11 fix is to force a clean plugin cache regeneration. You can do this in two ways:

  • Full reinstall: Uninstall VLC via Settings → Apps → Installed Apps, delete any leftover files in %APPDATA%\vlc, then download and reinstall the latest version from VideoLAN’s official site.

  • Manual cache reset: Navigate to C:\Program Files\VideoLAN\VLC\, delete plugins\plugins.dat, then launch VLC — it will rebuild the cache fresh on startup.

2. Add VLC to Microsoft Defender’s Exclusion List

This stops Defender from scanning and potentially corrupting VLC’s plugin cache in future:

  1. Open Windows Security → Virus & Threat Protection → Manage Settings.

  2. Scroll to Exclusions and click Add or remove exclusions.

  3. Add the full VLC installation folder: C:\Program Files\VideoLAN\VLC\.

  4. Restart VLC and test playback.

Note: Only exclude the VLC folder — do not add blanket exclusions to your entire Program Files directory.

3. Disable Hardware-Accelerated GPU Scheduling (if stuttering persists)

If you’re seeing VLC playback issues during video (not just on startup), HAGS may be the culprit:

  • Go to Settings → System → Display → Graphics → Change default graphics settings.

  • Toggle Hardware-accelerated GPU scheduling off.

  • Restart your PC and retest VLC performance on Windows 11.

4. Switch VLC’s Video Output to DirectDraw or OpenGL

Inside VLC, go to Tools → Preferences → Video and change the Output dropdown from Auto to DirectDraw (older hardware) or OpenGL (modern GPUs). This sidesteps certain Windows 11 compositor conflicts that throttle VLC playback on multi-monitor setups.

5. Increase VLC’s File Cache Value

In Tools → Preferences → Show All → Input / Codecs, find File caching (ms) and raise it from the default 300 ms to 1500 ms. This gives VLC more buffer headroom and reduces mid-playback stalls on systems where Defender or Windows 11’s I/O scheduler causes latency spikes.

Should You Upgrade or Reinstall Windows 11?

A clean Windows 11 install can help if you’re seeing system-wide performance degradation beyond VLC, but it is overkill for this specific VLC playback issue. The Defender exclusion and cache regeneration steps above resolve the 33-second startup delay without touching your OS installation. If you’re running a heavily updated Windows 11 build and performance is suffering across the board, that’s a broader conversation — but don’t wipe your drive just because VLC is slow.

What does make sense is ensuring your Windows 11 licence is legitimate and fully activated, since OEM or unactivated copies can exhibit unusual background service behaviour that compounds performance problems. At Buy Now Key, you can grab a genuine Windows 11 Pro licence from €17.90 or a Windows 11 Home OEM key from just €9.65 — both with lifetime activation. If you’re also struggling with broader Windows slowdowns beyond VLC, our guide to Windows performance tuning with built-in tools is a great next step.

What VLC Users Should Watch for Next

VideoLAN has stated it is working with community contributors to make VLC’s plugin cache more resilient against external interference — essentially, making the cache harder for third-party security tools to accidentally corrupt. Microsoft has not formally acknowledged a specific Defender definition error, though anecdotal reports suggest the most aggressive flagging behaviour has eased slightly in the most recent Defender updates pushed in August 2026.

In the meantime, the VLC Windows 11 fix steps above give you real, working relief. The wider lesson is that Windows 11’s tighter integration between Defender and the kernel — well-intentioned from a security standpoint — creates new categories of collateral damage for legitimate applications. Until Microsoft provides a more transparent mechanism for app developers to flag false positives, incidents like this will keep happening.

FAQ

Why is VLC so slow to open on Windows 11?

The most common cause in mid-2026 is a Microsoft Defender update that scans or quarantines VLC’s plugin cache file, forcing VLC to rebuild it on every launch. This can add 5 to 33 seconds to startup time. Regenerating the cache manually or adding VLC’s folder to Defender’s exclusion list fixes the problem immediately.

Is the VLC playback issue a VLC bug or a Windows 11 bug?

Microsoft Defender’s behaviour is the primary trigger — it is modifying files inside a legitimately installed application without user consent. VideoLAN confirmed this publicly. However, VLC’s bug tracker also shows separate, pre-existing playback regressions linked to Windows 11’s GPU scheduling on certain hardware, so it’s not entirely one-sided.

Will Microsoft release a patch for the VLC slow Windows 11 problem?

Microsoft has not officially acknowledged a specific bug tied to this incident. Defender definition updates are rolled out continuously, and the relevant false-positive behaviour may already be corrected silently in newer definitions. There is no scheduled Windows Update patch for this specific VLC playback issue.

Does disabling Microsoft Defender fix VLC performance on Windows 11?

You should not disable Defender entirely — that leaves your PC unprotected. Instead, add only VLC’s installation folder as a Defender exclusion. This stops the cache-scanning behaviour while keeping full system protection active everywhere else.

Which version of VLC works best on Windows 11?

VLC 3.0.23 and the latest 3.0.x release are the recommended stable versions for Windows 11 as of August 2026. Nightly builds of VLC 4.0 are available for testing but are not recommended for daily use. Always download directly from VideoLAN’s official website to avoid unofficial, modified versions.

Windows 11 cumulative updates notification on a modern laptop screen
August 13, 2026

Windows 11 Cumulative Updates August 2026: What’s Fixed

Post By administrator Microsoft, Windows , , , , , , No Comments

The August 2026 Windows 11 cumulative updates — KB5121003 and KB5120240 — are now rolling out to all supported devices, and they are not optional. Released on 12 August 2026 as part of Microsoft’s monthly Patch Tuesday cycle, these updates collectively address 400 security vulnerabilities, including three actively exploited zero-days, making them among the most critical releases of the year. If you haven’t installed them yet, read on to understand exactly what’s fixed, what’s improved, and how to get your PC protected.

What Are KB5121003 and KB5120240?

Windows 11 cumulative updates KB5121003 and KB5120240 package icons infographic

KB5121003 and KB5120240 are Windows 11 security patches targeting different release branches. KB5121003 applies to Windows 11 versions 24H2 and 25H2 (OS Builds 26100.9168 and 26200.9168), while KB5120240 covers earlier supported builds. Both updates are classified as mandatory cumulative updates — meaning Windows Update will push them automatically to devices that haven’t opted out of automatic updates. Together they represent the full August 2026 Patch Tuesday rollout for Windows 11.

Microsoft’s own support page for KB5121003 confirms the update provides broad security improvements and includes new Secure Boot certificate targeting, designed to harden systems against firmware-level attacks.

400 Vulnerabilities Fixed: The Security Breakdown

The August 2026 Patch Tuesday Windows 11 release is one of the largest in recent memory. According to reporting by BleepingComputer, the full patch batch addresses 400 flaws across the Windows ecosystem, with the most severe breakdown as follows:

  • 42 Critical vulnerabilities patched in total
  • 37 Remote Code Execution (RCE) flaws within those Critical CVEs
  • 5 Elevation of Privilege vulnerabilities rated Critical
  • 3 zero-day exploits confirmed as actively exploited in the wild

Remote code execution flaws are among the most dangerous classes of vulnerability — they can allow an attacker to run arbitrary code on your machine without any interaction from you beyond visiting a compromised page or opening a malicious file. The three zero-days mean threat actors were already using these gaps before Microsoft published the fix, which is precisely why this update should be treated as urgent.

Windows 11 Security Patch: Key Fixes in KB5121003

Windows 11 security patch August 2026 vulnerability breakdown chart with 400 fixes

Beyond raw vulnerability counts, the August Windows 11 security patch includes a range of targeted quality and stability fixes that real users will notice day-to-day. Here is a summary of the most significant changes confirmed across multiple sources:

  • Secure Boot certificate updates — Additional high-confidence device targeting to block unauthorised bootloaders, directly addressing firmware-level attack vectors.
  • Slow startup fix — A bug causing extremely slow boot times on certain hardware configurations has been resolved.
  • Memory leak resolved — A memory leak affecting background processes was causing gradual performance degradation; KB5121003 stops the leak.
  • App search improvements — The Start menu and Settings search now handle typos and partial app names more reliably, making it faster to find installed apps on low-end PCs.
  • Voice Isolation — The update activates Voice Isolation in supported audio settings, filtering background noise during calls and recordings.
  • File Explorer readable sizes — File sizes in Explorer are now displayed in a more human-readable format, removing ambiguity about whether a listed size is in KB, MB, or GB.
  • External fingerprint sign-in — Improved support for external fingerprint readers at the Windows Hello login screen, broadening biometric authentication without built-in hardware.
  • USB/xHCI regression fix — A regression introduced in a previous update that broke certain USB controller configurations has been corrected.

Patch Tuesday Windows 11: Which Versions Are Affected?

Not all Windows 11 installations receive the same update package. Here is how Microsoft has split the August rollout:

  • Windows 11 24H2 & 25H2 → KB5121003 (Builds 26100.9168 / 26200.9168)
  • Windows 11 26H1 → KB5121000 (Build 28000.2704)
  • Earlier supported builds → KB5120240

Devices running editions that have reached end-of-servicing will not receive these fixes. Microsoft’s support documentation explicitly states that such devices will no longer receive fixes for known issues or time zone updates — another strong reason to stay on a supported version. If you are still running Windows 10 or an out-of-support Windows 11 build, you are exposed to all 400 of these vulnerabilities with no official mitigation.

Should You Install the Windows 11 Updates Immediately?

Yes — particularly given the three active zero-days. Microsoft classifies these Windows 11 updates as mandatory, and independent security researchers echo that recommendation. The combination of three in-the-wild zero-days and 37 critical remote code execution flaws means the risk of delaying is measurably higher than the risk of installing. The known post-install issue is limited to a USB/xHCI regression for specific controller setups, which Microsoft has already confirmed is fixed within KB5121003 itself.

To install manually: open Settings → Windows Update → Check for updates. The update will appear automatically if it hasn’t already downloaded in the background. A restart is required to complete installation.

Windows 11 Updates and Your Licence: Are You Covered?

Windows 11 updates settings screen showing cumulative update installation steps

Cumulative updates like KB5121003 are free for all activated Windows 11 installations — Microsoft does not charge for security patches. However, they only apply to genuine, activated copies of Windows 11. If your PC is running an unactivated or counterfeit licence, Windows Update may still deliver the update file, but you remain at risk because system integrity protections are weakened on non-genuine installations.

If you’re on Windows 10 or an older version and these headlines are prompting an overdue upgrade, now is a sensible time to act. Buy Now Key offers genuine Microsoft Windows 11 Pro (Retail) licences from €17.90 — a one-time purchase that gives you lifetime activation, full Windows Update coverage, and every future security patch as it drops. There is also a more affordable Microsoft Windows 11 Home OEM option from €9.65 if you are activating on a single new device and don’t need the Pro feature set.

Not sure which edition suits you? Read our in-depth Windows 11 Pro vs Home comparison to pick the right version before you buy.

How These Windows 11 Security Patches Relate to Previous Updates

The August release builds on a year of increasingly substantial monthly updates. In May 2026, for example, Microsoft shipped KB5089549, which alone patched 120 vulnerabilities alongside Xbox mode integration and a critical BitLocker recovery fix. The August 2026 batch dwarfs that figure at 400 flaws, reflecting both the growing attack surface of a maturing OS and Microsoft’s shift toward consolidating previously deferred patches into single large rollouts.

The Secure Boot improvements in KB5121003 are particularly notable in the context of earlier 2026 vulnerabilities. A zero-day BitLocker bypass exploit (CVE-2026-45585) disclosed earlier this year demonstrated that firmware-level weaknesses can let attackers read encrypted drives with nothing more than a USB stick. The new Secure Boot certificate targeting in August’s update closes a related class of bootloader exploits before they reach that severity.

How to Check Your Current Windows 11 Build

Before or after installing the update, you can confirm exactly which build is running on your machine:

  1. Press Win + R, type winver, and press Enter.
  2. The About Windows dialog shows your exact OS build number.
  3. Compare it against the target build for your version (e.g. 26100.9168 for 24H2).
  4. If your build is lower, go to Settings → Windows Update and install pending updates.

After a successful install and restart, running winver again should reflect the updated build number, confirming KB5121003 or its equivalent is applied.

For the complete official changelog and issue history, refer to Microsoft’s own support article: August 11, 2026 — KB5121003 (OS Builds 26200.9168 and 26100.9168).

Frequently Asked Questions

Are KB5121003 and KB5120240 mandatory Windows 11 updates?

Yes. Both are classified as mandatory security updates by Microsoft. They form the August 2026 Patch Tuesday cumulative rollout and will be pushed automatically to devices running Windows Update. Because they address actively exploited zero-days, Microsoft and independent security researchers strongly advise installing them without delay.

What zero-days do the August 2026 Windows 11 updates fix?

The August 2026 Patch Tuesday fixes three zero-day vulnerabilities that were confirmed as being actively exploited in the wild at the time of release. Microsoft has not publicly disclosed the full technical details of all three at launch — this is standard practice to give users time to patch before full exploit code circulates widely.

Will these Windows 11 security patches slow down my PC?

No performance regressions have been widely reported with KB5121003. On the contrary, the update specifically fixes a memory leak and slow-startup bug, meaning many users may notice modest performance improvements after installation. The known USB/xHCI regression from an earlier update is also resolved in this release.

Do I need a new Windows licence to receive these updates?

No — cumulative security updates are free for all genuine, activated Windows 11 installations. If you are running an unactivated copy, obtaining a legitimate licence ensures you receive full update protection and system integrity features going forward.

What if I’m still on Windows 10 — am I protected by these patches?

Windows 10 receives separate Patch Tuesday updates and is not covered by KB5121003 or KB5120240. Windows 10 mainstream support ended in October 2025, meaning only paid Extended Security Updates (ESU) provide continued patches. Upgrading to Windows 11 on supported hardware is the most straightforward long-term solution for staying protected.

How do I manually download KB5121003 if Windows Update isn’t working?

You can download the update directly from the Microsoft Update Catalog by searching for the KB number at catalog.update.microsoft.com. Download the .msu file matching your build (24H2 or 25H2), double-click to run the Windows Update Standalone Installer, and restart when prompted. This method bypasses Windows Update delivery but installs the identical package.

Windows 11 fixes 2026 performance improvements shown on a modern desktop
August 11, 2026

Windows 11 Fixes 2026: The 5 Improvements That Actually Matter

Post By administrator Microsoft, Windows , , , , , , No Comments

Windows 11 fixes in 2026 are not vague roadmap promises — Microsoft is actively rolling them out through Insider builds and confirmed public previews. After years of criticism over sluggishness, intrusive AI widgets, and a locked-down taskbar, the company is addressing the core complaints head-on. We dug into the early builds and the official announcements to tell you exactly which of these Windows 11 improvements will change your day-to-day experience, and which are mostly cosmetic.

Why Microsoft Is Prioritising Windows 11 Performance in 2026

Windows 11 performance pillars for improved reliability and memory efficiency

The pressure on Microsoft is real. Windows 10 reaches end of life in October 2025, pushing tens of millions of users to evaluate whether Windows 11 is worth the move. User sentiment data and public forum complaints made it impossible for the company to ignore the performance gap: Windows 11 historically consumes more RAM at idle than Windows 10 and has measurably higher UI interaction latency. According to reporting by Thurrott, Microsoft is explicitly targeting memory efficiency, reduced interaction latency, and improved reliability as its three pillars for 2026 — a frank acknowledgement that the OS shipped with meaningful overhead that users shouldn’t have to tolerate.

The good news: several of these Windows 11 updates are already measurable in testing. Here is what matters most.

Fix 1 — Reduced RAM Usage Under Load

Reducing idle and under-load RAM consumption is Microsoft’s headline Windows 11 performance goal for 2026. Early Insider builds have shown meaningful reductions in the memory footprint of core system processes, with Microsoft specifically targeting background services that ballooned after the 22H2 and 23H2 updates. Independent testers at Windows Latest confirmed that Microsoft has committed to making apps “perform more consistently even under load” through improved memory scheduling.

For everyday users this means fewer situations where opening a browser tab causes a noticeable stutter because system RAM was already under pressure. For professionals running memory-hungry applications — video editors, developers, designers — this is the single most impactful of all the 2026 Windows 11 updates.

  • Reduced idle RAM usage from core system processes
  • Improved memory scheduling so heavy apps get priority
  • More consistent frame pacing in GPU-bound tasks
  • Better behaviour when multiple large applications run simultaneously

Fix 2 — A Movable, Flexible Taskbar

Windows 11 fixes 2026 including movable taskbar and low-latency UI improvements

One of Windows 11’s most-complained-about regressions was the loss of taskbar positioning options that Windows 10 users relied on. The centred Start menu came at the cost of flexibility: you could not move the taskbar to the top or sides of the screen, and resizing it was impossible. Microsoft is finally correcting this as part of the 2026 Windows 11 improvements.

Insider builds have demonstrated a taskbar that can be repositioned and resized, recovering a workflow staple that power users lost at launch. This is more than cosmetic — multi-monitor professionals who run a vertical taskbar on a portrait display have been forced to keep a Windows 10 machine or use third-party workarounds for years. The 2026 fix removes that dependency.

Fix 3 — Lower Interaction Latency Across the UI

Windows 11 performance improvements in 2026 extend well beyond memory. Microsoft has confirmed a dedicated Low Latency Profile for the OS — a system-level change that prioritises UI thread responsiveness. Early reports suggest the profile will enter public rollout around mid-2026, and Insider testing shows noticeably snappier window animations, faster context-menu responses, and reduced input lag when typing or clicking rapidly.

This matters most to anyone who has noticed that Windows 11 feels slightly “floaty” compared with Windows 10 — a perception rooted in the DWM (Desktop Window Manager) scheduling decisions Microsoft made at launch. The low-latency profile directly addresses that scheduling, making the desktop feel more immediate without sacrificing visual polish.

Fix 4 — File Explorer Stability and Speed

Windows 11 updates reducing AI interruptions and ads in the Start menu

File Explorer has been a recurring villain in Windows 11 stability complaints: tab crashes, slow folder opens when network drives are mapped, and the infamous delay when right-clicking large files. The 2026 Windows 11 updates include targeted File Explorer fixes covering all three pain points.

Microsoft has confirmed that File Explorer is receiving architectural improvements to how it handles shell extensions — the third-party add-ons (like 7-Zip or antivirus context-menu entries) that have historically caused the most Explorer crashes. By isolating these extensions in a separate process, a misbehaving shell extension can no longer bring down the entire Explorer window. For users with heavily customised environments, this alone will dramatically reduce the number of times they have to restart Explorer in a session.

  • Shell extensions isolated to prevent cascading crashes
  • Faster folder load times for network-mapped drives
  • Reduced right-click context-menu latency
  • Improved tab stability in multi-tab Explorer sessions

Fix 5 — Fewer Forced AI and Ad Interruptions

Among all the Windows 11 fixes 2026 brings, the reduction of unsolicited Copilot prompts, Start menu advertisements, and lock-screen recommendations may be the one that most visibly changes the experience for ordinary users. Microsoft has announced a deliberate rollback of the aggressiveness with which AI features and promotional content are surfaced, acknowledging that the volume of interruptions was eroding user trust.

Practically, this means fewer “Try Copilot” banners in the Start menu, fewer lock-screen content recommendations served as ads, and a Copilot integration that requires genuine user initiation rather than appearing unbidden. These are not small UX tweaks — they represent a policy shift about how Windows 11 communicates with its users.

Windows 11 Updates Timeline: What to Expect When

Not all of these improvements arrive simultaneously. Here is a rough deployment picture based on confirmed Insider and public-preview information as of mid-2026:

  1. Q1–Q2 2026: RAM efficiency improvements and File Explorer stability fixes — already in Insider Preview builds and rolling to Release Preview.
  2. Mid-2026: Low Latency Profile confirmed for public rollout; taskbar repositioning entering Release Preview.
  3. Late 2026 (25H2 / 26H1): Full public availability of taskbar flexibility and reduced AI interruption policies through the annual feature update cycle.

Microsoft’s version 26H1, scoped to support new 2026 hardware, already reflects silicon-level performance improvements. Users on existing machines will receive most of these improvements through cumulative updates rather than needing to wait for a new major version.

Should You Upgrade to Windows 11 Now or Wait?

The honest answer is that the Windows 11 improvements landing throughout 2026 make upgrading more compelling than it has been at any point since launch. If you are still on Windows 10 ahead of its end-of-support deadline, the risk calculus has shifted: staying on an unsupported OS is a security liability, and the OS you would be upgrading to is meaningfully better than the one that launched in October 2021.

If your machine meets the hardware requirements — and many users are surprised to find it does after checking the full system requirements — the path forward is straightforward. A genuine Windows 11 licence is the foundation: you get all cumulative updates including every Windows 11 performance improvement Microsoft ships, with no subscription required.

At Buy Now Key, Microsoft Windows 11 Pro is available from €17.90, giving you a lifetime retail licence that covers every future update in this wave of Windows 11 fixes. If you need the full OS and a productivity suite together, the Windows 11 Pro and Office 2024 Professional Plus bundle is available from €27.80 — a significant saving on buying both separately.

Windows 11 Performance Tips While You Wait for Updates

While the cumulative rollout of these Windows 11 updates continues, there are steps you can take right now to reduce overhead on your existing installation:

  • Disable startup apps you do not actively use (Settings → Apps → Startup).
  • Turn off background activity for non-essential apps (Settings → System → Power).
  • Review and limit widget panel content, which contributes to background memory usage.
  • Ensure your drivers — particularly GPU and chipset — are current, as driver-level optimisations accompany many of the OS-level Windows 11 performance gains.
  • Run a storage health check; SSD degradation disproportionately impacts the responsiveness improvements Microsoft is targeting at the scheduler level.

Frequently Asked Questions

Are the Windows 11 fixes 2026 free for existing users?

Yes. All the Windows 11 improvements described here are delivered through Windows Update at no additional charge for anyone with a valid Windows 11 licence. You do not need to purchase an upgrade; simply keep Windows Update enabled and the improvements will arrive automatically as they roll out.

When will Windows 11 performance improvements reach my PC?

Several fixes — including RAM efficiency and File Explorer stability — are already in Insider Preview builds and entering the Release Preview channel. Most users on mainstream builds should see these improvements by late 2026 via cumulative updates or the 25H2 feature update. Check Settings → Windows Update to ensure you have the latest cumulative update installed.

Do the 2026 Windows 11 updates require new hardware?

No. The vast majority of the performance and stability improvements are software-level changes that apply to existing hardware. Microsoft’s 26H1 version is specifically scoped to new 2026 silicon, but the RAM, latency, File Explorer, and taskbar fixes are coming to existing devices through cumulative updates.

Is it worth upgrading from Windows 10 now given these Windows 11 improvements?

With Windows 10 reaching end of support in October 2025, upgrading is increasingly important for security. The 2026 Windows 11 updates make the upgrade even more worthwhile — the performance gap that previously made users hesitant is being closed. If your hardware qualifies, upgrading now means you benefit from all incoming improvements immediately.

Will these fixes improve gaming performance on Windows 11?

Partially. The low-latency profile and RAM efficiency improvements will benefit gaming indirectly by reducing OS overhead and improving frame-time consistency. Microsoft has also indicated gaming-specific scheduler improvements are in progress for 2026, though the primary gaming gains will depend on GPU driver updates from Nvidia, AMD, and Intel alongside the OS changes.