Troubleshooting Common Issues When Upgrading to Windows 11

When a Windows 11 upgrade fails, start with the exact error, installation stage, current Windows build, and target release. Compatibility, storage, driver migration, and Windows servicing problems need different responses. A generic list of firmware changes and repair commands can create additional problems.

Check Firmware and Security Requirements Accurately

Windows 11 requires TPM 2.0 and UEFI firmware with Secure Boot capability, along with other hardware requirements. A firmware TPM implementation is not inherently inferior or ineligible: supported AMD fTPM and Intel PTT implementations can provide TPM 2.0.

Use PC Health Check and the manufacturer's specifications to identify the actual eligibility issue. Microsoft's TPM enabling guidance lists firmware options such as AMD fTPM and Intel Platform Trust Technology.

Do not require a separate TPM chip simply because the device uses firmware TPM. If firmware needs an update, use the exact manufacturer's supported package and procedure.

Back up data and secure the encryption recovery key before firmware changes. Do not clear the TPM, reset Secure Boot keys, restore BIOS defaults, or switch Legacy/UEFI mode as routine upgrade preparation. Such changes can affect encrypted drives and the existing boot configuration.

Manage Disk Space Beyond Minimum Requirements

The 64 GB requirement refers to the minimum storage-device capacity, not a requirement to have 64 GB free before every upgrade.

Setup needs additional working space, and the amount varies with the update, language resources, installed components, and rollback requirements. Follow its actual space request. A universal “20% extra free” rule is not an official requirement or a guarantee of success.

Review temporary-file categories before cleanup. Do not delete the only backup or previous-installation files without understanding the recovery consequences. If storage shows read errors or other failure signs, prioritize data recovery and hardware diagnosis before further write-intensive repairs.

Keep Hardware Eligibility and Safeguard Holds Separate

Passing PC Health Check does not guarantee compatibility with every application, driver, or target feature update. Review Microsoft's release-health page for that release.

If Windows Update is withholding an upgrade because of a safeguard hold, follow the documented resolution or wait for the supported offer. Installation Assistant or USB media should not be treated as a generic safe bypass.

On a managed device, check the organization's approved target version and update policy before changing anything.

Use Error Codes and Logs to Narrow the Cause

Record the complete error, including its extended code and the phase where the upgrade failed. A code such as 0xC1900101 commonly indicates driver-related rollback, but does not uniquely identify a storage controller or prove which driver is responsible.

Use Microsoft SetupDiag and relevant Setup logs where appropriate. SetupDiag analyses failures; it does not automatically repair every issue or always name a definitive culprit. Retain logs before cleanup removes them.

For a generic Installation Assistant error, follow the relevant troubleshooting guidance. Do not infer a specific disk or registry-permission defect from a code alone.

Handle Drivers and Security Software Deliberately

Review the devices or driver packages implicated by logs and compatibility messages. Obtain supported drivers from the PC or component manufacturer as appropriate. The newest generic package is not always the right replacement for an OEM-customized driver.

An absent Device Manager warning does not guarantee that a driver migrates correctly. Conversely, updating every driver indiscriminately can introduce unrelated changes.

Do not use Driver Verifier as a routine fix on a daily-use PC. Microsoft says it can cause crashes and is intended for testing and debugging. See the Driver Verifier documentation.

Security software can cause specific compatibility blocks, but universal antivirus removal is not required for every upgrade. If a named product is implicated, follow its vendor's supported update or removal procedure and the organization's policy. Verify protection is available afterward.

Do not attempt an upgrade in Safe Mode after disabling security tools as a substitute for resolving a block. Do not stop every security-related service to make Setup proceed.

Repair Servicing Components When the Evidence Supports It

For update failures, start with the Windows Update troubleshooter in Get Help and follow error-specific instructions.

If Windows component corruption is suspected, open an administrator Command Prompt inside the running Windows installation and run these separately:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Read each result. Successful repairs do not prove the upgrade will now succeed or that the original cause is gone. In recovery mode, these online commands do not automatically target the installed Windows system.

CHKDSK repairs logical file-system errors under the appropriate options; /r additionally examines sectors and attempts readable-data recovery. It is not a mandatory pre-upgrade scan and cannot repair defective hardware. Do not run intensive repair scans before recovering important data from a failing drive.

Distinguish Slow Progress from a Failed Installation

Some upgrade stages can remain at the same percentage for a considerable time. Keep reliable power connected and avoid forced shutdown based on a short arbitrary timeout.

When the normal desktop remains available, activity and logs can provide context, but disk activity alone does not prove Setup is progressing. During offline installation stages, Task Manager may not be accessible.

If Setup reports a failure or rolls back, retain the error and logs before retrying. A forced reboot followed by automatic SFC/CHKDSK is not a universal recovery sequence.

Choose the Right Installation Route

For a supported in-place upgrade with apps and files retained, run Setup inside the existing Windows installation and review the explicit keep options. Booting a USB is the clean-installation or recovery route, not the equivalent keep-apps upgrade.

Installation Assistant targets the current supported release and works on supported x64 configurations. It does not cure hardware incompatibility, a failing disk, or every Windows Update failure.

Keep Backup and Rollback Distinct

After a successful feature upgrade, Go back is normally available for a limited period, commonly 10 days, and requires retained rollback files. Setup's automatic rollback after a failed upgrade is a different mechanism. Neither is a substitute for an independent backup.

Review Microsoft's Go back guidance before relying on it. Check important files, apps, activation, and drivers after an upgrade, and retain the backup until the new installation is verified.

Change one relevant factor at a time. If the cause remains uncertain, provide support with the full error, setup stage, hardware model, and collected logs instead of repeating speculative firmware or security changes.