{"id":16087,"date":"2020-09-25T11:05:41","date_gmt":"2020-09-25T09:05:41","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=16087"},"modified":"2020-09-25T11:05:41","modified_gmt":"2020-09-25T09:05:41","slug":"windows-server-2016-microsoft-besttigt-bug-im-gruppenrichtlinieneditor","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/09\/25\/windows-server-2016-microsoft-besttigt-bug-im-gruppenrichtlinieneditor\/","title":{"rendered":"Windows Server 2016: Microsoft confirms bug in Group Policy Editor"},"content":{"rendered":"

[German<\/a>]Security update KB4577015, released September 8, 2020, causes a wsecedit.dll<\/em> error in GPO-MMC on Windows Server 2016, rendering the Group Policy Editor unusable.  But there is a temporary workaround to prevent the crash and Microsoft has admitted the bug in the meantime. <\/p>\n

<\/p>\n

The bug in GPO-MMC <\/h2>\n

\"\"I've addressed the bug within my blog post Windows Server 2016: Update KB4577015 throws a GPO MMC wsecedit.dll error<\/a>. Administrators who install the security update KB4577015 from September 8, 2020 on Windows Server 2016 get a problem. The Group Policy Editor (gpedit.msc<\/em>) 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<\/em> 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 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. There is now a fresh entry GPMC error for \"Security Options\" after Updates 2020-09 in Windows Server 2016 Domain Controllers<\/a> in Microsoft's Q&A. There several users confirmed the error description. There I had also left a comment about the issue reported from several of my blog readers. <\/p>\n

Microsoft confirms the error<\/h2>\n

The colleagues from Bleeping Computer spottet<\/a> that Microsoft has confirmed this bug on the status page for Windows 10 version 2016 and Windows Server 2016<\/a>. There it says:<\/p>\n

\n

Unable to access Security Options section in Group Policy Management Console<\/b> <\/p>\n

Accessing the Security Options data view in the Group Policy Management Editor (gpedit.msc) or Local Security Policy Editor (secpol.msc) might fail with the error \"MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC\" or \"MMC cannot initialize the snap-in\". This occurs from the MMC window, when the console tree is expanded in the following sequence: select Computer Configuration, then Policies, then Windows Settings, then Security Settings, then Local Policies, then Security Options. <\/p>\n

The resulting error dialog provides options to continue using the Management Console to view other nodes normally. Note<\/strong>: This issue does not affect the application of the Security Options or any other Group Policy Objects (GPOs) to devices in your environment. <\/p>\n

Affected platforms:<\/strong> <\/p>\n