Bug DirectAccess corrigé par Microsoft - Novembre 2022

Microsoft fixed a bug!

Microsoft fixed a connectivity issue that affected DirectAccess users on Windows. Let’s take a look at this bug.

As a reminder, DirectAccess is a feature available in Windows that allows you to connect remotely to an infrastructure, without directly using a VPN since this solution is used on the same principle.

Because of this bug, DirectAccess does not automatically reconnect when there is a network outage on the Windows machine connected in DirectAccess. Yet this is the very interest of this solution. For example, if there is a loss of connectivity between your PC and your WiFi network, DirectAccess does not escalate the connection because of this bug.

Microsoft specifies that DirectAccess is the only solution concerned, this means that this problem does not affect VPN or Always On VPN connections from Microsoft.

Microsoft “opened a ticket” for this bug on November 13, 2022 but it would be related to the out-of-band update released in mid-October (KB5019509). From now on, Microsoft fixed this bug in DirectAccess through the feature Known Issue Rollback (KIR) de Windows. Thanks to this patch which is pushed automatically on the machines, the problem will be solved. To speed up deployment, Microsoft recommends rebooting the machine to allow it to pick up the fix.

The following Windows versions are affected by this bug:

  • Windows desktop : Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
  • ​Windows Server : Windows Server 2022; Windows Server 2019

For more information, you can consult this page on the Microsoft site.

Currently, Microsoft is investigating another problem related to Active Directory and more specifically Kerberos authentication. To know more, you can read this article.


Logiciel – OS,Microsoft,Windows,

#Microsoft #fixed #bug

Leave a Comment

Your email address will not be published. Required fields are marked *