Hello, Trying to update Windows 7 with service pack 1 x64 (KB976932) on my notebook fails with error code 0x8000ffff. Digging into %windir%\Logs\CBS\CBS.log shows the error in detail: Error CBS SPI: (SPCompat::GetBIOSInformation:322)Model property of Win32_ComputerSystem class is not a string hr=0x8000ffff Error CBS SPI: (SPCompat::CheckBIOS:374)Failed to get BIOS information hr=0x8000ffff Error CBS SPI: (SPCompat::DriverScan:43)Failed checking BIOS hr=0x8000ffff Error CBS SPI: (CSPInstall::CompatibilityApplicabilityScan:1415)Failed to perform driver scan hr=0x8000ffff Info CBS SPI: Ending Compatibility\Applicability scan Error CBS SPI: (PerformSPInstallation:833)Failed to install SP using UI hr=0x8000ffff Error CBS SPI: (wmain:1105)Failed to perform SP installation hr=0x8000ffff Looking into Win32_ComputerSystem ( https://msdn.microsoft.com/en-us/library/aa394102(v=vs.85).aspx ) shows how the property Model is retrieved. I checked all the SMBIOS values with dmidecode. Here is an extract for type 1: Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Not Specified Product Name: Not Specified Version: 1.06A Serial Number: Not Specified UUID: Not Settable Wake-up Type: Power Switch SKU Number: N/A Family: A30 The needed values are not provided. I do not see a reason to abort the setup because of this. How can I force the setup to ignore these missing fields? Best regards.

Windows 7 SP1 Update failes with error code 0x8000ffff

Anonymous

Hello Aileen,

Because my issue was bound to my used BIOS I tried to perform the update after I put the HDD with Windows on into a different computer. That itself worked well after I fixed the incompatible driver issue with the Paragon Hard Disk Manager. I then tried to perform the SP1 update there and it installed everything. After a reboot, however, it found a failure and rolled the whole update back to square one. The error was:

2018-06-30 19:44:54, Info CBS SPI: Determining Version and Wave Values in SpInstall: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

2018-06-30 19:44:54, Info CBS SPI: Build number 6.1.1.17514

2018-06-30 19:44:54, Info CBS Session: 30675098_232432801 initialized by client SP Coordinater Engine.

2018-06-30 19:44:54, Info CBS SPI: Reviewing Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514. State: -19 Error: 0x80070005

After this I tried the following workarounds:

install: KB947821 v34
run: sfc /scannow
check the access rights for usbstor.inf and usbstor.PNF (SYSTEM and administrator have full access)
execute Reset Windows Update Agent steps 2, 5, 6, 7, 9, 11

I still get the same error message.

Digging a bit deeper into the CBS.log file I can see the following parts:

Old component: [l:0]""

New component: [ml:304{152},l:302{151}]"Microsoft-Windows-EOSNotify, Culture=neutral, Version=6.1.7600.18067, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"

Install mode: install

Installer ID: {386b5911-b69e-4d2d-a3ab-796d2ec6af38}

Installer name: [14]"Task Scheduler"

2018-06-30 19:15:37, Info CSI 00000675 Performing 1 operations; 1 are not lock/unlock and follow:

LockComponentPath (10): flags: 0 comp: {l:16 b:4139f0f69510d4010003000028016004} pathid: {l:16 b:4139f0f69510d4010103000028016004} path: [l:212{106}]"\SystemRoot\WinSxS\amd64_microsoft-windows-eosnotify_31bf3856ad364e35_6.1.7600.18067_none_41b0929ee4b7e75e" pid: 128 starttime: 131748523491469644 (0x01d410958664294c)

2018-06-30 19:15:38, Error CSI 00000014 (F) Logged @2018/6/30:17:15:37.969 : [ml:54{27},l:52{26}]"JobsHandler::Install enter"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000015 (F) Logged @2018/6/30:17:15:37.969 : [ml:70{35},l:68{34}]"JobsHandler::Install type=4 pass=4"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000016 (F) Logged @2018/6/30:17:15:37.969 : [ml:74{37},l:72{36}]"IsScheduleServiceRunning queries SCM"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000017 (F) Logged @2018/6/30:17:15:37.969 : [ml:76{38},l:74{37}]"IsScheduleServiceRunning returns true"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000018 (F) Logged @2018/6/30:17:15:37.969 : [ml:48{24},l:46{23}]"InstallTaskOnline enter"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000019 (F) Logged @2018/6/30:17:15:38.016 : [ml:100{50},l:98{49}]"InstallTaskOnline: RegisterTask failed 0x80070005"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001a (F) Logged @2018/6/30:17:15:38.016 : [ml:142{71},l:140{70}]"WmiCmiPlugin jobshandler.cpp(237): RegisterTask failed. HR=0x80070005."

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001b (F) Logged @2018/6/30:17:15:38.016 : [ml:116{58},l:114{57}]"WmiCmiPlugin plgutil.cpp(217): fnc failed. HR=0x80070005."

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001c (F) Logged @2018/6/30:17:15:38.016 : [ml:150{75},l:148{74}]"WmiCmiPlugin jobshandler.cpp(363): ForEachElementIn failed. HR=0x80070005."

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001d (F) Logged @2018/6/30:17:15:38.016 : [ml:174{87},l:172{86}]"WmiCmiPlugin jobshandler.cpp(676): InstallManifestSectionOnline failed. HR=0x80070005."

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001e@2018/6/30:17:15:38.156 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED)

[

[16]"Access denied

"

]

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 0000001f@2018/6/30:17:15:38.156 (F) CMIADAPTER: AI failed. HRESULT = HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED)

Element:

[2167]"<taskScheduler xmlns="urn:schemas-microsoft-com:asm.v3">

<URI>\Microsoft\Windows\Setup\EOSNotify</URI>

<Author>$(@%SystemRoot%\System32\EOSNotify.exe,-40000)</Author>

<Source>$(@%SystemRoot%\System32\EOSNotify.exe,-40001)</Source>

<Description>$(@%SystemRoot%\System32\EOSNotify.exe,-40002)</Description>

</RegistrationInfo>

<StateChange>SessionUnlock</StateChange>

</SessionStateChangeTrigger>

</LogonTrigger>

<StateChange>ConsoleConnect</StateChange>

</SessionStateChangeTrigger>

</Triggers>

<RunLevel>LeastPrivilege</RunLevel>

</Principal>

</Principals>

<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>

<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>

<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>

<StartWhenAvailable>false</StartWhenAvailable>

<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>

<StopOnIdleEnd>false</StopOnIdleEnd>

<RestartOnIdle>false</RestartOnIdle>

</IdleSettings>

<Hidden>false</Hidden>

<RunOnlyIfIdle>false</RunOnlyIfIdle>

<WakeToRun>false</WakeToRun>

<ExecutionTimeLimit>P3D</Exec[gle=0x80004005]

2018-06-30 19:15:38, Error CSI utionTimeLimit>

</Settings>

<Exec>

<Command>%windir%\system32\EOSNotify.exe</Command>

<WorkingDirectory>%windir%\system32</WorkingDirectory>

</Exec>

</Actions>

</Task>

</taskScheduler>"

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000676@2018/6/30:17:15:38.156 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(352): Error HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::ResolveAndInvokeInstaller expression: hr

[gle=0x80004005]

2018-06-30 19:15:38, Info CBS Progress: UI message updated. Operation type: Service Pack. Stage: 1 out of 1. Percent progress: 88.

2018-06-30 19:15:38, Error CSI 00000020@2018/6/30:17:15:38.687 (F) CMIADAPTER: Exiting with HRESULT code = HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED).

[gle=0x80004005]

2018-06-30 19:15:38, Error CSI 00000677@2018/6/30:17:15:38.687 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(123): Error HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::Install expression: hr

[gle=0x80004005]

2018-06-30 19:15:38, Info CSI 00000678@2018/6/30:17:15:38.765 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{386b5911-b69e-4d2d-a3ab-796d2ec6af38};Microsoft-Windows-EOSNotify, Version = 6.1.7600.18067, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;820418

2018-06-30 19:15:38, Info CSI 00000679 Performing 1 operations; 1 are not lock/unlock and follow:

LockComponentPath (10): flags: 0 comp: {l:16 b:cf006cf79510d4010203000028016004} pathid: {l:16 b:cf006cf79510d4010303000028016004} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.1.7600.16385_none_3868158f24725705" pid: 128 starttime: 131748523491469644 (0x01d410958664294c)

2018-06-30 19:15:38, Error [0x018003] CSI 0000067a (F) Failed execution of queue item Installer: Task Scheduler ({386b5911-b69e-4d2d-a3ab-796d2ec6af38}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]

2018-06-30 19:15:38, Info CSI 0000067b Creating NT transaction (seq 1), objectname [6]"(null)"

2018-06-30 19:15:38, Info CSI 0000067c Created NT transaction (seq 1) result 0x00000000, handle @0xc24

2018-06-30 19:15:39, Info CSI 0000067d@2018/6/30:17:15:39.373 CSI perf trace:

CSIPERF:TXCOMMIT;481511

2018-06-30 19:15:39, Info CSI 0000067e End executing advanced installer (sequence 1041)

Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

Any solution for this issue?

0 comments

Anonymous

Thank you for the update. These troubleshooting steps are supposed to address multiple possible causes of the error. Since the issue persists, we have to sort to more advanced troubleshooting.

Usually, issues with Windows Update occur when related services stop running, when there's a problem with the update cache, or when the required components are corrupted. In these situations, you can reset the Windows Update on Windows 7 to resolve most problems. You can download and run the script that resets the Windows Update components here.

Please note that serious problems might occur if you modify the registry incorrectly. It is highly recommended that you back up the registry for restoration in case problems occur. The steps on how to back up the registry can be found here.

Let me know how it turns out.

0 comments

Anonymous

Hi Aileen,

I performed a complete system scan for virus infections, updated my BIOS and drivers to the newest available versions and did the System File Checker run. I also updated the local date time via the internet time server time.windows.com. All tasks completed successfully. I then tried to install the Windows 7 SP1 Update again. Exactly the same issue that I had originally occurred. I can also not see how these workarounds relate to my issue. Nevertheless, is there anything else I can do to make this update ignore my missing SMBIOS fields?

Best regards.

0 comments

Anonymous

Here's what happens with one of your suggestions:

What happens when you follow your own suggestions on your Windows 7 system?

0 comments

Anonymous

Hi YaseenAli1,

May I know if you're experiencing the same issue? Have you tried the solutions provided above?

Let me know if you need further assistance.

0 comments

Share via

Windows 7 SP1 Update failes with error code 0x8000ffff

12 answers