Windows 7 x64 - Error 0x8000FFFF while installing updates

TheNozomi

Member
Joined
Aug 22, 2018
Posts
5
Hello everyone,

I'm currently unable to install two updates. Seeking for any advice.

The updates in question are:


  • 2018-07 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4338818)
  • Windows Management Framework 5.1 (KB3191566)

Both updates fail to install with error code 0x8000FFFF. For the Monthly Rollup, tried installing via the control panel and a standalone .msu installer, giving the same error.

Operating system information


  • Windows 7 SP1 (version 6.1.7601) 64-bit
  • Version 6.1.7601


Steps tried to solve the problem


  • Ran sfc /scannow. No corrupted files detected
  • Ran SURT. No errors detected
  • Renamed SoftwareDistribution and catroot2 folders as stated by this Microsoft article, the Windows Update database was regenerated but the error persists.
  • Ran the SFCFix tool and didn't detect any corruptions.

Log files

CheckSUR log:
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-08-22 20:27


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 2828
 No errors detected


SFCFix log:
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-08-22 23:22:40.466
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.






Failed to generate a complete zip file. Upload aborted.




SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-08-22 23:47:52.874
----------------------EOF-----------------------


Relevant entries on WindowsUpdate.log:
Code:
2018-08-22    21:48:11:626    5156    cc8    Handler    :::::::::::::
2018-08-22    21:48:11:687    5156    cc8    Handler    :: START ::  Handler: CBS Install
2018-08-22    21:48:11:726    5156    cc8    Handler    :::::::::
2018-08-22    21:48:11:878    5156    cc8    Handler    Starting install of CBS update C05F0AEA-8F8F-4EA3-A247-433C3B681C72
2018-08-22    21:48:12:281    5156    cc8    Handler    CBS package identity: Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.3.7601.16384
2018-08-22    21:48:12:665    5156    cc8    Handler    Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\8460062166f4d27e0b98e704f8682603\Windows6.1-KB3191566-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\8460062166f4d27e0b98e704f8682603\inst
2018-08-22    21:48:13:839    1072    1568    Report    REPORT EVENT: {29F18338-9AE5-49BF-AD78-9873D7A04F73}    2018-08-22 21:48:08:817-0300    1    181    101    {FFBF75AD-7C02-433B-9D69-649EFB9E93A9}    501    0    wusa    Success    Content Install    Installation Started: Windows successfully started the following update: Update for Windows (KB3191566)
2018-08-22    22:03:55:180    5156    7a0    Handler    FATAL: CBS called Error with 0x8000ffff, 
2018-08-22    22:06:16:028    5156    cc8    Handler    FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8000ffff
2018-08-22    22:06:17:354    5156    cc8    Handler    :::::::::
2018-08-22    22:06:17:355    5156    cc8    Handler    ::  END  ::  Handler: CBS Install
2018-08-22    22:06:17:355    5156    cc8    Handler    :::::::::::::

Relevant entries on CBS.log:
Code:
2018-08-22 22:01:22, Error                 CSI    00000013 (F) Assembly installed and uninstalled with same reference in single transaction (id = @0x16fc170, guid = {d16d444c-56d8-11d5-882d-0080c847b195}, ref = [82]"Package_235_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5.4343900-1126_neutral_LDR")
[gle=0x80004005]
2018-08-22 22:01:22, Error                 CSI    00000014@2018/8/23:01:01:22.378 (F) d:\win7sp1_gdr\base\wcp\servicingapi\assembly.cpp(572): Error E_UNEXPECTED originated in function Windows::ServicingAPI::CAssembly::AddUninstall expression: ((HRESULT)0x8000FFFFL)
[gle=0x80004005]
2018-08-22 22:03:42, Error                 CSI    00000015 (F) E_UNEXPECTED #1250392# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_UninstallDeployment(Flags = 0, a = ebdf901b67189fc9e28c6a5cb1194e2f, Version = 11.2.9600.19100, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [82]"Package_235_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5.4343900-1126_neutral_LDR", disp = 0)[gle=0x8000ffff]
2018-08-22 22:03:42, Info                  CBS    Failed to begin deployment uninstallation for Update: 4343900-1126_neutral_LDR [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    Failed to execute item[0] in Package: Package_235_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5, Update: 4343900-1126_neutral_LDR [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    Failed to execute execution update. [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    Failed to execute execution package: Package_235_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5 [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    Failed to prepare execution. [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    Failed to process component watch list. [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CSI    00000016@2018/8/23:01:03:42.529 CSI Transaction @0xd89dd70 destroyed
2018-08-22 22:03:42, Info                  CBS    Perf: InstallUninstallChain complete.
2018-08-22 22:03:42, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x8000ffff - Unknown Error]
2018-08-22 22:03:42, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.3.7601.16384, status: 0x8000ffff, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent

The full WindowsUpdate.log and CBS.log are attached.

Any help would be greatly appreciated.

Thanks in advance!
 

Attachments

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
Tried to install the update on clean boot with no luck, checked the CBS log and it shows the same error.
 
Please always attach the logs I request regardless of the fact that the error may be the same or not. Do the following again, but enable ProcMon 30 seconds or one minute prior to failure:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top