If it works this way, then one of your old config files was the culprit at this point, you can either just continue from the fresh config state, or you can try comparing the old and new config files, to figure out what went wrong, and maybe try to get back as many of your old settings as you can.In this article, we will be reviewing a network troubleshooting tool called “PingPlotter”.
Go to %AppData% and rename Notepad++ to Notepad++.bak run your installed Notepad++ – this will run it without any of the existing config files, and will create a new %AppData%\Notepad++ directory with fresh/known-good config files. Try them one at a time if you want them open again. If you want to look up what your old open files were, to try to re-open them in the responding Notepad++, look at %AppData%\Notepad++\, which will list the files. If it works, then it was one of the files that it was trying to re-open that was causing the problem exit Notepad++, go to %AppData%\Notepad++ 🛈, and rename session.xml to the next time you run Notepad++, it should work normally, but not have any of the previous open files open. Try to run your installed copy without loading the current session, because sometimes when it’s trying to load a network file or a file or directory that no longer exists, it can freeze or stop responding and if you had a huge file, maybe you no longer have the memory or resources to open that huge file again: go to C:\Program Files\Notepad++ (or wherever your installed copy of 8.1.4 is), and open up a cmd.exe or powershell window there on the command line, run notepad++ -nosession. If it runs without a “not responding” problem, then it is one of your plugins that is causing the problem if so, let us know, and we can give next steps for debugging which plugin is the culprit.
Try to run your installed copy without plugins: go to C:\Program Files\Notepad++ (or wherever your installed copy of 8.1.4 is), and open up a cmd.exe or powershell window there on the command line, run notepad++ -noPlugin. If it works, then it’s further confirmation that the problem lies with your particular installation. Run the executable that’s in that folder.
PINGPLOTTER NOT RESPONDING PORTABLE
We are keeping these experiments separate.ĭownload a portable zip edition, and unzip into a folder where you have write permission (like your Desktop). We have a FAQ Desk entry about %AppData% if you need to learn about it or need a refresher.įor all the experiments below, I am assuming you have killed any “not responding” notepad++ instances and closed any instances of notepad++ from a previous step. So my guess is that the “not responding” is probably a result of the particular plugins you have installed, or the config files you are using.įor all the experiments below, you will want to make sure you understand what I say when I mention %AppData%. Your old v7.5.6 was pretty old – so it was much better used with Win7 than the modern 8.1.4 will be (because there were more instances of Win7 back when v7.5.6 was new), so it should have in theory worked well.
PINGPLOTTER NOT RESPONDING DRIVER
(Even I still have one Win7 machine that I keep around because of one piece of hw that I rarely use that requires a driver that only works on Win7.) There are plenty of people who use Notepad++ every day without “not responding” difficulties and my guess is there are still plenty of people who, like you, still use Win7 despite MS dropping support more than a year ago, and still use Notepad++ on that older OS without difficulty.
0 kommentar(er)
