Command failed to execute fixed

[plugger812]

Windows Vista/32 bit/Home Premium. I installed IE8, started getting "command
failed to execute" when I tried to open an attachment in my Hotmail (old
style not Live) on MSN Premium with MSN Explorer. They would open in Live.
I like the old stuff because it's easier to use for me. I read the threads
to uninstall IE8. I did and problem fixed.
Go to microsoft.com, click on the support tab, click IE Solution Center,
click How to uninstall IE8, click Microsoft Fix It. If it goes to your
Download Manager, run it fro there after it downloads. Restart and check as
it tells you to see that it uninstalled. Hope this works for you also.
You'd think Microsoft could put a package together that would work with their
own systems.... I have another problem that no one seems to know how to fix,
had a recommendation to go to Mozilla Firefox... thinking about it..... Good
luck to all!

 

[davidh1]

There was no need to uninstall IE8. The problem is the setting of the "Start
in:" location for the shortcut to Windows Mail. It is pointing to the
%UserProfile% and that's a read-only locaiton.

I don't know why Microsoft hasn't fixed it yet.

 

[Gary VanderMolen]

That's only a partial fix. It does not help with JPG and TXT attachments.

 

[Rainald Taesler]

davidh1 wrote:

That's only a partial fix. It does not help with JPG and TXT
attachments.

I can confirm this.
Obviously the way these two more or less basic types of files on opening
attachments are handled differently. The error message for both is
identical and no path is specified there (contrary to all other types if
files I tried).

Rainald

 

[Rainald Taesler]

There was no need to uninstall IE8. The problem is the setting of the
"Start in:" location for the shortcut to Windows Mail. It is
pointing to the %UserProfile% and that's a read-only locaiton.

I don't know why Microsoft hasn't fixed it yet.

As Gary already said, this is working only *partially*.
The problems with JPG- and TXT-files remain.

Obviously there's more behind the bug than just the path for "Start in:"

BTW: I installed "Vista Enterprise 32 SP1 English" on my test-machine
the days before yesterday.
The said path was correctly specified as "%UserProfile% whereas with all
of my previous installs if "Business 32 German" the path in the
shortcuts' "Start in:" was pointing to WinMail's program location.

Rainald

 

[Van Pahrump]

David, can you please send me your oriingal it's "EASY" to fix post of around
10 days ago. I did what you said and now I can't get/send any e-mails. Maybe
I need to just undo your suggestion- but I can't seem to locate your
pertinent post.

TGhanks.

Van in Pahrump
(e-mail address removed)

 

[Rainald Taesler]

davidh1 wrote:

David, can you please send me your original it's "EASY" to fix post
of around 10 days ago.

Below pls find the posting you are after.

I did what you said and now I can't get/send
any e-mails. Maybe I need to just undo your suggestion- but I can't
seem to locate your pertinent post.

As said in my posting of earlier tonight: The bug discussed in this
thread and the related other ones certainly is not responsible for your
current problems.
It must be something else.

Try out what I suggested in my last reply to you.

BTW: Dave's "EASY" solution is just a *Pseudo*-solution.
It does not really *fix* the problem.
It's not more than a workaround for the mist types of files and leaves
others behind.

Rainald


*----
Von: "davidh1" <[email protected]>
Betreff: Fixing "Command Failed to Execute" on attachments
Datum: Donnerstag, 21. Mai 2009 05:55

I see lots and lots of discussions. This is EASY to fix.

I have Vista & IE8, BTW.

click on Start (or the circle thingy for Vista), All Programs and right
click Windows Mail (under All Programs, not on the start menu). Select
Properties.

The value "Start in:" is set to %UserProfile%. This does not work
because
opening an attachment cannot save the attachment to a temporary file on
that
folder.

I changed it to "%UserProfile%\Local Settings\Temp" and that fixes the
problem.

You can also just clear the field "Start in:" (remove the value) and
that
fixes it also.

Enjoy.

Dave