KB2919355 (Windows 8.1 Update) Fails (800f0092 and 80073712) on Windows 8.1 Pro w Media Center

Anonymous
2014-04-05T00:19:46+00:00

I am running Windows 8.1 Pro with Media Center. It is a 64-bit edition.

I downloaded the Windows 8.1 Update from MSDN. Installed it on two machines with no problems.

Update is a series of 6 updates packed in a single zip file. Unzipped the files. Went to install the first recommended update (KB2919442). Dialog box indicated it was already installed.

Went to install the second update (KB2919355). It ran through the dialogs and said installation completed. It indicated that a reboot was necessary. Rebooted. It began to install the update after the reboot. Got about 60% of the way through, then said it couldn't complete. Error message 800F0092.

Had successfully installed on two other machines, one a VM and one a Samsung tablet. Only difference is this computer is 1) Media Center, and 2) was running WebRoot antimalware agent.

Uninstalled WebRoot.

Retried the install. Got about 98% through the dialog (green progress bar almost at 100%), went it stopped and the dialog said Update Failed.

Error message in the update history is now 80073712.

Windows for home | Previous Windows versions | Install and upgrade

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-05-14T20:02:09+00:00

Hello all,

We wanted to take a moment to thank you for coming to the Microsoft Community to get the answers you need tosuccessfully install the Windows 8.1 Update.

We have published guidance for troubleshooting some known problems at*Install the latest Windows 8.1 Update*.

In order to give your questions the attention they deserve, we are opening new threads that will focus on solving each error individually:

If you are receiving the error ‘We couldn’t complete the updates, Undoing changes. Don’t turn off your computer’ please post to this thread foundhere

If you are receiving Error 0x800F0922 when installing KB 2919355 please posthere

If you are receiving Error 0x800F0923 when installing KB 2919355 please posthere

If you are receiving Error 0x80070003 when installing KB 2919355 please posthere

If you are receiving Error 0x80070005 when installing KB 2919355 please posthere

If you are receiving Error 0x80070490 when installing KB 2919355 please posthere

If you are receiving Error 0x80073712 when installing KB 2919355 please posthere

If you are having an issue not mentioned above, please*start a new thread*so that we can investigate your issue.

In order to keep these threads productive and prevent fellow customer’s questions from being lost we ask that you please keep any posts made to these threads on topic and constructive.

We are going to go ahead and lock this thread to prevent questions being posted in the wrong area and not getting the attention they deserve.

Thank you for your understanding

Was this answer helpful?

60+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2014-04-17T17:17:17+00:00

Please note that's 64bit only

To make that work on 32bit do:

Also note AMD does not mean this only works on AMD chipsets.  AMD invented the 64bit platform, so even if you are running 64bit intel, that amd64 notation is still valid.

sfc /scannow

DISM /online /get-packages /format:table | findstr KB2919355

DISM /online /remove-dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

DISM /online /cleanup-image /startcomponentcleanup /resetbase

cleanmgr.exe

@echo off

Echo Cleanup complete

pause

Was this answer helpful?

50+ people found this answer helpful.
0 comments

1,164 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-04-12T18:54:43+00:00

    Took an agonizing 2 days, but I just decided to go with a complete rebuild ( 8.1 pro install over the top).  Interesting (& nerve wracking) that shortly after the re-install, WU offerred up KB2919355 again.  I crossed fingers and chose to accept and it did look to take. S o in the end now all is well, but many hours and a lot of frustration!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-04-12T18:54:18+00:00

    Reporting success!

    After many attempts...

    In elevated command prompt:

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

    dism /online /cleanup-image /startcomponentcleanup

    shutdown /r /t 0

    After restart start:

    Windows8.1-KB2919355-x64.msu

    (before downloaded MS offline file)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-12T18:53:49+00:00

    Unfortunately this didn't work for me. I've tried it multiple times. Everything I've found doesn't work. Here's where I am at this point:

    My latest error after trying this resolution is error 80243003

    Seems to be:

    0x80243003

    WU_E_INSTALLATION_RESULTS_NOT_FOUND

    The results of download and installation are not available; the operation may have failed to start.

    I've tried pretty much everything I can think of.

    EDIT: Tried again with the standalone installer for this KB, received error 0x8024001e, seems to be:

    0x80240001

    WU_E_NO_SERVICE

    Windows Update Agent was unable to provide the service.

    I've also noticed that if I look in task manager:

    "Windows Modules Installer Worker" (TiWorker.exe) consumes CPU time for the entire duration of either a standalone installation or Windows Update (Whether through charms or the desktop version), and then also for quite some time after installation appears to either be done or error out.

    There's also this in the setup event log:

    • <eventdata>

    <data name="UpdateTitle"/> 

    <data name="ErrorCode">2149842974</data> 

    <data name="ErrorString"/> 

    <data name="CommandLine">"C:\WINDOWS\system32\wusa.exe" "C:\Users\USERNAME\Downloads\wu\Windows8.1-KB2919355-x64.msu"</data> 

    </eventdata>

    I'm wondering if there's some queue'd updates causing blocking of this update and it's just timing out.

    I also tried executing the WindowsUpdateDiagnostic.digicab and I get different output every time I run it.

    I've also tried all sorts of cleanup operations with DISM, those have not helped either.

    I'm digging through the CBS logs at the moment I'll update if I can deduce the root cause.

    EDIT: Even more.. after a lengthy cleanup operation trying everything under the sun.. here's some CBS.log interestingness..

    I see alot of these in the log for a few different packages:

    2014-04-12 14:04:59, Info CBS Opened cabinet package, package directory: \?\C:\WINDOWS\SoftwareDistribution\Download\bd52625e6765fc57111b95b0a324f53c, sandbox location: \?\C:\WINDOWS\SoftwareDistribution\Download\bd52625e6765fc57111b95b0a324f53c, cabinet location: \?\C:\WINDOWS\SoftwareDistribution\Download\bd52625e6765fc57111b95b0a324f53c\windows8.1-kb2937592-x64-express.cab, manifest location: \?\C:\WINDOWS\SoftwareDistribution\Download\bd52625e6765fc57111b95b0a324f53c\update.mum

    2014-04-12 14:04:59, Info DPX Started DPX phase: Resume and Download Job

    2014-04-12 14:04:59, Info DPX Started DPX phase: Apply Deltas Provided In File

    2014-04-12 14:04:59, Info DPX Ended DPX phase: Apply Deltas Provided In File

    2014-04-12 14:04:59, Info DPX CJob::Resume completed with status: 0x0

    2014-04-12 14:04:59, Info DPX Ended DPX phase: Resume and Download Job

    2014-04-12 14:04:59, Info DPX Extraction of file: update.ses failed because it is not present in the container.

    2014-04-12 14:04:59, Info DPX DpxException hr=0x80070002 code=0x020109

    2014-04-12 14:04:59, Info CBS Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-04-12 14:04:59, Info DPX Started DPX phase: Resume and Download Job

    2014-04-12 14:04:59, Info DPX Started DPX phase: Apply Deltas Provided In File

    2014-04-12 14:04:59, Info DPX Ended DPX phase: Apply Deltas Provided In File

    2014-04-12 14:04:59, Info DPX CJob::Resume completed with status: 0x0

    2014-04-12 14:04:59, Info DPX Ended DPX phase: Resume and Download Job

    Here's another one.. there's 5 total, I assume these are the 5 pacakges for this update..

    2014-04-12 14:05:47, Info CBS Opened cabinet package, package directory: \?\C:\WINDOWS\SoftwareDistribution\Download\ce6867754a6099c14441db30189b7459, sandbox location: \?\C:\WINDOWS\SoftwareDistribution\Download\ce6867754a6099c14441db30189b7459, cabinet location: \?\C:\WINDOWS\SoftwareDistribution\Download\ce6867754a6099c14441db30189b7459\windows8.1-kb2919355-x64-express.cab, manifest location: \?\C:\WINDOWS\SoftwareDistribution\Download\ce6867754a6099c14441db30189b7459\update.mum

    2014-04-12 14:05:47, Info DPX Started DPX phase: Resume and Download Job

    2014-04-12 14:05:47, Info DPX Started DPX phase: Apply Deltas Provided In File

    2014-04-12 14:05:48, Info DPX Ended DPX phase: Apply Deltas Provided In File

    2014-04-12 14:05:48, Info DPX CJob::Resume completed with status: 0x0

    2014-04-12 14:05:48, Info DPX Ended DPX phase: Resume and Download Job

    2014-04-12 14:05:48, Info DPX Extraction of file: update.ses failed because it is not present in the container.

    2014-04-12 14:05:48, Info DPX DpxException hr=0x80070002 code=0x020109

    2014-04-12 14:05:48, Info CBS Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-04-12 14:05:48, Info DPX Started DPX phase: Resume and Download Job

    2014-04-12 14:05:48, Info DPX Started DPX phase: Apply Deltas Provided In File

    2014-04-12 14:05:48, Info DPX Ended DPX phase: Apply Deltas Provided In File

    2014-04-12 14:05:48, Info DPX CJob::Resume completed with status: 0x0

    2014-04-12 14:05:48, Info DPX Ended DPX phase: Resume and Download Job

    .... then a little later....

    014-04-12 14:09:01, Info CBS Exec: This is a PSF Package. Job has been saved and we are returning to client.

    2014-04-12 14:09:01, Info CSI 0000069b@2014/4/12:18:09:01.382 CSI Transaction @0xac222a1460 destroyed

    2014-04-12 14:09:01, Info CBS Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.

    2014-04-12 14:09:01, Info CBS CommitPackagesState: Started persisting state of packages

    2014-04-12 14:09:01, Info CBS CommitPackagesState: Completed persisting state of packages

    2014-04-12 14:09:01, Info CSI 0000069c@2014/4/12:18:09:01.423 CSI Transaction @0xac222a01d0 destroyed

    2014-04-12 14:09:01, Info CBS Perf: Stage chain complete.

    2014-04-12 14:09:01, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    2014-04-12 14:09:01, Info CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    2014-04-12 14:09:01, Info CBS WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    2014-04-12 14:09:01, Info CBS Reboot mark cleared

    2014-04-12 14:09:01, Info CBS Winlogon: Deregistering for CreateSession notifications

    2014-04-12 14:09:01, Info CBS Winlogon: Stopping notify server

    2014-04-12 14:09:01, Info CBS Winlogon: Unloading SysNotify DLL

    2014-04-12 14:09:01, Info CBS FinalCommitPackagesState: Started persisting state of packages

    2014-04-12 14:09:01, Info CBS FinalCommitPackagesState: Completed persisting state of packages

    2014-04-12 14:09:01, Info CBS Enabling LKG boot option

    2014-04-12 14:09:01, Info CBS Exec: Processing complete. Session: 30365305_3552269961, Package: Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    2014-04-12 14:11:07, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

    EDIT:

    The part that is very interesting is that starting up the Desktop version of WU and checking for updates, it freezes for quite some time, never noticed this happening until the original failed update of the ~800M cumulative package. When I try to download the available update, it sits there like it's going to download then switches back to the "available updates" view and says there are no available updates. Meanwhile, the Windows Modules Installer Worker(TiWorker.exe) is churning away in the background.Eventually the WU UI switches to the fact that 1 update is available again..TiWorker.exe still churning away...

    Was this answer helpful?

    0 comments