My client has been using saved-to-desktop Outlook Express 6 draft messages,
and after a recent Windows Update (August, September, or October 2006 sets),
he can no longer use them.

Instead of editable fields for "To" and "Subject", those field are now
non-editable, and "none" appears in the "To" field.

My client is unwilling to accept this change, and will likely revert to
pre-update against my suggestions. If I cannot identify which one caused
this, then he'll likely dispense with updates in the future.

Rather than back off all the updates that were applied (on October 6), can
someone identify which one caused this?

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:64717156-DCB7-413E-B8E7-EFF15BFD5F0A@microsoft.com...
> My client has been using saved-to-desktop Outlook Express 6 draft
> messages,
> and after a recent Windows Update (August, September, or October 2006
> sets),
> he can no longer use them.
>
> Instead of editable fields for "To" and "Subject", those field are now
> non-editable, and "none" appears in the "To" field.
>
> My client is unwilling to accept this change, and will likely revert to
> pre-update against my suggestions. If I cannot identify which one caused
> this, then he'll likely dispense with updates in the future.
>
> Rather than back off all the updates that were applied (on October 6), can
> someone identify which one caused this?

This is to be addressed in a future patch, you can point your client here
for the solution.
http://insideoe.tomsterdam.com/


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

Greg Kirkpatrick wrote:
> My client has been using saved-to-desktop Outlook Express 6 draft
> messages, and after a recent Windows Update (August, September, or
> October 2006 sets), he can no longer use them.
>
> Instead of editable fields for "To" and "Subject", those field are now
> non-editable, and "none" appears in the "To" field.
>
> My client is unwilling to accept this change, and will likely revert
> to pre-update against my suggestions. If I cannot identify which one
> caused this, then he'll likely dispense with updates in the future.
>
> Rather than back off all the updates that were applied (on October
> 6), can someone identify which one caused this?

The problem was caused by KB911567, it has not yet been addressed by MS,
but there are fixes available.

See this from a recent post by Bruce Hagen -

Patch KB918766:
http://tinyurl.com/mx3r2

This patch addresses some of the issues that were caused by KB911567.

Address Book problems.
Unsent templates appearing as sent.
Manually compacting will now reset the registry counter to Zero in
WinXP/SP2
and also sends a copy of your dbx files to the recycle bin as a
temporary
backup.

To complete the fix for .eml templates, a registry change is needed.
See:
http://support.microsoft.com/kb/918766

Tom Koch also has this information at his site, along with a
downloadable
Zip file to do the registry change for you. See:
http://www.insideoe.com/#kb918651

--
Kath Adams
MS MVP - Windows (Outlook Express)