Can’t connect to C$, ADMIN$ or any administrative share on workstations 20

If you are attempting to access a Windows 7, Windows 8, Vista or Server 2008 (R2), Server 2012 (R2) computer you may get  the” Access Denied – Failed to connect to ADMIN$ share” error , even when supplying the appropriate local user credentials that have Administrator access. If the target computer is not a member of a Windows 2003 or later Domain then this is most likely because the target system has Remote UAC enabled. Remote UAC prevents local administrative accounts from accessing ADMIN$. (more appropriately Remote UAC prevents local accounts from running in an elevated mode when connecting from the network) If you need to be able to access the ADMIN$ using a local account then you will need to disable Remote UAC. You can accomplish this by editing the registry.

Assuming you have all your other ducks in a row (Firewall exceptions, appropriate credentials of local administrative user, etc) then you just need to add a quick entry in the registry of the target computer. In the registry, navigate to


Create a DWORD value called LocalAccountTokenFilterPolicy and assign it a value of 1.

You then can restart the Server service (but a reboot would be ideal ;-)).

cant't connect to admin$ or administrative share


* By default, when local credentials are used to access a Windows Vista (or later) system that is a member of a Windows Domain this problem does not exist. Your Windows domain may still disable Remote UAC.

** By default Remote administrative access is denied to local accounts when a Windows Vista (or later OS) is NOT a member of a Windows 2003 or later domain.

Microsoft info:

20 thoughts on “Can’t connect to C$, ADMIN$ or any administrative share on workstations

  1. Reply JohnBoyBilly Jun 4,2014 10:08 pm

    Ah. This fixed my problem. Thanks man

  2. Reply Greg N. Jun 5,2014 5:35 pm

    Thanks Stephan, this worked great! I had built an MDT/WDS on Server 2012 R2 and devices where not able to connect to the Deployment Share and display a Task Sequence. An error message noted a possible credential issue, which was weird because that information is correctly baked into the bootstrap.ini settings.

    After adding the registry entry and restarting the Server service, the networked PCs connected and deployments got rolling.

  3. Reply Stephan Wibier Jun 6,2014 10:03 am

    good to hear that this was helpful!

  4. Reply Paolo Jun 26,2014 12:25 pm


  5. Reply Alejandro Diaz (@alex_alex_alex_) Jul 25,2014 8:50 pm

    Excelente funciona en Windows Server 2012

  6. Reply Rich Mattiuzzo Feb 3,2015 7:14 am

    This issue was killing me. Thanks a ton for posting this.

  7. Reply Mohammed Gayas Feb 18,2015 7:31 am

    thanks a lot its help me. I was struggling with issue from last two days. Many thanks Stephan

  8. Reply Paul Hill Sep 1,2015 10:20 pm

    NICE. worked for me. Was getting veeam error “tr: Failed to create persistent connection to ADMIN$ shared folder on host ”

  9. Reply veera Dec 2,2015 2:14 am

    Thanks Stephan for the tip. It solved my problem.

  10. Reply Vatche Dec 12,2015 5:03 pm

    Are there any other options if this not worked.?

  11. Reply destrud0 Aug 2,2016 5:25 pm

    Thanks for the tip. I was totally lost

  12. Reply Blixkin Entopop Dec 15,2016 8:16 pm


  13. Reply Nahuel Feb 14,2017 9:31 pm

    Thanks man you save my as% XD really was very helpfull

  14. Reply Paul Mar 2,2017 6:55 pm

    Even easier than restarting the Server service or rebooting run GPUpdate from an admin command prompt.

  15. Reply Lukasz Apr 12,2018 11:22 am

    Hi, server restart is required?

  16. Reply prajeethpj2 Sep 24,2018 3:03 pm

    Hi Stephan
    I tried your tip. after restart still i cannot access the \\c$
    any advise.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.