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

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)

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...

I ment no disrespect... If you think I did I appologize!

If you look through the threads (this and others) the problem is however this is executed for many of us the 355 still won´t install. Neither before or after a "rollback" before 8th of april or before trying to attempt the Windows Update. It´s kind of the common nominator for everyone who´s just stuck.

I even made a clean install this week. I Removed all partitions on my HD, made a totally new install from my OEM-discs, provided by Packard Bell. Ran trough Windows Update to install all present updates, went to Store and upgraded to 8.1. Then again Windows Update to install remaining updates... and I got stuck on our beloved 355.

I have several friends who didn´t even notice anything before the system asked for a reboot... and then the Spring Update was there... flawless! I have a neighbour that managed the update after the DISM-repair-method... success! But I can´t...

If I had a proper licence key and a 8.1 ISO I would repair it that way... But I dont... and the key I extracted from my OEM-installation doesn´t work to install from a 8 ISO or 8.1 ISO.

Personally I have a "date" with a MS Tech on monday evening. But I really don´t think I´ll get lycky. Not after having restored my system and still with the same problem.

Mi MangeK,

No problem at all :-)

I do agree that this issue is a major one, and too many users are experiencing that.

I've read all the threads, both of this conversation and also of this similar one

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/windows-81-update-1-failing-to-install-with-errors/c3071122-e903-4775-b659-e98784bc786c?page=23&msgId=721adb0a-44a4-4317-baf9-37381bc6474d

Only a few minutes ago, on that other thread, one usere succeeded, just as an example:

<Start Quote>Finally after running the 2 cmd's w/admin privileges, dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 then the dism /online /cleanup-image /startcomponentcleanup, checked my registry and cleaned any bad entries w/ccleaner the update went in from windows update. I am running win8/64 that was updated to 8.1 on an Acer Aspire/v5 lapper.<End of Quote>

I don't have an ISO either, and I had already discussed with MS Italian Tech, and what they proposed to me was exactly what you did: Roll back to Win 8, then install Win 8.1 and then install Win 8.1 Update. The problem is that I would have needed at least another two full working days to install all my programs etc., so that was not an option for me.

I am very sorry you went through all that and it did not solve the issue for you!

I sincerely hope your MS Tech "date" will be able to solve your current issues!

I MADE IT!! I MADE IT!! I MADE IT!!!

Thanks to Marco, basically what he suggested is to remove the failed 8.1 update 1 package by running this command:

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

I believe this was created by the installer downloaded by the Windows Update. This is the one that is causing the problem.

Once I had that removed. I then reinstalled the windows 8.1 update manually (by running Windows8.1-KB2919355-x64.msu I had downloaded earlier).

I almost could not believe my eyes when it says Installation Successful, restart required. Lol...

Once that is installed, I went on to install the other 4 updates.

 Thanks to Marco for pointing me on that one. I owe you big man.

Hi rosdikasim,

You're welcome :-)

I'm so glad this also worked for you!

After getting so frustrated with several and varied failed attempts since April 8th (I've never used the command prompt so much like in these days...), as I said by using the procedure I described I could successfully install Windows 8.1 Update on my two systems today, and few friends/colleagues succeeded too, so I wished to share my solution. I hope it proves useful for many other users, but I'm already happy it helped you :-)  Thanks for letting me know.