Directory symbolic link not recognized as folder in open file dial

Discussion in 'Windows Vista File Management' started by Bjorn, Nov 22, 2007.

  1. Bjorn

    Bjorn Guest

    Hello everybody,

    The file dialogs of Vista do not recognize directory symbolic links as
    folders but as files. To demonstrate, run the following commands:

    1. Start cmd as Administrator and execute the following commands:

    2. cd \Users\Public
    3. mkdir TestFolder
    4. mkdir TestSubfolder
    5. cd TestFolder
    6. mklink /D TestSubfolder \\<computername>\Public\TestSubfolder

    7. Start Textpad:

    8. Select menu Open file
    9. Navigate in dialog to \Public\TestFolder
    10. Double-click TestSubfolder

    The last action results in the following error message:

    You don't have permission to open file.

    Also, changing ownership of the shortcut does not change the situation. A
    similar result can be observed trying the Save file dialog, which tries to
    replace the directory symbolic link.

    Windows Explorer on the other hand recognizes directory symbolic links
    properly as folders.

    Surely, this cannot be the intended behavior of the file dialog?
    Is there any solution?

    Kind regards, Bjorn
     
    Bjorn, Nov 22, 2007
    #1
    1. Advertisements

  2. Bjorn

    Jimmy Brush Guest

    Hello,

    I can confirm this behavior. It appears to be a bug in the file/open and
    file/save dialog.
     
    Jimmy Brush, Nov 25, 2007
    #2
    1. Advertisements

  3. Bjorn

    Bjorn Guest

    Thanks for confirming, I was afraid it would be. No fix around? How do I
    notify MS of this bug or is it magically taken care of? :)

    Although it is not breaking but rather annoyingly inconvenient for my
    selective and transparent sharing of private documents over all my personal
    computers (using offline folders and symbolic links).

    Bjorn
     
    Bjorn, Nov 25, 2007
    #3
  4. Bjorn

    Jimmy Brush Guest

    Hello,

    I will submit a bug report to Microsoft about this issue. As a workaround,
    things seem to work OK if you just make the symbolic link to
    \\server\rootshare. So, if you create shares on the "server" computer for
    the folders you need to access, and then link to those shares directly
    instead of through other shares, it should work.


    --
    - JB
    Microsoft MVP Windows Shell/User


     
    Jimmy Brush, Nov 25, 2007
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.