Frmupgr.sys is a legacy WIDCOMM/Broadcom Bluetooth firmware-upgrade (DFU) driver. Windows 11 can block Memory Integrity because this old kernel component does not meet current Hypervisor-protected Code Integrity (HVCI) requirements. The supported fix is to identify the driver package that contains frmupgr.sys, remove that package with elevated pnputil, restart, and then enable Memory Integrity again. Do not guess an oem#.inf number or delete the individual file first.
What Frmupgr.sys is
Frmupgr.sys is not a general Windows component. It belongs to an old WIDCOMM/Broadcom Bluetooth stack used for device-firmware upgrades, also called device firmware upgrade (DFU) mode. A Logitech Bluetooth guide lists it with btwusb.sys for a Bluetooth wireless hub, identifies WIDCOMM as the provider, and records file version 1.4.2.8 in that older stack. SystemLookup describes the related DFUBTUSB service as a legitimate WIDCOMM USB Bluetooth driver used during Broadcom flash-upgrade operations.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The documented stack dates from approximately 2003, while a Microsoft Q&A case describes a package installed by older, roughly 2007-era software. That age explains why a file can be legitimate yet incompatible with a security feature introduced much later. There is no authoritative study showing how common Frmupgr.sys incidents are, so the presence of the file alone does not indicate a widespread Windows defect.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWhy Windows 11 blocks Memory Integrity
Memory Integrity is the Windows 11 name for an HVCI protection under Core isolation. It checks kernel-mode drivers before allowing them to run in a protected environment. Legacy Bluetooth DFU code such as Frmupgr.sys was not designed for these requirements, so Windows Security may list it as an incompatible driver and refuse to turn Memory Integrity on.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
The warning does not, by itself, prove that the file is malware. In the documented cases, Windows identifies an old WIDCOMM package, often shown with a published name such as oem80.inf. The number is assigned per computer and can be different on yours. Treat the warning as a compatibility problem: identify the package, decide whether you still need the associated Bluetooth hardware, and remove or replace the old package before retrying HVCI.
Before changing the driver
Create a recovery point
Removing a driver package can make the device that depends on it stop working. Sign in with an administrator account and create a restore point before you edit the Driver Store:
- Press
Win, type Create a restore point, and open the matching Control Panel result. - Select the system drive, choose Configure if protection is disabled, turn on system protection, and apply the setting.
- Select Create, give the point a name such as
Before Frmupgr removal, and wait for Windows to confirm completion.
If Bluetooth is important to your workflow, download the current Bluetooth package for your PC or adapter from its manufacturer before removing the old one. Keep a wired keyboard or mouse available if your normal input devices use Bluetooth.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Understand what will and will not be removed
The goal is to remove the complete third-party driver package from the Driver Store, not merely erase Frmupgr.sys from a folder. Microsoft explains that permanent removal requires deleting the package from the Driver Store; otherwise Windows can stage it again. Removing the package may also remove the only driver that makes an older Bluetooth adapter usable.
Find the package that owns Frmupgr.sys
Use Microsoft’s built-in Plug and Play utility from an elevated terminal. This lists third-party driver packages and their original files.
- Right-click Start and choose Terminal (Admin). On systems that show it, Windows PowerShell (Admin) or Command Prompt (Admin) is also suitable.
- Approve the User Account Control prompt.
- Run:
pnputil /enum-drivers - Scroll through the output or save it to a text file for easier searching:
pnputil /enum-drivers > %USERPROFILE%Desktopdrivers.txt - Search the output for an entry whose original file is
frmupgr.sys. Note the Published Name in that same package block, for exampleoem80.inf. Also note the provider and class so you can distinguish the Bluetooth package from similarly named files.
Do not substitute a number from an online example. The published name is generated on each installation; your system could show oem12.inf, oem80.inf, or another value. If pnputil finds no package containing frmupgr.sys, stop rather than deleting a package by guesswork. The warning may refer to a different copy, a stale detection entry, or a driver already removed from the store.
Remove the incompatible package with PnPUtil
Standard removal
In the same administrator window, replace the example name with the published name you recorded:
Free tools Windows power users keep installed
One-click scans. No signup required.
pnputil /delete-driver oem80.inf /uninstall /force/uninstall removes the package from devices currently using it, and /force allows removal when Windows reports that the package is in use. Microsoft documents /delete-driver <Published Name> /uninstall as the core syntax and lists /force and /reboot as optional switches. If Windows says a restart is required, restart immediately; you can also use:
pnputil /delete-driver oem80.inf /uninstall /force /rebootReplace oem80.inf with your actual value in every command. Read the confirmation text carefully. It should identify the package you found by its frmupgr.sys original file, not an unrelated graphics, network, storage, or audio driver.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Restart and check the result
- Restart Windows after the deletion completes.
- Open Settings and go to Privacy & security → Windows Security → Device security.
- Select Core isolation details.
- Turn Memory integrity on, or choose the option to rescan incompatible drivers if that is what your Windows build displays.
- Restart again if Windows requests it, then return to the same page and verify that the toggle remains on.
Labels can vary slightly between Windows 11 builds. If the old warning remains immediately after removal, perform one more restart and check that the package no longer appears in pnputil /enum-drivers. A warning that names a different driver requires a separate compatibility decision; do not remove every package listed by Core isolation indiscriminately.
What to do if Bluetooth stops working
Loss of Bluetooth after removal is an expected risk when the old package was the only compatible driver. Microsoft warns that deleting a driver package can disable its device, and Windows Update may install a replacement later. Use this recovery order:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Install the current manufacturer driver
- Identify your PC model or the exact Bluetooth adapter model in Settings → System → About, on the adapter label, or in the computer manufacturer’s support utility.
- Using another device if necessary, obtain the current Bluetooth driver package from the PC or adapter manufacturer’s support page.
- Install it, restart, and test Bluetooth pairing and reconnection.
- Return to Device Manager and expand Bluetooth to confirm that the adapter appears without a warning icon.
The replacement should be a current package intended for your Windows edition and hardware. A generic package may restore basic operation but can omit vendor-specific power-management or firmware functions.
Use a compatible USB Bluetooth adapter
If the built-in adapter has no supported Windows 11 driver, a compatible USB Bluetooth adapter is a practical alternative. Compatibility is hardware- and driver-specific, so check the adapter maker’s Windows 11 support information before buying. This option follows from Frmupgr.sys being part of a Bluetooth stack; it is not a guarantee that every USB adapter will work with every PC.
Restore the system point
If you cannot obtain a working driver and Bluetooth is essential, launch System Restore, choose the point created before removal, and follow the wizard. Restoring returns system files and driver registration to the earlier state; it does not make the legacy driver compatible with Memory Integrity. After recovery, you may need to leave Memory Integrity off until you have a supported Bluetooth driver.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Should you rename or manually delete Frmupgr.sys?
A Microsoft Q&A response from 2022 suggests booting into Safe Mode and renaming FRMUPGR.sys to FRMUPGR.sys.old. That is an anecdotal workaround, not a complete package-removal method. Renaming can leave the INF package and Driver Store records intact, and Windows may restore the file or continue to flag the package. It can also make Bluetooth recovery harder if you have not prepared another driver.
Prefer the supported sequence: create a restore point, identify the exact published package with pnputil /enum-drivers, remove that package with /delete-driver ... /uninstall, and restart. Only consider a Safe Mode rename when a qualified technician has confirmed that package removal is impossible and you have a tested recovery plan.
Common errors and their fixes
| Message or symptom | Likely reason | Action |
|---|---|---|
Access is denied |
The terminal is not elevated, or policy prevents the operation. | Close the window, open Terminal (Admin), approve UAC, and run the command again. If policy still blocks it, use an administrator account or your organization’s support process. |
| Package is in use | A Bluetooth service or device is actively using the driver. | Close Bluetooth settings and applications, disconnect the adapter if practical, then retry with /uninstall /force. Restart when prompted. |
| Published name not found | The oem#.inf value was guessed or copied from another computer. |
Run pnputil /enum-drivers again and match the package whose original file is exactly frmupgr.sys. |
| Memory Integrity still refuses to enable | Another incompatible driver remains, or Windows has not refreshed its inventory. | Restart, rescan Core isolation, and identify the newly named driver. Remove only the package you can positively match, then install current hardware drivers. |
| Bluetooth disappeared | The removed package was the only usable Bluetooth driver. | Install the current PC or adapter manufacturer driver, use a compatible USB adapter, or apply the restore point. |
| Windows Update reinstalls the old package | The package remains available to Windows Update or the hardware is rediscovered. | After confirming the hardware has a current replacement, remove the obsolete package again and keep the replacement driver installed. Enterprise-managed PCs may require an administrator to control driver deployment. |
Is Frmupgr.sys safe to keep?
The file’s documented role is legitimate Bluetooth DFU functionality, so its name alone is not evidence of malware. Its age and kernel-mode operation are the reasons Windows 11 may reject it under HVCI. Keeping it can preserve compatibility with an old Bluetooth device, but it also means Memory Integrity may remain unavailable. Removing it is reasonable when you no longer use that hardware or have a current replacement driver; keep a restore point because device functionality can change.
Quick Recap
Optional shortcut
Outbyte Driver Updater is an optional shortcut that scans more than 100 devices for outdated, corrupted or missing drivers, installs official drivers, shows current and recommended versions, and includes driver backup, restore and scheduled scans. It runs on Windows 11, 10, 8 and 7 and offers a 2-day free trial with no credit card before a subscription. It does not replace identifying the Frmupgr.sys package with PnPUtil, and results vary.
Key points to remember
- Frmupgr.sys is a legacy WIDCOMM/Broadcom Bluetooth firmware-upgrade component, not a generic Windows system driver.
- Windows 11 Memory Integrity can reject it because the old package is incompatible with HVCI.
- Find the actual published
oem#.infname on your computer; never copy the number from an example. - Use elevated
pnputil /delete-driver <Published Name> /uninstall /force, then restart and rescan Core isolation. - Prepare a current manufacturer driver or compatible USB Bluetooth adapter because removal can disable Bluetooth.
- Do not rely on manually deleting or renaming the SYS file as a substitute for removing its Driver Store package.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
