Menu

#41 Error: Cannot open handle to a drive letter created by SUBST at startup

1.0
triaged
None
Medium
7(32bit)
2017-06-20
2016-11-27
Bill White
No
  1. Let's have a drive letter created by the MS-Dos SUBST command
  2. When Win32DiskImager is starting, it throws an error popup, that he cannot open handle to the assigned drive letter mentioned above (1). For example, if you assign a letter Z for drive C, the error complains about the Z drive.

Discussion

  • Bill White

    Bill White - 2016-11-27

     

    Last edit: Bill White 2017-04-06
  • Tobin Davis

    Tobin Davis - 2016-12-07
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,2 +1,2 @@
    -1. Let's have a driver letter created by the MS-Dos ASSIGN command
    -2. When Win32 Disk Imager is starting, it throws an error popup, that he cannot open handle to the assigned drive letter mentioned above (1). For example, if you assign a letter Z for drive C, the error complains about the Z drive.
    +1. Let's have a drive letter created by the MS-Dos ASSIGN command
    +2. When Win32DiskImager is starting, it throws an error popup, that he cannot open handle to the assigned drive letter mentioned above (1). For example, if you assign a letter Z for drive C, the error complains about the Z drive.
    
     
  • Tobin Davis

    Tobin Davis - 2017-02-18
    • summary: Error: Cannot open handle to a driver letter created by ASSIGN at startup --> Error: Cannot open handle to a drive letter created by ASSIGN at startup
     
  • Tobin Davis

    Tobin Davis - 2017-02-18

    I'm not entirely sure how to reproduce this. Are you refering to Diskpart? https://technet.microsoft.com/en-us/library/cc753321.aspx

    None of my Windows 7 installs have a command called 'assign'. I remember this tool form my old Dos days (MS-Dos 3.1 - 6.11), but I think it was merged into Diskpart sometime back.

    Can you give detailed steps on how to reproduce this? Thanks.

     
  • straycat

    straycat - 2017-03-28

    The I can confirm the crash to happen when drive letters are assigned to a local path with "subst". ("assign" was for assigning drive letters to other drives, maybe Bill White just mixed it up with subst.)

    A plain "subst" will report all substituted drives. "subst x: c:\users\straycat" will make the home folder and all its contents available under the shorter path "x:\".

    Sadly, this will also cause Win32 Disk Imager to crash on startup. After removing the mapping with "subst x: /d", Win32 Disk Imager will work again (provided no other mappings or similar snags exist.)

    **Note: ** If UAC is active, only the mappings for elevated rights are relevant, because Win32 Disk Imager asks for elevated execution. Mappings for unelevated execution do not interfere with Win32 Disk Imager. If in doubt, use subst in an elevated CMD window.

     
  • Tobin Davis

    Tobin Davis - 2017-03-28

    Thanks for posting this detailed information. I'll use it to debug the issue further. Likely need an additional API call early on for 'other' disk types (like I did with USB Floppies - Windows APIs are a mess).

     
  • Bill White

    Bill White - 2017-04-04

    I am sorry, straycat was right, I meant SUBST, not ASSIGN.

     

    Last edit: Bill White 2017-04-06
  • Tobin Davis

    Tobin Davis - 2017-04-04
    • summary: Error: Cannot open handle to a drive letter created by ASSIGN at startup --> Error: Cannot open handle to a drive letter created by SUBST at startup
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,2 +1,2 @@
    -1. Let's have a drive letter created by the MS-Dos ASSIGN command
    +1. Let's have a drive letter created by the MS-Dos SUBST command
    
     2. When Win32DiskImager is starting, it throws an error popup, that he cannot open handle to the assigned drive letter mentioned above (1). For example, if you assign a letter Z for drive C, the error complains about the Z drive.
    
     
  • Tobin Davis

    Tobin Davis - 2017-04-04

    Updated summary and description to change Assign to SUBST.

     
  • Tobin Davis

    Tobin Davis - 2017-04-04
    • assigned_to: Tobin Davis
    • Importance: Low --> Medium
     
  • Tobin Davis

    Tobin Davis - 2017-06-16
    • status: open --> triaged
     
  • Tobin Davis

    Tobin Davis - 2017-06-16

    Marking as triaged, as there is enough information to debug with.

     
  • Bill White

    Bill White - 2017-06-20

    I only want to update the thread info - this bug applies to version 0.9.5, not 1.0.
    The 1.0 is not capable to start at all with subst or ramdisk used, see the thread #47.

     

Log in to post a comment.

MongoDB Logo MongoDB