Windows 10: Mapped drives y and z not persistent

HiI am having problems mapping to Y and Z. I map MyDocuments to Z. When I turn the PC off and on, it forgets the mapping.I've usedWindows explorer, right click Network>Map network drive...alsonet use z: \\NETDRIVE\MYDocuments /persistent:yesDrive gets mapped ok but on powering off and on it's forgotten.Same problem with Y drive.If I map to W or V it works ok.Windows Spec.Edition Windows 11 Home Insider Preview Version Dev Installed on ‎18/‎10/‎2024 Evaluation expires on ‎15/‎09/‎2025 22:16 OS build 27729.1000 Experience Windows Feature Experience Pack 1000.26100.29.0

:)

 

Connecting NAS - mapping of drives

OK ... step by step all worked. I have now mapped the 2 volumes as Y & Z and can access the files on them Any idea why the Command line would work yet the Easy Find Utility that has worked for years does not ?

 

Drive letter for D, E, Y and Z are incorrect and I can't change them.

Also note that for the last few versions of Windows drive letter Z: has been used for the first Mapped Network drive then works back up the alphabet for additional such drives. I have Z: and Y: assigned for my 2 NAS drives. If never mapping such drives the letters can be used for other drives and I've noticed on a few computers that Z: was a partition used by the OEMs when installing.

 

Mapping network drives with script

I'm attempting to use a script to

1. unmap a drive
   
2. clear the cached credentials used to map that drive
   
3. map the drive again using different user credentials.
   

In Windows 7 the following script worked for me

This script is intended to unmount what is mapped to Z. Then clear the cached credentials used to mount z. Then remap the drive using another user's credentials.

When I run this on windows 10, the net stop and net start throw access denied errors. I have tried creating a shortcut of the script and setting the shortcut to always run as admin, but this option is greyed out on my box probably by group policy settings.

I am attempting to find a way to achieve this same unmap/map solution and am currently exploring options granted through powershell. My current attempt in powershell is using

mount -Name "z" -PSProvider filesystem -Root "\\path\to\directory" -Persist

The map needs to be persistent so that the drive appears in windows explorer.
This command works as it should when I run it in powershell, but double clicking on the file to run it does not map the drive, probably because of access issues. I'm new to powershell and am still learning it, so I don't know all options available to me. Does anyone know a way to achieve the effect I'm going for?