Thanks Engel.
I found a workaround for it. Basically I had to remove windows imaging.
That's fine, but I had to edit an ini file to get imaging to show in add
remove programs.
"Engel" <> wrote in message
news:471610CB-D13C-4F4E-981B-...
> Hello David,
>
> See if this thread helps.
>
>
> <http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windowsupdate&p=1&tid=b8a04 8de-bde6-4dd1-add7-ed54b2d13ad7&mid=b8a048de-bde6-4dd1-add7-ed54b2d13ad7>
>
>
>
> I hope this post is helpful.
>
> Let us know how it works ºut
> -=-
>
> "David" wrote:
>
>> Does anyone know how to fix this error while trying to deploy KB923810?
>>
>> [KB923810.log]
>> 0.079:
>> ================================================== ==============================
>> 0.079: 2008/08/04 14:14:49.722 (local)
>> 0.079: c:\fef8545e5cf4bfc66ca0ba34665544\update\UPDATE.EX E (version
>> 6.2.29.0)
>> 0.079: Hotfix started with following command line:
>> 0.219: FileVersion of C:\WINNT\system32\oieng400.dll is Not Equal To
>> 5.0.2195.6601
>> 0.282: FileVersion of C:\WINNT\system32\oieng400.dll is Not Equal To
>> 5.00.2195.6770
>> 0.282: Condition Check for Line 1 of PreRequisite returned FALSE
>> 0.313: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
>> 0.313: KB923810 Setup encountered an error: Setup cannot continue
>> because
>> one or more prerequisites required to install KB923810 failed. For More
>> details check the Log File c:\winnt\KB923810.log
>> 0.391: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
>> 0.391: Setup cannot continue because one or more prerequisites required
>> to
>> install KB923810 failed. For More details check the Log File
>> c:\winnt\KB923810.log
>> 103.844: Message displayed to the user: Setup cannot continue because one
>> or
>> more prerequisites required to install KB923810 failed. For More details
>> check the Log File c:\winnt\KB923810.log
>> 103.844: User Input: OK
>> 103.844: Update.exe extended error code = 0xf0f4
>> 103.844: Update.exe return code was masked to 0x643 for MSI custom action
>> compliance.
>>
>>
>>
>>
>>
|