"Windows has blocked access to these files to protect your computer"
I have a Windows 2003 terminal server, with all of the latest patches and
updates. I cannot extract files from a .ZIP archive, because it's blocked. I
went into the properties of the file, and checked "unblock", but that did
not help, and now if I go back into the properties the "unblock" is no
longer there.
I'm sure this is some security feature of one of the updates - is there a
way around it?
Re: "Windows has blocked access to these files to protect your computer"
Are you certain that is not being caused by some third-party software ?
"Steele" <ksteele@summitnetworking.net> wrote in message
news:O$XH$wtlGHA.3732@TK2MSFTNGP05.phx.gbl...
>I have a Windows 2003 terminal server, with all of the latest patches and
>updates. I cannot extract files from a .ZIP archive, because it's blocked.
>I went into the properties of the file, and checked "unblock", but that did
>not help, and now if I go back into the properties the "unblock" is no
>longer there.
>
> I'm sure this is some security feature of one of the updates - is there a
> way around it?
>
>
>
Re: "Windows has blocked access to these files to protect your computer"
I agree with Roger,
I do not recall a "block\unblock" option with Zip files. Sounds like a third
party firewall or security suite.
--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts
"Roger Abell [MVP]" <mvpNoSpam@asu.edu> wrote in message
news:ue%232wA3lGHA.4268@TK2MSFTNGP05.phx.gbl...
> Are you certain that is not being caused by some third-party software ?
>
>
> "Steele" <ksteele@summitnetworking.net> wrote in message
> news:O$XH$wtlGHA.3732@TK2MSFTNGP05.phx.gbl...
>>I have a Windows 2003 terminal server, with all of the latest patches and
>>updates. I cannot extract files from a .ZIP archive, because it's blocked.
>>I went into the properties of the file, and checked "unblock", but that
>>did not help, and now if I go back into the properties the "unblock" is no
>>longer there.
>>
>> I'm sure this is some security feature of one of the updates - is there a
>> way around it?
>>
>>
>>
>
>