Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.

Mark Colvin · Jan 20, 2025, 7:59 PM

I have had this issue with Windows 10 and Windows 11 on the same computer. I have tried a number of simple fixes to stop the Windows Explorer crashes, without any final solution. It occurs every day, one to 5 times a day, seems to be random.
Recently, I cleared the Windows events logs to help narrow down the last event that occurred during the time that Windows Explorer windows just vanish.

This is the first time I have been able to find something that points to a cause.
I have a .DOCX file with Application events log entries and the noted windows.wer file in one of entries.

Since I was not using NPP application at the time of the Windows Explorer crash, I included the ?/debug info as well.
Please advise on further steps to determine if this is a REAL NPP problems or not.

TIA,
Mark Colvin

Applications Events:
Log Name: Application
Source: Microsoft-Windows-Security-SPP
Date: 1/20/2025 1:00:14 PM
Event ID: 16384
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: MAC-LAPTOP
Description:
Successfully scheduled Software Protection service for re-start at 2124-12-27T19:00:14Z. Reason: RulesEngine.
Event Xml:
<Event xmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=“Microsoft-Windows-Security-SPP” Guid=“{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}” EventSourceName=“Software Protection Platform Service” />
<EventID Qualifiers=“16384”>16384</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=“2025-01-20T19:00:14.6231386Z” />
<EventRecordID>933591</EventRecordID>
<Correlation />
<Execution ProcessID=“11492” ThreadID=“0” />
<Channel>Application</Channel>
<Computer>MAC-LAPTOP</Computer>
<Security />
</System>
<EventData>
<Data>2124-12-27T19:00:14Z</Data>
<Data>RulesEngine</Data>
</EventData>
</Event>

Log Name: Application***********Win11 Explorer Crash – all windows are gone*******
Source: Application Error
Date: 1/20/2025 1:00:56 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: MAC-LAPTOP\mcolv
Computer: MAC-LAPTOP
Description:
Faulting application name: explorer.exe, version: 10.0.26100.2454, time stamp: 0xdc9c700e
Faulting module name: NppShell.dll, version: 1.5.0.0, time stamp: 0x66880559
Exception code: 0xc0000409
Fault offset: 0x000000000001fc25
Faulting process id: 0x4824
Faulting application start time: 0x1DB6B446A90FD36
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Program Files (x86)\Notepad++\contextMenu\NppShell.dll
Report Id: 10985112-baaa-4f53-9f4e-9f3fedf967ce
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=“Application Error” Guid=“{a0e9b465-b939-57d7-b27d-95d8e925ff57}” />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime=“2025-01-20T19:00:56.5056321Z” />
<EventRecordID>933592</EventRecordID>
<Correlation />
<Execution ProcessID=“24492” ThreadID=“13172” />
<Channel>Application</Channel>
<Computer>MAC-LAPTOP</Computer>
<Security UserID=“S-1-5-21-2470100382-2049306416-2370556751-1001” />
</System>
<EventData>
<Data Name=“AppName”>explorer.exe</Data>
<Data Name=“AppVersion”>10.0.26100.2454</Data>
<Data Name=“AppTimeStamp”>dc9c700e</Data>
<Data Name=“ModuleName”>NppShell.dll</Data>
<Data Name=“ModuleVersion”>1.5.0.0</Data>
<Data Name=“ModuleTimeStamp”>66880559</Data>
<Data Name=“ExceptionCode”>c0000409</Data>
<Data Name=“FaultingOffset”>000000000001fc25</Data>
<Data Name=“ProcessId”>0x4824</Data>
<Data Name=“ProcessCreationTime”>0x1db6b446a90fd36</Data>
<Data Name=“AppPath”>C:\WINDOWS\explorer.exe</Data>
<Data Name=“ModulePath”>C:\Program Files (x86)\Notepad++\contextMenu\NppShell.dll</Data>
<Data Name=“IntegratorReportId”>10985112-baaa-4f53-9f4e-9f3fedf967ce</Data>
<Data Name=“PackageFullName”>
</Data>
<Data Name=“PackageRelativeAppId”>
</Data>
</EventData>
</Event>

Log Name: Applicationlast reported error******
Source: Windows Error Reporting
Date: 1/20/2025 1:01:00 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: MAC-LAPTOP\mcolv
Computer: MAC-LAPTOP
Description:
Fault bucket 2055285806913895911, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.26100.2454
P3: dc9c700e
P4: NppShell.dll
P5: 1.5.0.0
P6: 66880559
P7: 000000000001fc25
P8: c0000409
P9: 0000000000000007
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b7e9da55-425c-4334-ab3b-74c5a420e371.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20203e92-8fe2-41d5-ac29-367728e13626.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f32086fd-1fc9-4212-a7c2-465e271e24ee.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.74ed2b09-b61e-445f-8c8a-ff15cf1b7c16.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b389a25f-72a3-4d73-853e-16c0b3f34b2a.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.61d12e62-49d2-4d5c-a5ba-7db1229c5ed1.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d45344fd-f051-4979-99f6-731764e9ed2b.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_explorer.exe_75a7b1a2e2a87c6ffabace606d6bd8c9b7488325_83fa2685_813c2fee-6603-4a7e-bbda-e55df3128adf

*******got this file from the above folder: Report.wer ***************

Analysis symbol:
Rechecking for solution: 0
Report Id: 10985112-baaa-4f53-9f4e-9f3fedf967ce
Report Status: 268435456
Hashed bucket: 7b8ca4834f227c9a4c85d78d51013de7
Cab Guid: 0
Event Xml:
<Event xmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=“Windows Error Reporting” Guid=“{0ead09bd-2157-539a-8d6d-c87f95b64d70}” />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime=“2025-01-20T19:01:00.4010358Z” />
<EventRecordID>933593</EventRecordID>
<Correlation />
<Execution ProcessID=“24492” ThreadID=“13172” />
<Channel>Application</Channel>
<Computer>MAC-LAPTOP</Computer>
<Security UserID=“S-1-5-21-2470100382-2049306416-2370556751-1001” />
</System>
<EventData>
<Data Name=“Bucket”>2055285806913895911</Data>
<Data Name=“BucketType”>5</Data>
<Data Name=“EventName”>BEX64</Data>
<Data Name=“Response”>Not available</Data>
<Data Name=“CabId”>0</Data>
<Data Name=“P1”>explorer.exe</Data>
<Data Name=“P2”>10.0.26100.2454</Data>
<Data Name=“P3”>dc9c700e</Data>
<Data Name=“P4”>NppShell.dll</Data>
<Data Name=“P5”>1.5.0.0</Data>
<Data Name=“P6”>66880559</Data>
<Data Name=“P7”>000000000001fc25</Data>
<Data Name=“P8”>c0000409</Data>
<Data Name=“P9”>0000000000000007</Data>
<Data Name=“P10”>
</Data>
<Data Name=“AttachedFiles”>
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b7e9da55-425c-4334-ab3b-74c5a420e371.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.20203e92-8fe2-41d5-ac29-367728e13626.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20241008_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f32086fd-1fc9-4212-a7c2-465e271e24ee.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.74ed2b09-b61e-445f-8c8a-ff15cf1b7c16.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b389a25f-72a3-4d73-853e-16c0b3f34b2a.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.61d12e62-49d2-4d5c-a5ba-7db1229c5ed1.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d45344fd-f051-4979-99f6-731764e9ed2b.tmp.xml</Data>
<Data Name=“StorePath”>\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_explorer.exe_75a7b1a2e2a87c6ffabace606d6bd8c9b7488325_83fa2685_813c2fee-6603-4a7e-bbda-e55df3128adf</Data>
<Data Name=“AnalysisSymbol”>
</Data>
<Data Name=“Rechecking”>0</Data>
<Data Name=“ReportId”>10985112-baaa-4f53-9f4e-9f3fedf967ce</Data>
<Data Name=“ReportStatus”>268435456</Data>
<Data Name=“HashedBucket”>7b8ca4834f227c9a4c85d78d51013de7</Data>
<Data Name=“CabGuid”>0</Data>
</EventData>
</Event>

*****I was not using NPP at the time of the Windows Explorer windows crashed… but here it is:

Notepad++ v8.7.1 (32-bit)
Build time : Oct 31 2024 - 00:41:42
Path : C:\Program Files (x86)\Notepad++\notepad++.exe
Command Line : “C:\Users\mcolv\OneDrive\Desktop\WindowsCrash all windows gone\Report.wer”
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
Periodic Backup : ON
OS Name : Windows 8 Pro (64-bit)
OS Version : 24H2
OS Build : 9200.2894
Current ANSI codepage : 1252
Plugins :
AnalysePlugin (1.12.47)
BigFiles (0.1.1.1)
CodeAlignmentNpp (14.1.107)
ComparePlugin (2.0.1)
GitSCM (1.4.8.2)
HexEditor (0.9.12)
LocationNavigate (0.4.7.7)
MarkdownViewerPlusPlus (0.8.2)
mimeTools (3.1)
NavigateTo (1.12.3)
NppAutoIndent (1.2)
NppCalc (1.5)
NppConverter (4.6)
NppExport (0.4)
NppTextFX (0.2.6)
NppToolBucket (1.10.6622.41336)
SourceCookifier (0.7.3)
WindowManager (1.2.2)
_CustomizeToolbar (4.2)

there is more available, ran out of the 16K char limit…
=========END OF DEBUG INFO=============

Terry R · Jan 20, 2025, 8:17 PM

@Mark-Colvin

There are a number of queries I have.

Your PC is called MAC-LAPTOP, so is it an Apple Mac with virtualized Windows running?
You have a very long list of plugins. Have you checked that all of them are up to date with versioning?
Again to do with plugins, there is a FAQ post that refers to plugins possibly being the cause of abnormal issues. Have a read of Notepad++ Crashes/Freezes/Unresponsive after Update. See if you can apply some of the steps there.
Although you say you weren’t running Notepad++, had it been running at any time during the current Windows session prior to the crash occuring? Possibly some remnant was left in memory causing the crash at a later stage.

Terry

Nicholas · Jan 20, 2025, 9:21 PM

NppShell.dll is used to put the “Edit with Notepad++” into the file explorer context menu.

Since you are using 64bit Windows I would recommend using the 64bit version of Notepad++. Try the portable version first to check all your extensions work. You will need to use the plugin admin to download the 64bit versions or manually get the correct version.

If you don’t want to change versions, then you could try using the installer to disable the “Context Menu Entry”.

Nicholas · Jan 20, 2025, 9:32 PM

@Mark-Colvin said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

OS Name : Windows 8 Pro (64-bit)
OS Version : 24H2

This doesn’t look right. 24H2 is a Windows 11 version. There could be a bug where they are detecting the wrong version and trying to do something with the new Windows 11 context menu.

Mark Colvin · Jan 20, 2025, 9:48 PM

@Terry-R ,

This laptop computer is running a complete Win11 Pro OS. - MAC is named related identification.
Not recently checked plugin versioning. I will do that soon. [edit] performed plug-in updates, still crashed Explorer.
I assume that you suggested read my help with Windows Explorer random crashes when no directly using NPP?
That may be possible, but how can I tell this action is related to Explorer crashes?

Thanks.

Mark Colvin · Jan 20, 2025, 9:56 PM

@Nicholas
There were reasons during Win10 x64 usage of staying with NPP x32 instead of NPP x64. I don’t remember that reason at the moment. I think it had to do with another Windows apps running at the same time as NPP and there were problems. I will try to find the details on this decision.

But I will try disable the Content Menu feature on NPP to see if the Explorer crashes go away.
I can also try switching back to NPP x64 to see if I can find the reason for staying with NPP x32.

Thanks.

xomx · Jan 20, 2025, 11:37 PM

@Mark-Colvin

It is a buffer overflow caused somehow by the NppShell.dll in the Windows Explorer process. As a temporary workaround, you can disable this shell extension by going to your C:\Program Files (x86)\Notepad++\contextMenu\ folder and run there this command in cmd (with admin rights): regsvr32 /u NppShell.dll

This is a known problem for some users (they reported it for x64 too) but unfortunately I was not able to reproduce it, so I cannot say if it is a problem of NppShell shell extension, Notepad++ app or some other SW. It can also be a conflict with some other shell extension installed in your system (otherwise I cannot explain why most Notepad++ users do not have this problem).

If you switch to x64 Notepad++ with its x64 NppShell and you still get these Explorer crashes, you can try to follow these instructions to help me with debugging of the issue:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/15683#issuecomment-2492113826

@Mark-Colvin said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

OS Name : Windows 8 Pro (64-bit)

I am also surprised to see this info when according to your post it should be reported as Win10 or Win11.

xomx · Jan 21, 2025, 9:55 AM

@Mark-Colvin

Could you please report your Windows Registry relevant info:

Save the following to a file (named e.g. WinVerRegKeys-export.cmd) somewhere writable on your disk:

PowerShell "$Key='HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'; Get-ItemProperty -Path $Key -Name *" > WinVerRegKeys64.txt
PowerShell "$Key='HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion'; Get-ItemProperty -Path $Key -Name *" > WinVerRegKeys32.txt

Run the WinVerRegKeys-export.cmd batch file by e.g. doubleclicking on it in Explorer.
Take the contents of the created WinVerRegKeys32.txt and WinVerRegKeys64.txt files and post them please here.

Mark Colvin · Jan 23, 2025, 8:57 PM

@xomx ,
posted here are the files you requested.

Also, I uninstalled NPP x32 and not seen any Windows Explorer errors nor crashes for over 48 hours. (normal laptop usage, about 6 to 10 hours per day)

WinVerRegKeys32.txt


BaseBuildRevisionNumber   : 1
BuildBranch               : ge_release
BuildGUID                 : ffffffff-ffff-ffff-ffff-ffffffffffff
BuildLab                  : 26100.ge_release.240331-1435
BuildLabEx                : 26100.1.amd64fre.ge_release.240331-1435
CompositionEditionID      : Enterprise
CurrentBuild              : 26100
CurrentBuildNumber        : 26100
CurrentMajorVersionNumber : 10
CurrentMinorVersionNumber : 0
CurrentType               : Multiprocessor Free
CurrentVersion            : 6.3
DisplayVersion            : 24H2
EditionID                 : Enterprise
EditionSubManufacturer    : 
EditionSubstring          : 
EditionSubVersion         : 
InstallationType          : Client
InstallDate               : 0
ProductName               : Windows 10 Enterprise
ReleaseId                 : 2009
SoftwareType              : System
SystemRoot                : C:\WINDOWS
UBR                       : 2894
RegisteredOwner           : __________@gmail.com
PSPath                    : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windo
                            ws NT\CurrentVersion
PSParentPath              : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windo
                            ws NT
PSChildName               : CurrentVersion
PSDrive                   : HKLM
PSProvider                : Microsoft.PowerShell.Core\Registry

WinVerRegKeys64.txt



SystemRoot                : C:\WINDOWS
BaseBuildRevisionNumber   : 1
BuildBranch               : ge_release
BuildGUID                 : ffffffff-ffff-ffff-ffff-ffffffffffff
BuildLab                  : 26100.ge_release.240331-1435
BuildLabEx                : 26100.1.amd64fre.ge_release.240331-1435
CompositionEditionID      : Enterprise
CurrentBuild              : 26100
CurrentBuildNumber        : 26100
CurrentMajorVersionNumber : 10
CurrentMinorVersionNumber : 0
CurrentType               : Multiprocessor Free
CurrentVersion            : 6.3
DisplayVersion            : 24H2
EditionID                 : Professional
EditionSubManufacturer    : 
EditionSubstring          : 
EditionSubVersion         : 
InstallationType          : Client
InstallDate               : 1732282151
LCUVer                    : 10.0.26100.2894
ProductName               : Windows 10 Pro
ReleaseId                 : 2009
SoftwareType              : System
UBR                       : 2894
PathName                  : C:\Windows
PendingInstall            : 0
ProductId                 : 00330-53097-84373-AAOEM
DigitalProductId          : {164, 0, 0, 0...}
DigitalProductId4         : {248, 4, 0, 0...}
RegisteredOwner           : __________@gmail.com
InstallTime               : 133767557516344286
PSPath                    : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows 
                            NT\CurrentVersion
PSParentPath              : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
PSChildName               : CurrentVersion
PSDrive                   : HKLM
PSProvider                : Microsoft.PowerShell.Core\Registry

Sorry, not enough karma to attach files to posts yet. Supplied as code.

Mark
—
moderator edited to remove real email address

xomx · Jan 23, 2025, 8:57 PM

@Mark-Colvin

Thanks.
But I didn’t find anything wrong in your data (that could explain your previously reported Win8).

But all this gives me the idea that perhaps the affected users here have something unusual/wrong in their Registry, which in turn causes the N++ shell extension to crash. I have checked the NppShell source code and indeed - some parts of the code are not the best in terms of resilience to unexpected input or some resource or data unavailability. I didn’t manage to crash Explorer exactly the same way as all affected users report, but in principle that could be it (maybe I just didn’t simulate the right bad data in the Registry).

I’ll try to raise some questions in the NppShell project issues.

Mark Colvin · Jan 28, 2025, 9:49 PM

@xomx ,

Update: I installed npp.8.7.5.Installer.x64 five days ago without Context Menu feature and fewer plugins. So far, no Windows Explorer crashes.

I really miss the Context Menu feature, NPP is so easy to open many file types with this quick step for a quick peek.

I will re-configure NPP soon with Context Menu turned on and see if the problem returns. Any advice on data collection for this issue if it re-occurs?

TIA,
Mark

xomx · Jan 29, 2025, 2:44 PM

@Mark-Colvin said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

Any advice on data collection for this issue if it re-occurs?

As I already said:

@xomx said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

If you switch to x64 Notepad++ with its x64 NppShell and you still get these Explorer crashes, you can try to follow these instructions to help me with debugging of the issue:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/15683#issuecomment-2492113826

So if you can, please follow the instructions in that GitHub comment and then somehow forward me the relevant Explorer crash dump file generated along with a possible NppShell.log.

If the GitHub procedure seems too complicated for you - the main thing is to get the crash-dump file while using my special version of the “C:\Program Files\Notepad++\contextMenu\NppShell.dll”, so download it and after the usual reinstall of your Notepad++ with the shell context extension, replace the standard NppShell.dll file there with the file from this archive: https://github.com/user-attachments/files/17850910/NppShell_v1500_x64_Debug.zip

If you have any questions about the GitHub instructions, do not hesitate to ask me.

Mark Colvin · Jan 29, 2025, 2:44 PM

@xomx ,
Thank you for the alternatives on this investigation. I will update as I get more information.

Thanks again,
Mark

Mark Colvin · Jan 30, 2025, 6:02 PM

@xomx,
Posted dump file and error dialog at:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/15683#issuecomment-2492113826

Saw when open .ZIP file… got the error dialog, clicked retry, and all explorer windows vanished.
Hope it helps…

Mark Colvin · Jan 30, 2025, 10:56 PM

@xomx,
5 hours later, another error with NppShell.DLL, but no new dump file created.
This occurred during a copy/paste operation from one Window to another.

xomx · Feb 5, 2025, 8:43 PM

@Mark-Colvin

Could you please check if you are not running N++ in Windows8 compatibility mode? More about it here.

Mark Colvin · Feb 5, 2025, 8:43 PM

@xomx
How does this compatibility mode affect the Explorer context menu invocations?
The one Shortcut I have is NOW set to Compatibility mode with Windows 8. But rarely use it directly…

What about the errors with NppShell.DLL which occur without NP++ even turned on?
(I am missing something on how this NppShell.DLL works outside of NP++)
See NppShell.log files posted in github thread…

Thanks,
Mark

xomx · Feb 9, 2025, 2:25 PM

@Mark-Colvin said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

How does this compatibility mode affect the Explorer context menu invocations?

Good point, this probably influences the N++ app only and not the NppShell extension DLL invoked by the shell Explorer.

David MS · Apr 22, 2025, 2:25 PM

Hello,

I have also constantly the problem that NppShell.dll crashes the Windows 11 Explorer.
After uninstalling Notepad++ the explorer runs without crahes.

I use the latest version of Notepad++ (8.7.9).

Does exists a workaround or a fix?

Thank you very much.

Best regards,

David

xomx · Apr 22, 2025, 11:30 PM

@David-MS said in Notepad++ v8.7.1 (32-bit) NppShell.dll is intermittently crashing Windows Explorer.:

Does exists a workaround

If you mean by this a workaround to not have to completely uninstall the N++ for preventing the Explorer crashes, then yes - unregistering of the NppShell context-menu handler helps: https://community.notepad-plus-plus.org/post/99261

or a fix?

I could not exactly reproduce the issue myself but found some potential problematic places in the NppShell source code and put a “hardening” of that code to my TODO. Unfortunately not enough free time yet. More info and possible future progress in the GitHub issue.