notepad-plus-plus / notepad-plus-plus/notepad-plus-plus

[BUG] NPP config file corrupted/reseted upon restarting into administrator mode

Open
#16,091 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
29.4k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Is there an existing issue for this?
  • I have searched the existing issues
Description of the Issue

I had a case of config file reseting when I restarted NPP to save edits made to windows hosts file with administrator privileges. Basically, everything that was opened remained open but I noticed all of a sudden NPP looking like default. Went to check further and verified that in fact that everything was back to default to my dismay.
I was unable to reproduce the issue.
This happened a few days ago on a PC at work so I couldn't access the log file when writing this nor can I get it.
NPP was up to date at the time (v8.7.5).
Side note: I appreciate the effort put into free software like Notepad++ and I am sorry the issue report is maybe lacking in details.

Steps To Reproduce

In theory:

  1. Start notepad without elevated privileges
  2. Write changes to the file that needs elevated privileges in NPP
  3. Go to restart with administrator mode when trying to save the changes.
    Now, if you are unlucky like I was that moment, ~all settings in NPP should be default.
Current Behavior

Its working fine now like it was before. I just had that happen one time.

Expected Behavior

I expect it to not reset/corrupt my configurations for NPP.

Debug Information
Notepad++ v8.7.5   (64-bit)
Unavailable, sorry.
Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, log, or entry point is identified. Start by investigating the reported restart-into-administrator workflow and whether configuration is reset when saving an elevated file; reproduce the sequence if possible and verify that existing settings remain intact after the restart.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.