Respect Root
Premium
join:2006-04-20
in the ether
| [XP Pro] Updates Fail after Fresh Install and XP SP3 Loaded
I tried but could not find a thread similar to the following (please excuse if I missed it):
After completing a clean install of XP SP2 today, I ran Microsoft Update and XP SP3 was listed as an available update. XP SP3 installed with no problems. Ran Microsoft Update again, which found two critical updates (one being IE7). Selected the two as well as all of the other optional updates (such as .net 1.1 and 2.0). All of them updated with no problems. The subsequent Microsoft Update found three more critical updates (i.e. .net 1.1 SP1 and security updates for .net 2.0 and Windows Media Format for 9.5 and 11). All three of those updates failed when I tried to install them.
Not sure if others are experiencing this same issue as this was a fresh install of XP (although googling did show a similar situation to this one but it appeared to be during beta testing and there wasn't a posted solution).
Any assistance would be greatly appreciated. Thanks |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs: 
 ·Verizon Online DSL
edit:
May 8th, @08:06PM
| This is a guess, as I have seen this issue bugged but no resolution.
A little over a year ago the Update Agent, a part of Windows Update and used at times by Windows Download, was silently upgraded. There was a lot of complaints about this being done silently at the time.
So now we have a clean install of XP SP2. Upgraded with Service Pack 3. But Service Pack 3 does not contain the updated Windows Update Agent.
Suggested Workaround:
1. Download the new Agent (but do not Run it yet) to your Desktop (so
you can find it below) :
X86 Version: »download.windowsupdate.com/Windo···-x86.exe
2. Start, Run, CMD
In the black box:
net stop wuauserv
"%userprofile%\Desktop\WindowsUpdateAgent30-x86.exe" /wuforce
(don't forget the quotation marks)
regsvr32 "%windir%\system32\wup2.dll"
net start wuauserv
exit
I have not tried this; not attempted to replicate the issue. But my gut instinct when I read of a few complaining of the issue with Updates not installing was that it was related to the missing Update Agent 2.0. I know for a fact that the upgrade Windows Update Agent was not distributed with either SP2 or SP3.
My workaround is based on this KB:
Updates are not installed successfully from Windows Update, from Microsoft Update, or by using Automatic Updates after you repair a Windows XP installation
»support.microsoft.com/kb/943144
Note: Also applies to clean installs, upgrade installs, and Recovery installs.
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
Gooiool
May God bless you.
Premium
join:2006-11-27
Roland, OK
clubs:
 ·Cox HSI
edit:
May 8th, @08:37PM
| reply to Respect Root
.net 1.1 SP1 is a fix for .net1.0 .
ok , bcastner  says this is not correct , And I will not argue with that .
" if you have .net3.0 you do not need .net1.1 or net 2.0 just disregard it . "
It work for me when the last application said you need Net 2.0 or higher. So that app. must use either 2.0 and 3.0 ? I guess .
And in order to fix the Net1.0 bug ( created it's own user on window start up ) I un-installed net1.0 ,net2.0 from the add/remove. |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| quote:
if you have .net3.0 you don not need .net1.1 or net 2.0 just disregard it.
I'm sorry, this is simply not true.
.NET Frameworks are not cumulative; having .NET Framework 3 does nothing for an application written to a Framework 1 or 2.
.NET Frameworks are virtual machines. The software developer writes to the features and APIs of that virtual machine model. They are not compatible. An application written to the .NET Framwork 2 virtual machine, will not run if only .NET Framework 3 is installed.
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
Melvin Fields
@umd.edu
| reply to Respect Root
This is definitely an issue with SP3, I had previously downloaded the standalone installer for SP3, ran it on clean install of SP2 and had the same experience you had. The last 3 updates you mention would not install! I chalked it up to a not ready for prime-time release of SP3, but today I did a clean install of XP SP2 and to my surprise I was offered SP3 from MS Update. I figured this was the real deal and I would have no issues, after install and reboot and next successful round of updates, the same 3 updates failed to install.
My workaround was to download the standalone installers for these 3 updates, these installed fine and MS Update no longer offers them to me. I did a search for the KB number for the 2 with KB's, the last I did a search for ".net 1.1 sp1"
My concern is "am I going to continue to have problems with MS Update?"
I will install Office 2003 and see if the updates for it come down and install.
I think MS is not done with SP3.
Melvin Fields (SP3 tag) |
|
Respect Root
Premium
join:2006-04-20
in the ether
| reply to bcastner
BC,
I do recall seeing only two updates show up (instead of the typical three) after XP SP2 completed installation (the update agent not included). I forgot about that slight change in the routine as I had noticed during that install...
I will give the workaround a try and let you know how goes.
Melvin,
Not sure if the manual install would resolve the update as I am not clear if the issue is with Windows/Microsoft Update knowing your patch version vs. a dependency associated with the Update Agent, which was not included in the first round of updates after a fresh install of XP SP2.
Keep you posted (most likely tomorrow since this gave me a headache). |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| Yes, I would be interested in hearing your results. Certainly if wup2.dll is not registered, and your installation scenario suggests it will not be (see the KB Article I linked earlier), then that aspect has to be sorted.
This has nothing to do with SP3.
On a last note, the toughest installations I know of have been anything related to security or other updates to existing .NET Frameworks, and anything related to Windows Media Player. My own view of the matter is that any update that Windows Update shows an installation failure gets the redistributable download from Microsoft downloads and installed that way.
There is a complication with the .NET framework updates in particular, as they are dependent on their instalation success on another component -- MDAC. It is unlikely at this point in time that your MDAC versioning is correct. If necessary, we can manually correct that later based on your results with the first repair I suggested earlier. At some point the resolution of any issues will require posting at least a portion of the Windows Update LOG.
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
jferello
J
Premium
join:2001-03-12
Hatboro, PA
clubs:
| reply to bcastner
bcastner,
I was having the exact same issue that the OP was having, those 3 updates would not install.
I followed your directions up until the wup2.dll file and it said it failed to find the file.
So then I just tried the updates again for the heck of it and they worked, so all you need to do is just install that agent update.
Thanks for the wonderful help!
--
I never thought something so simple would be so hard to find....... |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| Thank you for the report.
If a Search for wup2.dll returns nothing, then do not be concerned. wups2 is an update client proxy stub that 'marks' the location of updates from either Automatic Upates or Windows Updates; and when it's not registered (if present), the system can not install them because it can't find them. |
|
jferello
J
Premium
join:2001-03-12
Hatboro, PA
clubs:
| bcastner,
So the problem is that the Windows Update agent neededs to be updated, but because we did SP3 first instead of the WUA then the WUA got all confused and couldn't update itself then?
--
I never thought something so simple would be so hard to find....... |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| Yes, roughly.
It is that neither SP2 nor SP3 includes the updated Windows Update Agent.
Therefore if you do a clean install with an XP SP2 image you begin without the newer Update Agent. Since SP3 does not contain this either, at the end of the process you are still without the newer Update Agent.
Now Windows Update cannot work for on-demand access to obtain Hotfixes without the newer Update Agent installed. Hence, because of this "Catch-22", it led to reasoning by Microsoft to push this update to all with Automatic Windows Update enabled silently. Since they could use the Automatic Update mechanism of a client-server link with BITS, the update could be pushed out to clients without involving the Update Agent, only the Automatic Update service.
So with a specific fact case you can end up, as was the case here, without the newer Update Client, and no way to update this using Windows Update. The only choice is to wait and see if it gets pushed to you through Automatic Updates; or resolve the issue by downloading the newer Update Agent and installing it yourself.
Best wishes,
Bill Castner.
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
jferello
J
Premium
join:2001-03-12
Hatboro, PA
clubs: | My god your amazing, your like an MS God!! I am adding you to my friends list, if that is ok with you.
--
I never thought something so simple would be so hard to find....... |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs: | It is nice to have friends.
Best,
Bill |
|
Respect Root
Premium
join:2006-04-20
in the ether
| reply to bcastner
Considering it was a fresh install, I phoned Microsoft support and they listed the following steps, which resolved the issue with installing the aforementioned updates (sharing notes as the other workarounds mentioned in this topic will likely resolve the issue):
Solution: re-registered the .dll files for updates
action: stop the BITS, .ASPnet, cryptographic services
action: rename the software distribution folders, catroot2 folders
action: start the BITS,AUTOMATIC UPDATES ,CRYPTOGRAPHIC SERVICES
action: register the following update files
cd /d %SystemRoot%\system32
Regsvr32 wups2.dll /s
Regsvr32 licdll.dll /s
Regsvr32 regwizc.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 comcat.dll /s
regsvr32 shdoc401.dll /s
regsvr32 shdoc401.dll /i /s
regsvr32 asctrls.ocx /s
regsvr32 oleaut32.dll /s
regsvr32 shdocvw.dll /I /s
regsvr32 shdocvw.dll /s
regsvr32 browseui.dll /s
regsvr32 browseui.dll /I /s
regsvr32 msrating.dll /s
regsvr32 mlang.dll /s
regsvr32 hlink.dll /s
regsvr32 mshtmled.dll /s
regsvr32 urlmon.dll /s
regsvr32 plugin.ocx /s
regsvr32 sendmail.dll /s
regsvr32 scrobj.dll /s
regsvr32 mmefxe.ocx /s
regsvr32 corpol.dll /s
regsvr32 jscript.dll /s
regsvr32 msxml.dll /s
regsvr32 imgutil.dll /s
regsvr32 thumbvw.dll /s
regsvr32 cryptext.dll /s
regsvr32 rsabase.dll /s
regsvr32 inseng.dll /s
regsvr32 iesetup.dll /i /s
regsvr32 cryptdlg.dll /s
regsvr32 actxprxy.dll /s
regsvr32 dispex.dll /s
regsvr32 occache.dll /s
regsvr32 occache.dll /i /s
regsvr32 iepeers.dll /s
regsvr32 urlmon.dll /i /s
regsvr32 cdfview.dll /s
regsvr32 webcheck.dll /s
regsvr32 mobsync.dll /s
regsvr32 pngfilt.dll /s
regsvr32 licmgr10.dll /s
regsvr32 icmfilter.dll /s
regsvr32 hhctrl.ocx /s
regsvr32 inetcfg.dll /s
regsvr32 tdc.ocx /s
regsvr32 MSR2C.DLL /s
regsvr32 msident.dll /s
regsvr32 msieftp.dll /s
regsvr32 xmsconf.ocx /s
regsvr32 ils.dll /s
regsvr32 msoeacct.dll /s
regsvr32 inetcomm.dll /s
regsvr32 msdxm.ocx /s
regsvr32 dxmasf.dll /s
regsvr32 l3codecx.ax /s
regsvr32 acelpdec.ax /s
regsvr32 mpg4ds32.ax /s
regsvr32 voxmsdec.ax /s
regsvr32 danim.dll /s
regsvr32 Daxctle.ocx /s
regsvr32 lmrt.dll /s
regsvr32 datime.dll /s
regsvr32 dxtrans.dll /s
regsvr32 dxtmsft.dll /s
regsvr32 WEBPOST.DLL /s
regsvr32 WPWIZDLL.DLL /s
regsvr32 POSTWPP.DLL /s
regsvr32 CRSWPP.DLL /s
regsvr32 FTPWPP.DLL /s
regsvr32 FPWPP.DLL /s
regsvr32 WUAPI.DLL /s
regsvr32 WUAUENG.DLL /s
regsvr32 ATL.DLL /s
regsvr32 WUCLTUI.DLL /s
regsvr32 WUPS.DLL /s
regsvr32 WUWEB.DLL /s
regsvr32 wshom.ocx /s
regsvr32 wshext.dll /s
regsvr32 vbscript.dll /s
regsvr32 scrrun.dll mstinit.exe /setup /s
regsvr32 msnsspc.dll /SspcCreateSspiReg /s
regsvr32 msapsspc.dll /SspcCreateSspiReg /s
exit
action:tried to install the updates
result:able to install the updates
==============================================
Wondering if including the update agent in the first round of updates would resolve this issue? If it could be included with SP2, is there something in SP3 prohibiting that possibility? Just curious...
Thanks for all your help, BC!! |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs: | The new Update Agent was not included with SP2.
(It was not even issued until several years after SP2). |
|
szabogi
join:2008-06-07
Cincinnati, OH
| reply to bcastner
Thanks a million for your post. I had done a fresh install of XP Professional with no service packs slipstreamed in. Then, applied SP2, followed by SP3. Had nothing else installed - including AV. Turned on automatic updates and was alerted to install KB898461. This update would not install. Downloaded the update manually from Microsoft and was able to install that way. Then, tried update.microsoft.com to see what other updates were available. Found 4 critical, including IE7. Attempting to install. All 4 failed. That's when I found your post. Followed your instructions -- here's a summary of what I did to get everything working. A few steps in your CMD window step were not needed.
1. Get the windows updater here and save to desktop:
»download.windowsupdate.com/Windo···eAgent30
2. Start, Run, CMD
Type these two commands in (one at a time) into the black window to install the update agent. The service will be started again after installation automatically:
net stop wuauserv
"%userprofile%\Desktop\WindowsUpdateAgent30-x86.exe" /wuforce
3. Finished. Try installing updates from the yellow shield OR update.microsoft.com. Should be good to go now. |
|
bcastner
Premium,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| I should note that I have substantially changed how I approach this whole issue, as a utility that formerly was only available directly through Microsoft PSS has been released to the general public; and because there are some other frameworks that I think should also come into play.
The new utility comprehensively re-registers and updates any needed components for Windows Update -- for any DLL used, to any Agent version or other piece that is not at the current release level.
Recommended highly for any issue with Windows Update: »aumha.net/viewtopic.php?f=62&t=33560
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
Ronnie_USA
BigBlueFan
Premium
join:2003-10-09
Morehead, KY | reply to szabogi
Thank You very much for the fix.
I reformatted thinking I had done something wrong.
Your fix worked like a charm. |
|
Finger2208
join:2001-04-07
Lindale, TX
edit:
June 8th, @07:46AM
| Not trying to hijack the thread, but I do have a question and looking for advice along these lines. I am receiving a new hdd for my laptop on Tuesday, and will be reinstalling XP Home. My CD install doesn't even have SP2, so is there anything special I will need to do for my reinstall along the lines you guys are discussing? Any and all help is most appreciated! BTW, I do plan on going with SP3 on the laptop, as my tower has been fine with it. |
|
ITAdmin
@ccpdocs.com | reply to Respect Root
Thanks VERY much for such a great forum! I fixed my MS updates failed issue after a fresh install of XP SP2 and then SP3 with the advice I found here.
Thanks Again!
ITAdmin |
|
