Compartir a través de

Update is not applicable to your computer- but it is

  • Artículo

I encounter a rather weird issue with this error message, when trying to install an update: Update is not applicable to your computer, although it was.

Apparently this can also appear, because of the TrustedInstaller. To see if you are affected, view the CBS.log, you`ll see a lot of entries like:

, Info                  CBS    Failed to get Transaction State for package: Microsoft-Windows-DirectoryServices-DomainController-Tools-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, update: DirectoryServices-DomainController-Tools [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
, Error                 CBS    Failed to get store state [HRESULT = , ,- ERROR_FAIL_REBOOT_REQUIRED]

So there is an issue here that the TrustedInstaller service changes the default service startup type of Manual (3) to Automatic (2), when it encounters an update that has to process a transaction after a restart.   When the value is set back to Manual before the restart the transaction that has to be applied after restart cannot be applied.  This transaction will be pended. It will block all other update installations that might come up.

You can check following key to see if you are affected, it should be 3: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TrustedInstaller\Start

Resolution:

Start the TrustedInstaller service

Reboot the machine

You should be able now to install updates

Comments

  • Anonymous
    October 23, 2014
    Susan Bradley pointed me here (Thanks!) - now I'm in the "ballpark", I think...

    Symptoms same as described here, but the regedit shows the setting is -correct- yet I get the dreaded "Update is not applicable to your computer...", yet it is a Win7HomePremium system, and I compared the settings with a Win7Pro system onsite and they seem the same, yet I get the dreaded 'Update is not applicable to your computer...' msg only on the Win7HomeP system. Any tips you can share about this conundrum would be much appreciated.

    Regards,

    pc.tech3@verizon.net
    .
  • Anonymous
    September 19, 2017
    Great article!For us, this issue occurred on a Windows 2012 R2 server. Two items to assist in narrowing down.1. To validate the issue exists, use this PowerShell. (Get-Content -Path $env:WINDIR\Logs\CBS\CBS.log -Tail 1000 | ? {$_ -match "ERROR_FAIL_REBOOT_REQUIRED"} | Select-Object -Last 1)2. The resolution states to reboot the computer. For us, it took several reboots waiting about 15 minutes in-between.