@shridhar-singh Yes, this is most propably related to the discussion above. You can try to remove some plugins to the one who is responsible for that or just wait for the next Notepad++ release which fixes it.

in my windows 10, last version fixed this problem. you can upgrade to notepad.

I’ve done quite extensive debug testing and troubleshooting on an issue which arose after 8.5.5.

In short, Notepad++ simply won’t visibly open when being opened from another application which uses VFS (Virtual File System). I say “visibly” because when looking at debug logs, the program seems to open before closing or crashing right after.

Downgrading to 8.5.4 fixes the incompatibility issue.

Kindly let me know if you’d like me to share my more extensive troubleshooting, thanks!

But I am in holiday for 2 weeks and took my Notebook with me and I am not able to reproduce the issue on my Notebook (Windows 11) . Therefore I can’t unfortunately confirm that the fix does the trick.

But once the new exe is available for download I can ask the SQLinForm Plugin User, who reported the issue, to inform me about the results.

When will the new exe be available for public download?

I have just pushed a new commit which fixes plugin crash into master here:
https://github.com/notepad-plus-plus/notepad-plus-plus/commit/c45d7aca75211434651745059647f4c29bac7ec6

Please let me know if it fixes your problem.

I first was able to reproduce the crash from the 64bit SQLinForm Plugin together with N++ 8.5.5 , which has been reported by a plugin user, on my Desktop PC (Windows 11) in my office.

Now I am in holiday with my Notebook (Windows 11) and can’t reproduce the error anymore.

So, I think I first should be able to reproduce the crash on my Notebook and then in a seconde step try to make it working again using your instructions.

Can I myself change the CETCOMPAT Flag?

If you’re running Windows 11, you can try this:

• Start the Run dialog: ⊞ (Windows key) + R. Enter windowsdefender: and click “OK”
• From the left-hand menu, click “App & browser control”
• In the “Exploit protection” section, click Exploit protection settings
• Select the “Program settings” tab
• Click “＋ Add program to customize” and choose an option, “program name” or “exact path”
• Depending on your choice, enter Notepad++ in the input box, or navigate to the notepad++.exe file in the explorer
• In the menu that appears, find “Validate exception chains (SEHOP)”, choose “Override system settings” and slide the radio button to “Off”

You should do the same for “Control Flow Guard (CFG)” and “Validate heap integrity”, but I would apply all overrides one-by-one to pin down which is effective, if any.

If @Fruchtzwerg94 is right and the issue really is Control Enhancement (CET), then Win 11 users are more likely to encounter it, as the comments on this related GitHub issue suggest. Exploit mitigation features like CET are enabled by default on Win 11, whereas Win 10 users have to manually activate them. Hardened security was, after all, the main selling point of the new OS.

Many thenks
Guido

I am facing an interesting problem after upgrading Notepad++ to the latest version. It is related to the change of commit ‘Enable optimization flags & CET’.
To break it down: Due to the change

<CETCompat>true</CETCompat>

plugins may cause a crash if they catch an exception internally. I am clearly able to reproduce this with my PlantUMLViewer plugin. During its initialization, it catches an IOEcxception. Due the CETCOMPAT feature enabled, Notepad++ detects this as a violation and stops without any further information.

More details about the feature:

• Developer Guidance for Hardware-enforced Stack Protection
• /guard:ehcont (Enable EH Continuation Metadata)

I was not able to find a better solution yet than disabling CETCOMPAT for the Notepad++ build. I assume other plugins could be affected as well here.
Do you have an idea how to deal with this? Maybe its better to disable the feature again?

2. Add change history navigation commands: Go to next/prev change & Clear change history.

A little visual on this:

13. Make find/replace in files result more inaccurate while used RegExpr is invalid. (Fix #13164)

I think the phrasing here should be “more accurate”…unless…? :-)