Error code 0x643 for Net framework 2.0

I'm having trouble with .net framework 2.0. I've had it installed for a
while. Last December (I think), I also had the same problem and followed the
guide in KB923100 to fix it. Real pain too. Now I just tried to install the
latest security update for it and the same error code happened. I, once
again, followed the guide in KB923100 (2 times) and am still getting the
0x643 error.

What's my next approach to getting it straightened out? I tried googling
the error and haven't run into anything new other than KB923100.

Forgot to add that I'm running XP Home SP2.


"Ed Y" <> wrote in message
news:...
> I'm having trouble with .net framework 2.0. I've had it installed for a
> while. Last December (I think), I also had the same problem and followed
> the guide in KB923100 to fix it. Real pain too. Now I just tried to
> install the latest security update for it and the same error code
> happened. I, once again, followed the guide in KB923100 (2 times) and am
> still getting the 0x643 error.
>
> What's my next approach to getting it straightened out? I tried googling
> the error and haven't run into anything new other than KB923100.
>

Also forgot to mention that the 0x643 error now happens when I try to
re-install 2.0 not when trying to install the security update.


"Ed Y" <> wrote in message
news:...
> I'm having trouble with .net framework 2.0. I've had it installed for a
> while. Last December (I think), I also had the same problem and followed
> the guide in KB923100 to fix it. Real pain too. Now I just tried to
> install the latest security update for it and the same error code
> happened. I, once again, followed the guide in KB923100 (2 times) and am
> still getting the 0x643 error.
>
> What's my next approach to getting it straightened out? I tried googling
> the error and haven't run into anything new other than KB923100.
>

"Ed Y" <> wrote in message
news:...
> I'm having trouble with .net framework 2.0. I've had it installed for a
> while. Last December (I think), I also had the same problem and followed the
> guide in KB923100 to fix it. Real pain too. Now I just tried to install the
> latest security update for it and the same error code happened. I, once
> again, followed the guide in KB923100 (2 times) and am still getting the
> 0x643 error.
>
> What's my next approach to getting it straightened out? I tried googling
> the error and haven't run into anything new other than KB923100.


<cmd_output OS="XPsp2">
F:\>set /a c = 0x643
1603
F:\>net helpmsg %c%

Fatal error during installation.
</cmd_output>

Looks like you need to go into the logs and find the real problem.
This is undoubtedly just a summary code for a more significant
message which would have been issued earlier there.

BTW there is an abundance of diagnostics available with these installs
if you look for it. If you're lucky you might even find a more precise clue
more easily in the Event log or if you install the same update manually
you may get shown some messages which get suppressed by doing
the install automatically. Also, when you do an manual install you have
the option of invoking verbose logging, if it is not already in effect.


Good luck

Robert Aldwinckle
---

"Robert Aldwinckle" <> wrote in message
news:%...
>
> Looks like you need to go into the logs and find the real problem.
> This is undoubtedly just a summary code for a more significant
> message which would have been issued earlier there.
>
> BTW there is an abundance of diagnostics available with these installs
> if you look for it. If you're lucky you might even find a more precise
> clue
> more easily in the Event log or if you install the same update manually
> you may get shown some messages which get suppressed by doing
> the install automatically. Also, when you do an manual install you have
> the option of invoking verbose logging, if it is not already in effect.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>

Thanks for the info but that's mostly way over my head as to how to do that.
Don't suppose there is any kind of detailed info available laying out
the steps required to do what you suggest??

When you try to install an update for the .NET Framework 1.0, 1.1, or 2.0, you may receive
Windows Update error code "0x643" or Windows Installer error code "1603"
http://support.microsoft.com/kb/923100

--
====================================
TaurArian [MVP] 2005-2008 - Australia
====================================
How to ask a question: http://support.microsoft.com/kb/555375
http://taurarian.mvps.org/index.htm
Emails will not be acknowledged - please post to the newsgroup so all may benefit.


"Ed Y" <> wrote in message
news:...
| I'm having trouble with .net framework 2.0. I've had it installed for a
| while. Last December (I think), I also had the same problem and followed the
| guide in KB923100 to fix it. Real pain too. Now I just tried to install the
| latest security update for it and the same error code happened. I, once
| again, followed the guide in KB923100 (2 times) and am still getting the
| 0x643 error.
|
| What's my next approach to getting it straightened out? I tried googling
| the error and haven't run into anything new other than KB923100.
|
|

"Ed Y" <> wrote in message
news:%...
>
> "Robert Aldwinckle" <> wrote in message
> news:%...
>>
>> Looks like you need to go into the logs and find the real problem.
>> This is undoubtedly just a summary code for a more significant
>> message which would have been issued earlier there.
>>
>> BTW there is an abundance of diagnostics available with these installs
>> if you look for it. If you're lucky you might even find a more precise
>> clue
>> more easily in the Event log or if you install the same update manually
>> you may get shown some messages which get suppressed by doing
>> the install automatically. Also, when you do an manual install you have
>> the option of invoking verbose logging, if it is not already in effect.
>>
>>
>> Good luck
>>
>> Robert Aldwinckle
>> ---
>>
>>
>
> Thanks for the info but that's mostly way over my head as to how to do that.
> Don't suppose there is any kind of detailed info available laying out
> the steps required to do what you suggest??


What? Finding some files with those codes in them?
Do a Find Files (e.g. press Win-F and use Search Companion.)
Take advantage of the When was it modified filter to limit the files
actually searched to files which changed on the day that the update was done.
Use View Details and sort the results list by Date Modified.
(E.g. click on that header label or use View, Arrange icons by... that label.)
Add that column to your Details view if necessary. (E.g. right-click in the
Details headers and check Date Modified if it isn't already checked.) Etc.

Note: with Search Companion you can only search for one string at a time.
If you have a more capable file search tool use the Boolean expression
(643 OR 1603). Depending on whether your search tool can find substrings
in words (e.g. ignore prefixes) you might have to include 0x643 in your
search specifically too.

Tip: If a file has an extension without an associated filetype you can drag
it to an open Notepad window for browsing. Searching for all files could mean
that you find files with binary data but I think that with the Date Modified filter that
should be unlikely. In any case you are only interested in files which contain
readable data, e.g. diagnostics such as log files.

Even if Search Companion can't find files with any of those strings in them
(unfortunately a possibility due to deficiencies in the program) you can still
take advantage of the sorted list of *all* files which were changed on a date
of the update (which it can find). In that case since the update probably occurred
within a few minutes all you need to do is scroll the results list to that time period
to find (probably) all the files that the update changed grouped together.
Then you would have to manually search each file which seemed as if it
would be readable for each of those codes. Assuming you found them
in logs of diagnostic messages (for example) the context for those codes
would be the messages which preceded them.


Good luck

Robert
---