<![CDATA[How to create notepad++ log file to attach to issue report?]]>Hi,

Notepad++ does start, but then locks up when I just start it from the Windows-Dock / Startbar. I wonder how to create a helpful issue report, e. g. by creating some startup logs.

Right now, all I know is that a white screen occurs which claims that I see “New 1” as a file, but the application is no longer responding. I assume, that no one will be able to reproduce or investigate the error.

Is there a way to increase log level and create a usefull log file to attach to an issue report?

If I open Notepad++ from the context menu of a file, it will start up smoothly. And now it also starts form the startbar again. I assume it is related to the network location of the last closed file or something.

Thanks,
Oliver

]]>https://community.notepad-plus-plus.org/topic/21004/how-to-create-notepad-log-file-to-attach-to-issue-reportRSS for NodeSun, 15 Mar 2026 04:33:43 GMTThu, 08 Apr 2021 12:18:59 GMT60<![CDATA[Reply to How to create notepad++ log file to attach to issue report? on Thu, 08 Apr 2021 13:13:27 GMT]]>@Oliver-Meyer said in How to create notepad++ log file to attach to issue report?:

I assume it is related to the network location of the last closed file or something.

That is a good guess. If Notepad++ cannot see the network location for files in the current session, or sometimes for files in the recent files history, then it can get confused.

For the recent files history, there is a setting which influences it: Settings > Preferences > Recent Files History > ☑ Don’t check at launch time. By clicking that checkbox, Notepad++ will not try to verify whether or not the MRU files still exist.

Is there a way to increase log level and create a useful log file to attach to an issue report?

Not that I’ve ever seen or heard of.

]]>https://community.notepad-plus-plus.org/post/64770https://community.notepad-plus-plus.org/post/64770Thu, 08 Apr 2021 13:13:27 GMT