{"id":16036,"date":"2020-09-22T23:52:10","date_gmt":"2020-09-22T21:52:10","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=16036"},"modified":"2020-09-22T23:52:10","modified_gmt":"2020-09-22T21:52:10","slug":"windows-server-2016-workaround-fr-gpo-mmc-wsecedit-dll-fehler","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/09\/22\/windows-server-2016-workaround-fr-gpo-mmc-wsecedit-dll-fehler\/","title":{"rendered":"Windows Server 2016: Workaround for GPO-MMC wsecedit.dll error"},"content":{"rendered":"

[German<\/a>]Is anyone affected by the GPO-MMC wsecedit.dll error in Windows Server 2016 caused by security update KB4577015 dated September 8, 2020? There is a temporary workaround to prevent the crash. This can be used until a fix from Microsoft is available.<\/p>\n

<\/p>\n

Background to the GPO-MMC wsecedit.dll error<\/h2>\n

\"\"Cumulative update KB4577015<\/a>  was released by Microsoft on September 8, 2020 as a security update for Windows 10 1607 Enterprise LTSC. The update is also available for Windows Server 2016. I had mentioned the update briefly in the article Patchday: Windows 10 Updates (September 8, 2020). <\/p>\n

However, security update KB4577015 from September 8, 2020 causes problems on Windows Server 2016, which acts as domain controller. The group policy editor (gpedit.msc) throws a wsecedit.dll<\/em> error when loading an MMC snap-in when changing security options. The error occurs when trying to traverse the following path in Group Policy:<\/p>\n

Computer Configuration > Windows Setting > Security Settings > Local Policy > Security Options <\/p>\n

A gpedit.msc error message appears stating that an MMC snap-in cannot be loaded because a wsecedit.dll error has occurred.  <\/p>\n

\"gpedit.msc <\/p>\n

The hint to restart the Group Policy Editor or to ignore the error in the session does not help. The functions for customizing the security options can no longer be used (see my blog post Windows Server 2016: Update KB4577015 throws a GPO MMC wsecedit.dll error<\/a>). The bug has also be confirmed by users in the post GPMC error for \"Security Options\" after Updates 2020-09 in Windows Server 2016 Domain Controllers<\/a> in Microsoft's Q&A. <\/p>\n

A workaround for this bug<\/h2>\n

In this comment<\/a> Germanblog reader Mario Flohrer points out a workaround, a user has posted in Microsoft's Q&A thread GPMC error for \"Security Options\" after Updates 2020-09 in Windows Server 2016 Domain Controllers<\/a>. <\/p>\n

\n

The crash can be avoided by deleting the following registry key. Please make sure to export the reg key before deleting anything. Deleting the key will cause the \"Interactive logon: Display user information when the session is locked\" policy to not appear in the console. (The policy is still effective, but you can't see it in the UI to edit it). You will need to import the key back later, after the fix has been released. <\/p>\n

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SecEdit\\Reg Values\\MACHINE\/Software\/Microsoft\/Windows\/CurrentVersion\/Policies\/System\/DontDisplayLockedUserId<\/p>\n<\/blockquote>\n

So you should export the specified registry key (needed if a fix from Microsoft is available) and then delete the key. Then the error message will not appear. As soon as a fix from Microsoft is available, the key must be imported again. <\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Is anyone affected by the GPO-MMC wsecedit.dll error in Windows Server 2016 caused by security update KB4577015 dated September 8, 2020? There is a temporary workaround to prevent the crash. This can be used until a fix from Microsoft is … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[47,483],"class_list":["post-16036","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-issue","tag-windows-server-2016"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/16036","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=16036"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/16036\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=16036"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=16036"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=16036"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}