Running Brother printers cos they seem to be the sanest option.
Today the Win11 AV Defender slop stopped entire SW for printer because it's missing some signature on .dll file.
There was no update on the printer SW so some Defender database update cause this perhaps.
So no one in the family can get the printer to work now ffs.
Interestingly the scanning from printer to linked PC does work, despite it calls the same SW to process the job, perhaps not entire stack.
Anyway, hate printers.
(On Linux it does work but it's finicky.)
npub1m4…sc2n3
2026-08-23 21:43:55 UTC
Author Public Key
npub1m4d4mtxnj6ka8zmntupledeud29hh0vu7w74768gc0fp89dxjmsq3sc2n3Seen on
wss://nostr.momPublished at
2026-08-23 21:43:55 UTCEvent JSON
{
"id": "000000dc5a2b36bc6902afd03969f3dee6bca85aa07c1c449d48224a71596ac9",
"pubkey": "dd5b5dacd396add38b735f03fcb73c6a8b7bbd9cf3bd5f68e8c3d21395a696e0",
"created_at": 1787521435,
"kind": 1,
"tags": [
[
"nonce",
"4226",
"21"
]
],
"content": "Running Brother printers cos they seem to be the sanest option.\nToday the Win11 AV Defender slop stopped entire SW for printer because it's missing some signature on .dll file.\n\nThere was no update on the printer SW so some Defender database update cause this perhaps.\n\nSo no one in the family can get the printer to work now ffs.\nInterestingly the scanning from printer to linked PC does work, despite it calls the same SW to process the job, perhaps not entire stack.\n\nAnyway, hate printers.\n\n(On Linux it does work but it's finicky.)",
"sig": "2277bacf164e33fc419fbd229237f012084cc6ff5cb7402b8824e0f80150f07579ca8d8cf29106c8d76c17b7bba86e81f4fc3348a94e5926281c4f5f763cf0c2"
}