Access NAS Drive using Windows 10 PIN login

3 min 430 words
Peter Tillemans Profile picture

Each time I login using the PIN of my Microsoft account, my mounted folders on the NAS are not mounted. After login I get a notification that not all mounted drives could be connected. When double clicking on the failed mount I get a silly error regarding duplicate sessions or something, and I can access after logging in.

This is irritating, but also breaks automations like auto importing notes and documents into evernote from the NAS folder.

Attempt 1

This seems to be a known issue with PIN (and by extension face recognition (?)) login.

On Windows answers I found a workaround :

  • Open the Credential Manager
  • Select Windows Credential
  • Add a Windows Credential (it will actually modify the existing one)
  • network address : \\ [your NAS]{.underline}
  • User name : your NAS_\pti{=latex}
  • Password : [your password on the NAS]{.underline}

From now on your drive should be mounted after rebooting.

Unfortunately, it does not.

Removing and adding again does not help either.

Attempt 2 : remap network drives on login

In 2018 [another workaround](,t%20automatically%20reconnect%20network%20drives.&text=A%20log%20file%20(StartupLog.,to%20open%20the%20mapped%20drives.) was published.

This relies on a powershell script launched by a Command script to walk over unavailable mapped drives and map them again.

It uses 2 scripts:

*%ProgramData%\Microsoft{=latex}\Windows{=latex}\Start{=latex} Menu\Programs{=latex}\StartUp{=latex}\MapDrives{=latex}.cmd

A startup scrip to kickoff remapping after login

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%\StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" >> "%TEMP%\StartupLog.txt" 2>&1


    $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath
    foreach( $MappedDrive in $MappedDrives)
        try {
            New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
        } catch {
            Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
    $i = $i - 1
    if($error.Count -eq 0 -Or $i -eq 0) {break}

    Start-Sleep -Seconds 30



After rebooting and logging in, I still get the error that not all drives could be mounted, however, by the time I can check in the explorer the volume is mounted and ready to be used.

Not very elegant as the notification still feels terribly yanky, but at least it no longer interferes my workflows.