Cannot install applications "Unable to access setup log"

[Guest]

Whether I use Windows Update to install new updates or try to install
personal applications, I get this error and the install aborts.

"Installation Failure: Windows failed to install the following update with
error 0x80070643: Microsoft .NET Framework version 1.1." The error message
box says that the Windows Installer cannot access the setup log file. What's
that, anyway?

Of course, in this example I was trying to install the .NET framework.
However, I get similar results when installing games (like Quake 4) and I
just don't know what could be causing this problem.

I run NIS 2006 (which includes Norton AntiVirus) and nothing is ever
reported to be wrong. I'm stumped AND I'm unable to install new software. Can
you help?

I see the same issue on XP Home and Win2K (different machines, not dual boot).

HELP!

John

 

[Carey Frisch [MVP]]

You cannot install some updates or programs
http://support.microsoft.com/kb/822798/en-us

Email the Windows Update support team:
http://support.microsoft.com/oas/default.aspx?gprid=6527

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Whether I use Windows Update to install new updates or try to install
| personal applications, I get this error and the install aborts.
|
| "Installation Failure: Windows failed to install the following update with
| error 0x80070643: Microsoft .NET Framework version 1.1." The error message
| box says that the Windows Installer cannot access the setup log file. What's
| that, anyway?
|
| Of course, in this example I was trying to install the .NET framework.
| However, I get similar results when installing games (like Quake 4) and I
| just don't know what could be causing this problem.
|
| I run NIS 2006 (which includes Norton AntiVirus) and nothing is ever
| reported to be wrong. I'm stumped AND I'm unable to install new software. Can
| you help?
|
| I see the same issue on XP Home and Win2K (different machines, not dual boot).
|
| HELP!
|
| John

 

[Guest]

I tried ALL the suggestions at the first link and these did not resolve my
problem. I have submitted an email to the Windoes Update support team as
suggested. However, this involves ANY installation of software that uses the
Windows Installer for its installation package. Do you have further suggests
I can try that focuses on this tool? I do not believe this is specific to
Windows Update although it does show itself there if the update uses Windows
Update. More ideas?

 

[Carey Frisch [MVP]]

Re-register the Windows Installer per this article:
http://support.microsoft.com/kb/315346/en-us

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| I tried ALL the suggestions at the first link and these did not resolve my
| problem. I have submitted an email to the Windoes Update support team as
| suggested. However, this involves ANY installation of software that uses the
| Windows Installer for its installation package. Do you have further suggests
| I can try that focuses on this tool? I do not believe this is specific to
| Windows Update although it does show itself there if the update uses Windows
| Update. More ideas?

 

[Guest]

Carey Frisch, thanks for all the effort you are putting into this. The last
suggestion did work for the Win2K box but not for XP. I hope the query I
submitted (per your suggestion) will provide the info I need to finish this
issue short of reloading the OS. Just as baffling is how this all happened.
If it were one machine I'd say it's just a fluke. But multiple machines means
I've got a faulty install someplace. Even reloading the OS won't help until I
find the "bad boy".

I'll post more later if I solve the problem (there were other KB articles
referenced) or the other MS crew is of any help. Thanks again. I believe we
are headed in the right direction just not home yet.

My best,
John