notepad-plus-plus / notepad-plus-plus/notepad-plus-plus
Opening files from mapped drives fails when launching Notepad++ in Administrator mode.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description of the Issue
Notepad++ is unable to open files from mapped drives when it has been launched in Administrator mode.
Steps to Reproduce the Issue
- Map a network drive to a network share; i.e. J:\ to \server\share
- Open Notepad++
- Open a file such as C:\Windows\System32\drivers\etc\hosts
- Make a change to the hosts file. Notepad++ will ask if you want to "launch Notepad++ in Administrator mode?"
- Click Yes.
- Open File Explorer and try to open any file in your network drive; i.e. J:\readme.txt
Expected Behavior
I expected Notepad++ to be able to open the file.
Actual Behavior
Notepad++ gives the error: "J:\files\readme.txt" cannot be opened: Folder "J:\files" doesn't exist.
Debug Information
Notepad++ v7.9 (64-bit)
Build time : Sep 22 2020 - 03:19:04
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : ON
Local Conf mode : OFF
OS Name : Windows 10 Pro (64-bit)
OS Version : 1909
OS Build : 18363.1198
Current ANSI codepage : 1252
Plugins : mimeTools.dll NppConverter.dll NppExport.dll
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mapped-drive failure using the listed Windows 10 steps, including relaunching Notepad++ in Administrator mode. Verify that a file on the mapped drive opens normally before elevation and fails afterward; done means the same file opens successfully in Administrator mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100