Share via

Enable and Connect to Administrative Shares on Windows 10

Question

Wednesday, August 23, 2017 8:23 PM

Hi,

I'm trying to get administrative share up and running on Windows 10. I took the exact same steps as I did for Windows 7, but those don't seem to work. I also followed the steps in this post:

https://social.technet.microsoft.com/Forums/en-US/fb5518e8-67ea-43fc-a2e6-cca935c123b1/how-to-enable-administrative-shares?forum=win10itprogeneral

...but they didn't have any effect. The Windows Firewall allows exceptions for file and printer sharing. The admin shares are present in the MMC.

What else can I try?

Jason

All replies (16)

Thursday, August 24, 2017 2:42 AM

Hi Jason, 

Did you mean that you cannot access Administrative share even you got all share configured properly? Any error message when you try to access? What' the OS version you try to access from?

All detailed steps in this article have been done, right? Make sure to create password for build-in administrator account which was enabled, and enable policy for LocalAccountTokenFilterPolicy. 

https://www.repairwin.com/enable-admin-shares-windows-10-8-7/

Would you please let me if you can access general share on this Windows 10 PC both with IP and UNC path?

If all shares don't work on Windows 10 PC, we can also consider the SMB issue. 

Try run following powershell commands to configure SMB: 

Set-SmbClientConfiguration -RequireSecuritySignature 1

Answer Y when prompted to confirm the modification.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force

*Set-SmbServerConfiguration -EncryptData $true -RejectUnencryptedAccess $false *

Let me know if there is any update.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, August 24, 2017 1:28 PM

The odd thing is that there is no error message. The connection just doesn't happen. I can ping the target host, RDP into it, but not connect through an SMB share. Nothing happens... Weird...

Jason

Friday, August 25, 2017 9:25 AM

Have you tried what I suggested in my last post? Did they fix your issue?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Saturday, August 26, 2017 1:18 PM

Hi,

I did give your suggestions a try, but had no luck. Apologies for the late follow-up.

Jason

Tuesday, August 29, 2017 9:50 AM

Hi Jason, 

Would you please let me if you can access general share on this Windows 10 PC both with IP and UNC path?

On the other PCs, can you ping the Windows 10 on which you enable the administrative share?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, August 29, 2017 12:32 PM

I can access no shares on any of the Windows 10 PCs.

\IP_Address or \Hostname yields nothing

PINGs work just fine.

Thanks

Jason

Wednesday, August 30, 2017 9:26 AM

Hi,

Please install Samba support in Windows 10, do as follows:

  1. Open Control Panel (by clicking on the Start button and typing in Control Panel, then click the App).

  2. I use Classic View, in which case click on "Programs ansd Settings". If you use the standard view, I'm afraid you need to find it yourself. Fairly easy.

  3. In the left panel, click on "Turn Windows features on or off".

  4. If the Security dialog box appears asking for your OK, give it the OK.

  5. The "Windows Features" dialog box appears.

  6. Scroll down to "SMB 1.0/CIFS File Sharing Support" and tick the box. This installs the Samba support.

  7. Reboot once it finishes and you should be able to see your PCs and folders on the network. 

Check the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Set restrictanonymous = 1

See it you can get this issue fixed.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, September 1, 2017 6:30 AM

Hi,

Have you had time to check my suggestions? If there is anything unclear, please post back for further help.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, September 6, 2017 5:26 AM

Is there any update on this issue? If so, please post back here.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, September 6, 2017 5:57 PM

I cannot enable SMB v.1.0 per security policy. We just finished disabling it network-wide. 

Jason

Friday, September 8, 2017 2:22 AM

Well, to find the root cause, would you please help to collect network traffic when reproducing this issue? Upload the saved files onto OneDrive and share the link here for our research.

Network monitor:

https://technet.microsoft.com/en-us/library/cc938655.aspx?f=255&MSPPError=-2147217396

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, September 8, 2017 5:22 AM

I cannot enable SMB v.1.0 per security policy. We just finished disabling it network-wide. 

Jason

  And you didn't think to mention that in your original post? I would have suspected that was relevant.

Bill

Wednesday, September 20, 2017 6:34 AM

Hi Jason

You are right, SMB v1.0 does have gaping security holes.  However the Computer Browser service depends on SMB v1.0.  When Microsoft deprecated SMB v1.0 they decided that we don't need the Computer Browsing service any more and did not upgrade it to work with the more secure protocols available now.  Please see this explanation from Microsoft:

SMBv1 is not installed by default in Windows 10 Fall Creators Update 2017 and Windows Server, Semi-annual Channel

There are numerous posts in the forums lately that relate to this.  People who are having problems seeing shares, browsing resources, performing a net view in a workgroup, adding a printer, accessing shared storage devices.  The standard response from Microsoft support staff has been to tell them to ensure SMB 1.0/CIFS File Sharing Support is enabled and if not, enable it.  They rarely seem to mention the security reasons behind having it switched off!

Good luck...

Friday, September 22, 2017 3:14 AM

Hi Jason, how did you get on?  I'd be interested to know how you resolved it for your situation.

Wednesday, February 21, 2018 7:22 PM

I FINALLY found the solution to this thanks to the following article:  http://www.tomsitpro.com/articles/windows-10-administrative-shares,2-47.html

I had been able to connect to regular (non-administrative/hidden) shares but not to an administrative share like C$ when the computers are in a Workgroup.

After creating the new DWORD as described in the article, I was suddenly able to connect to c$.

Thursday, July 5, 2018 5:10 PM

I had to uninstall Hyper-V on my computers, something broke in the last years. After that my c$ shares works on all my computers.