7 replies to this topic

[Bill M]

I recently ran Autopatcher to update my W2K system. There were still a few missing updates according to Belarc Advisor, so I re-ran AP with the /log option. The log file is posted below.

I have two questions:
- I used AP to update DirectX last spring. The files downloaded at that time are causing an UNOFFICIAL designation as listed in the log file. Should anything be done with these files?

- One of the missing updates is KB952954. I verified that the update file had been downloaded from MS, but it is not available in the AP update listing, as noted in the log file. How should this be resolved?

Thank you in advance for any help on this.

Bill M

AutoPatcher log file follows:

AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows 2000 Professional Service Pack 4

System Components:
Internet Explorer: 6.0.2800.1613
Windows Media Player:
.NET Framework:
Windows Installer: 3.1.4000.1823
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

UNOFFICIAL: File 'C:\Program Files\apup\modules\Components\directx.apm' was found, but not mentioned by any RTI!

UNOFFICIAL: File 'C:\Program Files\apup\modules\Components\directx_files\directx_mar2008_redist.exe' was found, but not mentioned by any RTI!

Module 'Security Update for Windows 2000 (KB952954)' (unique id: 'KB952954_2K_ENU') cannot be loaded because it's uniqueID is duplicate (the module named 'Security Update for Windows 2000 (KB950582)' also uses it).

[James]

Hi Bill M

It seems you have a mismatch between the updates you actually have and the list that AutoPatcher is working from. Secondly you have what looks like an error in an AutoPatcher .apm file.

The best way to resolve this is to run APUP again.

However, you can remedy the first two errors manually, by removing the files directx.apm and directx_mar2008_redist.exe yourself. You can either delete them, or if you want to save them, move them to a folder that is not a subfolder of C:\Program Files\apup\.

The third error is a bit more complicated - if you have not run APUP recently, then please do so. From memory kb952954 and kb950582 are not related so this looks like a typing error.

Can you please let me know the date (modification date) of KB952954_2K_ENU.apm?

Can you also let me know what date you last ran APUP?

--

[Bill M]

James, on Sep 9 2008, 12:10 PM, said:

Can you please let me know the date (modification date) of KB952954_2K_ENU.apm?

Can you also let me know what date you last ran APUP?

--

I can move the DirectX files, so that will be solved.

I ran APUP on Sept. 9.

The mod date of KB952954_2K_ENU.apm is 24 August, and also for of KB950582_2K_ENU.apm. But I think I found the problem: in both of these files, the UniqueID is given as -
[Behavior]
ParentID=WINDOWS_CRITICAL_PARENT
UniqueID=KB952954_2K_ENU

Is it enough to make the obvious edit in the latter file, or are there other changes required?

Thanks for your help.

[Erik Ramey]

Thanks for the report. I went ahead and updated KB950582 module and uploaded it to the servers. Go ahead and run APUP again and this conflict should be resovled.

Your AP installation for 2K will show "unoffical" until I can compile another rti file tonight.

[Bill M]

Erik Ramey, on Sep 9 2008, 12:54 PM, said:

Thanks for the report. I went ahead and updated KB950582 module and uploaded it to the servers. Go ahead and run APUP again and this conflict should be resovled.

Your AP installation for 2K will show "unoffical" until I can compile another rti file tonight.

I ran APUP and AP yesterday, and the module conflict was resolved.

I am still getting the "Unofficial" error messages in the log file. Were you able to compile the rti file - the file 2k_x86_enu.rti was downloaded yesterday.

According to Belarc Advisor, there is still one hot patch required - 951698 - but it is not being 'offered' by AP. This is a DirectX patch. I note that the apm file for this patch shows under
[SystemComponents]
. . .
DirectX=9
while, in my autopatcher.log, the listing under System Components is
DirectX: 4.09.00.0904.
Is this why AP is not including this in the patch list?

Could I deal with this by removing the DirectX component using AP, and then re-installing it, or do you have another suggestion?

Thanks again for your help and for a very useful program.

Bill M

[James]

Hi Bill

I missed this -- and I think Erik is away for a day or two.

When AutoPatcher reports "DirectX: 4.09.00.0904" that is Version 9.
Anything that begins with "4.09" is Version 9 and "4.09.00.0904" is actually Version 9.0c

There are multiple versions of the kb951698 patch, but in my tests APUP has downloaded the correct patch for DirectX 9. However, as you say, it is not offered.

I think there is a problem with the .APM file, but I need Erik to confirm this and then fix it.

In my tests, there seems to be another problem with the .RTI file as well. So you may still have AutoPatcher showing as Unofficial.

--

[James]

Bill,

I have now had a chance to look properly at this. There is definitely an error in the APM file.

So here are the answers to your questions:

Bill M, on Sep 11 2008, 04:25 PM, said:

... Is this why AP is not including this in the patch list? ...

Yes

Bill M, on Sep 11 2008, 04:25 PM, said:

... Could I deal with this by removing the DirectX component using AP, and then re-installing it, ...

No

Bill M, on Sep 11 2008, 04:25 PM, said:

... or do you have another suggestion? ...

Yes
In the APM module, in the [SystemComponents] section, replace the line that reads

DirectX=9

with

DirectX=4.09.00.0900,4.09.00.0901,4.09.00.0902,4.09.00.0904

which sets this update to be installed with DirectX 9.0, 9.0a, 9.0b and 9.0c as specified by MSFT.
(Those are points "." within each 4-part version number and commas "," between each of the 4-part version numbers.)

You should then find this update correctly offered by AutoPatcher in the Critical section.

This will have three consequences:
1) AutoPatcher will go "Unofficial"
2) the log will complain of a size error for KB951698_2K_enu.apm
3) due to an error/bug in the RTI file the log will complain (wrongly) for about 50 other files

--

Edited by James, 13 September 2008 - 09:12 PM.

[Bill M]

Thanks, James, that did the trick. And also to Erik, for his earlier advice.

Hopefully, the errors/bugs will be cleared up for the next release.

Thanks again,
BillM