@Coises said: I expect that Version 0.6.5 will fix this. Noted, thanks again, and I’ll let him know — although he actually doesn’t typically use regex for his own purposes.

@PeterJones Ah sorry! I was thinking afterwards there must be an && and didn’t pay attention to your hyperlink. I checked it out thanks!!! One other question. So if I search using (?=.*Error)(?=.*Foobar1)(?=.*Foobar2) With regular expression and newline checked. I do see it boil down to the files I am interested in. My only other need is to see all the lines associated/contained with the AND. It just shows the chunk of text from the beginning of the file to the first match it finds which in this example is Foobar1. I was more interested in seeing each line (e.g. also Error) that matched. I didn’t see this in the help page. Maybe this is not possible but thought I would ask. Thanks for all your help so far!

@J-Mark-Barfield , that was not a “regedit”, that was a normal command-line command all those two commands did was run an instance of notepad++.exe without RunAsAdmin privileges, even before you made the change to the executable compatibility settings it was completely unnecessary all you had to do was exit Notepad++ application completely (so it wasn’t running), then do the steps I explained to get notepad++.exe to not run as admin, and then the next time you ran Notepad++ (either using your shortcut or double clicking on the exe or running the exe from the command line normally or double clicking on a text file or right clicking and choosing Edit with Notepad++) would have run Notepad++ not as admin if you didn’t exit Notepad++ first, then the still running Notepad++ instance would still be running as Admin. Changing the exe properties while the exe is running doesn’t magically drop the running Notepad++ out of Admin mode. And thus your right click would not have worked, because the running Notepad++ was still in Admin mode. all you did by doing those extra commands was close the Notepad++ that was running as admin open a new instance that wasn’t running as admin change the exe properties so that it wouldn’t run as admin next time (I understand that you got it working, so you don’t really care at this point. But I don’t want future people to read this discussion, and come to the wrong conclusion that they need to do your extra steps. Those steps were completely unnecessary.)

@PeterJones thanks mate.

@PeterJones i check both the shortcut and the actual file, and both of them have the “run as administrator” unchecked. so any ideas why it keeps opening in admin mode? inside AppData i have only 3 folders: local, locallow, and roaming

Search++ version 0.6.5 is available: Update to ICU 78.3 and use static linking for ICU. This is expected to fix problems some testers have had running Search++ on older systems or on minimal Windows installs (like Windows Sandbox). For most users there will be no functional difference between this version and version 0.6.4. Note: There are five icu——.dll files in older versions of Search++ that are not used beginning with version 0.6.5; so it is best to delete the existing Search++ folder (or its contents) before copying, rather than copying the new folder over the old one.

@Passant-Delarue , Initial guess: turn off “. matches newline”, otherwise your .* will greedily match the whole file.