Problema aggiornamento KB2686509 (0x8007f0f4)

 

In alcune circostanze può capitare che l’aggiornamento della sicurezza 2686509 non venga installato generando un errore 0x8007f0f4.

Se utilizzate Windows Update otterrete un errore del tipo:

image

mentre eseguendo l’installazione a mano l’errore sarà:

image

Andando ad esaminare il file di log c:\windows\KB2686509.log:

0.781: 2012/07/24 11:33:04.675 (local)
0.781: c:\474d144fade63494a280e12a8ba65d2d\update\update.exe (version 6.3.4.1)
0.797: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f
0.812: Hotfix started with following command line:
0.812: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.828: CreateUserInterface:  GetProcAddress for DefineInstallCustomUI failed:  0x7f
1.140: Return Value From IsMachineSafe = 0
1.140: IsMachineSafe returned 441092
1.140: Fist Condition in Prereq.IsMachineSafe.Section Failed
1.140: Condition Check for Line 1 of PreRequisite returned FALSE
1.156: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
1.156: KB2686509 Setup encountered an error:  Setup cannot continue because one or more prerequisites required to install KB2686509 failed. For More details check the Log File c:\windows\KB2686509.log
1.156: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
1.156: Setup cannot continue because one or more prerequisites required to install KB2686509 failed. For More details check the Log File c:\windows\KB2686509.log

possiamo notare un problema con i prerequisiti per l’installazione dell’aggiornamento.

Nella directory c:\windows dovreste avere il file faultykeyboard.log, all’interno del quale ci sono i file mancanti nella directory c:\windows\system32:

kbd101.dll
kbdkor.dll

Se avete altre macchine con lo stesso sistema operativo potete provare a copiarle oppure potete scaricarle da uno dei tanti siti tipo http://www.dll-files-download.com/.

Una volta che tutti i file necessari saranno stati copiati lanciate di nuovo l’installazione e questa volta il file di log dovrebbere contenere:

0.844: 2012/07/24 12:37:20.599 (local)
0.844: c:\a7efbdf2524089ab3086fca3e13e31a3\update\update.exe (version 6.3.4.1)
0.859: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f
0.859: Hotfix started with following command line:
0.859: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.859: CreateUserInterface:  GetProcAddress for DefineInstallCustomUI failed:  0x7f
0.984: Return Value From IsMachineSafe = 1
0.984: IsMachineSafe returned 441092
1.016: Return Value From IsMachineSafe = 1
1.016: IsMachineSafe returned value( 0x1 ) which is Equal To 0x1
1.016: Condition succeeded for section Prereq.IsMachineSafe.Section in Line 1 of PreRequisite

3.141: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed with error 0x2
3.141: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed with error 0x2
3.141: DoInstallation: CleanPFR failed: 0x2
3.141: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
3.156: SetProductTypes: InfProductBuildType=BuildType.IS
3.156: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.250: DoInstallation: FetchSourceURL for c:\a7efbdf2524089ab3086fca3e13e31a3\update\update_SP2GDR.inf failed
3.250: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
3.266: BuildCabinetManifest: update.url absent
3.266: Starting AnalyzeComponents
3.266: AnalyzePhaseZero used 0 ticks
3.281: OEM file scan used 0 ticks
3.281: AnalyzePhaseOne: used 15 ticks
3.281: AnalyzeComponents: Hotpatch analysis disabled; skipping.
3.281: AnalyzeComponents: Hotpatching is disabled.
3.281: FindFirstFile c:\windows\$hf_mig$\*.*
9.031: AnalyzeForBranching used 0 ticks.
9.047: AnalyzePhaseTwo used 16 ticks
9.047: AnalyzePhaseThree used 0 ticks
9.047: AnalyzePhaseFive used 0 ticks
9.047: AnalyzePhaseSix used 0 ticks

e dovrebbe apparire la schermata corretta:

image

 

Maggiori dettagli sono disponibili nella pagina della KB http://support.microsoft.com/kb/2686509.

Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *