Microsoft Defender SmartScreen is hurting independent developers • Hacker News Board

Re: Microsoft Defender SmartScreen is hurting independent developers

#241

Post by luord » Wed, Jun 03, 2020, 10:29 PM UTC

I like to think that these stupid corporations would try harder at solving the problems they create if whenever those problems are mentioned, those corporations didn't get dozens of apologists. Or maybe I'm just frustrated.

Microsoft doesn't need some oddly loyal developers defending them nor the free publicity they provide. Developers affected by stuff like this don't need some guy asking them what they would do better. It's not indie developers' job to fix microsoft, it's microsoft's.

Re: Microsoft Defender SmartScreen is hurting independent developers

#242

Post by wronex » Thu, Jun 04, 2020, 4:09 PM UTC

mehrdadn wrote: post #209

wronex wrote: post #187

Please note that EV code signing certificates are not the magic bullet they first appear. SmartScreen is reputation based. An EV code signing certificate does not grant immediate access. You will have to build reputation regardless. There is no pay to win solution. I've learnt this the hard way. You can however place the executable in a Zip archive to bypass SmartScreen. An unzipped file won't bear the mark of the we…

Wait really? How do you unzip your files? I thought files unzipped inside with Windows's built-in unzipper still keep the attachment manager metadata that Windows stores?

You are correct.

I've been using 7zip. It does clear the flag. Windows built-in unzipper does not.

Re: Microsoft Defender SmartScreen is hurting independent developers

#243

Post by my123 » Tue, Jun 09, 2020, 1:52 PM UTC

Wowfunhappy wrote: post #132

my123 wrote: post #107

Earlier quoted context omitted.

There is: bcdedit -set testsigning on and bcdedit -set nointegritychecks on

This works for some drivers and not others! EDID overrides, for example, require the rigamarole I described. (The command you mentioned does need to be run regardless, or even drivers installed when rebooted into the special mode will actually stop working after the next reboot.) If anyone understands more about the differences, I'd be very curious to learn more...

Unsigned will stop working, you need to self-sign with any key for it to last.