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

    • No operating system works well with programs that modify its interface. There will always be bugs, whether it's MacOS or Linux. Windows too, you'll only suffer from bugs using this crap software.
    • KDE brings UI improvements, bug fixes and more to Plasma 6.4 as stable release draws near by David Uzondu With less than a month to the release of Plasma 6.4, the KDE dev team has shared what it has been working on in the latest issue of its weekly roundup. The update shows a heavy focus on user interface polish and a whole slew of bug fixes as the June 17 release date gets closer. The team has pushed a number of UI refinements for the upcoming version. On the System Settings page for Wi-Fi, the network list can now be fully navigated with a keyboard. KDE also disabled the ability to drag and drop displays on top of one another in the monitor settings. This was done because it could create unsupported arrangements that triggered a cascade of strange bugs throughout the system. Waking up a sleeping computer by pressing the power button no longer causes the bizarre logout screen to appear after you unlock it, which is a relief. Alignment issues in the settings page for the Digital Clock widget were also resolved. The list of bug fixes for 6.4 is extensive. The development team has fixed the most common crash affecting the System Monitor and squashed another one related to a divide-by-zero error. For users with multiple monitors, a long-awaited fix has landed that prevents windows from disappearing when the screen they are on gets disconnected. Even the humble Sticky Notes widget received attention; it will no longer freeze the Plasma shell if you place it on a very thick panel. Discover, the software center, also had a bug patched that caused it to crash if closed too quickly after launch. Here's the full list of improvements: Putting a Sticky Note widget on a very thick panel can no longer cause Plasma to freeze; now, you can use a thick panel with a sticky note on it as a notes sidebar. Fixed the most common System Monitor crash. Fixed another crash in System Monitor, this time a divide-by-zero. Fixed a case where xdg-desktop-portal-kde could crash after you choose a video source to start streaming. Fixed a bug that caused Discover to crash if you close it immediately after it launched. Fixed multiple subtle bugs with the screen chooser widget and OSD that caused it to do the wrong thing on rotated screens or when mirroring screens. Fixed a bug that caused the System Settings’ search field not to be focused properly when pressing Ctrl+F while any UI elements in a settings page already had focus. Fixed the root cause of multiple issues involving windows disappearing when you disconnect the screen they’re on. Clicking a button on a desktop widget that opens a menu no longer inappropriately makes the widget enter Widget Edit Mode. Files with a # or ? character in their name or full path are no longer unexpectedly missing from the history lists in Kicker/Kickoff/etc launchers. Fixed a bug that caused the screen chooser window to sometimes not appear as expected when OBS was launched. Fixed a bug that caused tiled windows on a multi-screen setup to lose their tiling settings when the system went to sleep and woke up again. The "Move window to [activity]" feature now works properly when invoked from the Task Manager widget. Fixed a bug in the Kicker Application Menu that caused keyboard navigation not to work if the popup opened with an item under the pointer. In the Overview effect’s grid view, dragging windows tiled on one virtual desktop over to a different virtual desktop now keeps them tiled as expected. The focus may be on the imminent 6.4 release, but work on what comes next never really stops. Looking ahead, development on Plasma 6.5 is already well underway. Just last week, the KDE team brought several performance improvements to Plasma 6.5.0. This week, the team fixed a nagging bug that sometimes caused the Networks widget to think a hotspot was still enabled after disconnecting from Wi-Fi. On the features side, the System Settings' Fonts page now prevents you from breaking your system entirely by setting fonts below 4pt. In addition to that, switching time spans in the Info Center’s energy page now features smooth graph animations. Performance-wise, kwriteconfig should also be faster, allowing changes you made to the keyboard layout using the tool to reflect immediately.
    • Display Driver Uninstaller (DDU) 18.1.1.4 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.1.4 changelog: Intel: Added NPU presence detection before removing shared DLL files (these were previously left to prevent potential NPU-related issues). Intel: Added optional NPU removal Improved "Extension" driver removal process. Updated several translations. Download: Display Driver Uninstaller 18.1.1.4 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot | Forum Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • That is what I also think to a point. How is 26 necessarily different than just another iteration like 18, 19, 20, etc? At first I think it would be better for Apple to use 2026, 2027, and then maybe truncate it to just 28, 29, and so on. Granted, I also think it makes more sense to use the year when it was released (2025 or 25), not 26/2026. Maybe Apple's thinking is as stated by Aditya that the bulk of a release being the current release is during the following year (2026, for example) after it is released (2025, for example). There are other examples of these sorts of things. In the NBA, the season has always started in the Fall and ends in the Spring. When the season ends is how the season is named. So, this is the 2025 NBA season and the Pacers and Thunder are playing to be the 2025 NBA Champions. The NFL starts in the Fall and the end of the season is always in the beginning of the next year as well. The Super Bowl was played on February 9, 2025, but that was the end of the 2024 NFL season. So, contrary to the NBA, the NFL names it season based on when it starts, not when it ends. Maybe that is because more of the NFL season is played at the end of the year (2024 in the most recent example) whereas most of the NBA season is played in the first half of the following year (2025 in the current example).
  • Recent Achievements

    • Week One Done
      abortretryfail earned a badge
      Week One Done
    • First Post
      Mr bot earned a badge
      First Post
    • First Post
      Bkl211 earned a badge
      First Post
    • One Year In
      Mido gaber earned a badge
      One Year In
    • One Year In
      Vladimir Migunov earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      snowy owl
      252
    3. 3
      +FloatingFatMan
      251
    4. 4
      ATLien_0
      228
    5. 5
      +Edouard
      191
  • Tell a friend

    Love Neowin? Tell a friend!