Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 833549" data-attributes="member: 32260">Some people (on another forum) think that the WD ASR rule &quot;Block untrusted and unsigned processes that run from USB&quot; is just SmartScreen forced on files executed from USB drives (similarly to &quot;Run By SmartScreen&quot;). But, it is not, in fact. For example, I can run without SmartScreen alert some unsigned applications with MOTW, downloaded to my hard disk from the Internet. But, the same files are blocked by this ASR rule when ran from the USB drive.Furthermore, if the file is blocked on the USB drive, then it is also blocked on the hard disk after copying it to this hard disk. You can get rid of the block on the hard disk, by renaming the file on the hard disk.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /></blockquote>

[QUOTE="Andy Ful, post: 833549, member: 32260"] Some people (on another forum) think that the WD ASR rule "Block untrusted and unsigned processes that run from USB" is just SmartScreen forced on files executed from USB drives (similarly to "Run By SmartScreen"). But, it is not, in fact. For example, I can run without SmartScreen alert some unsigned applications with MOTW, downloaded to my hard disk from the Internet. But, the same files are blocked by this ASR rule when ran from the USB drive. Furthermore, if the file is blocked on the USB drive, then it is also blocked on the hard disk after copying it to this hard disk. You can get rid of the block on the hard disk, by renaming the file on the hard disk.(y) [/QUOTE]

Verification