• Login
Community
  • Login

v7.5.2 of N++ will not launch

Scheduled Pinned Locked Moved Help wanted · · · – – – · · ·
7.5.2 launch
14 Posts 2 Posters 5.4k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    no9on
    last edited by Nov 28, 2017, 9:00 PM

    I’m sure that this related to something on my system, however, the latest N++ 7.5.2 has incorporated something in its code that prevents it from launching. Everything perfectly normal prior to this update.
    The changes may be perfectly valid for the majority, but something is definitely being implemented differently now.
    Note: Notepad++ 7.5.2 does not show up in Taskmgr and there are no error codes.
    Win 7N Pro x86

    C 1 Reply Last reply Nov 28, 2017, 9:54 PM Reply Quote 0
    • C
      Claudia Frank @no9on
      last edited by Nov 28, 2017, 9:54 PM

      @no9on

      Did you try to start npp from the shortcut or by double clicking exe file
      or by using context menu in explorer view? Or something different?
      Did you check windows event log?

      Cheers
      Claudia

      1 Reply Last reply Reply Quote 0
      • N
        no9on
        last edited by Nov 28, 2017, 10:16 PM

        Thank you for the reply.

        Sorry, I should have included the Windows Event log earlier.
        These were started by direct exe clicking:

        Faulting application name: notepad++.exe, version: 7.5.2.0, time stamp: 0x5a1b4b1f
        Faulting module name: notepad++.exe, version: 7.5.2.0, time stamp: 0x5a1b4b1f
        Exception code: 0xc0000005
        Fault offset: 0x00092892
        Faulting process id: 0x990
        Faulting application start time: 0x01d3688d8c9e054e
        Faulting application path: D:\Notepad++\notepad++.exe
        Faulting module path: D:
        \Notepad++\notepad++.exe
        Report Id: ca74e2e6-d480-11e7-bd2b-001cc08d5b1c

        Fault bucket , type 0
        Event Name: APPCRASH
        Response: Not available
        Cab Id: 0

        Problem signature:
        P1: notepad++.exe
        P2: 7.5.2.0
        P3: 5a1b4b1f
        P4: notepad++.exe
        P5: 7.5.2.0
        P6: 5a1b4b1f
        P7: c0000005
        P8: 00092892
        P9:
        P10:

        C 1 Reply Last reply Nov 28, 2017, 10:30 PM Reply Quote 1
        • C
          Claudia Frank @no9on
          last edited by Nov 28, 2017, 10:30 PM

          @no9on

          Does not give any additional info, unfortunately.
          Did you try to start as normal user and using “run as administrator”?
          Behave both the same?

          The error 0xc0000005 itself points to accessing memory location which isn’t
          allowed as owned by other application, system …

          You did install the 32bit version did you? Btw. what version is Win 7N Pro x86?

          Have you tried to deinstall, clean directory, reboot and install it again?

          Cheers
          Claudia

          1 Reply Last reply Reply Quote 0
          • N
            no9on
            last edited by Nov 28, 2017, 10:44 PM

            Running as administrator. User has admin rights also.
            Using the 7z x86 (32-bit) version.
            Installed to different drive, new folder.

            I appreciate the help and recognize that this is something on my side that needs to be resolved, BUT since all previous versions and updates prior to today ran w/o a problem, and I haven’t added any apps or hardware recently; there must be some implementation of the code which is different for this update. Memory resources haven’t changed.

            Also, Win 7N (also true for 10N) is a European version (running for several years) that comes w/o IE and the windows media player apps. It was produced after MS was sued by European Union interests to separate out those functions which are normally deeply integrated into the OS.

            C 1 Reply Last reply Nov 28, 2017, 10:56 PM Reply Quote 1
            • C
              Claudia Frank @no9on
              last edited by Nov 28, 2017, 10:56 PM

              @no9on

              can you double check the size of the exe and scintilla dll

              2599088 Nov 27 01:36 notepad++.exe
              1052848 Nov 27 01:36 SciLexer.dll

              Note, I’m using the zip version but the sizes must be the same.

              Thx, for clarification - wasn’t aware of it although I live in Europe.

              Cheers
              Claudia

              1 Reply Last reply Reply Quote 0
              • N
                no9on
                last edited by Nov 28, 2017, 11:09 PM

                Everything seems to check.

                notepad++.exe -> (2,599,088 bytes)

                SciLexer.dll -> (1,052,848 bytes)

                Again, it has to be in the code itself. Since the developer would probably have to partially reverse whatever changes were made, one-by-one, I will have to make this an EOL for me.At some point, I will re-install the OS, but for the moment, since everything else is functioning, I will postpone that.

                Thank you so much for your time.

                C 1 Reply Last reply Nov 28, 2017, 11:58 PM Reply Quote 0
                • C
                  Claudia Frank @no9on
                  last edited by Nov 28, 2017, 11:58 PM

                  @no9on

                  if you don’t mind one final suggestion.
                  Download procmon from sysinternals.

                  Run it and create a filter process name is notepad++.exe
                  Apply it

                  In main procmon gui press the icon which is named something like
                  process and threads (one of the last ones)

                  Start npp

                  Now you should see some infos coming in - are there any useful informations
                  which could indicate what your problem is?

                  Cheers
                  Claudia

                  1 Reply Last reply Reply Quote 0
                  • N
                    no9on
                    last edited by Nov 29, 2017, 2:12 AM

                    I certainly don’t mind any suggestions.
                    So, I ran procmon with the notepad++.exe filter for both the 7.5.2 version and the 7.5.1 version. Since the 7.5.1 version works, it has a much longer output log. There is a lot to go through and it will take me a good long time to see if I can make anything out of it, but I do have a preliminary catch.

                    I am comparing the two outs and the first instance of a difference seems to be a Load Image operation. This particular operation occurs with v7.5.2. The path is:

                    “…\Windows\System32\api-ms-win-core-synch-l1-2-0.dll”

                    The result for the operation says Success. Not sure why v7.5.1 did not have this operation at the same process location. The api-ms-win-core-synch-l1-2-0.dll type files are part of the VC++ 20xx redistributables.

                    Note: I ran the exe with four of the filter options, including Registry, File System Activity, Process and Threads, and Network (though I’m not on a LAN).

                    Thank you for the suggestion Claudia.

                    C 1 Reply Last reply Nov 30, 2017, 7:02 PM Reply Quote 0
                    • C
                      Claudia Frank @no9on
                      last edited by Nov 30, 2017, 7:02 PM

                      @no9on

                      as npp doesn’t show up I assume it crashes during image load. Don’t you see any error there?
                      A success means it was able to load it, so it can’t be the reason for the issue you encountered.

                      Cheers
                      Claudia

                      1 Reply Last reply Reply Quote 0
                      • N
                        no9on
                        last edited by Dec 1, 2017, 8:35 PM

                        OK, I isolated just the file system activity. The VC++ dll operations, even though they show success in loading, are only present in the latest, v7.5.2 version - and, calling them is the last step prior to failure to error reporting.

                        N++ v7.5.2
                        .
                        .
                        .
                        J:\Windows\System32\Wldap32.dll
                        J:\Windows\System32\uxtheme.dll
                        J:\Windows\System32\api-ms-win-core-file-l2-1-1.dll
                        Thread Create
                        Thread Create
                        J:\Windows\System32\api-ms-win-core-sysinfo-l1-2-1.dll
                        J:\Windows\system32\WerFault.exe
                        J:\Windows\System32\apphelp.dll
                        .
                        .
                        .
                        crash

                        N++ v7.5.1
                        .
                        .
                        .
                        J:\Windows\System32\Wldap32.dll
                        J:\Windows\System32\uxtheme.dll
                        Thread Create
                        Thread Create
                        J:\Windows\System32\WindowsCodecs.dll
                        J:\PortableApps\Notepad++\plugins\ccc.dll
                        J:\PortableApps\Notepad++\plugins\ccc.dll
                        J:\Windows\System32\version.dll
                        J:\Windows\System32\oleacc.dll
                        J:\Windows\System32\winspool.drv
                        J:\Windows\System32\winmm.dll
                        J:\Windows\System32\olepro32.dll
                        .
                        .
                        .
                        success

                        C 1 Reply Last reply Dec 2, 2017, 12:40 PM Reply Quote 0
                        • C
                          Claudia Frank
                          last edited by Dec 1, 2017, 9:06 PM

                          What are the actions (File, Process and Registry) just before

                          J:\Windows\system32\WerFault.exe

                          as this is the time when windows jumps in to collect information to report the issue.
                          Any errors just before this call?

                          Cheers
                          Claudia

                          1 Reply Last reply Reply Quote 0
                          • N
                            no9on
                            last edited by Dec 1, 2017, 10:26 PM

                            This includes Registry calls and File System activity leading up to WerFault.exe. Some repetitive registry keys may not be shown. The v7.5.1 is shown in the same spot for comparison.

                            There are definite differences, omissions, and additions to the two groups of apps with both file and registry processes.

                            N++ v7.5.2
                            .
                            .
                            .
                            J:\Windows\System32\Wldap32.dll

                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\WLDAP32.dll
                            HKLM\System\CurrentControlSet\Services\LDAP
                            .
                            .
                            .
                            HKLM\Software\Microsoft\Rpc\Extensions
                            HKLM\SOFTWARE\Microsoft\Rpc\Extensions\NdrOleExtDLL
                            HKLM\SOFTWARE\Microsoft\Rpc\Extensions
                            HKCU\Software\Classes
                            HKLM\Software\Microsoft\Rpc
                            HKLM\SOFTWARE\Microsoft\Rpc\MaxRpcSize
                            HKLM\SOFTWARE\Microsoft\Rpc

                            J:\Windows\System32\uxtheme.dll

                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\uxtheme.dll
                            HKLM\System\CurrentControlSet\Control\ComputerName\ActiveComputerName
                            HKLM\System\Setup
                            HKLM\SYSTEM\Setup\OOBEInProgress
                            HKLM\SYSTEM\Setup
                            HKLM\System\Setup
                            HKLM\SYSTEM\Setup\SystemSetupInProgress
                            HKLM\SYSTEM\Setup
                            HKLM\Software\Policies\Microsoft\Windows NT\Rpc
                            HKLM\Software\Policies\Microsoft\SQMClient\Windows
                            HKLM\SOFTWARE\Policies\Microsoft\SQMClient\Windows
                            HKLM\SOFTWARE\Policies\Microsoft\SQMClient\Windows\CEIPEnable
                            HKLM\SOFTWARE\Policies\Microsoft\SQMClient\Windows

                            J:\Windows\System32\api-ms-win-core-file-l2-1-1.dll

                            HKLM\Software\Policies\Microsoft\Windows\System
                            HKLM\SOFTWARE\Policies\Microsoft\Windows\System
                            HKLM\SOFTWARE\Policies\Microsoft\Windows\System\CopyFileBufferedSynchronousIo
                            HKLM\SOFTWARE\Policies\Microsoft\Windows\System

                            Thread Create

                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{423c6661-cfca-11e7-b7e1-806e6f6e6963}
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{423c6661-cfca-11e7-b7e1-806e6f6e6963}\Data
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{423c6661-cfca-11e7-b7e1-806e6f6e6963}\Generation

                            Thread Create

                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{2e1971d0-82c9-11e5-a7f7-806e6f6e6963}
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{2e1971d0-82c9-11e5-a7f7-806e6f6e6963}\Data
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{2e1971d0-82c9-11e5-a7f7-806e6f6e6963}\Generation

                            J:\Windows\System32\api-ms-win-core-sysinfo-l1-2-1.dll

                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\WerFault.exe

                            J:\Windows\system32\WerFault.exe

                            HKLM\System\CurrentControlSet\Control\Session Manager\AppCertDlls
                            HKLM\System\CurrentControlSet\Control\SafeBoot\Option
                            HKLM\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers

                            J:\Windows\System32\apphelp.dll
                            .
                            .
                            .
                            crash

                            ========
                            ////////

                            N++ v7.5.1
                            .
                            .
                            .
                            J:\Windows\System32\Wldap32.dll

                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\WLDAP32.dll
                            HKLM\System\CurrentControlSet\Services\LDAP
                            .
                            .
                            .
                            HKLM\Software\Microsoft\Rpc\Extensions
                            HKLM\SOFTWARE\Microsoft\Rpc\Extensions\NdrOleExtDLL
                            HKLM\SOFTWARE\Microsoft\Rpc\Extensions
                            HKCU\Software\Classes

                            J:\Windows\System32\uxtheme.dll

                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\uxtheme.dll
                            HKLM\Software\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST
                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST\FirstEntry
                            .
                            .
                            .
                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST\LastEntry
                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST\2015
                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST\2007
                            HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Pacific Standard Time\Dynamic DST

                            Thread Create

                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume
                            .
                            .
                            .
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume{423c6661-cfca-11e7-b7e1-806e6f6e6963}

                            Thread Create

                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\Volume
                            .
                            .
                            .
                            HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2{bb600dfd-cdb4-11e7-9b8d-806e6f6e6963}
                            HKLM\System\CurrentControlSet\Control\Nls\Locale
                            HKLM\System\CurrentControlSet\Control\Nls\Locale\Alternate Sorts
                            HKLM\System\CurrentControlSet\Control\Nls\Language Groups
                            HKLM\System\CurrentControlSet\Control\Nls\Locale\00000409
                            HKLM\System\CurrentControlSet\Control\Nls\Language Groups\1

                            J:\Windows\System32\WindowsCodecs.dll
                            J:\PortableApps\Notepad++\plugins\ccc.dll
                            J:\PortableApps\Notepad++\plugins\ccc.dll
                            J:\Windows\System32\version.dll
                            J:\Windows\System32\oleacc.dll
                            J:\Windows\System32\winspool.drv
                            J:\Windows\System32\winmm.dll
                            J:\Windows\System32\olepro32.dll
                            .
                            .
                            .
                            success

                            1 Reply Last reply Reply Quote 0
                            • C
                              Claudia Frank @no9on
                              last edited by Dec 2, 2017, 12:40 PM

                              @no9on

                              sorry, unfortunately nothing which makes me think this could be the problem.
                              Btw. the tests were done with clean npp setup, means no additional plugins used, correct?

                              Cheers
                              Claudia

                              1 Reply Last reply Reply Quote 0
                              2 out of 14
                              • First post
                                2/14
                                Last post
                              The Community of users of the Notepad++ text editor.
                              Powered by NodeBB | Contributors