Just TODAY I generated a text file via a bash script, and when attempting to open it in Notepad++ Windows insisted on warning me about potential hazards because it couldn’t verify who created the file. A text file! Heavens. I wonder how long I’ll last in that blasted Windows centric environment.
I call BS. More likely notepad++ attempted to update and their new installer is no longer signed as the developer has been having issues getting a new signing certificate based on the app name (they want a legal identity).
No, Windows Explorer itself does this when attempting to access network files under some byzantine set of conditions I’ve never been able to get to the bottom of. For instance, my machine at work bitches at me whenever I attempt to open or copy any log file (which is obviously just a text file) from either of my Linux based servers.
I use Notepad++ also, and trying to open one of these files either from Explorer or the file open dialog in NP++ triggers the warning.
I literally did it just now to generate this screenshot.
Okay that is a common error when accessing unknown network shares and network settings are misconfigured. Need to add whatever IP or network name to intranet zone. It’s not to do with the file type or contents.
Just TODAY I generated a text file via a bash script, and when attempting to open it in Notepad++ Windows insisted on warning me about potential hazards because it couldn’t verify who created the file. A text file! Heavens. I wonder how long I’ll last in that blasted Windows centric environment.
Not so far-fetched when you realize that Windows crams AI into everything and the text file might contain malicious instructions.
It was a text file with 80 rows of `username=“username username@example.com” mappings (for an svn to git conversion). Nothing nefarious.
Yeah, but honestly it wouldn’t even need AI to have this issue with the kind of bloated spaghetti code that MS seems to produce.
I call BS. More likely notepad++ attempted to update and their new installer is no longer signed as the developer has been having issues getting a new signing certificate based on the app name (they want a legal identity).
No, Windows Explorer itself does this when attempting to access network files under some byzantine set of conditions I’ve never been able to get to the bottom of. For instance, my machine at work bitches at me whenever I attempt to open or copy any log file (which is obviously just a text file) from either of my Linux based servers.
I use Notepad++ also, and trying to open one of these files either from Explorer or the file open dialog in NP++ triggers the warning.
I literally did it just now to generate this screenshot.
Okay that is a common error when accessing unknown network shares and network settings are misconfigured. Need to add whatever IP or network name to intranet zone. It’s not to do with the file type or contents.
It was most certainly not Notepad trying to update, it very definitely was Windows intercepting the file open process.
the ongoing security nightmare that is the np++ auto-update mechanism continues to generate content