AP fails install KB941569. Affects: EVERYONE, experts included
Posted 26 July 2008 - 06:34 AM
1) The user must manually download WindowsXP-KB941569-x86-ENU.EXE from Microsoft's website:
2) Run the exe, not in silent mode. Do not hit Next at this point, continue to step 3.
3) Close MSN IM (Windows Live Messenger), IE6 or IE7, and any other applications.
4) Bring up the Task Manager (CTRL ALT DEL) by right clicking the toolbar and clicking Task Manager.
5) Find all instances of explorer.exe in the list and right click them and click End Process. At this point your desktop should vanish, do not close the Task Manager, leave it open.
6) Now click through the screens provided by the KB941569 patch and install it. If the patch suggests you close a particular application, do so before continuing.
7) Once the install is complete, click Finish.
8) Now in the Task Manager click the File menu and New Task (Run...), then type explorer and click OK. Your desktop will now reappear.
I would suggest for the next version of AP that additional rules be provided for certain patches to give AP the ability to kill certain processes automatically if necessary for this sort of situation.
I hope this helps everyone. I wish I had caught it sooner.
Posted 26 July 2008 - 09:27 AM
Thanks for reporting your findings. So that we can better understand what is happening here, can you please let us know what version of Media Player you have, as well as all AntiVirus, AntiSpyware/AntiMalware and anti-IE hijacking software you may have running. Any other media players present (e.g. iTunes, Firefox plugins)? I assume from the thread you are posting in, that your OS is XP-SP3?
I need to firm this up because my records show that I have at least one successful fully silent install of KB941569 on XP-SP2, WMP9 (verified by file version) back in January. At the time, no AV/AntiSpyware/AntiMalware was running nor was IE or any version of Messenger. However the Desktop (i.e. the explorer.exe process) was fully functional.
MSFT's update process can usually manage quite well if files are in use: all you save by killing processes off is a reboot. Your reference to the Desktop also surpriises me as the explorer.exe process does not load, nor does it maintain handles to either wmasf.dll or wmvcore.dll. Did you verify dll's in memory with Process Explorer or anything else?
I understand the difference between Belarc and PSI detection, but there are documented cases of Belarc being wrong. Does anything from Microsoft support your experience of which one of these third-party tools is correct (e.g. WSUS, MBSA, WU, MU)?
At what point did you reboot?
Posted 26 July 2008 - 08:33 PM
you may count a few dozens with me. i always check for failed modules. maybe not this one, but all that shows also not installed. i always install all critical, noncritical and a few others (including wmp11) at once.
but keep in mind that i always let ap run alone. nothing else running at same time. since a few things may lock certain files, for sure that some issue may happend if you are running ap with another background thing running
Posted 27 July 2008 - 03:20 AM
I verified the patch was not correctly installed independently of Belarc/PSI by running the patch manually and discovering that it required me to close explorer.exe (after a fresh reboot) with no other software open (Firefox/MSN/IE/etc were all closed). Belarc verified that the files had not been updated, but the moment I killed explorer and installed the patch myself, Belarc detected the system as successfully patched.
Also, I always reboot after applying hotfixes.
It may only happen to a small percentage of people then, if I'm one of the rare cases and this hasn't been discovered yet. But, the unlikeliness of it happening does not preclude my previous suggestion that there be dependency rules that can allow patches given to apup the ability to shut down processes during a silent install and bring them back again afterward.
Sorry if I cried wolf here, I thought this affected everyone equally.
Posted 28 July 2008 - 08:08 AM
I have no proof, from this remote distance, but I would regard spyware doctor with suspicion and would not want this running during updates/installs. One computer I repaired had spyware doctor + McAfee on it and was effectively unusable for about 6 minutes (or more) after switch-on each day.
Posted 28 July 2008 - 10:54 PM
Perhaps a better solution for apup is to make the patch non-silent if it requires termination of running tasks.
Posted 30 July 2008 - 06:18 AM
Posted 31 July 2008 - 04:53 PM
I've found a few other patches that Belarc is complaining about but my manual installs haven't corrected them, I'm still trying to sort that out. These may be the false positives you were talking about before. But, as far as the KB941569 patch, I'm certain it was never installed properly because of the silent install.
Well, the non-silent installs would be for rare circumstances where the patch has the possibility of failing to install if made silent. I don't think most patches fall under this category, as you mentioned before worst-case you have to reboot for some things to apply properly. But, in this situation, the patch couldn't do its job. There has to be a small percentage of people who have had the same problem as me and just don't realize it. Just one person is one too many for this to affect hehe.
I think a smarter autopatcher is good for everyone, the current version can't be adjusted remotely very well. If there are situations like this that come up in the future that are far more serious, there isn't anything that the autopatcher team can do about it except mention it on the forums and hope people resolve it themselves, or release a new version of autopatcher, which is an unreasonable expectation to have every time there's a unique patch problem to solve. That's why I think the dependency rules could solve all unforeseeable problems in the future.
Posted 01 August 2008 - 06:51 AM
Your comments are appreciated, as always.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users