none
Urgent: Error Code 0x643 or 1603 RRS feed

  • Question

  • Hi All -

    Can't get .NET v2 re-installed.  Getting the dreaded 1603 or 0x643 error codes.  Found a MS kb article that said that if you encounter this you should call an 866 phone number for free support.  Of course the phone number is disconnected....

    I have used the installer version verification tool to verify that I have only 1.1 and 1.1sp1 installed.

    I have used the clean up tool just in case.

    I have even manually gone through and deleted all the files, etc, as instructed in http://support.microsoft.com/kb/908077

    Of course that kb references an installer clean up tool that microsoft no longer provides.  So I can't do that step.  But I have done all the other steps.

    Now if I try to install the 3.5sp1 file, I get the error saying that I need 2.0a installed first.

    But if I try to install 2.0 (which the log calls 2.0a), it says it can't install it because it can't load fusion.  (Shim fails to load)

    So I can't make any progress either way and most of my apps don't work anymore because they all require 2.0.  This is day four and I'm still in the same place as I was on day one.

    Please can you help with this?

    Thanks!

    Tuesday, October 11, 2011 3:47 AM

Answers

  • It appears that regardless of the O/S, the solution seems to be to delete the \WINDOWS\WinSxS\Policies   folder as described in this thread:

    http://social.msdn.microsoft.com/forums/en-US/netfxbcl/thread/47c93410-2ee2-4dd1-812a-04475d50de7c/

    It worked for me anyway, as well as for a large number of people who have indicated in that thread that it solved their problem. 

    It sure would be good if the clean up tool cleaned up that as well.  So simple a solution surely could be incorporated.

    For the record books, since you asked, I am running XP Pro, SP3.  While I did state this in a separate thread, understandably that wasn't noticed, and my bad for not remembering to state it again in this thread. 

    Anyway, that part of the problem is solved.  I still have one lingering problem but will deal with that in a new thread.

    • Marked as answer by junk1958a Wednesday, October 12, 2011 3:30 AM
    Wednesday, October 12, 2011 3:30 AM

All replies

  • FIRST, what Windows version are you using? Without that information, nobody can provide you with specific recommendations.

    Please provide you install logs for analysis as follows:

    Collect your install logs with this:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=E0DA314F-6216-4A18-BC6B-7D29CF83AF20&displaylang=e&displaylang=en

    After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.

     

    Tuesday, October 11, 2011 9:55 PM
  • It appears that regardless of the O/S, the solution seems to be to delete the \WINDOWS\WinSxS\Policies   folder as described in this thread:

    http://social.msdn.microsoft.com/forums/en-US/netfxbcl/thread/47c93410-2ee2-4dd1-812a-04475d50de7c/

    It worked for me anyway, as well as for a large number of people who have indicated in that thread that it solved their problem. 

    It sure would be good if the clean up tool cleaned up that as well.  So simple a solution surely could be incorporated.

    For the record books, since you asked, I am running XP Pro, SP3.  While I did state this in a separate thread, understandably that wasn't noticed, and my bad for not remembering to state it again in this thread. 

    Anyway, that part of the problem is solved.  I still have one lingering problem but will deal with that in a new thread.

    • Marked as answer by junk1958a Wednesday, October 12, 2011 3:30 AM
    Wednesday, October 12, 2011 3:30 AM