If you are using PowerShell v3, you can use the Unblock-File</code> cmdlet.


The "blocking" part is simply an alternate data stream of the file, named "Zone.Identifier". You can display it in CMD by using input redirection (no other way to get to a stream in CMD, though):

H</span>:</span>\Downloads</span>></span> more </span><</span> test</span>.</span>exe</span>:</span>Zone</span>.</span>Identifier</span>
[</span>ZoneTransfer</span>]</span>
ZoneId</span>=</span>3</span></code></pre>
You can find them using dir /r</code> on Windows Vista and later:

2009</span>-</span>10</span>-</span>24</span>  12</span>:</span>18</span>        54.538</span>.</span>056</span> test</span>.</span>exe
</span>24</span> test</span>.</span>exe</span>:</span>Zone</span>.</span>Identifier</span>:</span>$DATA</span></code></pre>
Also in CMD you can easily get rid of that by overwriting it (using output redirection, this time):

echo</span>.></span>myDownloadedFile</span>.</span>exe</span>:</span>Zone</span>.</span>Identifier</span></code></pre>
which isn't quite</em> the same as removing the ADS completely, but works in that Explorer doesn't complain anymore.

There doesn't seem to be native support for handling ADS from within PowerShell (as mentioned on The PowerShell Guy's blog here</a>. That article also has some information how to get that functionality in PowerShell). You could, however, simply call cmd:

cmd </span>/</span>c </span>"echo.>test.exe:Zone.Identifier"</span></code></pre>
That works from PowerShell as well.

streams </span>-</span>d myDownloadedFile</span>.</span>exe</span></code></pre>
does work as well.

</div>

Another option would be Mark Russinovich's streams</code></a> utility which allows you to inspect a file's ADS and also to delete them. So