Recommended Posts

I installed Windows 10 build 10061 today. On booting, the first thing I did was connect to the network share (QNAP NAS). It connected fine and I installed MS Office 2013 off it.

 

But on reboot, it does not connect to it anymore. I can access the same NAS from another W 8.1 based laptop. I can also ping it from command prompt from within Windows 10.

 

Any ideas?

 

ad7u1pV.png

 

hjZc6a7.png

Found out what is causing it.

 

Did a fresh install again and connected to my network share.

 

Now I wanted to use 4 digit pin to log-in to Windows. So to create it, Windows asked me to verify my Microsoft account using 2-step verification and code was sent on my registered mobile number. Once it was done and 4 digit pin was set up, I restarted the PC. 

 

...and bang!! my network drive stopped connecting. What kind of weird bug is this? Completely a deal breaker. This has been going on since first public preview from Jan.

 

yTpw1Rw.png

I found a way to map a Nas drive.  Go to File Explorer,  Right click on Network shortcut.  Map network drive and enter the IP of you NAS drive using exp  \\192.168.1.2 is mine and hit browse.  You should be able to browse some of your folders there and then map them.  Or, after you hit browse, add the 192.168.1.2 to either quick links or quick access. 

 

I hope that helps.  It's a bit different but it works.

  • Like 1

IP addresses are different? Wow, and this whole time, when explorer wouldn't see my shares, and I typed the direct IP it was magic? Who knew.... /s

  On 28/04/2015 at 05:10, Obi-Wan Kenobi said:

IP addresses are different? Wow, and this whole time, when explorer wouldn't see my shares, and I typed the direct IP it was magic? Who knew.... /s

Wrong. It did not work even after typing direct IP. 

 

Worked once I disabled 4 digit pin while signing.

Open Control Panel (Not sure these are in the PC Settings app yet).

 

Click "Credential Manager"

Click "Windows Credentials"

Click "Add a Windows credential"

Type in the credentials you use with the QNAP device.

 

Assuming you have password protected shares.

  • 4 weeks later...

^^ 

Tried that but it just doesn't connect to the share if I verify my account using mobile number. If it is a local account, the mapped network share starts working again.

 

Same problem in build 10122.

 

I can ping the server fine. But as soon as I try to mount it by typing it's name or IP address in explorer, Windows cannot find it. This problem started right from 1st publicly available Windows 10 beta.

 

These days, over complicating things is the new IN-thing. Once the settings are over complicated, you hide them. Problem solved. (Y)

 

:angry:

  • 5 weeks later...

This problem continues to exist in leaked build 10147.

1. Map a network drive in This PC as Z:

2. Working flawlessly so far. I can browse all my files.

3. Go to settings and under Login, create 4 digit PIN to be used to login, instead of a regular password.

4. Reboot the PC.

5. BAM!! Network drive is now not accessible.

6. I can ping it through Command prompt but it just doesn't map no matter what.

7. I try to map it by typing IP address but still fail

8. Then again go to settings, and under Login, reset PIN. Then instead of entering new PIN, close the window to disable PIN completely and switch to login by Microsoft account password.

9. Reboot the PC.

10. Now the network drive can be mapped and works as before.

I just can't believe a bug like this is seeping through all the builds released so far.

I tried all the solutions but when PIN is enabled, the network drives just fail to mount no matter what.

Side note question:  In build 10130, I don't have an option to Reset PIN under my Settings > Accounts > Sign In Options.  There's a button for Forgot My PIN, and Change, but no Reset.  And typing in no PIN on the Change page doesn't work. So, is there a way to revert from using a PIN in 10130?

Thank god I found this thread.  The PIN problem was keeping me out of my network drives as well!  10130 and the new 10162 builds were the same.  

 

The only way I found to ditch the PIN is to go into Settings > Accounts, click sign in with a local account instead, create the local account, then do the same thing again - but choose sign in with Microsoft account.  When you're going through the setup for that, and it gets to the PIN option, choose no thanks.  You lose the convenience of the PIN, but signing in with your password on a Microsoft account allows you to connect to your network drives again!  

 

  On 29/06/2015 at 12:26, BeerFan said:

Side note question:  In build 10130, I don't have an option to Reset PIN under my Settings > Accounts > Sign In Options.  There's a button for Forgot My PIN, and Change, but no Reset.  And typing in no PIN on the Change page doesn't work. So, is there a way to revert from using a PIN in 10130?

I found another easier way to disable the PIN. Go into Settings > Accounts > Sign In Options. Clic on button for Forgot My PIN, Clic on Continue, you may be prompted to enter the password for your account, type it, and when ask for the new PIN, you clic on Cancel and then the PIN will be disable.

 

You must log off (no need restart) and signing again with your password on a Microsoft or local account allows you to connect to your network drives again!

  On 05/07/2015 at 04:32, ChrisPollard77 said:

Thank god I found this thread.  The PIN problem was keeping me out of my network drives as well!  10130 and the new 10162 builds were the same.  

 

The only way I found to ditch the PIN is to go into Settings > Accounts, click sign in with a local account instead, create the local account, then do the same thing again - but choose sign in with Microsoft account.  When you're going through the setup for that, and it gets to the PIN option, choose no thanks.  You lose the convenience of the PIN, but signing in with your password on a Microsoft account allows you to connect to your network drives again!  

 

This problem is solved.

 

enter username as servername\username

password as password

  • 3 weeks later...
Thank god I found this forum. Spend all day re-installing / repairing the Windows 10 trying to figure out what was causing this issue.

After a repair I could acces my network shares on my NAS, but thanks to this forum I now know the PIN was causing this issue for me.
W10 was released a few days ago in my country. Very bad from Microsoft.
 
Gonna report this bug on the official MS website.
  • 5 weeks later...

Has there been any solution to this issue? I have it on a new ASUS Zenbook (10 Home) and my custom built desktop (10 Pro), but not my Surface Pro 3 (10 Pro). It's not a huge deal, but I can't come up with any rational explnation as to why the pin vs password would limit what you can see on the network.

  • xendrome locked this topic
This topic is now closed to further replies.
  • Posts

    • Tesla instructor reportedly said staff leave with a 'negative taste in their mouth' by Hamid Ganji Tesla has been making the headlines over the past few months due to Elon Musk's controversy in the Department of Government Efficiency, aka DOGE. People have been marching to the streets, boycotting Tesla, and even setting their already-bought Tesla cars on fire. Tesla temporarily shut down its factory in Austin for the week of Memorial Day, and employees could either take paid time off or attend a series of training sessions. Business Insider now claims to have obtained a recording of the sessions that reveals some interesting details about the Tesla culture and how its employees feel about the company. The Tesla instructor reportedly asked employees to respond if they ever felt "I can't work under these conditions" and were uneasy about the company's constant change. "I know I have," the instructor said. "A lot of people leave this company, and they have kind of a negative taste in their mouth," the Tesla instructor added. "They think: 'Man, it was terrible. It was bad. I got burnt out. I feel like I didn't get anything done, nobody listened to me.'" Hundreds of Tesla employees allegedly attended the meetings, where they were asked to take more responsibility for improving the company's culture. "Leadership has kind of another level of responsibility for trying to guide and direct that culture," the instructor told Tesla staff. "But at the end of the day, it's us as the people on the ground that are the reflection of the culture." Tesla's factory in Austin produces Cybertruck and Model Y. The staff said shutting down the factory for the sake of Memorial Day has been unusual for the company. Elon Musk recently announced that he would leave his position at the White House and added that he'll remain Tesla CEO for another five years. In the meantime, the latest data shows Tesla sales in Europe have dropped 49 percent, and the company's profit in Q1 2025 declined by 71 percent.
    • More like you took offense to the letdown and I find it hilarious. Most people aren’t reading tech blogs, and for those that do, they know what the difference is. So really it’s a non-story to YOU, because you don’t like what it says.
    • Building 100 hospitals around the world would have spent his fortune easily. But that would not keep him at the table with the elites in the world for the rest of his life. Or keep him from chanting about how good he is to the poor people around the globe to the media.
    • Exactly. that's what I use when I do use Windows 10 on my Linux through QEMU/KVM VM (the 'activation' is tied to the UUID of the VM) and, like you said, that Jan 2032 version of Win10, even if decent program/game support ends earlier than Jan 2032, I suspect, for a conservative figure, that we got at least 2-3 years from now (so call it 2027-2028) before Win10 may start to become more of a legitimate issue. but for general usage I suspect we got a 'easy' 2-3+ years. because like you say, as long as browsers don't start to become a issue, all the more reason to continue using Win10 for many, probably most, people. even when it comes to browsers, you mentioned Firefox supports Win7 until end of August etc... but I think it's just ESR releases which, while I get it technically works, are when browser support is getting a bit long-in-the-tooth. but as long as the standard Firefox release is still supported, then one is still easily well within the 'good support range', which my comment basically plays inline with what Werct said, which I suspect comes back to my 2027-2028 estimate before Win10 'starts' to legitimately fade off into the sunset
    • Intel's new GPU driver adds support for FBC: Firebreak, Stellar Blade, and more by Taras Buria Intel has released a new non-WHQL driver under version 32.0.101.6876. The update brings support and optimizations for four games and a single fix for visual artifacts that appear in certain situations. Here is the list of newly-supported games in driver 32.0.101.6876 on systems with Intel Arc B-Series, A-Series, and Intel Core Ultra with built-in Arc graphics: FBC: Firebreak Rematch Stellar Blade Tom Clancy's Rainbow Six Siege X There is also a single bug fixed in today's release: Intermittent visual artifacts may appear in certain usage scenarios. Known issues remain the same as in the latest WHQL release, except for a new bug that causes audio glitches on handheld devices: Certain handheld devices may experience audio glitches and lower-than-expected performance while audio is playing. You can mitigate the problem by following a guide that Intel published on the official forum. It requires reinstalling the graphics and NPU drivers on the affected systems. A proper fix will be available in a future driver update. You can install Intel 32.0.101.6876 non-WHQL driver on PCs with 64-bit Windows 10 and Windows 11 with the following graphics products from Intel: Discrete GPUs Integrated GPUs Intel Arc A-Series (Alchemist) Intel Arc B-Series (Battlemage) Intel Iris Xe Discrete Graphics (DG1) Intel Core Ultra Series 2 (Lunar Lake and Arrow Lake) Intel Core Ultra (Meteor Lake) Intel Core 14th Gen (Raptor Lake Refresh) Intel Core 13th Gen (Raptor Lake) Intel Core 12th Gen (Alder Lake) Intel Core 11th Gen (Tiger Lake) You can download the driver from the official website here. Full release notes are available here (PDF). Keep in mind that this is a non-WHQL driver, which means it could be less stable than certified WHQL drivers.
  • Recent Achievements

    • Dedicated
      jbatch earned a badge
      Dedicated
    • Week One Done
      Leonard grant earned a badge
      Week One Done
    • One Month Later
      portacnb1 earned a badge
      One Month Later
    • Week One Done
      portacnb1 earned a badge
      Week One Done
    • First Post
      m10d earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      266
    2. 2
      snowy owl
      158
    3. 3
      +FloatingFatMan
      145
    4. 4
      ATLien_0
      140
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!