Bulk Unblock of Files

I think since XP SP2 days, a new security attribute was added to files
such that files that came in by IM, email, or across the network were
separately identified and blocked from being executed. To unblock,
one need to go the Properties of the file and then click the Unblock
button.

XP was rather lax in enforcing blocking. But Vista appears to block
everything, including html files inside a zip file.

Each time I unzip the contents of a compressed file, I have to go and
unblock each and every of its files. What is the method to Unblock
more than one file at a time? The moment I select two files, the
Unblock button cannot be seen anymore, even if both individually is
blocked. What is the Windows Powershell cmdlet to unblock a file?

Thanks for any help.

S & B

PS: I went to Windows Help and Support and enter "Unblock a file" as
search words, but the first 30 results were not relevant to the
subject.

This is a PowerShell forum.. but in the spirit of it, you just need to go to
User Configuration > Administrative Templates > Windows Components >
Attachment Manager and enable 'Do not preserve zone information in file
attachments'

"Sue & Bill" wrote:

You can use this tool from SysInternals, Streams, ie the -d option

Streams v1.56
http://technet.microsoft.com/en-us/s.../bb897440.aspx


--
Jon


"Sue & Bill" <sue.and.bill@xxxxxx> wrote in message
news:463bbc44-ba90-4840-af1e-695a856e561c@xxxxxx

On Jan 11, 2:05*pm, NeilOz <Nei...@xxxxxx> wrote: Mmm.... thanks. I knew I would get better answers here ;-). Had
posted to .vista.general and vista.file_management before posting to
here.

That policy object is well hidden and interesting. But it is a global
setting. The Streams program might do it, but is there something that
comes with Windows?

Don't reply if this is deviating too far from Powershell.

S&B

Check thePowerShellGuy blog:

http://thepowershellguy.com/blogs/po...fs-volume.aspx



-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

On Jan 12, 7:30*am, Shay Levi <n...@xxxxxx> wrote: Shay, I think this is it! But I will require some time to figure out
what is going on.

S & B

"Sue & Bill" <sue.and.bill@xxxxxx> wrote in message
news:6f160f5f-fc87-406c-b0b3-56e81b4f9d71@xxxxxx IMO using the Sysinternals streams.exe -d <filename> (as suggested by Jon)
is the way to go. It is very straightforward. Don't lose sight of the fact
that PowerShell doesn't mean you can't or shouldn't use older but still
useful console utilities.

--
Keith