November 8, 2022—KB5020010

Redzuan @ ShariqPartners 1 Reputation point

Im having Windows server 2012 R2 as my DC/AD server, last Friday 11th Nov 2022 i have successfully installed the security update

After installing all of the PC that are connected to this Domain network is not able to connect, it displays as public network or just network, by right is should be our network "domain name".

I have uninstall this 5 sets of the updated as shown above and now its able to connect.

I need to get this update and i need assistance or guidance on the work around after i have installed the update, meaning what should i do to make it work after installing the update


Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,213 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Gideoney 446 Reputation points

    Domain issues are a known issue with KB5020010. Microsoft provides KB5020276 to help us solve this problem.

    For more details:


  2. Limitless Technology 44,101 Reputation points

    Hello there,

    This seems to be an known issue.

    After this update or a later Windows update is installed, domain join operations might be unsuccessful and error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" occurs. Additionally, text stating "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy" might be displayed.

    Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain.

    More info here


    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments

  3. Redzuan @ ShariqPartners 1 Reputation point


    1st of all thank you for your response, its a good read.... but unfortunately I'm not so sure what I need to do.

    Im not very good at this AD function, is there any quick resolve?


    0 comments No comments