After updating to Windows 10, version 20H2, you might receive an error when accessing the sign-in options or users MMC snap-in

Applies to: Windows 10, version 20H2, all editionsWindows 10, version 2004, all editions


If you are trying to update to Windows 10, version 2004 or Windows 10, version 20H2, you might encounter an update compatibility hold and receive the message, "This PC can't be upgraded to Windows 10. Your PC settings aren't supported yet on this version of Windows 10. Windows Update will automatically offer you this version of Windows 10 when these settings are supported."

screenshot of safeguard hold dialog


After updating to Windows 10, version 20H2, you might receive the error in LSASS.exe with the text "Your PC will automatically restart in one minute" when interacting with any dialog window that lists users, for example accessing the sign-in options settings app page or the users folder in the Local user and groups MMC snap-in. This issue only affects devices in which any of the local built-in accounts have been renamed, such as Administrator or Guest. You might also receive an error in the Application Event log with Event ID 1015 that LSASS.EXE failed with status code C0000374. C0000374 is related to heap corruption.

This issue is caused by duplicate built-in user accounts being created with the same security identifiers (SIDs) and relative identifiers (RIDs) during the update to Windows 10, version 20H2. SIDs and RIDs for built-in user accounts are well-known as documented here and must be unique on a given device.

To safeguard your update experience, we have applied a compatibility hold on these devices from installing or being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard IDs is 30103339.


 If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options

To prevent the issue and not recieve the safeguard hold, you will need to name all built-in user counts back to their default name before attempting to update to Windows 10, version 2004 or Windows 10, version 20H2.

Next Steps

We are working on a resolution and will provide an update in an upcoming release. In the coming weeks, we will also provide updated bundles and refreshed media to prevent the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.