It appears that the detection methods used in .APM files may not be able to cope with this type of issue.
KB3068368-x64-ENU.apm calls WindowsServer2003-KB3068368-x64-ENU.exe whose job it is to update C:\WINDOWS\system32\vbscript.dll.
The WindowsServer2003-KB3068368-x64-ENU.exe update fails with the following information detailed in the KB3068368.log file.
0.437: Hotfix started with following command line: /quiet /norestart
0.437: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.437: C:\WINDOWS\system32\vbscript.dll is Present
0.484: FileVersion of C:\WINDOWS\system32\vbscript.dll is Greater or Equal To 184.108.40.206
0.484: FileVersion of C:\WINDOWS\system32\vbscript.dll is Greater or Equal To 220.127.116.11
0.484: Second Condition in Vbscriptdll.AndOp.Section Failed
0.484: Condition Check for Line 1 of PreRequisite returned FALSE
0.484: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
0.484: KB3068368 Setup encountered an error: Setup cannot continue because one or more prerequisites required to install KB3068368 failed. For More details check the Log File c:\windows\KB3068368.log
If you extract the WindowsServer2003-KB3068368-x64-ENU.exe update and check the update_SP2QFE.inf for the above mentioned PreRequisite one will find:
GreatOrEqualOp=CheckFilever, Vbscript.Files, vbscript.dll,">=",18.104.22.168
LessOp=CheckFilever, Vbscript.Files, vbscript.dll,"<",22.214.171.124
The version of my vbscript.dll file is 5.8.6001.23707 hence, it fails the "LessOp=CheckFilever, Vbscript.Files, vbscript.dll,"<",126.96.36.199" portion of the PreRequisite test and the "WindowsServer2003-KB3068368-x64-ENU.exe" will never install.
I have not looked at all that many .APM files. Is there a method to directly check a files version to avoid this type of vicious circle?
Windows XP Releases Both (x86) And (x64)
1 post • Page 1 of 1
Who is online
Users browsing this forum: Google Adsense [Bot] and 4 guests