Microsoft’s last Windows 11 preview of the year quietly bundled two very different stories: a December preview cumulative (KB5070311) that appears to reduce a string of AMD Radeon “GPU hung” and DirectX 12 game-timeout failures for some users, and an emergent community tool — RemoveWindowsAI — claiming to strip nearly every AI component out of Windows 11. Both developments matter for different constituencies: gamers hoping for stability, and users and admins pushing back against the rapidly growing AI surface in the OS. This article verifies the technical claims, cross-checks multiple sources, and offers clear, practical guidance for enthusiasts and IT pros weighing whether to install the update or run a third‑party removal script.
Windows servicing in late 2025 has been unusually active: monthly cumulatives, preview updates, and vendor driver releases have combined with Microsoft’s expanding AI push to create a complex, fast-moving ecosystem. That velocity has surfaced both genuine quality improvements and regressions — from File Explorer polish to game-timeout regressions — and has amplified user unease about AI features appearing system-wide by default. The December preview update KB5070311 (OS builds 26200.7309 for 25H2 and 26100.7309 for 24H2) is Microsoft’s vehicle for a mixed bag of fixes and UX polish that also touches the display and gaming stacks. Simultaneously, community developers and privacy-conscious users have circulated tools designed to reclaim system control. The RemoveWindowsAI project on GitHub — authored under the handle zoicware — surfaced this week as a polished PowerShell utility (with a GUI) that automates disabling or removing Copilot, Recall, AI-enhanced apps, appx packages, and various registry keys tied to Windows 11’s agentic features. Multiple outlets and guides tested or documented the tool; its popularity underscores a widening gap between Microsoft’s product direction and the preferences of a vocal subset of users.
KB5070311 includes targeted improvements to the monitor-mode query path and several display enumeration timing improvements. By smoothing or offloading blocking operations, the OS reduces the risk that the exact timing window which previously triggered a TDR will be hit. This is an OS-level mitigation; permanent fixes often still require updated GPU drivers or game-side patches to remove root causes in shader compilation or driver workloads.
Microsoft’s December preview illustrates two broader trends in Windows Windows 11: a continuing push to ship AI-first features and a servicing model that allows rapid fixes and rapid corrections. The community response — from gamer troubleshooting threads to a fully fledged script to opt out of AI — reflects an ecosystem trying to reconcile innovation with control. Both the KB5070311 evidence and the RemoveWindowsAI tool are real and useful in context, but neither replaces careful testing, measured deployment, and the basic hygiene of backups and rollback plans. The sensible path forward for most users is conservative experimentation: test the update or the script on nonessential hardware, keep detailed logs, and prefer official cumulative releases and managed policies for production environments.
Source: www.guru3d.com https://www.guru3d.com/story/windows-11-december-update-fixes-amd-gpu-hangs-and-dx12-game-crashes/
Source: www.guru3d.com https://www.guru3d.com/story/window...laiming-to-strip-all-ai-features-from-the-os/
Background
Windows servicing in late 2025 has been unusually active: monthly cumulatives, preview updates, and vendor driver releases have combined with Microsoft’s expanding AI push to create a complex, fast-moving ecosystem. That velocity has surfaced both genuine quality improvements and regressions — from File Explorer polish to game-timeout regressions — and has amplified user unease about AI features appearing system-wide by default. The December preview update KB5070311 (OS builds 26200.7309 for 25H2 and 26100.7309 for 24H2) is Microsoft’s vehicle for a mixed bag of fixes and UX polish that also touches the display and gaming stacks. Simultaneously, community developers and privacy-conscious users have circulated tools designed to reclaim system control. The RemoveWindowsAI project on GitHub — authored under the handle zoicware — surfaced this week as a polished PowerShell utility (with a GUI) that automates disabling or removing Copilot, Recall, AI-enhanced apps, appx packages, and various registry keys tied to Windows 11’s agentic features. Multiple outlets and guides tested or documented the tool; its popularity underscores a widening gap between Microsoft’s product direction and the preferences of a vocal subset of users. KB5070311: What Microsoft shipped and why it matters
What’s in the update (official summary)
KB5070311 is a non‑security preview cumulative that lists improvements across File Explorer, Settings, display/graphics behavior, and several quality-of-life features such as Virtual Workspaces and improved keyboard/backlight handling. Critically for gamers and enthusiasts, Microsoft explicitly documented fixes that touch the display/graphics interaction layer: improved performance when apps query monitors for their full list of supported modes, and a fix for a spurious “Unsupported graphics card detected” message that appeared in some titles. Those two items are the most relevant pieces for GPU‑related timeouts and driver watchdog tripping.Community reports: AMD GPU hangs and DX12 timeouts
Following the release of KB5070311 in the preview channel, multiple community threads and enthusiast sites reported that some AMD users — notably owners of high-end RX 9000-series hardware running Adrenalin 25.11.1 — saw an immediate reduction or disappearance of GPU-hang errors and “driver removed / not accepting more commands” messages in demanding DX12 titles such as Battlefield 6, Call of Duty: Black Ops 7, and ARC Raiders. Those reports are mostly anecdotal and configuration-dependent, but they are consistent across forum threads and user posts collected during early testing. Two important caveats apply:- KB5070311 is a preview (optional) update: it’s intended for testing and may introduce regressions of its own. Microsoft explicitly listed a known issue where File Explorer briefly flashes white when running in Dark Mode after installing this preview. The company later folded fixes into the December 9 cumulative (KB5072033) that addressed that white-flash regression. Test first and do not push previews to mission-critical machines.
- The package alters OS-level enumeration and timing, not GPU driver internals. That means the fix is often a timing/compatibility mitigation: changing when and how Windows responds to display queries can avoid the precise timing window that previously tripped the driver watchdog (TDR), but lingering driver-level bugs remain a possibility and may require vendor drivers or game patches. Cross-vendor interplay (OS timing + driver behavior + game engine) explains why some users see instant improvement while others do not.
How the apparent fix plausibly works (technical explanation)
Modern GPUs and games interact with Windows through a chain of queries and handshakes: the game queries the display for supported modes, the OS performs mode checks and driver calls, and the driver submits GPU work. If any stage blocks or times out — for example, a long mode query, a delayed driver response, or a heavy shader compile in DX12 — Windows may register a TDR (Timeout Detection and Recovery) and reset the GPU, which manifests to the user as “GPU hung / driver removed” errors.KB5070311 includes targeted improvements to the monitor-mode query path and several display enumeration timing improvements. By smoothing or offloading blocking operations, the OS reduces the risk that the exact timing window which previously triggered a TDR will be hit. This is an OS-level mitigation; permanent fixes often still require updated GPU drivers or game-side patches to remove root causes in shader compilation or driver workloads.
Practical guidance: should you install KB5070311?
For gamers and enthusiasts
- If you are on a production or competitive rig: do not install preview updates. Wait for the cumulative release that includes these fixes (Microsoft shipped a cumulative on Dec 9 that folded in KB5070311 fixes and addressed the dark-mode flash).
- If you are willing to test on a secondary machine: install KB5070311 (optional preview), update your AMD driver to the latest Adrenalin build, and stress-test the offending titles. Record crash logs and Event Viewer TDR entries to provide evidence if the issue persists.
- If you experience new regressions (white-flash in File Explorer, login icon issues, or other UI anomalies), uninstall the preview and report the behavior via Feedback Hub. Microsoft’s preview track is designed for this feedback loop.
For IT administrators
- Pilot KB5070311 across a representative set of hardware and driver combinations in a staged ring. The update contains a servicing stack update (SSU) and other components that can affect deployment behavior; staging reduces the chance of a widely felt regression.
- Maintain rollback and imaging plans. Preview updates can be uninstalled, but SSUs and certain servicing changes may complicate rollbacks. Validate restore points and recovery images before adopting preview code.
RemoveWindowsAI: what it claims and what it actually does
What the tool does (feature list)
RemoveWindowsAI is an open-source PowerShell project that automates a long list of disabling and removal actions:- Toggle or remove registry keys associated with Copilot, Recall, Input Insights, image and text AI features, and voice access.
- Remove Appx/Provisioned AI packages and forced removal of some ‘nonremovable’ packages from CBS.
- Prevent reinstallation by installing a custom Windows Update package that blocks targeted AI packages in the Component-Based Servicing (CBS) store.
- Provide a GUI overlay, non-interactive automation, backups, and a “Revert Mode” to undo changes if needed.
Independent verification and coverage
Multiple outlets and guides tested or documented the script. Tom’s Hardware reported hands-on testing and noted the tool’s GUI and revert capabilities; PureInfotech published a step-by-step guide and warned about the risks; Decrypt and other outlets covered the social traction and privacy-driven enthusiasm behind the tool’s popularity. All coverage emphasized that the script is third-party and not supported by Microsoft, and that users should back up before running it.Critical analysis: strengths, limitations, and risks
Strengths and legitimate reasons for using the script
- User choice and control: RemoveWindowsAI packages a community-driven approach to give users explicit control over whether agentic features run on their devices. For privacy-minded users and certain enterprise scenarios, that control can be meaningful.
- Automation of a tedious process: Manually hunting down registry keys, Appx packages, and CBS entries is error-prone and time-consuming; an audited script simplifies repeatable deployments for testers and hobbyists.
- Revert capability: The presence of a documented Revert Mode and backup steps reduces the long-term risk of accidental permanent removal.
Risks and limitations — be explicit
- Unsupported, unverified at scale: This is a community script. Running it on production fleets or unmanaged mission-critical devices risks breaking functionality that admins rely on, and it has no formal support contract. Microsoft updates may restore removed components or block the custom blocking package, producing complex update interactions.
- Partial coverage and manual steps: Not all AI features can be programmatically removed. The repo itself documents manual shutdown steps for features like Gaming Copilot, OneDrive AI, and Windows Studio Effects. Claims that it “removes every AI feature” should be qualified — it removes or disables a very large surface, but some parts require manual action. Treat “every” as aspirational, not absolute.
- Update and servicing friction: The tool installs a custom package to block reinstallation via CBS. That can interfere with future Microsoft servicing, create update errors, or leave a device in a nonstandard state that’s harder to troubleshoot. Enterprises should avoid unilateral automation without testing.
- Security and integrity considerations: Running arbitrary PowerShell scripts that modify system packages and the CBS store carries supply-chain and integrity risk. Even open-source code requires an independent audit — both for malicious intent (unlikely here) and for accidental, destructive logic paths. Verify the script contents locally and run in an isolated environment first.
Practical guidance for anyone considering RemoveWindowsAI
- Create a full system image and a restore point before running anything that removes system packages. Backups are non-negotiable.
- Test in a disposable VM or a non-essential physical machine first — prefer a fresh image that can be reimaged quickly.
- Review the script manually (read the PowerShell) and understand precisely which registry keys, Appx packages, and CBS entries it will modify or remove.
- Use the script’s Revert Mode — test revert on your test image first to ensure it actually restores the desired state.
- Expect that Windows Update may reinstall some elements on major feature or servicing updates; make a remediation plan if you need the machine to remain AI-free.
- For enterprises: treat this as a prototype, not as a sanctioned remediation. Use group policies and official Microsoft management tooling where possible. If policy controls aren’t sufficient, escalate to vendor support or consider formal change requests before deploying community tools at scale.
Cross-references and verification — key claims checked against independent sources
- Microsoft published the KB5070311 preview release notes and explicitly lists display/graphics improvements and File Explorer changes. That claim is verified in Microsoft’s KB and update history.
- Community evidence that KB5070311 reduced AMD-related GPU hung errors in some configurations is corroborated by reporting from enthusiast outlets and aggregated forum posts; the evidence is credible but largely anecdotal and configuration-dependent. Use caution and cross-check on a test machine.
- The RemoveWindowsAI repository exists on GitHub, documents its approach (registry changes, Appx removals, blocking package), and offers a GUI and revert functionality. Independent outlets tested or documented the tool’s behavior. Those facts are cross-checked with GitHub and several news guides.
Security and support implications — enterprise view
- Removing built-in OS components or installing custom CBS-blocking packages complicates vendor support: if Microsoft’s support flow needs to re-provision a component for diagnosis, restoration may be nontrivial. Enterprises should weigh operational risk and auditability before allowing third‑party system‑level removals.
- Preview OS updates should be treated as test artifacts in deployment rings; they signal future stable changes but are not guaranteed safe for broad corporate rollout. KB5070311’s known UX regression (white flash in dark mode) and the subsequent corrective cumulative demonstrate the intended preview->cumulative process.
- For security posture: some AI features also integrate telemetry and cloud components. Removing local UI features does not necessarily remove server-side processing tied to cloud services unless the script or policy also disables account-level or cloud integrations. Treat local removal as one piece of a broader privacy plan.
Bottom line and smart next steps
- For gamers experiencing DX12-related GPU hangs: start with safer remediation first — update AMD drivers (consider a clean install), test forcing DX12 if applicable, and stage KB5070311 on a non-critical machine before broad adoption. If the preview resolves your problem in testing, wait for the stable cumulative that includes the same fixes before deploying widely.
- For users who are uncomfortable with Windows’ growing AI footprint: RemoveWindowsAI is a capable community tool that automates much of the work, but it’s third‑party and not risk‑free. Use it on test hardware first, read the code, and keep backups. Prefer policy-based and supported blocking options inside enterprise management when possible.
- All parties — Microsoft, GPU vendors, and game developers — share responsibility for end-to-end stability. An OS update that changes timing or enumeration behavior can be a legitimate and practical mitigation, but long-term robustness requires vendor driver updates and, in some cases, game patches. Users should collect logs and collaborate with vendors when issues persist.
Microsoft’s December preview illustrates two broader trends in Windows Windows 11: a continuing push to ship AI-first features and a servicing model that allows rapid fixes and rapid corrections. The community response — from gamer troubleshooting threads to a fully fledged script to opt out of AI — reflects an ecosystem trying to reconcile innovation with control. Both the KB5070311 evidence and the RemoveWindowsAI tool are real and useful in context, but neither replaces careful testing, measured deployment, and the basic hygiene of backups and rollback plans. The sensible path forward for most users is conservative experimentation: test the update or the script on nonessential hardware, keep detailed logs, and prefer official cumulative releases and managed policies for production environments.
Source: www.guru3d.com https://www.guru3d.com/story/windows-11-december-update-fixes-amd-gpu-hangs-and-dx12-game-crashes/
Source: www.guru3d.com https://www.guru3d.com/story/window...laiming-to-strip-all-ai-features-from-the-os/
