Windows 10 uses SMB1, 2 or 3?

lolcocks said:

Any idea if RedStone fixes this?

If not, I will have to manually enable SMB1 and 2 on all my devices.
Will this break anything such as slow speed issues or certain other devices not showing up?

Not that I have heard. The only thing about Redstone that I have heard is around 1200 changes, with a lot in a bad way.

After the last rollout which broke stuff on my test box, 10 got yanked and the discs destroyed. I am done playing with Microsoft and being their Beta tester.

From this point on, it is purely Linux in my house.

jimbo45 said:

Hi there

One problem I notice with SAMBA to W10 is that the Linux boxes while seeing W10 seem to get a strange message when you try and access the Windows C drive -- no problem with any other Windows share or the "Users" directory on the C drive.

Cheers
jimbo

I saw that also, until I disabled SMB 1 & 2 on my test box with 10. Once I did, all shares showed up on the 10 box and Linux boxes.

lx07 said:

If you mean C$ Administrative share then that is because of UAC. You could add a LocalAccountTokenFilterPolicy DWORD in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and set it to 1.

Access denied to Administrative (Admin) shares in Windows 8 - 4sysops

It has nothing to do with UAC. No Registry edit needed.

The Root of the file tree has always been locked down since 7. Only way in by share is to give the User control at that level, which is how malware takes over.