Menu

Crash when opening .nfo files

2007-05-11
2012-11-13
  • Nobody/Anonymous

    Strange bug with 4.1 where opening a .nfo file results in Notepad++ crashing. Rename the same file into .txt and there's no such problem. Anyone else encountered this?

     
    • Nobody/Anonymous

      I had the same issue and here's what I did to fix it.  Go into Notepad++ and un-associate all file extensions.  Uninstall Notepad++ and make sure everything is removed, including any directories.  Also make sure to unregister the dll for explorer context menu too if your using the bin zip version (not the actual setup).  Then I ran CCleaner (free app you can get on internet) and performed a "search for issues" in the registry.  Came up with a bunch of stuff and I told it to fix them.  Ran it until I had no more issues.  Rebooted my system and re-installed Notepad++.  NFO files were no loading up like a charm!  Hope this helps you.

      FGump

       
      • Nobody/Anonymous

        Thanks a lot for real solution!

        Uninstall Notepad++ -> delete NP++ files from Program Files & Docs & Settings -> Start -> Run + regedit -> Find and delete all Notepad++ records -> Reboot -> Reinstall

         
    • Don HO

      Don HO - 2007-05-11

      Send me your nfo file so that I can work on this crash issue.

      Don

       
    • Nobody/Anonymous

      This happens with any file, as long as the extension is .nfo - I can even create a new 0-byte file and name it test.nfo: Notepad++ will crash when opening it.

       
      • Don HO

        Don HO - 2007-05-12

        Tested with v4.1, Works perfectly for me.

        Rename the plugins directory to whatever you want, then try again.

        Let me know if it works now.

        Don

         
        • Nobody/Anonymous

          No, renaming the plugins dir didn't help. I tried un- & reinstalling NP++, but the problem still persists.

           
    • Nobody/Anonymous

      I am having the same issue even did the ccleaner and still no luck opening a basic nfo file

       
    • Nobody/Anonymous

      Well it seems like all it took was a reboot and it started to work

       
MongoDB Logo MongoDB