you are viewing a single comment's thread
view the rest of the comments
[–] 54 points 1 year ago (8 children)

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.

  • source
  • hideshow 8 child comments
  • [–] 46 points 1 year ago (2 children)

    Not so far-fetched when you realize that Windows crams AI into everything and the text file might contain malicious instructions.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 year ago (4 children)

    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).

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    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.

  • source
  • parent