Windows 10: No longer see Network Attached Storage in Network View on Build 10049

I can no longer see my Network Attached Storage in this build(10049) Enterprise. I have Network Discovery enabled and can get to the device by IP Address in a browser but am unable to map a drive to any share. Anyone else having these issues. I have Windows Credentials setup properly(at least it worked in previous builds) lol.

:)

 

Network Attached Storage

Has anyone else noticed if you select the properties of an item on the NAS then the Size on disk is more than it should be. If I do the same on a folder on an internal drive then the Size on disk is as normal.



The NAS is configured with two 1TB drives as RAID1 so I don't see how the Size on disk can be correct.

 

Nas drive 0x80070035 issue

Hi Ben,

It looks like you've lost connection with your Network Attached Storage. This may be caused by restrictions in the PC's firewall or possible that the network path can no longer be found. For us to sort this out, we would like to ask a few more information
regarding this problem.

• How was your Network Attached Storage connected?
• To which device is it connected?
• How do you access it?
  
• Have you tried remapping the drive on your computer?
• What firewall is installed on that specific computer?
  

We look forward to your reply.

Regards.

 

I'm in the same boat. Mine disappeared on 10049 after the 10th of April. No idea why.

 

You can get to it by IP address to be able to map a drive but that still doesn't fix what Microsoft has once again broke!

 

My issue's the same only it started with 10041 update (haven't done a clean install). re-did all the 'share' things to no avail. Have got 10 pc's with Win7, Win 8, Win 10 10041 and 10049. Win 10 can see rest but can't access - consistently - and then only the Public shares.

 

I fixed mine by clean installing 10041 and then upgraded immediately to 10049.

 

I have done clean installs of 10049 and 10056 and both are not able to see the NAS

 

10056 will definitely not see it. 10056 is a leaked ISO upgraded from 10051 (because of the windows.old folder in it). I also clean installed 10049 from ISO I created with no success (there is no official ISO for 10049).
But the clean install of 10041 (official ISO) upgraded (online) to 10049 fixed it.

Here's the proof (it even sees my Rapsberry Pi *Biggrin ):





Bottom line, you need clean installs from clean ISO. Not upgraded or leaked ISO. Why? That's how it worked for me.

 

Thanks BADROBOT. MS needs to put out something new soon hopefully..

 

No problem. It's been my motto here for the longest time. If something doesn't work right, clean install (from clean ISO) will always fix it (at least 99% of the time... *Biggrin ).

 

I am using the same type of NAS linw. WD MyBookLive (white one with blue light)

 

Snap! Except mine is black.

I'm hoping we get another build soon that corrects this problem. Seems like 10056 has the same problem.

Hard to figure out what is different with the NAS. Maybe its Linux OS?? Stupid thing is that this 10049 was accessing it up to 10 Apr. Can't figure out what changed at that time.

 

I wonder if a patch came out the day yours stopped working.

 

The March updates (2) went through on the 9th so they shouldn't have been the problem as the backup on the 10th was OK. The other updates were just Defender ones.

Just did a system restore back to the 7th and, bingo, all shares pop up incl the NAS! Should have thought of this sooner.

Guess I just wait to see if the problem resurfaces.

Good result - backups immediately sprang into life!