If you see “System found unauthorized changes on the firmware, operating system or UEFI drivers,” it means your computer’s Secure Boot detected a file that wasn’t signed by a trusted key during startup. The fix is usually to update your BIOS/UEFI, disable Secure Boot temporarily, or reset the TPM—but first, you need to identify which component triggered the warning.
What Triggers This Warning
This message appears on Windows 10 and 11 PCs when Secure Boot—a UEFI security feature—verifies the digital signatures of boot components. If any file fails verification, the system halts to prevent potentially malicious code from loading. Common triggers include:
- Outdated UEFI firmware with a bug that misidentifies valid drivers as unauthorized.
- Recently installed hardware like a new SSD or graphics card whose option ROM isn’t signed.
- A Windows update that modifies boot files or the TPM (Trusted Platform Module) state.
- Overclocking or undervolting settings that alter the boot environment.
- Third-party security software that hooks into the boot process.
The warning is a safety measure, not a guarantee of malware. In many cases, it’s a false positive caused by a firmware bug or a legitimate driver update.
How Secure Boot and UEFI Work
UEFI (Unified Extensible Firmware Interface) replaces the old BIOS. It initializes hardware and loads the OS. Secure Boot is a UEFI protocol that checks each boot loader and driver against a database of approved signatures stored in the firmware. If a signature is missing or invalid, the boot process stops and you see this exact message.
The TPM (Trusted Platform Module) is a separate chip that stores cryptographic keys. It works with Secure Boot to ensure the OS hasn’t been tampered with. Windows uses TPM for features like BitLocker and Windows Hello. When the TPM detects a change (e.g., a firmware update), it may invalidate the current boot state, causing the warning.
Step-by-Step Fixes
Try these in order. Each step is safe and reversible, but back up important data before changing firmware settings.
- Restart and check for pending updates. Sometimes the warning appears after a Windows update that didn’t finish. Go to Settings > Update & Security > Windows Update and install any pending updates, then restart.
- Update your motherboard’s UEFI/BIOS. Visit your motherboard or PC manufacturer’s support page, download the latest firmware, and follow their instructions. This often fixes false positives.
- Reset the TPM. In Windows, open the TPM Management console (tpm.msc), click “Clear TPM,” then restart. This resets the TPM keys but may require you to re-set up BitLocker or Windows Hello.
- Disable Secure Boot temporarily. Enter your UEFI settings (usually by pressing Del, F2, or F12 during startup). Find Secure Boot under the Boot or Security tab, set it to Disabled, save and exit. If Windows boots normally, the issue is likely a driver or firmware bug.
- Check for a new driver or hardware. If you recently installed a new component, remove it and see if the warning disappears. If it does, check for a firmware update for that component.
- Run a system file check. Boot into Windows (if possible), open Command Prompt as administrator, and run
sfc /scannowto repair corrupted system files.
If none of these work, the warning may indicate a genuine security issue. In that case, run a full antivirus scan and consider reinstalling Windows.
Common Misconceptions
Many users assume this message means their PC is hacked. That’s rarely the case. The warning is a generic message that appears for any Secure Boot verification failure, including benign ones like a new keyboard driver. Another misconception is that disabling Secure Boot is dangerous—it is safe for most users, but it reduces protection against boot-level malware. Also, some believe that resetting the TPM will erase data; it doesn’t, but it may require you to re-enter recovery keys for encrypted drives.
When to Seek Professional Help
If the warning persists after trying all steps, or if you cannot boot into Windows at all, you may need to:
- Use a Windows installation USB to access Advanced Startup options and run Startup Repair.
- Check if your motherboard has a CMOS clear jumper—this resets all UEFI settings to default.
- Contact your PC manufacturer’s support. They may have specific firmware patches.
If you’re not comfortable changing firmware settings, a local repair shop can do it safely.
Preventing Future Occurrences
To reduce the chance of this warning recurring:
- Keep your UEFI firmware and drivers updated.
- Avoid installing unsigned drivers, especially for older hardware.
- If you overclock, test stability—some unstable settings can trigger the warning.
- Regularly back up your TPM recovery keys if you use BitLocker.
Frequently Asked Questions
Will I lose data if I clear the TPM?
Clearing the TPM does not delete your files. It resets the cryptographic keys used for encryption and security features. If you use BitLocker, you’ll need your recovery key to access the drive after clearing.
Can I ignore this warning and continue?
No. The system will not continue until you address the issue. You can either fix the cause or disable Secure Boot, but ignoring it means you can’t boot.
Is it safe to disable Secure Boot permanently?
For most home users, yes. Secure Boot protects against certain types of malware, but if you don’t install untrusted software, the risk is low. Some games or hardware may require it disabled.
Why does this happen after a Windows update?
Windows updates sometimes modify boot files or update the TPM state. If the update isn’t signed correctly or conflicts with an existing driver, Secure Boot flags it. Usually, restarting or updating again fixes it.
Does this warning mean I have a virus?
Not necessarily. It means a boot component didn’t pass signature verification. It could be a virus, but it’s more often a firmware bug or driver issue. Run a reputable antivirus scan to be sure.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Set a Google Play Budget & Stop Accidental Purchases
- Destiny 2 Error Code Anteater: Fixes & Causes
- View Android Photos on Chromebook: Step-by-Step
- Fix Windows Could Not Prepare the Computer to Boot
- Windows 11 Security Settings: Best Config Guide
- Install Custom Recovery on Samsung Galaxy Trend