Let’s understand how to fix FIX This PC can’t be upgraded to Windows 10 version 2004 or 20H2 issue. Microsoft recently resolved an issue where you might encounter an update compatibility hold and receive the message “This PC can’t be upgraded to Windows 10. Your PC settings need to be adjusted before upgrading to the latest version of Windows 10” when you are trying to upgrade to Windows 10 version 2004 or version 20H2.
This issue only affects devices during the upgrade to Windows 10, version 2004 or Windows 10, version 20H2 in which any of the local Administrator or Guest accounts have been renamed. It is mainly caused by duplicate built-in user accounts (Administrator or Guest) being created with the same security identifiers (SIDs) and relative identifiers (RIDs).
After updating to Windows 10, version 20H2, you also might receive an error with “Your PC will automatically restart in one minute” when trying to access the sign-in options or users MMC snap-in. To safeguard the update experience, Microsoft had applied a compatibility hold on these devices. Adam Gross, Microsoft MVP, has also recently Tweeted about the same update.
Let’s know about Safeguard holds – Safeguard holds prevent a device with a known issue from updating to a new version of Windows 10. Microsoft uses quality and compatibility data to identify issues that might cause a Windows 10 feature update to fail or roll back. When Microsoft find such an issue then might apply holds to the updating service to prevent affected devices from installing the update to ensure users have a successful experience.
Resolution – Fix This PC can’t be upgraded to Windows 10
Let’s check what is the resolution/This PC can’t be upgraded to Windows 10. This issue is now resolved and the safeguard hold has been removed when devices are using the latest feature update bundles and refreshed Windows 10 ISO. You should only receive the safeguard hold if you are using outdated feature update bundles or media.
As per Microsoft’s latest update, Feature update bundles released December 3, 2020, or later will resolve this issue when deploying Windows 10 servicing upgrade using ConfigMgr. It can take up to 48 hours before you will be able to update to Windows 10, version 2004, or version 20H2.