jvidal Posted February 11, 2010 Share Posted February 11, 2010 Hi everyone (especially tommyp).I just rebuilt my xp64 CD with yesterday's updates and I noticed that KB975713 didn't take, even though it was present in the HF folder.any ideas?bye! Link to comment Share on other sites More sharing options...
tommyp Posted February 11, 2010 Share Posted February 11, 2010 Maybe you can help since I don't have x64 windows. Extact the hotfix (do a commanline, and use the /x switch). Extract to whereever you like. Next look at the files inside the various folders. Now, look at the same files on the OS and make note of the version numbers. Run the hotfix normally. Finally look at the resultant file changes and see whether or not those same files are part of the sourcess folder. I'm not sure when I'll get around to fixing things though. Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 (edited) Thx for answering, tommy.Here's what you wanted:The HF contains two folders:SP2GDR and SP2QFE.inside SP2GDR there is shlwapi.dll v6.0.3790.4603 and a 'wow' folder, with wshlwapi.dll v6.0.3790.4603inside SP2QFE there is shlwapi.dll v6.0.3790.4603 and a 'wow' folder, with wshlwapi.dll v6.0.3790.4603In the OS, after a clean install of the hfsliped CD, the files are:system32\shlwapi.dll v6.0.3790.2795syswow64\shlwapi.dll v6.0.3790.4603system32\dllcache\shlwapi.dll v6.0.3790.2795system32\dllcache\wshlwapi.dll v6.0.3790.4603And after manually installing the HF, I've got:system32\shlwapi.dll v6.0.3790.4603syswow64\shlwapi.dll v6.0.3790.4603system32\dllcache\shlwapi.dll v6.0.3790.4603system32\dllcache\wshlwapi.dll v6.0.3790.4603Finally, the files in sourcess areAMD64\shlwapi.dll v6.0.3790.2795 (incorrect) (although it has today's date!)I386\wshlwapi.dll v6.0.3790.4603 (correct)Hope this helps! Edited February 12, 2010 by jvidal Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 I did a little experiment, I took shlwapi.dll v 4603, renamed it to shlwapi.dl_ (without actually compressing it) and copied it to sourcess\AMD64.Next, I ran hfslip with the makeiso "undocumented" feature.Installing as we speak. Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 Ok, after my experiment, everything went fine, no updates wanted by MU.So, the question is why is the file shlwapi.dll not being copied to AMD64?bye! Link to comment Share on other sites More sharing options...
tommyp Posted February 12, 2010 Share Posted February 12, 2010 I'm not sure why it's not getting copied correctly. Perhaps there's another hotfix that is interfering with things. Can you run a test case where you only use 975713 in HF and nothing else? Then go into the sourcess and just double check to see if the offending dlls have the right revision. Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 Ok, I'll do that and report back to you asap.bye! Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 Ok, did it.AMD64\shlwapi.dll is now v6.0.3790.4603, which is correct (the version from the HF)I386\wshlwapi.dll , same as above.So, there is s/thing interferring with the HF.The weird thing is that the filver from the original file is the same as the resulting one, so there shouldn't be another HF replacing the file, in that case it would probably have a different version num.I mean, before HFslip--> v6.0.3790.2795. After hfslip with 975713--> v6.0.3790.2795.No, wait, that's not right. I just checked shlwapi.dll from source\AMD and it has filever 6.0.3790.3959.So, it seems that one HF is installing a version that's even older than the one in source.I'll check other HFs, maybe there is an obsolete one that's messing things up. Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 Ok. I found the problem.Shlwapi v6.0.3790.2795 comes in the IE8 installer. (why it's older than the one in the source it's anyone's guess)If IE is processed first, then why doesn't the file from 975713 replace it?bye! Link to comment Share on other sites More sharing options...
jvidal Posted February 12, 2010 Author Share Posted February 12, 2010 I did another "experiment". This time I installed xp64 SP2 (non-hfsliped).Shlwapi.dll had version 6.0.3790.3959 (the one from the CD)Then I manually installed IE8 (which contains the older version of the file, v6.0.3790.2795). Rebooted and checked the file versions.Turns out the file still was ver. 6.0.3790.3959 (the file was NOT replaced by the older version). Then I installed 975713 and the file was updated to v6.0.3790.4603.bye again! Link to comment Share on other sites More sharing options...
tommyp Posted February 14, 2010 Share Posted February 14, 2010 I see the prob. Looks like one less binary needs to get processed if doing IE8. I'm surprised WU didn't report this before. Can you open the script, locate the following, my textreader says it's around line number 940. ECHO>>%MAINSS%\TXTSETUP.SIF sdesktop.scf = 1,,,,,,,,3,3&ECHO>>%MAINSS%\DOSNET.INF d1,sdesktop.scf:: MOVEXCOPY/Y WORK\MSIE\UPDATE\*.CAT WORK\SVCPACK >NULadd the following between the two lines (just before the move line). :: BANDAIDS FOR BAD HOTFIXESDEL/Q/F WORK\MSIE\shlwapi.dllReport your findings. On a sidenote, is wshlwapi.dll part of the IE8 installer? Can you do the rev check like you did before (orig cd, post IE8 install, post HF install)? That last post you did nailed the shlwapi.dll prob. Link to comment Share on other sites More sharing options...
jvidal Posted February 14, 2010 Author Share Posted February 14, 2010 (edited) thx, tommy.I'll do that and report back to you.c ya!Oh, BTW, wshlwapi.dll also comes in the IE8 installer, inside a wow folder. Edited February 14, 2010 by jvidal Link to comment Share on other sites More sharing options...
tommyp Posted February 14, 2010 Share Posted February 14, 2010 Can you do the wshlwapi.dll version check? Check the version after a barebones normal (non hfslip) install, post IE8 install, and post HF install. I may need to tailor that little fix. Thanks! Link to comment Share on other sites More sharing options...
jvidal Posted February 14, 2010 Author Share Posted February 14, 2010 (edited) Ok, Done.system32\shlwapi.dll , syswow64\shlwapi.dll , system32\dllcache\shlwapi.dll & system32\dllcache\wshlwapi.dllare all the correct ver. i.e. 6.0.3790.4603.(no need for that wshlwapi.dll check, as you can see)Also, it was never an issue, read #3 again.Plus, MU is completely happy, nthing required.Time for a new final I guess. Edited February 14, 2010 by jvidal Link to comment Share on other sites More sharing options...
jvidal Posted February 18, 2010 Author Share Posted February 18, 2010 well? 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