Share via

January 2022 Cumulative Updates break Active Directory Users and Computers

Anonymous
2022-01-24T23:45:51.333+00:00

2022-01 Cumulative Updates for Windows 10 causes an error when changing from our Parent domain to our Child domain. We receive this error: "Active Directory Domain Services: the domain could not be found because: the user name or password is incorrect" We found that if we remove the 2022-01 cumulative updates and reboot that the issue is resolved. This is happening on Windows 10 20H1, 20H2, 21H1, 21H2, and Windows 11. Is there another way we can resolve this without having to remove the Jan 2022 cumulative updates?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,919 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Luca Bassi 21 Reputation points
    2022-01-26T11:39:38.35+00:00

    Hi all,

    i've the same problem crossdomain.

    I have to uninstall the january security patch to resolve the issue.

    any fix?

    thanks

    0 comments
  2. Martin Presumido Szymczak 1 Reputation point
    2022-01-31T07:31:01.033+00:00

    I have exactly the same problem! Waiting for a fix!

    0 comments
  3. Stan Cooper 1 Reputation point
    2022-02-11T13:28:41.997+00:00

    I just found a work-around here: https://community.spiceworks.com/topic/2250881-rsat-active-directory-users-and-computers

    When you open AD Users and Computers connected to your primary domain, right-click the domain and instead of Change Domain, select Change Domain Controller and under "Change to" select This Domain Controller and click where it says "Type a Directory Server name"

    In there, type the fqdn or IP Address of the child domain DC and hit Enter and OK. You'll receive a message that the DC is in another domain and "Do you want to manage that domain?" Select Yes and you will be connected to the child domain.

    If you want to go back to your primary domain, right click on Active Directory Users and Computers at the top and select Change Domain. Select your primary domain and you're there.

    The janky part is that it won't remember the domain controller, so every time you change domains you have to go through the steps of typing the fqdn or IP Address of the domain controller. It's at least a work-around.

  4. Michael Leefers 1 Reputation point
    2022-03-04T17:07:08.68+00:00

    Hey everyone,

    We had the same issue when using cross-domain accounts. We identified the problem as one of our security policies applied to our systems in conjunction with our trust configuration.

    Policy
    Network security: Configure encryption types allowed for Kerberos

    Settings
    DES_CBC_CRC Disabled
    DES_CBC_MD5 Disabled
    RC4_HMAC_MD5 Disabled
    AES128_HMAC_SHA1 Enabled
    AES256_HMAC_SHA1 Enabled
    Future encryption types Enabled

    Our solution was to update our Domain Trusts with "The other domain supports Kerberos AES Encryption"
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain

    0 comments