How to Stop Windows 11 From Installing Manufacturer Bloatware Apps Automatically

Manufacturers bundle bloatware into the factory image before the device ever reaches a store shelf. OEMs do this because software vendors pay placement fees to have their trials and companion apps preinstalled, and the OEM licensing terms with Microsoft leave room for this customization on consumer SKUs. Once a PC ships, there is no setting that stops an OEM from adding that software to the image. What you can control is whether your installation uses that image at all, and whether removed bloatware stays gone. This guide covers both.

Install Windows 11 Without Manufacturer Bloatware Using a Clean ISO

A clean install skips the OEM customization layer completely, since the manufacturer never touches a Microsoft-signed ISO.

1. Download the Windows 11 ISO directly from the official Microsoft software download page.
2. Create bootable media using the Media Creation Tool or Rufus.
3. Boot from the USB drive instead of using the manufacturer’s recovery partition.
4. Complete setup with your product key, or sign in with the Microsoft account already linked to the device for automatic reactivation.

This method removes every OEM app, trial, and companion tool in one step, since none of them exist outside the OEM recovery image.

Buy a Windows 11 Signature Edition or Business Laptop With No Bloatware

Some hardware categories ship clean by design, which avoids the bloatware problem before you even open the box.

Microsoft Store Signature Edition laptops ship with no OEM software installed. Business-targeted SKUs such as ThinkPad Pro models, Dell Latitude and Precision lines, and HP EliteBook devices also ship lighter than consumer SKUs, since business buyers expect a minimal image without trial software or promotional apps.

Stop Windows From Installing Manufacturer Apps When You Connect Hardware

Windows 11 can also download manufacturer companion apps automatically when you connect compatible hardware, separate from anything baked into the factory image. The feature was built to fetch device utilities so hardware works out of the box, but some manufacturers use it to push branded control centers and bundled software through the same pipeline. Razer’s camera drivers, for example, have used this channel to automatically bootstrap the Synapse app onto systems where it was not deliberately installed.

The fix depends on your Windows 11 edition.

On any edition, using Settings:

1. Open Settings > System > About.
2. Click Advanced system settings.
3. Open the Hardware tab and click Device Installation Settings.
4. Select No (your device might not work as expected).
5. Click Save Changes.

On Pro, Enterprise, or Education, using Group Policy:

1. Open gpedit.msc.
2. Go to Computer Configuration > Administrative Templates > System > Device Installation.
3. Double-click Prevent automatic download of applications associated with device metadata.
4. Select Enabled, then click Apply and OK.

On Home edition, using the Registry:

1. Open regedit.msc.
2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Device Metadata.
3. Set the PreventDeviceMetadataFromNetwork DWORD value to 1.
4. Restart the computer.

You can also run this from an elevated Command Prompt instead of editing the Registry directly:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Device Metadata" /v PreventDeviceMetadataFromNetwork /t REG_DWORD /d 1 /f

Back up your system before editing the Registry, since incorrect changes elsewhere in the Registry can cause system problems. This setting only blocks new companion app downloads triggered by connecting hardware. It does not remove apps already installed through OEM factory images, which later sections in this guide cover separately.

Stop Removed Bloatware From Reinstalling via Microsoft Store

The setting above blocks new hardware-triggered installs. If existing bloatware keeps reinstalling itself through the Microsoft Store instead, that is a separate issue, tied to a scheduled task or a Store auto-install rule rather than the OEM rerunning setup. The steps below handle the Store side. OEM scheduled tasks are covered in the next section.

1. Open gpedit.msc (Pro and Enterprise editions only).
2. Go to Computer Configuration > Administrative Templates > Windows Components > Cloud Content.
3. Enable Turn off Microsoft consumer experiences.

This stops Windows from pushing Microsoft Store suggested apps automatically. It does not remove software already baked into the OEM image, since that software was installed before this policy takes effect.

Disable OEM Support App Bloatware Using Task Scheduler

Companion tools like Dell SupportAssist, HP Support Assistant, and Lenovo Vantage often pull updates or reinstall bundled apps through their own scheduled tasks, independent of Windows Update.

1. Open Task Scheduler.
2. Navigate to the Task Scheduler Library and locate the OEM vendor’s folder.
3. Disable tasks tied to update checks or companion app installs.

Disabling the task stops the reinstall trigger without needing to uninstall the parent support app. Keep the parent app itself installed if your device warranty terms require diagnostic software like SupportAssist or Support Assistant to remain present for hardware claims.

Remove Preinstalled Bloatware With O&O AppBuster

Manual removal does not survive every Windows Update, since feature updates can reintroduce OEM apps tied to the original image. Many debloat scripts also disable system services to force-remove stubborn apps, which can break Windows Update in the process.

O&O AppBuster, a free portable tool from O&O Software, avoids that problem. It scans for both visible and hidden preinstalled apps and removes them in a single pass without disabling any system services, so Windows Update keeps working normally. Since it does not touch update-related services, you can rerun it after a feature update reintroduces an OEM app instead of repeating a manual uninstall process.

Deploy Bloatware-Free Windows 11 Across Multiple PCs With Provisioning Packages

For IT-managed environments setting up several devices, a provisioning package applies a clean baseline automatically during OOBE, before OEM first-boot scripts run.

1. Install Windows Configuration Designer from the Microsoft Store.
2. Create a new provisioning package and select the “Provision desktop devices” option.
3. Under Runtime settings, add the app removal and baseline app configuration for your target image.
4. Build the package and save it as a .ppkg file.
5. Apply the package during OOBE on each device, or via a USB drive at first boot, before the OEM’s own setup scripts run.

This approach applies the clean state at deployment time, which avoids removing bloatware machine by machine after the fact.

The Limit of What You Can Control

None of these steps prevent a manufacturer from shipping bloatware on the retail image itself. That decision sits between the OEM and Microsoft’s OEM licensing terms, and it is not something end users or IT admins can override through a device setting or policy. The realistic outcome is a clean install or a reliable removal process, not prevention at the factory level.

Frequently Asked Questions

Related Guides

• Fix Group Policy Event ID 1129: Group Policy Fails Due to Network Connectivity
• How to Disable Web Search in Windows 11 and Remove Spam from Search Results
• How to Update Drivers in Windows 11 Using Device Manager (6 Methods)