Using IE7, which I set to delete all temp files after closing the app, I
downloaded the new Windows Defender. Instead of SAVE I chose RUN. The
install cranked up and then informed me that it could not proceed because IE7
was still running.

I then exited IE7. Drumroll please.

Windows Defender install then proceeded for a while and then came up with
FAILED, unable to access file \yada\yada\windowsdefender.msi. But of course,
it was downloaded to the temp folder which was cleared when IE7 closed.

Happily I figured out what was happening before my 20th try!

Might be nice to figure out a way to prevent this from happening.

Interesting--this came up during the beta as well--some folks had that
setting with IE6 as well, I think?

Since presumably this would happen with any download for which you make the
"run" versus "save" choice, I guess you'd figure it out after a while.

It is a little startling that a presumably in-use file was deleted--wish it
was that easy to get rid of malware in the temporary file stores!

--

"fullscreenlover" <(E-Mail Removed)> wrote in
message news:F3009236-F920-4074-A046-(E-Mail Removed)...
> Using IE7, which I set to delete all temp files after closing the app, I
> downloaded the new Windows Defender. Instead of SAVE I chose RUN. The
> install cranked up and then informed me that it could not proceed because
> IE7
> was still running.
>
> I then exited IE7. Drumroll please.
>
> Windows Defender install then proceeded for a while and then came up with
> FAILED, unable to access file \yada\yada\windowsdefender.msi. But of
> course,
> it was downloaded to the temp folder which was cleared when IE7 closed.
>
> Happily I figured out what was happening before my 20th try!
>
> Might be nice to figure out a way to prevent this from happening.
>
>