{"id":3148,"date":"2017-05-24T09:59:16","date_gmt":"2017-05-24T16:59:16","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=3148"},"modified":"2017-05-24T09:59:16","modified_gmt":"2017-05-24T16:59:16","slug":"microsoft-smartscreen-filter","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/windows\/microsoft-smartscreen-filter\/","title":{"rendered":"Why Does Windows SmartScreen Flag Our Software?"},"content":{"rendered":"<div align=\"center\"><img decoding=\"async\" src=\"\/blog\/images\/smartscreen-warning.png\" title=\"Windows SmartScreen Filter Warning\" alt=\"Windows SmartScreen Filter Warning\" border=\"0\" width=\"520\"><\/div>\n<p>Last month we released a new version of our popular run-anything-as-a-windows-service software, <a href=\"\/products\/AlwaysUp\/\">AlwaysUp<\/a>. Everything was going smoothly &#8212; until we encountered a very alarming situation while testing the new software on Windows 10!<\/p>\n<p>After downloading the new AlwaysUp installation executable with <a href=\"https:\/\/www.microsoft.com\/en-us\/windows\/microsoft-edge\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Edge<\/a>, the browser asserted that <b>&#8220;AlwaysUp_Installer.exe is not commonly downloaded and may harm your computer&#8221;<\/b>. WHAT?? <\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/windows-10-smartscreen-filter-alwaysup.jpg\" class=\"zoomPopup\" rel=\"zoomgroup noopener noreferrer\" title=\"SmartScreen Filter complains about AlwaysUp\" target=\"_blank\"><br \/>\n<img decoding=\"async\" src=\"\/blog\/images\/windows-10-smartscreen-filter-alwaysup.jpg\" title=\"SmartScreen Filter complains about AlwaysUp (click to enlarge)\" alt=\"SmartScreen Filter complains about AlwaysUp\" border=\"0\" width=\"520\"><\/a><\/div>\n<\/p>\n<p>Clicking the <b>Actions<\/b> button gave us the option to &#8220;Run Anyway&#8221;, and the installation completed without further incident, but the whole experience left our team worried and full of questions. Specifically:<\/p>\n<ul>\n<li>Why did this suddenly start happening?<\/li>\n<li>How will our customers react to Microsoft&#8217;s unfounded suspicions?<\/li>\n<li>And most importantly, how do we get rid of the chilling warnings?<\/li>\n<\/ul>\n<h2><b>SmartScreen Complains because our Software is &#8220;New&#8221;<\/b><\/h2>\n<p>Apparently we&#8217;re not the only developers tormented by SmartScreen. Warnings are common, especially for small software companies like ours. The &#8220;Criticism&#8221; section of the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Microsoft_SmartScreen\" target=\"_blank\" rel=\"noopener noreferrer\">Wikipedia article on SmartScreen Filter<\/a> says it best:<\/p>\n<blockquote><p>\n<img loading=\"lazy\" decoding=\"async\" src=\"\/blog\/images\/quote-left-black.gif\" width=\"16\" height=\"16\"> SmartScreen Filter creates a problem for small software vendors when they distribute an <b>updated version of installation or binary files over the internet<\/b>. Whenever an updated version is released, SmartScreen responds by stating that the file is not commonly downloaded and can therefore install harmful files on your system.\n<\/p><\/blockquote>\n<h2><b>Only a Few Customers are Blocked by SmartScreen Filter<\/b><\/h2>\n<p>To date, only one customer has asked about SmartScreen&#8217;s warning. We had expected hundreds! Fortunately there are a few reasons why many customers aren&#8217;t being tripped up by Microsoft&#8217;s overly cautious approach:<\/p>\n<ol>\n<li>Our products are digitally signed for security and authenticity. SmartScreen takes this as a positive sign and is likely to avoid prompting all customers all the time.<\/li>\n<li>Prior to Windows 8, SmartScreen Filter was a part of Internet Explorer. Thus customers using Chrome or Firefox on Windows 7 and Server 2008 will never encounter SmartScreen warnings.<\/li>\n<li>After testing downloads on Windows 8, 10 and Windows Server 2012 and 2016, we only received warnings on Windows 10 with Edge.<\/li>\n<\/ol>\n<p>So it seems that SmartScreen warnings are largely limited to customers using Internet Explorer or Edge. Metrics gathered from our website (via the incredibly useful <a href=\"http:\/\/statcounter.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">StatCounter<\/a>) tell us that <b>only about 11%<\/b> of all visitors are using those browsers:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/alwaysup-browser-stats.png\" class=\"zoomPopup\" rel=\"zoomgroup noopener noreferrer\" title=\"AlwaysUp Browser Statistics\" target=\"_blank\"><br \/>\n<img decoding=\"async\" src=\"\/blog\/images\/alwaysup-browser-stats.png\" title=\"AlwaysUp Browser Statistics (click to enlarge)\" alt=\"AlwaysUp Browser Statistics\" border=\"0\" width=\"520\"><\/a><\/div>\n<\/p>\n<h2><b>Time (and Good Behavior) will Disarm SmartScreen Filter<\/b><\/h2>\n<p>We hoped for a simple solution: Inform Microsoft that our software is 100% safe and they would promptly update their SmartScreen database to remove all warnings. All would be right with the world. But SmartScreen doesn&#8217;t work like that.<\/p>\n<p>SmartScreen is reputation based. Each time someone downloads our software package and declares that it is safe to install, that executable gains some positive reputation. Once enough people have successfully installed and the accumulated reputation crosses some magic threshold, the warnings disappear. Only an established track record of doing no harm will halt the SmartScreen dogs.<\/p>\n<p>Indeed, after a couple of weeks the warnings for AlwaysUp version 10 seems to have gone away:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/alwaysup-download-edge.png\" class=\"zoomPopup\" rel=\"zoomgroup noopener noreferrer\" title=\"AlwaysUp Download - No SmartScreen Warning\" target=\"_blank\"><br \/>\n<img decoding=\"async\" src=\"\/blog\/images\/alwaysup-download-edge.png\" title=\"AlwaysUp Download - No SmartScreen Warning (click to enlarge)\" alt=\"AlwaysUp Download - No SmartScreen Warning\" border=\"0\" width=\"520\"><\/a><\/div>\n<\/p>\n<p>Yay!<\/p>\n<!-- relpost-thumb-wrapper --><div class=\"relpost-thumb-wrapper\"><!-- filter-class --><div class=\"relpost-thumb-container\"><style>.relpost-block-single-image, .relpost-post-image { margin-bottom: 10px; }<\/style><h3>You may also like...<\/h3><div style=\"clear: both\"><\/div><div style=\"clear: both\"><\/div><!-- relpost-block-container --><div class=\"relpost-block-container relpost-block-column-layout\" style=\"--relposth-columns: 3;--relposth-columns_t: 2; --relposth-columns_m: 2\"><a href=\"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/eliminate-console-app-errors\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"Q&amp;A: How do I Eliminate Errors from my C# Console App Windows Service?\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/service-error-150x150-1.png\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">Q&amp;A: How do I Eliminate Errors from my C# Console App Windows Service?<\/h2><\/div><\/div><\/a><a href=\"https:\/\/www.coretechnologies.com\/blog\/software\/dropbox-selective-sync-popup\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"Watch out for Dropbox Prompts when Running as a Service!\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/hand-stop-150x150.png\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">Watch out for Dropbox Prompts when Running as a Service!<\/h2><\/div><\/div><\/a><a href=\"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/netman-service-warning\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"Q&amp;A: Why can&#039;t AlwaysUp Open the Netman Service?\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/network-service-150x150-1.png\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">Q&amp;A: Why can&#039;t AlwaysUp Open the Netman Service?<\/h2><\/div><\/div><\/a><\/div><!-- close relpost-block-container --><div style=\"clear: both\"><\/div><\/div><!-- close filter class --><\/div><!-- close relpost-thumb-wrapper -->","protected":false},"excerpt":{"rendered":"<p>Last month we released a new version of our popular run-anything-as-a-windows-service software, AlwaysUp. Everything was going smoothly &#8212; until we encountered a very alarming situation while testing the new software on Windows 10! After downloading the new AlwaysUp installation executable &hellip; <a href=\"https:\/\/www.coretechnologies.com\/blog\/windows\/microsoft-smartscreen-filter\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":3154,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[26,73,92,143,156],"class_list":["post-3148","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-windows","tag-alwaysup-tag","tag-edge-browser","tag-internet-explorer","tag-security","tag-smartscreen-filter"],"_links":{"self":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/3148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/comments?post=3148"}],"version-history":[{"count":0,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/3148\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/media\/3154"}],"wp:attachment":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/media?parent=3148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/categories?post=3148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/tags?post=3148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}