Not able to see network drive

I have a master folder with my scripts in it. It’s connected to another machine on my network. I have a mapping to it, however when I try to example Z:, its says cannot set location to the drive. Is there some change with PowerShell 7 where it won’t see the network drive? I assume just tying Z: it would change to the network drive?

Welcome to the forum. :wave:t3:

Uuui … your name is already from the future. :open_mouth: :laughing:

Can you access it with the according UNC path? I’d recommend to use the UNC path anyway because it does not depend on mappings saved in your profile. :wink:

You say “it’s connected to another machine on my network” what exactly is the connected, the folder? A physical drive etc.

If there is more than 1 network hop in terms of computers you’re going to have problems even using UNC paths.

Hehe yeah my name is from the future, I thought it would be cool. So the drive is connected by usb to another machine in the same room. I made a map to it from the machine I’m working from. I just feel like I’m missing something simple that I have done before. Re-brushing up on the PowerShell skills.

What is also weird is if I use Windows Powershell and not PowerShell 7 and I type Z: it points to the drive

OK, my bad … I thought we are talking about a network share. :man_shrugging:t3:

Again … can you use it by an UNC path? If yes - why not unsing it this way?

Since it is USB - why don’t you connect it to your machine?


Did you map the drive prior to the PowerShell session you want to use the mapping in?

Ok my bad too, I may have made this seem confusing. I am sharing the drive on my local network so that I can access from any machine. It’s my version of a network share if you will. I do have another drive that can connect to the network by IP only which I would like to create it as a network drive, truly! I would! But I would need to create another conversation for that. Once I can see it on the network I did the whole “map this drive” is all.

So I notice that when I’m in shell as admin, I can’t point to the drive in either shell 7 or Windows PowerShell. When in normal shell on both I can type Z: and boom its goes there. So I’m still confused there.

OK, once again … CAN YOU ACCESS IT BY ITS UNC PATH??? :smirk:

Mappings of drives are user specific. If you map a drive as normal user you can only access it as this normal user. You would need to map it as admin when you want to use it as admin. That’s why I reommended to use it with its UNC path. This will stay the same for all users.

The drive is mapped to the normal user token. Anything running as admin won’t be able to see it. There are ways around this but I’d stick with Olafs suggestion to simply use the UNC path instead of the mapped drive letter.

Well my machine must have heard you, I can access it by UNC from explorer and now when I do set-location in shell and use \server\share it all a sudden works wow!

I use to do this stuff in my sleep.

Great. :+1:t3:

This could have been over 2 hours ago. :smirk:

:laughing: Yeah yeah, well I went to lunch and had to deal with some other stuff. I swear I entered that UNC like I dunno how many times. Anyway.

I see you in Berlin, well that’s cool getting some help from a fellow in Berlin. I enjoy this stuff.


… according to your IP address you don’t seem to be in Berlin?!

Anyway … I’m not exactly looking like my profile picture. :wink: … I just coincidently have the same name.

Yeah I’m not in Berlin, so gotta ask since I’m going to research it, how you find my ip address out of our chat? I just think it’s cool I got a response for anyone on this forum. I’ll be posting more stuff. I don’t know what ever happened to the community. Lol about the profile pic, you’re helpful though for sure. I’m about for the day over here, I’ll check this forum tomorrow.

I have some admin or moderator priviliges and can look up your IP address in my admin panel. :wink:

Well that is cool, wonder how you got those specialities :grinning: Well this thread is resolved. Onto other topics with PowerShell.