Share via

Windows 8.1 update fails to install - KB2919355

Anonymous
2014-04-17T17:26:28+00:00

On several occasions the update KB2919355 has failed to install with error code 80073712 on my computer. I have an HP envy with touch support, which came with Windows 8 64-bit preinstalled.  Latest updates (including 8.1) have been applied. The machine has issues with the fingerprint reader not working on occasion as well as blurry text in some windows despite a 1920x1080 display, but I don't see how that is related.

I have tried the following:

  1. DISM.exe
  1. created a .bat file with the lines

%windir%\system32\Dism.exe /Online /Cleanup-Image /ScanHealth

%windir%\system32\Dism.exe /Online /Cleanup-Image /CheckHealth

%windir%\system32\Dism.exe /Online /Cleanup-Image /RestoreHealth

in it and 2. ran it as an administrator. ScanHealth reports that the component store is repairable. CheckHealth reports the same. However, RestoreHealth is stuck at 40% after 12 hours. I terminated the process. The log file in C:\WINDOWS\LOGS\DISM is a garbled mess with Chinese characters. 3. I read here on this forum that I should run Microsoft's safety scanner, which I did. It reports no problems.

  1. Another attempt:
  1. Created a batch script (from another thread here) with the lines

net stop wuauserv

cd %systemroot%\SoftwareDistribution

ren Download Download.old

net start wuauserv

net stop bits

net start bits

net stop cryptsvc

cd %systemroot%\system32

ren catroot2 catroot2old

net start cryptsvc

in it and 2. ran it is admin. It runs successfully, but the error is the same (80073712)

  1. Ran the windows troubleshooter from Windows help and it reports the following:

Problems installing recent updates (not fixed)

Check for missing or corrupt files (detected) [SFC Output, Windows Resource Protection could not start the repair service]

Some security settings are missing or have been changed (fixed)

Service registration is missing or corrupt (fixed)

  1. Followed the instructions given here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/kb2919355-windows-81-update-fails-800f0092-and/4d4d23a3-695a-4bd4-b340-d2ce9c75919d
  1. Opened command prompt with as admin
  2. Executed:

dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

This reports that it's removing the package and gets to 100% quickly and then sits there for a while before finishing successfully. 3. Executed:

DISM.exe /Online /Cleanup-image /Restorehealth

This again gets to 20% within seconds, makes it up to 40% after a half hour and does nothing afterwards. Should I let this tool run for multiple days to see if it creeps up to 60%?

I am out of ideas. I would rather not refresh my PC at this point. Are there any other solutions?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2014-04-22T13:19:32+00:00

This was posted in a separate thread i followed these instructions and got a new error "

Error code 0x800f0902 " (see end for fix to this code)

Following several unsuccessful attempts to install the Windows 8.1 Update for x64-based Systems (KB2919355), each of which produced error code 80070002, the following sequence succeeded on my Windows 8.1 Pro (x64) PC.

  1. Verify that Windows Update KB2919442 is installed by examining Control Panel\System and Security\Windows Update\View update history and, if not, download and install it (http://www.microsoft.com/en-us/download/details.aspx?id=42162)
  2. Download the Windows 8.1 Update for x64-based Systems (KB2919355, published 4/16/2014) (http://www.microsoft.com/en-us/download/details.aspx?id=42335), including all six files:

     Windows8.1-KB2919355-x64.msu

     Windows8.1-KB2932046-x64.msu

     Windows8.1-KB2934018-x64.msu

     Windows8.1-KB2937592-x64.msu

     Windows8.1-KB2938439-x64.msu

     Windows8.1-KB2959977-x64.msu

  1. If it does not already exist, add an empty System Tools folder to C:\ProgramData\Microsoft\Windows\Start Menu\Programs
  2. Run the following command with administrative privileges:

     dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14

  1. Reboot PC
  2. Run the following two commands with administrative privileges:

dism /Online /Cleanup-image /Restorehealth

dism /online /cleanup-image /startcomponentcleanup

  1. Run the Microsoft Fixit tool for Windows Update (http://support.microsoft.com/kb/971058)
  2. Select and run “Cleanup system files” by using the Disk
  3. Reboot PC
  4. Temporarily disable anti-virus software while executing the following step
  5. Manually install the updates (downloaded in step 2) in the following order:

     KB2919355

     KB2932046

     KB2959977

     KB2937592

     KB2938439

     KB2934018

Thank you to all the prior contributors to this thread, from whom the above amalgamated sequence was developed.

At the point of running KB2919355 i got a new error 0x800f0902

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TrustedInstaller

Check and see if start is set to manual or automatic this article explains it 3 = manual, 2=auto (it cannot be changed through registry)

http://support.microsoft.com/kb/968440

start the service mentioned in the article to and change to automatic and the manual update instals with a reboot notification. I hope this is the end of my troubles I am about to reboot and check it out.

Was this answer helpful?

40+ people found this answer helpful.
0 comments

75 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-04-26T17:39:41+00:00

    I'm also having trouble installing this update KB2919355. 

    CBS.Log shows this section:

    2014-04-26 17:31:11, Info                  CSI    0000064f Regenerating payload files from delta files on component: [ml:280{140},l:202{101}]"amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.17031_en-gb_68408c0dc1958b90"

    2014-04-26 17:31:11, Error                 CSI    00000650 (F) Delta file missing on generating delta for: [l:32{16}]"bootmgfw.efi.mui"[gle=0x80004005]

    2014-04-26 17:31:11, Error                 CSI    00000651 (F) STATUS_ACCESS_DENIED #7422258# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysSetInformationFile(flags = 0, h = 1308 ("\Device\HarddiskVolume4\Windows\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.16384_en-gb_680d99c9c1bb411e*bootmgr.efi.mui*"), iosb = @0x947a1ad728, buff = @0x940eb78a70, bufflen = 296 (0x00000128), ic = 11 (0x0000000b), disp = Invalid)

    [gle=0xd0000022]

    2014-04-26 17:31:11, Error                 CSI    00000652@2014/4/26:15:31:11.890 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2643): Error STATUS_ACCESS_DENIED originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysSetInformationFile expression: (null)

    [gle=0x80004005]

    2014-04-26 17:31:11, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140426152113.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140426144502.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140423191209.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140423185541.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20140423183343.log to WER report.

    2014-04-26 17:31:12, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-04-26 17:31:12, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-04-26 17:31:12, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-04-26 17:31:16, Error                 CSI    00000653 (F) STATUS_ACCESS_DENIED #7422251# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (ReplaceIfExists|OpenForBackupIntent), op = [8]"HardLink", odir = @0x9410b43ff8, oname = [l:30{15}]"bootmgr.efi.mui", ndir = @0x9410b459d8, nname = [l:30{15}]"bootmgr.efi.mui", disp = (null))

    [gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    00000654 (F) STATUS_ACCESS_DENIED #7422155# from CFileInstaller::DoComponentOperation(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    00000655 (F) STATUS_ACCESS_DENIED #7422080# from CFileInstaller::ProcessComponentChange(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    00000656 (F) STATUS_ACCESS_DENIED #7422079# from PrimitiveInstaller::CCoordinator::ProcessChange(Change 6.3.9600.16384 -> 6.3.9600.17031 for Microsoft-Windows-BootEnvironment-Core-BootManager-EFI.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0xd0000022]

    2014-04-26 17:31:16, Info                  CSI    000002dc SMI Primitive Installer [done]

    2014-04-26 17:31:16, Error                 CSI    00000657 (F) STATUS_ACCESS_DENIED #6060670# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    00000658 (F) STATUS_ACCESS_DENIED #6060669# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    00000659 (F) STATUS_ACCESS_DENIED #6060668# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    0000065a (F) STATUS_ACCESS_DENIED #6060667# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0000022]

    2014-04-26 17:31:16, Error                 CSI    0000065b (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #2222359# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80070005]

    2014-04-26 17:31:17, Error                 CSI    0000065c (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #2085663# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80070005]

    2014-04-26 17:31:17, Error                 CSI    0000065d (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #2085662# 97100997 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)

    [gle=0x80070005]

    Found this using ProcessMon:

    Date & Time: 2014-04-26 05:30:50 PM

    Event Class: File System

    Operation: SetLinkInformationFile

    Result: ACCESS DENIED

    Path: C:\Windows\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.16384_en-gb_680d99c9c1bb411e\bootmgr.efi.mui

    TID: 3056

    Duration: 0.0000421

    ReplaceIfExists: True

    FileName: \SystemRoot\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.17031_en-gb_68408c0dc1958b90\bootmgr.efi.mui

    Process details:

    Description: Windows Modules Installer Worker

    Company: Microsoft Corporation

    Name: TiWorker.exe

    Version: 6.3.9600.17031 (winblue_gdr.140221-1952)

    Path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17031_none_fa50b3979b1bcb4a\TiWorker.exe

    Command Line: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17031_none_fa50b3979b1bcb4a\TiWorker.exe -Embedding

    PID: 3316

    Parent PID: 672

    Session ID: 0

    User: NT AUTHORITY\SYSTEM

    Auth ID: 00000000:000003e7

    Architecture: 64-bit

    Virtualized: False

    Integrity: System

    Started: 2014-04-26 05:21:13 PM

    Ended: (Running)

    Having a look at the bootmgr.efi.mui files, SYSTEM user (as which above TiWorker.exe seems to run) only has Read & Execute and Read access on them, could this be the issue?

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2014-04-24T21:01:30+00:00

    Solution****for Windows 8.1 64-bit (not Pro) on – HP Pavilion 15-n066us.

    I manually downloaded and attempted to install the Windows 8.1 64-bit Update (KB2919355):

    http://www.microsoft.com/en-us/download/details.aspx?id=42327

    The installation failed.

    I have “Install Updates Automatically” on my computer so I chose to "update and restart" on the power option.

    The update failed.

    I then went back and attempted the update using the manual download and successfully updated the first part of Windows 8.1 Update (KB2919355) on my computer and was prompted to restart the computer.

    After 2nd restart, when I returned to my desktop, the Microsoft Store icon was placed on my task bar.

    I checked the "Windows Update" window again and there was 196MB left to Update. The “Install” button was clicked on and the Windows Update ran successfully to a “Restart Now” button.

    After 3rd restart, I checked the Windows Update again and 2 updates were listed (KB2933809 & KB2957390) which were installed quickly and the “Restart Now” button was available & chosen.

    After the 4th restart, I checked the Windows Update and there were no Windows updates available.

    Thanks,

    Kenner L

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more