Re: New shdocvw.dll in Security Update?

From: Cycloid Torus (fictitious_at_hotmail.com)
Date: 04/19/05 

Date: Tue, 19 Apr 2005 13:52:38 -0400

Happily, 1st check came thru:
"Your browser has been checked for parasites. None was found."

While at this I did learn that recent update from Norton (the Windows
Management thingy) had apparently borked a bit of registry (found and
resolved with RegistryMechanic from pctools). This nice utility also let
about 14 megs of air out of the registry which has bloated over the past
year to 64 megs (is Registry Mechanic the best "bloat killer" or is there
another?).
I promise to download and run HiJack_This, as it is prudent - and spend the
time to learn what it says. I run with NAV, ASw, SpywareBlaster and Spybot
together with Internet Zone set to "High" if I use IE in an Admin priv user
account - all behind ZoneAlarm and a NAT router.

Since I checked and confirmed size and datestamp on shdocvw.dll (see below)
I am still inclined to think this is a quirk in ASw. Apparently, the
February version of shdocvw.dll is replaced by a slightly different version
for the second "hotfix".

Check what Microsoft says about its Security Update.

http://www.microsoft.com/technet/security/Bulletin/MS05-020.mspx

If you dig down through "Security Update Information", they finally tell you
what files on which they they did things - with time stamp (different from
February) and size (same as February). I found this thru your earlier
comment (Thanks PA_Bear!).

"The English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files are
listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference between
UTC and local time, use the Time Zone tab in the Date and Time tool in
Control Panel.

Internet Explorer 6 for Windows XP Service Pack 2:

      File Name Version Date Time Size Folder

      Shdocvw.dll
     6.0.2900.2627
     10-Mar-2005
     08:02
     1,483,264
     SP2GDR

      Shdocvw.dll
     6.0.2900.2627
     10-Mar-2005
     07:43
     1,484,288
     SP2QFE

Note When you install this security update on Windows XP Service Pack 2, the
installer checks to see if one or more of the files that are being updated
on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update an affected file, the
installer copies the SP2QFE files to your system.

If you have not previously installed a hotfix to update an affected file,
the installer copies the SP2GDR files to your system.

For more information about this behavior, see Microsoft Knowledge Base
Article 824994."

I think the change caused a sufficient "dance" for ASw to report a possible
exception.

I am beginning to understand why MS is going thru all this "versioning"
(killing DLL hell before it starts, etc) - I just hope it doesn't bring more
problems than it solves.

Best regards,

CT

ps Hope the AWOL was fun.

Relevant Pages

  • Re: New shdocvw.dll in Security Update?
    ... about 14 megs of air out of the registry which has bloated over the past ... Check what Microsoft says about its Security Update. ... on your system have previously been updated by a Microsoft hotfix. ... installer copies the SP2QFE files to your system. ...
    (microsoft.public.security)
  • Re: office update is unable to check for updates
    ... Windows Installer version 1.0 to Windows Installer version 1.1. ... Here is another post I saw on the forums that seems to have work for other users, but it requires advanced knowledge of the OS, basically registry editing, so please be careful if you try it. ... we need to manually delete all the registry keys for Office. ...
    (microsoft.public.officeupdate)
  • Re: Office unable to update
    ... You installed Office updates in the past and then upgraded from Windows Installer version 1.0 to Windows Installer version 1.1. ... basically registry editing, so please be careful if you try it. ... Delete the following registry keys if they exist: ...
    (microsoft.public.officeupdate)
  • Re: Windows Installer patch files (.MSP files) from previously app
    ... The installer patch never opens for me. ... understand why Microsoft are not addressing this issue. ... delete registry entries is not an acceptable solution. ... If you use Registry Editor ...
    (microsoft.public.officeupdate)
  • RE: Fix for Office repair and Office Updates install fail
    ... This resolves the install problem with the last Office updates. ... Tried the often suggested method of using the Windows Installer Cleanup ... aware that it involves a lot of registry editing, but it did fix ALL of my ... Delete the following registry keys if they exist: ...
    (microsoft.public.windowsupdate)