[German]After installing the June 2021 security updates, Windows 7 through Windows 10 (and server counterparts) may experience issues with applications accessing event logs on remote devices. Microsoft has made a corresponding entry in the Windows 10 status area for versions 2004 to 21H1.
This is caused by changes made to Windows to close the CVE-2021-31958 vulnerability. But there is a simple workaround. The whole thing affects all Windows versions (clients and servers) still in support that have the June 8, 2021 updates installed. From my point of view, the problem mainly affects administrators who need to access other machines and their event viewer with remote applications.
The problem: No remote access to events
Microsoft has posted a corresponding entry on the Windows 10 status page for version 2004, 20H2 and 21H1, indicating the problems with cumulative update KB5003637. It states:
After installing this or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
After installing this or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:error 5: access is denied
error 1764: The requested operation is not supported.
Windows has not provided an error code.
Microsoft states that this bug may occur due to security fixes because of the CVE-2021-31958 vulnerability in Event Tracing for Windows (ETW). Even though the support article only mentions cumulative update KB5003637 for Windows 10 version 2004 to 21H1, this issue affects all Windows versions listed below and thus their June 2021 updates.
- Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
The workaround Microsoft suggests is quite simple. The appropriate June 2021 security updates must be installed on all Windows machines. Once the appropriate update (e.g. KB5003637) is installed on both the local and remote machine, the error should be gone. The relevant updates are listed in subsequent articles.
Patchday: Windows 10-Updates (June 8, 2021)
Patchday: Windows 8.1/Server 2012-Updates (June 8, 2021)
Patchday: Updates for Windows 7/Server 2008 R2 (June 8, 2021)
Cookies helps to fund this blog: Cookie settings