Win11Debloat Update Lets Windows Users Block OEM Companion Apps

Win11Debloat’s newest release adds a toggle that blocks the vendor software Windows Update quietly bundles alongside hardware drivers. The open source PowerShell script still installs the driver itself. It just cuts the manufacturer add-ons that used to ride along uninvited.

Windows Update has doubled for years as a distribution pipe for software from the original equipment manufacturer (OEM, the company that built the PC). Most people who ran it never noticed an extra program had hitched a ride alongside the driver they actually needed.

Windows Update Still Installs the Driver, Just Not the Extras

The new option sits in Win11Debloat’s tweaks list, next to the script’s older telemetry and app-removal switches. Turn it on, and Windows Update keeps delivering whatever driver a printer, webcam, or graphics card needs.

What it drops is the software vendors attach to that delivery: OEM control panels, update checkers, and promotional utilities that install themselves without asking. Neowin first reported the addition this week; the underlying changelog is published on the project’s GitHub page.

Win11Debloat itself is an open source PowerShell script maintained on GitHub by a developer known as Raphire. The project bills itself as a way to strip pre-installed apps, disable telemetry, and remove unneeded features from Windows 10 and Windows 11, and it has shipped updates on a rolling basis through 2026.

The rest of the July 11 changelog is narrower in scope but still touches everyday annoyances.

The PowerShell 7 refusal addresses a common support headache. Scripts written for Windows PowerShell 5.1 can behave unpredictably when someone runs them under the newer, cross-platform PowerShell 7 by mistake, and the script now says so plainly instead of failing in confusing ways.

The Hidden OEM Channel Inside Windows Update

Microsoft’s own support documentation describes Windows Update as the default path for automatically installing recommended and updated hardware drivers for printers, network adapters, and graphics cards.

That same channel has become a convenient spot for PC makers to slip in their own software. A laptop’s Wi-Fi driver might arrive with a bundled vendor dashboard for warranty registration, battery calibration, or an upsell offer, none of which the user asked to install.

IT departments managing fleets of machines have long worked around this with Group Policy or device management suites built for that purpose. Win11Debloat’s new switch brings a version of that same control to home users who have no access to enterprise tooling.

PC makers already answer to Microsoft on a tighter schedule than most buyers realize. Manufacturers spent recent weeks pushing out firmware fixes tied to a Secure Boot certificate deadline, the kind of mandatory update that runs through the same OEM-to-Windows-Update pipeline now getting a companion app filter.

A Frustrating Weekend Set the Backdrop

Neowin ran two separate pieces over the weekend cataloging reader frustration with Windows 11, one focused on home users and another on IT professionals managing fleets of machines. Both threads share a common complaint: updates pitched as improvements keep breaking habits nobody wanted disturbed.

The most recent cumulative update illustrates the tension. It introduced a reworked Start menu, one administrators can now adjust through new group policies, while separately fixing a bug that had been quietly consuming gigabytes of disk space. Microsoft has also said users cannot indefinitely defer installing these updates.

That dynamic pushes some people toward alternatives Microsoft did not build. Some switch to Files instead of the built-in Explorer app; it is a third-party file manager already popular among power users. Others just wait for the next official milestone. Microsoft has already confirmed a sub-500KB October update carrying Bing and Edge changes under the 26H2 label.

Everything Else Packed Into the 2026.07.11 Release

Beyond the two headline features, the full changelog for the July 11 update lists a run of smaller fixes that had apparently been sitting in the queue.

• Registry backup failures now surface a visible error instead of failing silently.
• File Explorer no longer restarts on systems running in Sysprep, the imaging mode IT teams use to prep new machines for deployment.
• The script’s admin relaunch now works correctly for file paths containing certain special characters.
• run.bat no longer breaks when launched from a path with certain characters.
• Icons load correctly again on Windows 10.
• Several issues affecting domain-joined accounts are fixed.
• Store suggestions in search now reset permissions correctly when re-enabled.

The Sysprep fix lines up with a broader pattern of File Explorer quirks Microsoft has been chasing this year. A recent Windows 10 update, KB5094127, brought its own File Explorer and Secure Boot fixes the same month.

Does Debloating Windows Pay Off?

Independent testing of debloat utilities, including Win11Debloat, generally finds modest results rather than a dramatic overhaul. Freed storage and a few fewer background processes are typical. The double-digit speed gains some users expect rarely show up, and a script that misjudges what counts as safe to remove can create new problems.

Testing across four separate debloat tools found RAM savings of 100 to 200MB at most, well short of what marketing around these scripts implies.

The same testing flagged false positives as the bigger practical risk. A run of Win11Debloat flagged Bing Weather, Bing Translator, Windows Tools, and Quick Assist for removal, even though each has a legitimate use for some households.

Win11Debloat also disables Fast Startup by default, a change that makes shutdowns more complete but can noticeably lengthen the time a machine takes to boot back up. Blocking unwanted OEM software still has clear value. Reading the checklist carefully before clicking through remains the safer approach.

Two or Three Releases a Month, Like Clockwork

Win11Debloat’s release history shows how quickly the project has picked up pace this year.

1. February 7, 2026: a tagged release lands after a quiet stretch.
2. May 11, 2026: the next tagged version follows roughly three months later.
3. June 11, 2026: automatic detection of previously applied tweaks and full SYSTEM account support ship.
4. June 24, 2026: support is dropped for several sunset apps, including Fitbit, Shazam, and Twitter.
5. July 11, 2026: the driver companion app blocker and Windows Notifications toggle ship.

At least five tagged releases landed between February and July, with the gap between them shrinking from roughly three months at the start of the year to two or three weeks by midyear.

Frequently Asked Questions

What Does Win11Debloat’s Driver Feature Change?

It adds an opt-in toggle that blocks vendor companion software from installing alongside a hardware driver, while leaving the driver itself untouched. Windows Update still delivers whatever driver a printer, webcam, or graphics card needs; only the extra OEM app that used to ride along gets stopped.

Is Win11Debloat Safe to Run on Windows 11?

It is open source, requires administrator rights, and includes a registry backup option that the July release fixed so failures now surface a visible error instead of failing quietly. Because debloat scripts can occasionally misjudge which apps are safe to remove, creating a system restore point before running any tweak is a reasonable precaution.

Does Win11Debloat Work on Windows 10?

Yes. The script supports both Windows 10 and Windows 11, and the 2026.07.11 release specifically fixes icons that were failing to load correctly on Windows 10, along with hiding several Settings home page entries that do not apply to that version.

Can I Undo Changes Win11Debloat Makes?

Most tweaks can be reversed by unchecking the setting that applied them, a workflow the script has supported since its June 11 update added automatic detection of previously applied changes. The July release adds a new warning when undoing a setting, such as Window Snapping, will require a restart, something earlier versions did not flag.

How Often Does Win11Debloat Release Updates?

The project shipped at least five tagged releases between February and July 2026, and the gap between them narrowed to roughly two to three weeks by midyear. Anyone relying on the script for a specific fix can generally expect the next tagged version within a month.