Windows 10: Build 10041 Samba doesn't show C drive properly !!!!

Hi there

3 Linux servers with different distros seem to be unable to read the C drive directory properly on a new Windows 10041 (Real) machine.

Seems to be NO problem in accessing the other shared drives on the computer. This problem only seems to be when SAMBA wants to access the computer (Windows to Windows works OK even a windows 10 VM on the Linux HOST to a real W10 machine).

Cheers
jimbo

:)

 

Storage Sense not working on second drive

UPDATE:

No this does not work properly either. I have a clean build notebook PC, just tried the same tests.

With the user data in the default C:\users\PROFILENAME\ folder, you can drill down and open the Music folder.

But when the users profile is on D: drive it doesn't work properly as I have discussed.

Next Update..

GETTING SILLY :

If I drill down on the C: drive pictures folder which shows 0 Bytes, then I am taken to the D: picture directory with 87GB of data in it. Same applies for the other profile folders moved from the C: drive to D: drive.

Anybody looking into this?

 

Build 10041 doesn't update further

Hello!

Had installed Win Technical preview 10041 a few months ago, since then it's has no intentions to update to further builds. I wonder, where can be a problem there?

Windows Update doesn't give me any update, except for some security update and sometimes gives me error 0x8024044a.

 

It could be a SAMBA issue.

The Linux Mint 17.1 install on my laptop does something similar.
I have 12 shared folders (NTFS) on my Windows 7 desktop.

The only shared folder the laptop can see is the one with "read and write" set on it.
The other 11 "read only" folders do not appear in the file browser.

My friend's Arch Linux system can see and access all the folders (with the correct restrictions).

Luckily I can use the W7 install on the laptop to transfer files to my W7 install on my desktop (or vice versa).

I have no idea what is happening and I can't even come up with a plausible hypothesis. *Confused

 

It's a surprise that a linux distro is having that issue. I tested samba sharing between 10041 and the Ras-Pi 2 and everything seems to be fine. Raspberry Pi can see all C folders including hidden folders.







Even permissions are set correctly. I tried copying a file from Windows C folder to Ras-Pi desktop and everything is okay.

 

Hi there

On my ANDROID phone I can access all W10 shared folders too -- the phone reports an SMB:// IP address of windows. (Android 5.0) using EZ-File explorer from google play store.

Could be something with Samba -- it's not a mega issue as most of my shared folders are not on the "C" drive.

It only happens with W10 though -- other windows releases work perfectly.

A get around though

1) Get the IP address of the Windows machine --say 192.168.1.105
2) create a directory on your Linux system /mnt/winc
3) mount the windows disk as root or sudo mount -t cifs //192.168.1.105/C /mnt/winc

You'll be prompted for your password for the windows share

Then it's fine the winc directory has all the files. You might need to set to RW if you want to write to the shares.

I'll mess around and see if some sort of Host resolution works too --I don't want to rely on specific IP addresses - but it works for the moment.

Cheers
jimbo

 

Thanks jimbo45.
*Thumbs

I'll test it out later (I'm behind schedule on a bunch of projects).