The issue with this update is that same as the issue I sited in another thread titled "Problem with KB3068368 Detection".
If you extract the WindowsServer2003-KB3000988-x64-ENU.exe update and check the update_SP2QFE.inf for PreRequisites, one will find:
[Msidll.AndOp.Section]
GreatOrEqualOp=CheckFilever,system32.Files,msi.dll,">=",4.5.6001.22159
LessOrEqualOp=CheckFilever,system32.Files,msi.dll,"<=",4.5.6002.23507
The version of my msi.dll file is 4.5.6002.23731 hence, it fails the "LessOrEqualOp=CheckFilever,system32.Files,msi.dll,"<=",4.5.6002.23507" portion of the PreRequisite test and the "WindowsServer2003-KB3000988-x64-ENU.exe" will never install.
AP would need to be able to perform an exclusionary test to prevent display of updates for extant file(s) with versions greater than the file(s) in the updtae.
Problem with KB3000988 Detection
- Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
Re: Problem with KB3000988 Detection
It would appear that this particular update is NOT for Windows XP x64. I will amend the apm module and update the files on the server.
BTW I checked my VM and tried manually installing the update, It reported that this is NOT Applicable to this system...
Apm Module updated and uploaded onto the server..
BTW I checked my VM and tried manually installing the update, It reported that this is NOT Applicable to this system...
Apm Module updated and uploaded onto the server..
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
Re: Problem with KB3000988 Detection
AP used to employ custom dependencies using =, <=, >=, to check for an existing file...?
Don't remember? maybe a comma could be used --- ComponentVersion=>4.5.6001.22159,=<4.5.6002.23507
I thought -- ComponentVersion=8,9 was used alot, not sure why =< & => would not also work seperated by a comma?
Don't remember? maybe a comma could be used --- ComponentVersion=>4.5.6001.22159,=<4.5.6002.23507
I thought -- ComponentVersion=8,9 was used alot, not sure why =< & => would not also work seperated by a comma?
Re: Problem with KB3000988 Detection
This is in use currently in most apms.ChrisJ wrote:AP used to employ custom dependencies using =, <=, >=, to check for an existing file...?
This is doable... I will make code changes to add this or something similar.ChrisJ wrote:Don't remember? maybe a comma could be used --- ComponentVersion=>4.5.6001.22159,=<4.5.6002.23507
I thought -- ComponentVersion=8,9 was used alot, not sure why =< & => would not also work seperated by a comma?
Re: Problem with KB3000988 Detection
Thanks for the info on the use of dependencies TAPG, much appreciated. I've not looked exhaustively at all the apm files but had noticed the use of the obvious: <, >, =. ... wasn't sure how far they could be stretched, how precise, specific.
I'm unclear how much AP 5x & 6x have changed from when I was familiar with the inner workings, back around v1x
reeeepeating myself here
I've wanted to write up a quick and messy starter doc for newcomers but now I have so many questions too... I hate feeling clueless to the point of being unfamiliar
There's very little activity on the forum it doesn't seem necessary at this point I figure, versus 5 or so years ago... most people find their way eventually - Sorry, OT!
![Uber Geek :ugeek:](./images/smilies/icon_e_ugeek.gif)
I'm unclear how much AP 5x & 6x have changed from when I was familiar with the inner workings, back around v1x
![Smile :)](./images/smilies/icon_e_smile.gif)
![Arrow :arrow:](./images/smilies/icon_arrow.gif)
![Confused :?](./images/smilies/icon_e_confused.gif)
![Uber Geek :ugeek:](./images/smilies/icon_e_ugeek.gif)
Re: Problem with KB3000988 Detection
NP, start a new thread and ask your questions. Begin the interview!
Re: Problem with KB3000988 Detection
KB3000988 is superseded by KB3072630 (MS15-074) and according to this guy, the KB3072630 Server 2003 x64 security update can also be installed under WinXP X64 SP2. In fact many of the Windows Server 2003 X64 SP2 security updates made in 2015 CAN be installed under Windows XP X64 SP2 as I have confirmed myself on a PC running XP Pro x64 edition.