chezy666 Posted July 1, 2005 Share Posted July 1, 2005 yup, 100% sure that cab has the activex control as this is the shortcut used to launch Microsoft Update C:\WINDOWS\system32\rundll32.exe C:\WINDOWS\system32\muweb.dll,LaunchMUSiteThe file goes to the system32 directory, register the dll and create the shortcut in All Programs to this link C:\WINDOWS\system32\rundll32.exe C:\WINDOWS\system32\muweb.dll,LaunchMUSitehavent tested this, and am not sure if more files r required to make this possible. Link to comment Share on other sites More sharing options...
Gee Posted July 1, 2005 Share Posted July 1, 2005 (edited) Looks like Shark's Method works the best. I have not tried it yet, but I did go to Windows update and updated the client to version 6. Here is my log after the update. This should clear up a lot of things about Shark's method. It appears that a few more .dll files have to be registered.So if you are using his method. Download the new files, use ModifyPE to correct the checksums, then use makecab to recompress them. Drop them into your i386 folder. The one missing file wups2.dll should be copied into$OEM$\$$\System32as mentioned in Shark's original guide and then using Cleanup or Reboot.cmd to register the .dllPlease note: I have found several other files that need to be registered, instead of just one.Good luck.=========== Logging initialized (build: 5.8.0.2469, tz: -0400) ===========Misc = Process: C:\Program Files\Internet Explorer\iexplore.exeMisc = Module: C:\WINDOWS\System32\wuweb.dllSetup *********** Setup: Checking whether self-update is required ***********Setup * Inf file: C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.infSetup Update required for C:\WINDOWS\system32\cdm.dll: target version = 5.5.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\iuengine.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuapi.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuauclt.exe: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuauclt1.exe: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuaueng.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wuaueng1.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wucltui.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wups.dll: target version = 5.4.3790.2182, required version = 5.8.0.2469Setup Update required for C:\WINDOWS\system32\wups2.dll: target version = 0.0.0.0, required version = 5.8.0.2469This checks to see if I need an update. My previous version was 5.4.3790.2182, the new version 6 code is 5.8.0.2649. Notice all the required files are listed.cdm.dlliuengine.dllwuapi.dllwuauclt.exewuauclt1.exewuaucpl.cplwuaueng.dllwuaueng1.dllwucltui.dllwups.dllwups2.dllThis list appears to be incomplete as my system32 folder has a few more files relating to Windows Update with version 5.8.0.2469. So it is best to use the complete list from Shark's post.Setup * IsUpdateRequired = YesSetup *************Setup ** START ** Setup: Downloading client CABsSetup *********Setup * Main CAB URL: http://download.windowsupdate.com/v6/windowsupdate/b/selfupdate/AU/x86/XP/enSetup * MUI CAB URL: http://download.windowsupdate.com/v6/windowsupdate/b/selfupdate/AU/x86/XP/muiSetup * Download directory: C:\WINDOWS\SoftwareDistribution\WebSetupSetup *********Setup ** END ** Setup: Downloading client CABsSetup *************Setup *************Setup ** START ** Setup: Installing client binariesSetup *********Setup * Download directory: C:\WINDOWS\SoftwareDistribution\WebSetupSetup * Stop and start service: YesSo it proceeds to download the required files fromhttp://download.windowsupdate.com/v6/windo...te/AU/x86/XP/enhttp://download.windowsupdate.com/v6/windo...e/AU/x86/XP/muiService received SERVICE_CONTROL_STOP controlExiting Service MainOut of proc datastore is shutting downWUAUENG ServiceMain exits. Exit code is 0x240001Out of proc datastore is now inactiveSetup Starting file operations for section cdmSuccessfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\cdm.dll to C:\WINDOWS\system32\cdm.dll.wusetup.124538687.newSetup successfullly moved C:\WINDOWS\system32\cdm.dll.wusetup.124538687.new to C:\WINDOWS\system32\cdm.dllFile operations for section cdm completed successfullyStarting file operations for section iuengineSuccessfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\iuengine.dll to C:\WINDOWS\system32\iuengine.dll.wusetup.124541046.newSetup successfullly moved C:\WINDOWS\system32\iuengine.dll.wusetup.124541046.new to C:\WINDOWS\system32\iuengine.dllFile operations for section iuengine completed successfullyStarting file operations for section wuapiSuccessfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.124541406.newWARNING: Could not move C:\WINDOWS\system32\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.124541406.bak due to 0x80070020File operations for section wuapi completed successfullyStarting file operations for section wuaucltSuccessfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt.exe to C:\WINDOWS\system32\wuauclt.exe.wusetup.124541593.newSetup Setup successfullly moved C:\WINDOWS\system32\wuauclt.exe.wusetup.124541593.new to C:\WINDOWS\system32\wuauclt.exeSetup File operations for section wuauclt completed successfullySetup Starting file operations for section wuauclt1Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt1.exe to C:\WINDOWS\system32\wuauclt1.exe.wusetup.124541906.newSetup Setup successfullly moved C:\WINDOWS\system32\wuauclt1.exe.wusetup.124541906.new to C:\WINDOWS\system32\wuauclt1.exeSetup File operations for section wuauclt1 completed successfullySetup Starting file operations for section wuaucplSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaucpl.cpl to C:\WINDOWS\system32\wuaucpl.cpl.wusetup.124542218.newSetup Setup successfullly moved C:\WINDOWS\system32\wuaucpl.cpl.wusetup.124542218.new to C:\WINDOWS\system32\wuaucpl.cplSetup File operations for section wuaucpl completed successfullySetup Starting file operations for section wuaueng_WebSetupSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng.dll to C:\WINDOWS\system32\wuaueng.dll.wusetup.124542671.newSetup Setup successfullly moved C:\WINDOWS\system32\wuaueng.dll.wusetup.124542671.new to C:\WINDOWS\system32\wuaueng.dllSetup File operations for section wuaueng_WebSetup completed successfullySetup Starting file operations for section wuaueng1Setup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng1.dll to C:\WINDOWS\system32\wuaueng1.dll.wusetup.124544250.newSetup Setup successfullly moved C:\WINDOWS\system32\wuaueng1.dll.wusetup.124544250.new to C:\WINDOWS\system32\wuaueng1.dllSetup File operations for section wuaueng1 completed successfullySetup Starting file operations for section wucltuiSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wucltui.dll to C:\WINDOWS\system32\wucltui.dll.wusetup.124544750.newSetup Setup successfullly moved C:\WINDOWS\system32\wucltui.dll.wusetup.124544750.new to C:\WINDOWS\system32\wucltui.dllSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauhelp.chm to C:\WINDOWS\help\wuauhelp.chm.wusetup.124545140.newSetup Setup successfullly moved C:\WINDOWS\help\wuauhelp.chm.wusetup.124545140.new to C:\WINDOWS\help\wuauhelp.chmSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wuau.adm to C:\WINDOWS\INF\wuau.adm.wusetup.124545250.newSetup Setup successfullly moved C:\WINDOWS\INF\wuau.adm.wusetup.124545250.new to C:\WINDOWS\INF\wuau.admSetup File operations for section wucltui completed successfullySetup Starting file operations for section wupsSetup Successfully copied source file C:\WINDOWS\SoftwareDistribution\WebSetup\wups.dll to C:\WINDOWS\system32\wups.dll.wusetup.124545375.newSetup File operations for section wups completed successfullySetup Starting file operations for section wups2Setup Successfully copied source fileNow it kills the process and copies the new files over to c:\windows\system32C:\WINDOWS\SoftwareDistribution\WebSetup\wups2.dll to C:\WINDOWS\system32\wups2.dll.wusetup.124545484.newSetup Setup found that target file C:\WINDOWS\system32\wups2.dll doesn't existSetup Setup successfullly moved C:\WINDOWS\system32\wups2.dll.wusetup.124545484.new to C:\WINDOWS\system32\wups2.dllwups2.dllThis is the new file that is missing from version 5. Copy this to $OEM$\$$\System32Setup File operations for section wups2 completed successfullySetup Starting registry operations for section cdmSetup Completed registration operations for section cdm: status 0Setup Starting registry operations for section iuengineSetup Completed registration operations for section iuengine: status 0Setup Starting registry operations for section wuapiSetup Completed registration operations for section wuapi: status 0Setup Starting registry operations for section wuaucltSetup Completed registration operations for section wuauclt: status 0Setup Starting registry operations for section wuauclt1Setup Completed registration operations for section wuauclt1: status 0Setup Starting registry operations for section wuaucplSetup Completed registration operations for section wuaucpl: status 0Setup Starting registry operations for section wuaueng_WebSetupChecking to make sure the files are registered in the registry.Setup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"Setup Completed registration operations for section wuaueng_WebSetup: status 0Setup Starting registry operations for section wuaueng1Setup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng1.dll"Setup Completed registration operations for section wuaueng1: status 0Setup Starting registry operations for section wucltuiSetup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wucltui.dll"Setup Completed registration operations for section wucltui: status 0Setup Starting registry operations for section wupsSetup Completed registration operations for section wups: status 0Setup Starting registry operations for section wups2Setup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"Setup Completed registration operations for section wups2: status 0According to this, there should be four files that need to be registered.C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng1.dll"C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wucltui.dll"C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"Setup Processing registry operations completed. Deleting backup files.Setup Successfully deleted backup file C:\WINDOWS\system32\cdm.dll.wusetup.124538687.bakSetup Successfully deleted backup file C:\WINDOWS\system32\iuengine.dll.wusetup.124541062.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wuauclt.exe.wusetup.124541593.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wuauclt1.exe.wusetup.124541906.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wuaucpl.cpl.wusetup.124542234.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wuaueng.dll.wusetup.124542671.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wuaueng1.dll.wusetup.124544250.bakSetup Successfully deleted backup file C:\WINDOWS\system32\wucltui.dll.wusetup.124544765.bakSetup Successfully deleted backup file C:\WINDOWS\help\wuauhelp.chm.wusetup.124545140.bakSetup Successfully deleted backup file C:\WINDOWS\INF\wuau.adm.wusetup.124545250.bakDeleting back ups files from version 5Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0400) ===========Misc = Process: C:\WINDOWS\System32\svchost.exeMisc = Module: C:\WINDOWS\system32\wuaueng.dllService *************Service ** START ** Service: Service startupService *********Restarting Update ServiceSetup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\5.8.0.2469\wuapi.dll"Setup Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\5.8.0.2469\wups.dll"Here register two more .dll filesregsvr32.exe /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\5.8.0.2469\wuapi.dll"regsvr32.exe /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\5.8.0.2469\wups.dll"Agent * WU client version 5.8.0.2469Agent * SusClientId = ' <deleted>'Agent * Base directory: C:\WINDOWS\SoftwareDistributionAgent * Access type: No proxyAgent * Network state: ConnectedSetup *********Setup ** END ** Setup: Installing client binariesSetup *************Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0400) ===========Misc = Process: C:\Program Files\Internet Explorer\iexplore.exeMisc = Module: C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wuapi.dll\5.8.0.2469\wuapi.dllThe rest of Windows Update continues Edited July 1, 2005 by Gee Link to comment Share on other sites More sharing options...
Body Posted July 1, 2005 Share Posted July 1, 2005 So sorry of my bad English..I meant all of the CABinet files for MU by saying "ActiveX Files"The only file that i can get is that muweb_site file lol:) Link to comment Share on other sites More sharing options...
chezy666 Posted July 1, 2005 Share Posted July 1, 2005 @gee : You only need to register wup2.dll, since the other files are already there in i386 (assuming you copied the updated v6 one's) and get registered as a result of normal installation and also since you are merely copying wups2.dll to system32 not integrating it .@body: To get microsoft update to work you require Windows installer 3.1, windows update v6 files and the muweb.dll file.Windows installer link is http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=enThe Windows update v6 files are in the first post of this topic. Link to comment Share on other sites More sharing options...
Body Posted July 1, 2005 Share Posted July 1, 2005 hmm ok Thank You. Link to comment Share on other sites More sharing options...
Gee Posted July 1, 2005 Share Posted July 1, 2005 @gee : You only need to register wup2.dll, since the other files are already there in i386 (assuming you copied the updated v6 one's) and get registered as a result of normal installation and also since you are merely copying wups2.dll to system32 not integrating it .Good point, since the files are recompressed back into i386, when they are unpacked during setup, they would have been registered.I should have known that. It is getting late, I should get some sleep. Link to comment Share on other sites More sharing options...
Coolsights2000 Posted July 1, 2005 Share Posted July 1, 2005 (edited) I have a question why are trying to reinvent the wheel and not just use the full installer that was posted above. .....http://go.microsoft.com/fwlink/?LinkId=43264M$ already made a package to install the V6 site file...... Edited July 1, 2005 by Coolsights2000 Link to comment Share on other sites More sharing options...
enuffsaid Posted July 1, 2005 Share Posted July 1, 2005 I have a question why are trying to reinvent the wheel and not just use the full installer that was posted above. .....http://go.microsoft.com/fwlink/?LinkId=43264M$ already made a package to install the V6 site file......<{POST_SNAPBACK}> Link to comment Share on other sites More sharing options...
Sonic Posted July 1, 2005 Share Posted July 1, 2005 here we speak about integrated version of V6 .. not silent install or simple install ... Sorry if I don't understand the two past posts ... (french here ...) Link to comment Share on other sites More sharing options...
Coolsights2000 Posted July 1, 2005 Share Posted July 1, 2005 integrated or not to integrate.. I like to leave the original files as much as possible original cause when a new update comes out it easier to change later.I use the SVCPACK.INF and when they come up with a new list I do a min install then update the [setupHotfixesToRun] list.........when you integrate you have to redo the integration after major updates anywayto me just a waste of time... I have played and always go back to SVCPACK.INF......There have been issue/conflicts with integrating update so using the SVCPACK.INF clears those issues,,,,,,, But like I tell people you can do it how ever you want it is your computerJust my two cents...Mac! Link to comment Share on other sites More sharing options...
Sonic Posted July 1, 2005 Share Posted July 1, 2005 okay ... for me I have choosen another method perhaps I will switch to svcpack.inf Link to comment Share on other sites More sharing options...
Gee Posted July 1, 2005 Share Posted July 1, 2005 I have a question why are trying to reinvent the wheel and not just use the full installer that was posted above. .....http://go.microsoft.com/fwlink/?LinkId=43264M$ already made a package to install the V6 site file......<{POST_SNAPBACK}>I agree with you, but this post was about integration.Using the Microsoft pack and SVCPack is better, because if a new version arrives, it would be easier to just replace the package Microsoft released.The downside is that the installer is 4.3 Megs. This is due to all the extra languages. So if space is a problem, you better repack the installer by removing all the unnecessary languages. Link to comment Share on other sites More sharing options...
Incroyable HULK Posted July 1, 2005 Share Posted July 1, 2005 I have integrated this update to my svcpack.inf but when I go to windows update it still ask me for Windows Installer 3.1 and then I have to reboot... Link to comment Share on other sites More sharing options...
chezy666 Posted July 2, 2005 Share Posted July 2, 2005 I have integrated this update to my svcpack.inf but when I go to windows update it still ask me for Windows Installer 3.1 and then I have to reboot...<{POST_SNAPBACK}>either integrate or svpack the windows installer 3.1 package to your uacd, thats required aswell . Link to comment Share on other sites More sharing options...
zorro1 Posted July 2, 2005 Share Posted July 2, 2005 (sorry for my english)For me, i have put wups2.dll in $OEM$\$$\sytem32 and it work fine Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now