Outlook Banter - View Single Post

**Dr Weekes-Money**

"mac" wrote:

"Dr Weekes-Money" Dr wrote in
message ...
After installing the latest security updates (as recommended by
Microsoft,) I
am suddenly unable to open or save any of the attachments in any of my
folders. The security patches won't let me uninstall them. I have
consdered
upgrading to Outlook, but the export function in Outlook Express seems to
have been broken as well. I have even tried a complete reinstall of XP
Home,
and though I was then able to open the attachments again when I first
installed it, as soon as I installed MS's updates, the attachments stopped
working again. There is no error message when I try to open attachments,
and
when I try to save them I am told to check my free disk space and try
again.
I have 122GB free!

In any order:

Try Giving the registry a kick start :-) Check the security
itemtoolsoptionssecurityreboot, uncheck the security itemreboot, can
you see your attachments now?

Delete your cache (TIF) in Internet Explorer?

Are you using ZoneAlarm, if so, is mail safe activated?

Is your AV set to scan incoming and outgoing mail? If so disable it.

Do you have this registry key: "BlockExeAttachments"?

Close OE, then in Regedit via - startrunregeditlook under this key:
HK_LOCAL_MACHINE\Software\Microsoft\Outlook Express
If you see the value "BlockExeAttachments" in the right-hand pane,
Change it to 0. (zero) (right click-modify).

--
Regards Steve.
MS-MVP. OE. [DTS]

Dear MacSteve,
Have tried all the checking/unchecking/rebooting stuff more times than I can
count, even with my shoes and socks off.

I've deleted the IE cache

I don't use Zone alarm.

I use the Kaspersky Home Security suite and it makes no difference if I turn
all the elements off.

I have tried stopping Windows Defender.

There is no sign of the registry key: "BlockExeAttachments"

The only thing that works is using Add/remove programs and uninstalling XP
service pack 2. I can then read attachments and download internet files. This
looks suspiciously like a fault in SP2, but more people should have had the
same problem if that's the case.