Active Directory Users and Computers, dsa.msc

Andrzej Wysocki 26 Reputation points


What could cause dsa.msc, the Active Directory Users and Computers snap-in, to start after 5-10 minutes? It cannot be opened. Windows Server 2019 fixes?
I request information.

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,824 questions
{count} vote

5 answers

Sort by: Most helpful
  1. Daisy Zhou 18,701 Reputation points Microsoft Vendor

    Hello @Andrzej Wysocki ,

    Thank you for posting here.

    To better understand the question, please confirm the following information at your convenience.

    1.Based on "What could cause dsa.msc, the Active Directory Users and Computers snap-in, to start after 5-10 minutes?", did you mean you can open ADUC, but every 5-10 minutes, ADUC will be automatically start again?

    2.Based on "It cannot be opened.", what error message did you receive when you open ADUC?

    3.Does this issue appear as soon as the new domain control is promoted? Or is the domain controller able to work normally after being promoted, but this problem suddenly appeared one day?

    4.Have you made any change before the issue occurs?

    5.Can you open other AD tools(such as AD site and services or AD domains and trusts) on this DC?

    Meanwhile, please check if any third-app/third-service caused the issue. You can perform a clean boot on this DC, then check if the issue persists.

    How to perform a clean boot in Windows

    Hope the information above is also helpful.

    Should you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  2. Andrzej Wysocki 26 Reputation points

    Thank you for your response

    1. The Active Directory Users and Computers snap-in takes a long time to start. It takes more than 5 minutes. It opens up. Reading account properties takes a long time, etc. You can work on it, but it takes a long time to perform tasks on it.
    2. It shows no error. It opens but after a while.
    3. Everything worked fine. The domain controller was working fine. I don't know if this happened after system updates.
    4. Working at AD
    5. Yes I can open other entrees. They work normally.

  3. Andrzej Wysocki 26 Reputation points


    Thank you for your response.

    yes only one DC,

    yes, only the Active Directory Users and Computers snap-in and Active Directory sites and services open badly. Very long. DNS, DHCP, etc. open well.

    I did a clean boot. The problem is the same. The starters take a long time to run.

    Updates broke it. Was well. What to do? Help? It is impossible to work.

  4. Andrzej Wysocki 26 Reputation points

    The problem is that I don't know which KB it is: - (((

    Thank you.

  5. dale titley 1 Reputation point


    This issue is likely due to the way that DNS is being handled by the application, and can likely be resolved by running dsa.msc while specifying the DC you are connecting to via IP as below:

    runas /profile /env /user:domain\username "mmc %windir%\system32\dsa.msc /server=yourDomainControllersIPaddress"

    This will launch ADUC without needing to resolve your DC's hostname through DNS and should resolve the latency issues.


    0 comments No comments