Kb953297

I have gone through a similar hell to what Vladimir describes here:

http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/ed025d8a-98af-47d7-a2c9-1cc10a547d06

I had 1.0, 1.1, 2.0, 3.0, 3.5, 4.5, and 4-beta-something installed just fine, but 3 diff security patches all kept bouncing. (one on 1.1 and two on 2.0 I think)

I tried uninstalling all of them and redoing from scratch. Same 3 bounced. Did again, but used a standalone 1.1 installer, rather than the automated Updates. Ditto same 3.

Using that "msicuu2" installer cleanup utility (which MS describes as a "last resort"), suddenly two of them fell into line. The two patches for 2.0, I believe.

I may have had to do another uninstall/reinstall of 2.0 itself in the course of this, I can't remember.

But try as I may, I can't get the one for 1.1 (better known as KB953297) to go away! I have tried uninstalling 1.1, reinstalling 1.1, using the cleanup utility, using some OTHER cleanup utility (KB928366-KB929729-KB928367-Cleanup-x86, billed as being for 1.0 and 1.1 specifically), using clwireg-x86 (some registry correction tool billed as dealing with this problem), and using the kludge just mentioned in the end of that thread (MicrosoftFixit50123.msi).

In all cases, my 1.1 is restored just fine, but the PATCH for it won't take! And not all of the other frameworks present themselves for reinstall either. I have gone from the 8 or so mentioned above to "1.1, 2.0 SP2, 3.0 SP2, and 3.5 SP1". Well, I don't mind filling them in by hand later, but if MS is so unsure of the necessity of half of these, then why don't they just select 1.1 for the "optional" list, and put me out of my misery!!!!

Anything left to try? I see that Vlad eventually got it going, but he's a little vague on what the key differences were in his last couple of attempts.

I am very very close to just HIDING the damn patch. Or 1.1 itself which the patch applies to. Is it better to have it sitting there uncorrected or not at all?

 

OK, 2 week has passed and I am much wiser. The basic problem is that several of these versions keep sloppy records when you install them, such that if you later uninstall them (or even just do an upgrade/overwrite), you end up in a weird limbo where pieces of them are still sitting causing problems, while "add/remove programs" (and even stronger apps like UninstallerPRO) think they're already gone. This leads to comical loops such as system messages saying "WARNING: Must uninstall 3.0 before proceeding" followed by "Framework 3.0 is not installed on this computer" when you try! Or the reverse "Cannot install 3.0 - you have a more recent version [3.5] already installed" followed by "3.5 AFU coz of missing 3.0"...yadda yadda.

Unfortunately, it generally lets you go on to the next install, such that 2.0 is now problematic b/c is was blanketed onto the semi-absent 1.1, Etc. etc., and the whole thing SNOWBALLS.

There are a millions "fixes" on the net, but far and away the best is THIS page: http://blogs.msdn.com/astebner/pages/8904493.aspx

Earlier versions (and competing pages) instruct you to uninstall/clean up each version from highest to lowest, until you get back to where the first problem was. I.e., strip away 3.5, then 3.0, then 2.0, etc., until you're quite sure 1.1 (SP1) is solidly installed. Then cautiously reinstall the next one (2.0 here) and work THOSE bugs out before the next jump.

There is also a "windows cleanup utility" which is supposed to be run between each layer-stripping, and a "net framework cleanup utility" and some sort of "registry cleanup utility", yadda yadda. Even if you eventually get everything installed, it's such a PIECEMEAL MESS that I would never trust its functionality after that.

Far better, IMHO, is to use Mr. Stebner's app to remove **ALL** netframeworks from the gitgo and start all over completely. At that point Automatic Updates should be able to see 1.1 for what it is (absent!), and give you a nice, clean copy to build upon. Ditto 2.0. And then ditto 3.0.

I guess. Complicating things further is the fact that 1.0, 1.1, and 2.0 are intended to coexist simulltaneously on a PC, whereas 3.0 onward are truly "upgrades". Thus, your system should go from having 1.0/1.1/2.0 all togther to 1.0/1.1/3.0 to 1.0/1.1/3.5, etc.

Anyway...just follow Stebner's instructions. He has saved a lot of ppl a LOTTTTTTTTTTTTTTTTTTTTTTTTTTTT of aggravation. Why they can't draft him over to the "Automatic Updates" division is beyond me....

 

HOO BOY, now I have to retract everything I just said!

I had managed to chip my way along to 3.0 using a combination of the windows uninstaller and those registry cleaners, etc. It looked like I was FINALLY in range of actually getting 3.5 SP1 in, and being *DONE* (!) with this whole mess.

But, like I said, it felt all too kludgey / piecemeal to me...so I used Stebners tool to wipe the slate clean and start all over. Whereupon now I can't even get 1.1 to install!!!! Neither via Windows Update nor with the redistributable version I had DLed before.

EGADS. And I'm not talking about the PATCH on 1.1 here -- my original problem -- but 1.1 itself. Which was the ONE THING which has given me no problems whatsoever. UNTIL NOW.

So yes, it's official. I am now GOING BACKWARDS.

 

Hoo boy, I don't know how I managed, but somewhere around the 5th "strip down" (uninstall of all versions) I managed to get 1.1, 2.0 Service Pack 2, 3.0 Service Pack 2, and 3.5 SP1 [sic] loaded. So XP has officially stopped bugging me about anything outstanding, visible OR hidden. Not sure what became of 1.0 along the way, but at this point, I ain't askin'!!



However, I did all this 3 weeks ago (like a DAY after the previous post; sorry, didn't update MG sooner) and it hasn't offered me a *SINGLE* update since! Is this POSSIBLE?! Has there really not been ANYTHING in 3 full weeks?!

I didn't think you went 3 DAYS without a hotfix or two!

Have I now mucked something ELSE up, such that it's just not LOOKING for updates any more?!

 

Indeed, I did end up getting 2 things last week, and now one today. But what was that 1-2 week GAP in the middle?!

Just my luck it happened right after I'd mucked around with everything, and was unsure if updates was working!

Anyway, all's well for now. Updates are fine, and .NET Framework has settled down.

Thanks again!