Re: KB922760-second offer to download

Howdy Antioch,

I neglected to tell you that the .dll files *should* be present in WINDOWS\system32

Notes When you install these security updates, 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 one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
http://support.microsoft.com/kb/824684

So, since there is an SP2QFE folder in $hf_mig$, one would compare the SP2QFE files on the Security Bulletin page with the ones located in the system\32 folder.
When I asked you to check the registry it was just to see what the Filelist contained, not for any Data or Names.

Since you've uninstalled and reinstalled and are getting no prompt to reinstall it, then apparently it has installed properly this time.
( Could one possibly get more versions of install into one sentence? :)

Now, apply all of that newly attained knowledge to KB920213.
http://www.microsoft.com/technet/security/Bulletin/MS06-068.mspx

AND, *please post* the KB920213.log.
There are always errors in the KBxxxxxx.logs; some are actually quite helpful in diagnosing installation failures. Most of them are common and will appear in the logs whether the update installs properly or not.


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



antioch wrote:
Hello Mow
Apologies for the length - felt it important to detail what has been done.
Yes, your first response did get through to me @ 23:06 GMT 29 Nov.
I have only just picked up your replies.
Being a complete idiot and terrified of Registry, I did however summon up the courage to enter Reg and at the place to which you directed me, under the file list it showed a stream of numbers from 0-56incl. In the right hand section there was
entered 'default REG_SZ (Value not set)
I thought that does not sound right. Tried to follow your further advice, re comparing but I may have got lost.
I went to the MS bulletin and read the security update and printed out the list of file attributes under the heading 'file information'. I guess that is the place you suggested. This showed two sets of ID files with Folder names of SP2GRD and SP2QFE.
An hour later(I kid not)I went to C:Windows\Shf_migs - opened this folder - then opened the KB922760 folder - then opened the SP2QFE one(there was no SP2GDR showing)
and noted that all the .dll corresponded with those on the MS file info list I printed.
Prior to doing this, more for the reason to gain knowledge then any other, I did look in the notepad for KB922760, and there were error entries and at the end there was something re Isreboot for filequeue .dllfiles delayed:reboot required????
Since uninstall and reinstall, this notepad appears to show the same info - certainly errors and the .dll delayed.
Howsomever, I went back to MSU Home and did NOT get the offer of KB922760 - Great!
As I am typing this, up pops that bloody shield again - no it is not that KB but another I installed on 15 Nov - this time it is KB920213.
Now I cannot get that stupid nursery rhyme about going round a mulberry bush out of my head(I know you cant fix that).

"MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx> wrote in message news:e6FAjZMFHHA.2464@xxxxxxxxxxxxxxxxxxxxxxx

Weird ... I answered this yesterday and the post never showed up ?
Here's another attempt .....

It has not been reissued. Best bet to determine why it's being reoffered is to go over the file list on the MS Sec Bulletin MS06-067 page, Antioch. (They're under Security Update Information)
Also, check the file list in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB922760\Filelist

It is possible that one of the .dll files either did not get updated or did not register properly.
You can compare the file list with the installation log ... the KB922760.log located in WINDOWS.

Check the files on the system vs the ones listed on the Sec Bulletin page
If they differ, compare the files that were installed in the KB log against the ones listed on the Sec Bulletin page.

OR, just uninstall it from ARP and manually download the update from -

http://www.microsoft.com/downloads/details.aspx?FamilyId=EA3CE61C-3A28-4777-9EEF-1486BB483C4F
(For IE6 on SP2)


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============

antioch wrote:


On Sunday 25Nov, the little yellow shield popped up - clicked on it and there was KB922760 on offer.
Looked in Add/Remove, there was KB922760, along with the other criticals I installed on 15Nov from their respective download sites, one at a time, off-line, AV etc all turned off/disabled - no problems experienced.
Did a WU to the Home Page - selected Custom and the only thing on offer was KB922760.
Clicked on 'Details....... and the window popped up showing a published date of 21Nov????
Clicked on this link

http://go.microsoft.com/fwlink/?LinkId=78172

Which took me to the MS Bulletin MS06-067 with a published date of 14Nov.
I have looked through the group and cannot see a report of this KB being re-offered - plenty cannot install it.
Is this a fix/patch for the original one I downloaded on 15Nov?
I can find nothing in MS re any article for MS06-067 being published on 21Nov.
I can uninstall from Add/Remove - no warnings re an uninstall effecting other updates.
OR I could just but it in the 'Hidden' folder in MSU Home.
There may be another alternative of course....
Rgds
Antioch



.

Relevant Pages

  • Re: REGSVR32 0x80070005
    ... Since the issue is with .dll files I'd suspect Permission issues in ... If the installer is an .msi you can enable verbose logging and perhaps get a clue as to where in the registry the error is occurring. ... I first attemped the install as a member of the local administrators and after it failed I gave it another go using the built-in local administrator account but that produced the same problem. ... The dll files themselves are not restricted via NTFS. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: REGSVR32 0x80070005
    ... Since the issue is with .dll files I'd suspect Permission issues in ... If the installer is an .msi you can enable verbose logging and perhaps get ... a clue as to where in the registry the error is occurring. ... The dll files themselves are not restricted via NTFS. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Program Works On XP But Not W98
    ... > statically the files I need, and how do I know which .dll files? ... > As for including the .dll files in the installer, ... The MFC code can be in DLLs or it can be linked into your exe. ... Most Windows programs need more ...
    (microsoft.public.vc.mfc)
  • Re: Cannot install SP1
    ... start or due to some corruption on DLL files for the installer. ... > The component in the window is Microsoft Exchange. ...
    (microsoft.public.exchange.admin)
  • Re: How to best communicate with Microsoft about the difficulties of uninstalling the 2007 Office sy
    ... the "uninstall" is supposed to be the automated removal tool...which doesn't always work as intended. ... In my past dealings with folks from Microsoft, I think there are a lot of really smart people who have way too many priorities and PR issues to deal with. ... Automation would be great, though it's always dangerous to automate stuff when you don't know the configuration of everyone's particular system, and the risk of toasting something is pretty high. ... it would be great if the Windows Installer Cleanup Utility would be updated to support Office 2007. ...
    (microsoft.public.office.setup)
Loading