Had a lovely experience with this a few months ago. I built a little WPF GUI as an internal tool for my company. Literally all it does is read some data from an

Had a lovely experience with this a few months ago. I built a little WPF GUI as an internal tool for my company. Literally all it does is read some data from an XML file and squirt some bytes out of a serial port. I zip up a build and send it over to the production team and windows refuses to open it. It absolutely insists it's a Trojan or something. Fortunately there's an option to ignore Defender and keep doing our jobs. I submitted the build to Microsoft for verification and it reports totally clean. Gee, thanks. We also get Defender warnings for anything that isn't signed. We also get Defender warnings for things that are signed. Apparently we have to pay an extra couple hundred dollars a month for the "real" signing certificate. The one we already pay for apparently isn't secure enough to disable Defender warnings? Sounds like an absolute racket to me