As
@oldschool mentioned, I downloaded the update from the VS site. and then executed it. SmartScreen popped, and I chose to pass on the update. The last thing I need to do is to install compromised security software. Since insufficient into existed to determine an FP, I went the conservative route.
So, SmartScreen saved the users from installing the beta version.
But, the main thing is that the updater was downloaded/executed by you, so your post cannot be related to my post:
"Dan is wrong when thinking that Windows native SS could block the VoodooShield update.
Any update made by VoodooShield does not attach MOTW. " Of course, the developer has to implement updates via application to avoid SmartScreen false positives (developers know it from years).
It is probable, that I misinterpreted Dan's words, and he had in mind not the future VS version with implemented SmartScreen, but the actual situation with 5.01 beta version.
Nope. Even stopped the VS service. Redownloaded 5.01 and no change. SmartScreen does not like 5.01.
SmartScreen cannot stop a service. Did you see the SmartScreen alert for that service?
Anyway, it is impossible because the service binary was not downloaded via the web browser to your disk (it is never recognized as a file from the Internet).
Generally, SmartScreen can block files downloaded from the Internet or files that have attached MOTW in another way (forced SmartScreen). It cannot block application executables which were dropped to disk by installer or updater (also any malware downloader). So, something else blocked the service.
You probably know most of the above. I wrote this for other readers because most readers have a problem with understanding how SmartScreen works.
