Windows 10: Accessing default shares

Creating the DWORD LocalAccountTokenFilterPolicy was the method to enable hidden/default and administrative shares since Windows 7. However, in Windows 10, at least on my three computers, it doesn't work anymore. I create this DWORD by default on any new Windows installation, but in Windows 10, doesn't seem to be enough. The computers are visible on the network, but the hidden shares are not accessible. I'm very surprised it's working for you.

 

That's strange because here it's working just fine as you can see

 

True. You need to add 2 more entries in the registry as shown:
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "LocalAccountTokenFilterPolicy"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters] "AutoShareWks"=dword:00000001 "AutoShareServer"=dword:00000001[/quote] NOTE: You might also have to disable UAC

 

Sounds like the same sort of problem in this thread in "Network and Sharing"?


Is it possible to Share a Windows 10 machine on a WorkGroup

 

guys,
Windows10 uses "SMB over IP" rather than "NBSTAT over IP", SMB is using port 445. But MS also changes the behavior. Not using 445<>445, but 445<>Dynamic Client port.

you must add or alter the firewall rule to accept 445 requests to dynamic ports!

Thanks to Redmond!


Thanks to Microsoft.

 

Hi there

this doesn't always work -- I've had problems even with firewall totally disabled. Sometimes W10 computers can see other computers in the network, sometimes they can't --seems to be unpredictable and even when you have 2 seemingly identical machines one works fine and one doesn't.

Never had this problem on W7 or XP. Networking though IMO is still a TOTAL HOSEUP on any Windows system. If it works - breathe a sigh of relief --if it doesn't you can try 2,000 zillion different things and it sometimes STILL doesn't work. It's a total crap shoot IMHO.

Cheers
jimbo

 

I'm having a similar issue as the OP, only I'm trying to connect to the admin shares from win10, to Win7.

When I do this from Win7 to Win7, there are no issues whatsoever, when I do it from Win10, I get Access Denied.

-No computers are using Homegroup.
-both computers have the same user as admin; so, I'm logged in win10 with the same username and password, this user existing in Win7 as an admin
-both computers are in the same workgroup
-**when connecting and get a Access Denies, I try to connect using other credentials and use Win7computername\username and the password (this username and password are the same ones I'm logged in to the Win10 computer)
-I have disabled the Firewall on Win10 to make sure no ports are blocked.

**note that when it's Win7 to Win7, I don't need to specify the username as othercomputername\username, as long as it's the same username and password, connecting to admin shares works immediately.

It's very obvious that MS has screwed things again with no explanation.

Incidentally, if I go to my Win7 computer, and I connect back to the win10 admin shares, it works just fine with the same username/pwd I'm trying above, with or w/o firewall enabled on Win10

This is such a PITA, hopefully someone has some sort of resolution...

 

Well, I did find a solution that worked for me as described earlier in this thread but guess you already tried that to no avail since you're asking?

 

Did not work. That solution is for a Win10 machine that you are trying to connect TO, not connect FROM. If I connect from Win7 to Win10, it works (admin shares), if i try from Win10 to Win7, it doesn't work.

If it's win7 to win7, again, works just fine.

 

Ah, sorry...didn't read close enough.

 

I'm not looking forward to the hardware challenges that are probably going to hit me in the near future:

I'm upgrading the old WRT54 that I've probably had for 20 years, replacing it with a dual WRT1900ac system in Master/Bridge mode, to insure best operating speed for both Wifi and streaming video around the house.

Oh, left out a little detail - The machines I'm attaching are a Win10, Win7-SP1, WinXP-SP3, Win95 and Win98se. The XP and 95 machines are laptops (Dell D820 w/XP, Toshiba XT Portable w/ISA slot w/95).

The Win10 is not here and online yet. All of the other above machines are peacefully coexisting on the network. I actually spent tonight putting in a Gigabit/100/10 card and a Belkin USB2.0/4port USB card in the Win98se machine in order to backup trade/audio tracks recorded in the studio using the 98se machine in DOS mode w/proprietary software that requires two ISA slots for studio interface.

At this point I can transfer files willy-nilly among all of the machines, and the music studio is a dream to work with.

So the idea of getting that "FREE" copy of Win10 for my current project (Win8 machine) and pushing it to the network is a bit scary. I'm hoping to downgrade the Win10 networking to a NetBEUI or pure IP machine client.

Thanks to you guys for the posts and the information. I'm writing copious notes to hopefully head off the future "elephant in the room."

Rick

 

Well I guess that Redmond screwed us a bit here. I was looking for the same issue all the web-round with no clear solution. But I got this workaround that might help others. RDP!! As long your "controlled" PC has a WIn10 Pro. Your "controlling" PC might be a Win 10 Home. Do not forget to enable remote access on the controlled PC and do not forget to check local resources. Drives in this case particularly. That's it. I know, I know, it's not what was asked in the first place, but might be a workaround for someone.

Cheers, D.

 

You can try this... A small registry hack is all it takes to get around the issue by creating a policy manually that overrides the default setting. Do this on the server that has the shares you want to access remotely:

• Click the Windows Start icon and search for “regedit”. Right-click and select “run as administrator”.
• Expand the tree to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft\ Windows \ CurrentVersion \ policies \ system.
• Create a new key (Right click -> New -> choose “DWORD Value (32bit)”).
• Name the key LocalAccountTokenFilterPolicy and give it the value of “1”. Click OK. (refer below pic)
  
  
• Reboot the server to enable the setting to take effect.
• Now when you try to access the administrative shares on the remote computer, it should magically work.

Pl reply if it works for you.

 

jimbo i totally agree with you.
I have tried zillions of fixes but none has worked for me yet. The anniversary update done something to my computer that broke the communication and MS will not admit it.
I just have to wait patiently until a fix works *Sad

cheers

 

Ok, sunday morning - just took some time to figure this out for myself, as I had the same problem. Since I switched to 2x Win10 machines (let's call them "A" and "B"), I can't access the default share on A from B anymore... Note that currently I dont have on both machines the same account (name & password), but both accounts have admin rights. When I try to access the default share on A from B like "\\A\c$", the popupbox shows up where I have to provide my account from machine A. As discussed here, I also had the "Access denied" problem... So (as already discussed here too) I tryed editing the registry and adding "LocalAccountTokenFilterPolicy" to HKLM... But actually on my machine B that entry was already there... on another forum somebody wrote, that on 64bit machines it should be QWORD instead DWORD (tryed that too, but didn't help). I just found the solution on this Website: "How To Enable Remote Access To Administrative Shares in Windows 10" and now it's clear why this thread here never got closed: I had to add that registry key on Machine A (and NOT on machine B)! While on machine B that key was already there, interestingly on machine A it wasnt... However, I just added "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\LocalAccountTokenFilte rPolicy" DWORD Value 1 on machine A (even A is a Windows 10 64bit machine, I did add DWORD and not QWORD) and after that rebootet A. Et voila - I can now access the default share on A from B.

Cheers,
Alen