|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
After updating to 20H2, if you try to edit a user’s permissions using Computer Management as soon as you click on “user” to choose the user to edit, the cursor shows “working” and shortly after the system will request to restart.
“A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000374. The machine must now be restarted”
The system reboots after 1 minute.
It seems an old bug has been reintroduced.
Thought I’ve posted it already here – but probably got lost. I’ve summarized that within the blog post: Windows 10 20H2: lsass.exe crashes (Oct. 2020) a few days ago. Then I forwarded the links to Microsoft’s social media teams responsible for Windows Update and WindowsITPro, and I’ve escalated a MS answer case to all MS moderators and asked to forward the case to developers. But I haven’t any feedback.
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
Cause
After upgrading 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.
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.
Workaround
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 receive 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 you have installed newer drivers or have performed the workaround above.
That value of “2010” may not work any more. I was testing the other day with a fully updated (including the November updates) version of W10 Pro x64, and I wasn’t offered the 20H2 update with the TargetReleaseVersion value set to “2010” nor to “2009”, I had to set it to “20H2”.
For the purposes of the testing, I wasn’t clicking on “Check for Updates” but was using wushowhide instead. The 20H2 update didn’t show up in wushowhide unless I changed the Feature Update value to 20H2. As mentioned in the paragraph above, no other value produced the 20H2 Feature Update in wushowhide.
For further information, I didn’t change the number I have set for Feature Update deferral days, since that setting is overridden by the Feature Update version setting.
Also, I noticed that the title has now changed in GPEdit to “Select the target Feature Update version” from what it was before.
All this on Windows 10 Pro x64 version 2004 build 19041.630. 🙂
try installing the KB4592438 update (build 19042.685) and reboot to see if the lsass.exe problem is fixed or not
Microsoft now claims this lsass.exe issue in 20H2 has been “resolved”
appears to be fixed using refreshed 20H2 install media with at least build 19042.631 or greater
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
