How to remove mapped network drive with Powershell?











up vote
0
down vote

favorite












I am trying to create and remove a new mapped network drive using PowerShell.



It creates the mapped drive, however I can't seem to remove the mapped drive. The error message I receive is:




Dir : Cannot find path 'C:Windowssystem32P' because it does not exist.




New-PSDrive -Name "P" -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 

#Get-PSDrive P | Remove-PSDrive

#Remove-PSDrive -Name P -Force

#Remove-PSDrive P, Z


All Google and Stack Overflow has suggested to me thus far is using the commands that I have previously commented out. I am unsure of what I am doing wrong but had a feeling it could be done to the location of my files perhaps?



All help would be greatly appreciated!






powershell







share|improve this question
























  • Are you getting any specific error messages using Remove-PSDrive?
    – TobyU
    20 hours ago










  • @TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
    – Edward Muldrew
    20 hours ago






  • 1




    If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
    – LotPings
    19 hours ago






  • 1




    The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
    – James C.
    19 hours ago

















up vote
0
down vote

favorite












I am trying to create and remove a new mapped network drive using PowerShell.



It creates the mapped drive, however I can't seem to remove the mapped drive. The error message I receive is:




Dir : Cannot find path 'C:Windowssystem32P' because it does not exist.




New-PSDrive -Name "P" -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 

#Get-PSDrive P | Remove-PSDrive

#Remove-PSDrive -Name P -Force

#Remove-PSDrive P, Z


All Google and Stack Overflow has suggested to me thus far is using the commands that I have previously commented out. I am unsure of what I am doing wrong but had a feeling it could be done to the location of my files perhaps?



All help would be greatly appreciated!






powershell







share|improve this question
























  • Are you getting any specific error messages using Remove-PSDrive?
    – TobyU
    20 hours ago










  • @TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
    – Edward Muldrew
    20 hours ago






  • 1




    If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
    – LotPings
    19 hours ago






  • 1




    The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
    – James C.
    19 hours ago















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am trying to create and remove a new mapped network drive using PowerShell.



It creates the mapped drive, however I can't seem to remove the mapped drive. The error message I receive is:




Dir : Cannot find path 'C:Windowssystem32P' because it does not exist.




New-PSDrive -Name "P" -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 

#Get-PSDrive P | Remove-PSDrive

#Remove-PSDrive -Name P -Force

#Remove-PSDrive P, Z


All Google and Stack Overflow has suggested to me thus far is using the commands that I have previously commented out. I am unsure of what I am doing wrong but had a feeling it could be done to the location of my files perhaps?



All help would be greatly appreciated!






powershell







share|improve this question















I am trying to create and remove a new mapped network drive using PowerShell.



It creates the mapped drive, however I can't seem to remove the mapped drive. The error message I receive is:




Dir : Cannot find path 'C:Windowssystem32P' because it does not exist.




New-PSDrive -Name "P" -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 

#Get-PSDrive P | Remove-PSDrive

#Remove-PSDrive -Name P -Force

#Remove-PSDrive P, Z


All Google and Stack Overflow has suggested to me thus far is using the commands that I have previously commented out. I am unsure of what I am doing wrong but had a feeling it could be done to the location of my files perhaps?



All help would be greatly appreciated!






powershell




powershell






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 19 hours ago









James C.

7,95722030




7,95722030










asked 21 hours ago









Edward Muldrew

4611




4611












  • Are you getting any specific error messages using Remove-PSDrive?
    – TobyU
    20 hours ago










  • @TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
    – Edward Muldrew
    20 hours ago






  • 1




    If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
    – LotPings
    19 hours ago






  • 1




    The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
    – James C.
    19 hours ago




















  • Are you getting any specific error messages using Remove-PSDrive?
    – TobyU
    20 hours ago










  • @TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
    – Edward Muldrew
    20 hours ago






  • 1




    If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
    – LotPings
    19 hours ago






  • 1




    The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
    – James C.
    19 hours ago


















Are you getting any specific error messages using Remove-PSDrive?
– TobyU
20 hours ago




Are you getting any specific error messages using Remove-PSDrive?
– TobyU
20 hours ago












@TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
– Edward Muldrew
20 hours ago




@TobyU it ays Dir : Cannot find path 'C:Windowssystem32P' because it does not exist. However when I run Dir P, or Get-PSDrive. I can see the drive does exist
– Edward Muldrew
20 hours ago




1




1




If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
– LotPings
19 hours ago




If you intend to remove the drive soon, why do you add the -Persist parameter and I'D then add a -Sope to minimize possible other processes stepping in.
– LotPings
19 hours ago




1




1




The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
– James C.
19 hours ago






The error is because your running dir P instead of dir P: You need the : to signify a drive not a folder.
– James C.
19 hours ago














1 Answer
1






active

oldest

votes

















up vote
2
down vote













The error is because you're running dir P instead of dir P: You need the : to signify a drive not a folder.



dir (which in Powershell is a actually an alias for Get-ChildItem) can read multiple areas of the OS so you need to be more specific with what you tell it.



Examples:




  • File system: Get-ChildItem C:

  • Registry: Get-ChildItem HKCU:

  • Certificate Store: Get-ChildItem cert:


Whilst with Get/Remove-PSDrive commands you are specifically telling it you want a "FileSystem" drive so it knows that Name is a drive letter.




With regards to removing the drive, either of the two commands you've listed will work fine:



New-PSDrive -Name P -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 



Get-PSDrive P | Remove-PSDrive

Remove-PSDrive -Name P -Force





share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372049%2fhow-to-remove-mapped-network-drive-with-powershell%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    The error is because you're running dir P instead of dir P: You need the : to signify a drive not a folder.



    dir (which in Powershell is a actually an alias for Get-ChildItem) can read multiple areas of the OS so you need to be more specific with what you tell it.



    Examples:




    • File system: Get-ChildItem C:

    • Registry: Get-ChildItem HKCU:

    • Certificate Store: Get-ChildItem cert:


    Whilst with Get/Remove-PSDrive commands you are specifically telling it you want a "FileSystem" drive so it knows that Name is a drive letter.




    With regards to removing the drive, either of the two commands you've listed will work fine:



    New-PSDrive -Name P -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 
    

    
Get-PSDrive P | Remove-PSDrive
    
Remove-PSDrive -Name P -Force





    share|improve this answer

























      up vote
      2
      down vote













      The error is because you're running dir P instead of dir P: You need the : to signify a drive not a folder.



      dir (which in Powershell is a actually an alias for Get-ChildItem) can read multiple areas of the OS so you need to be more specific with what you tell it.



      Examples:




      • File system: Get-ChildItem C:

      • Registry: Get-ChildItem HKCU:

      • Certificate Store: Get-ChildItem cert:


      Whilst with Get/Remove-PSDrive commands you are specifically telling it you want a "FileSystem" drive so it knows that Name is a drive letter.




      With regards to removing the drive, either of the two commands you've listed will work fine:



      New-PSDrive -Name P -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 
      

      
Get-PSDrive P | Remove-PSDrive
      
Remove-PSDrive -Name P -Force





      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        The error is because you're running dir P instead of dir P: You need the : to signify a drive not a folder.



        dir (which in Powershell is a actually an alias for Get-ChildItem) can read multiple areas of the OS so you need to be more specific with what you tell it.



        Examples:




        • File system: Get-ChildItem C:

        • Registry: Get-ChildItem HKCU:

        • Certificate Store: Get-ChildItem cert:


        Whilst with Get/Remove-PSDrive commands you are specifically telling it you want a "FileSystem" drive so it knows that Name is a drive letter.




        With regards to removing the drive, either of the two commands you've listed will work fine:



        New-PSDrive -Name P -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 
        

        
Get-PSDrive P | Remove-PSDrive
        
Remove-PSDrive -Name P -Force





        share|improve this answer












        The error is because you're running dir P instead of dir P: You need the : to signify a drive not a folder.



        dir (which in Powershell is a actually an alias for Get-ChildItem) can read multiple areas of the OS so you need to be more specific with what you tell it.



        Examples:




        • File system: Get-ChildItem C:

        • Registry: Get-ChildItem HKCU:

        • Certificate Store: Get-ChildItem cert:


        Whilst with Get/Remove-PSDrive commands you are specifically telling it you want a "FileSystem" drive so it knows that Name is a drive letter.




        With regards to removing the drive, either of the two commands you've listed will work fine:



        New-PSDrive -Name P -Root "\VM-Blue-RobinTesting" -Persist -PSProvider "FileSystem" 
        

        
Get-PSDrive P | Remove-PSDrive
        
Remove-PSDrive -Name P -Force






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 19 hours ago









        James C.

        7,95722030




        7,95722030






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372049%2fhow-to-remove-mapped-network-drive-with-powershell%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            'app-layout' is not a known element: how to share Component with different Modules

            Image
            0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule ...
            Read more

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            Image
            .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d ...
            Read more

            WPF add header to Image with URL pettitions [duplicate]

            Image
            up vote 0 down vote favorite This question already has an answer here: Image source URI requiring authorization 3 answers Add header to all* HTTP requests on a machine 1 answer first of all sorry for my english. Recently I added some security in the backend of my project, and now I need to send a validation code(apiKey) inside the headers to retrieve the images. I have a problem with ALL images in my project that I had attached in my UI. For example, before I had: <Image Height="90" Source="{Binding Video.Thumbnail}"/> Now I need to change my code to create a CUSTOM petition add the apiKey in the header:...
            Read more