45 replies to this topic

[Cristiano]

sometimes, yes. but not all updates have registry detections. it may be true for this one

[]s

[mbonwick]

Is there any way of knowing which updates can be detected via the registry? As far as I can see, all the previous modules have reistry detection values.

I still can't find any .inf file: if I extract the .mps file, I get a long list of folders and
!_Columns
!_StringData
!_StringPool
!_Tables
!MsiPatchMetadata
!MsiPatchSequence
[5]SummaryInformation
PCW_CAB_H15057_1

All of which are just listed as "file"
Any thoughts? Am I missing the blindingly obvious?

[Cristiano]

> is there any way of knowing which updates can be detected via the registry?
no. except when you look into the registry of an machine that is already running that update and take the detection from that machine. and still, some updates are extracted like this one: no valid files to look.

[]s

[mbonwick]

The problem with taking the detection from another machine is from updates like the Junk e-mail filter.

The detection is the same (OUTLFLTR.msp), but it appears in about 6 registry keys so there's no way of knowing which is the right one

[Cristiano]

there's an install date in any of those?

[]s

[mbonwick]

I don't have office 03 here right now to check, but I don't think there is an install date.

Is there any way of telling when a registry key was created?

[Cristiano]

no, but i can track that in a vm. i'm rebuilding an enu vm to test if the removal of one update has any effect and i can try install that update alone, in a clean machine. and this may be more easy to track. do you have the link for the most up-to-date version for this one?

[]s

[mbonwick]

http://download.micr...ullFile-ENU.exe

[Cristiano]

ok, thanks. i will activate another fan into my spare machine and run the vm and the updates. 35ºC at night... no one deserves that...

[]s

[Cristiano]

ok, test done. office 2003 enu installed and updated only with KB974771. looking into the entire registry for KB974771, it was found only in this key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patches\3EC7C09BE3A2B5E41A0B5E5BCB6FACE8]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000001
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20091031"
"DisplayName"="Update for Outlook 2003: Junk E-mail Filter (KB974771): OUTLFLTR"
"MoreInfoURL"="http://support.microsoft.com/kb/974771"

please, take a look to see if this work also detection.

[]s

[mbonwick]

Yep, that key seems to exist on both my installations as well.

Thanks for your help in this matter, I shall look for the others accordingly.

[Cristiano]

glad to help

[]s

[mbonwick]

I can't believe how long this is taking me! I sit down with the best intentions, then something else crops up and I have to stop. Grrr. I'll get there eventually.

[Cristiano]

don't worry. this happens all the time with me too. too often, to my taste, but ok

[]s

[mbonwick]

I thought I'd do some of the quicker modules tonight - basically, the viewers as there's no way of getting registry keys for them - and I've come across a problem with GUIDs.

The document I've found on MS don't say what the SKU of Word viewer is - any help?
I think I'm right in saying it sould be {**YY0409-6000-11D3-8CFE-0150048383C9} (where YY are numbers I need to know)

[Cristiano]

sorry. i can't help with that. Domenico is doing the office 2k7 updates. he shall be more familiarized with office updates than me. he is lying in a bed right now, recovering from an accident and may take a few days to you get your reply, but in this matter, surely he knows more than me. so, an idea: pm him

[]s

[mbonwick]

Apart from a Visio module, that I can't get values for (as I don't have Visio) and one for word viewer (I'm waiting to get in touch with Domenico about the GUID), I've finished all the .apm files.
I'm now going to check through the download script for any more files that have been superceeded, update the MD5 of the .apm files, and then I think it'll be ready for testing.

One question: what does the .rti file do?

[Cristiano]

the rti file is an checking for the script. basically, it checks if all files are in the proper place or if there's something that should not be in there. the usage of that tool is restricted to the autopatcher team

[]s

[mbonwick]

Right, I think that's all I can do done then.
Someone else needs to finish the apm for KB955655 as I don't have visio, so can't get registry/file values.

I think everything is done apart from that, shall I send the script over?

[Cristiano]

please, check your pms

[]s