I've had this (KB 291355 fails with 800f0922) happen twice. It's worse than an install problem, it gave a BSOD etc.
I wonder why this appears not to have been tested enough?
Details:
- Machine in 64 bit Win 8.1,
- with Media Centre,
- set up to never run in "metro mode" except under direst of situations.
I like the OS even though the Metro "experience" can't be entirely banished.
- KB 2919355 presented as an option, not ticked.
- I installed other patches first before trying this one.
- First install went to completion then said "We couldn't complete the changes. Undoing changes. Don't turn off your computer."
- Then it uninstalled.
- Ran sfc / scannow. It found one file that was suspect ("Amd64\CNBJ2530.DPB" : Found: {l:32 b:5gW7lKEb/1Wk+ahLnhdoae2xeoyRqb48zi+s9nKgDUE=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}).
- Ran DISM.exe /Online /Cleanup-image /Restorehealth which fixed it. (I found that this little beauty (CNBJ2530.DPB) is fairly common, couldn't find root cause though!) Thought problem solved.
- Installed from Update again.
- Same process, it uninstalled itself.
- Then I got a BSOD. CRITICAL_PROCESS_DIED.
- Never seen before. Is it caused by the Update?
- Then machine wouldn't boot, said HDD was a problem. Shut down and left it overnight.
- Went through troubleshooting next day. BIOS based troubleshooting, long list of tests. All passed including HDD.
- Then restarted Windows worked as expected with maybe a bit of extra time at start (checking out / fixing OS?).
- Has now run for a day, no problems.
- Discussed with hardware supplier support (Dell). Only suggestion was that it was the update did it. Had a look at the update log, my untrained eye didn't spot any obvious cause, or "FATAL" entries. I'm currently downloading the manual install option.
Anybody have any suggestions about installing that before I bite the bullet.
My plan is,
- START
- create restore point,
- apply next update in sequence,
- BACK TO START AFTER TESTING UNTIL DONE.
After above: This is still a bust, similar failures. By reporting it here I might help others.
Update 2014-04-16.
- I did as follows (in the absence of being able to find any sure guidance).
- Checked partitions, none full so that's not an issue.
- Found a couple of references that the 2919355 installer is borked. http://news.softpedia.com/news/How-to-Fix-80070020-80073712-and-0x800f081f-Errors-on-Windows-8-1-Update-437334.shtml and http://superuser.com/questions/741065/cannot-install-windows-8-1-update-kb2919355-windows-update-error-80073712.
- These suggest some additional DISM work to clear out junk left by previous install. (Your own risk, I don't understand DISM sufficiently.)
I did it, seemed to work fine. Made a restore point. Installed 2919355 from manual msu file. It went to completion, went into reboots etc. then gave me the "We couldn't... screen". It then went a bit further, ran a reboot then got yet another
we couldn't BSOD...
Exception code the same even though symptoms differ.
The help screens from installer are still empty, unacceptable, somebody is asleep at the wheel.
That's enough for me. Good luck to you.
Update 2014-04-28. On my last look the official pages for this download have not been updated. The guys who supplied my system, and may be technically responsible (to some degree) refer to the MS install by hand link, so they aren't ahead
of me.
This fault ID clearly conflates more than one underlying issue so that the error code (800F0922) by itself is not enough to identify the problem.
I see at least 3 problems,
- Reserved Partition Full,
- unable to invoke netcfg
- and whatever I have.
(That might be useful to others finding themselves in update ****. It's not clear cut.)
Be careful of editing your posts, the editor can bork them