this post was submitted on 23 Sep 2025
766 points (98.6% liked)
Microblog Memes
9320 readers
3336 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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