Hi Jaxx,
Microsoft has issued a fix for your error: http://support.microsoft.com/kb/2969339
After you install it, the rest of the updates should download automatically.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Ok so here are the system specs
After the last update and restart. I am unable to use Windows update.
I have tried the troubleshooting steps but the problem still exists.
SFC returns no problem at all.
Problem occurring for updates KB2936068 and KB2919355
Using their standalone installer isn't working either.
--------- | --------- | --------------- | -------------------
Package Identity
| State | Release Type | Install Time
--------- | --------- | --------------- | -------------------
Microsoft-Windows-CameraCodec-Package~31bf3856ad364e35~amd64~~6.3.9600.16453
| Installed | Update | 11-12-2013 01:33:PM
Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~6.3.9
600.16384 | Installed | Language Pack | 30-09-2013 03:56:AM
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
| Installed | Foundation | 22-08-2013 02:46:PM
Package_for_KB2843630~31bf3856ad364e35~amd64~~6.3.3.0
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2862152~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Security Update | 23-11-2013 08:02:PM
Package_for_KB2868626~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Security Update | 23-11-2013 08:02:PM
Package_for_KB2876331~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 23-11-2013 08:02:PM
Package_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18
| Installed | Update | 30-09-2013 04:25:AM
Package_for_KB2884101~31bf3856ad364e35~amd64~~6.3.1.9
| Installed | Update | 27-10-2013 11:10:PM
Package_for_KB2884846~31bf3856ad364e35~amd64~~6.3.1.4
| Installed | Update | 27-10-2013 11:10:PM
Package_for_KB2887595~31bf3856ad364e35~amd64~~6.3.2.0
| Installed | Update | 23-11-2013 08:02:PM
Package_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 30-09-2013 04:25:AM
Package_for_KB2891214~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 28-10-2013 04:32:AM
Package_for_KB2892074~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 11-12-2013 01:33:PM
Package_for_KB2893294~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Security Update | 14-12-2013 01:38:PM
Package_for_KB2894029~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 30-09-2013 04:25:AM
Package_for_KB2894179~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 30-09-2013 04:25:AM
Package_for_KB2894853~31bf3856ad364e35~amd64~~6.3.1.3
| Installed | Update | 17-03-2014 07:41:PM
Package_for_KB2898514~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Update | 23-11-2013 08:02:PM
Package_for_KB2898868~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2898871~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2900986~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Security Update | 13-11-2013 09:41:PM
Package_for_KB2901125~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2901128~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2902892~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 01-11-2013 07:45:PM
Package_for_KB2903939~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Update | 18-12-2013 08:08:PM
Package_for_KB2904266~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 11-12-2013 01:33:PM
Package_for_KB2904440~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 28-01-2014 11:26:PM
Package_for_KB2908816~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2909210~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2909569~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 11-12-2013 01:32:PM
Package_for_KB2909921~31bf3856ad364e35~amd64~~6.3.1.5
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2911106~31bf3856ad364e35~amd64~~6.3.1.3
| Installed | Update | 24-02-2014 12:03:PM
Package_for_KB2912390~31bf3856ad364e35~amd64~~6.3.1.3
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2913152~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 11-12-2013 01:33:PM
Package_for_KB2913270~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 18-01-2014 07:54:PM
Package_for_KB2913760~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 17-03-2014 07:41:PM
Package_for_KB2916036~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Security Update | 15-02-2014 10:59:PM
Package_for_KB2917929~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2917993~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 18-01-2014 07:54:PM
Package_for_KB2919394~31bf3856ad364e35~amd64~~6.3.1.3
| Installed | Update | 29-03-2014 08:17:PM
Package_for_KB2919442~31bf3856ad364e35~amd64~~6.3.1.8
| Installed | Update | 17-03-2014 07:41:PM
Package_for_KB2919907~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2922229~31bf3856ad364e35~amd64~~6.3.1.3
| Installed | Security Update | 10-04-2014 12:42:PM
Package_for_KB2923300~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2923528~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2923768~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 15-02-2014 10:59:PM
Package_for_KB2925418~31bf3856ad364e35~amd64~~6.3.1.4
| Installed | Security Update | 17-03-2014 07:41:PM
Package_for_KB2928680~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Update | 17-03-2014 07:41:PM
Package_for_KB2929961~31bf3856ad364e35~amd64~~6.3.1.2
| Installed | Security Update | 17-03-2014 07:41:PM
Package_for_KB2930275~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Security Update | 17-03-2014 07:41:PM
Package_for_KB2934802~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 24-02-2014 12:03:PM
Package_for_KB2938527~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 17-03-2014 07:41:PM
Package_for_KB2939087~31bf3856ad364e35~amd64~~6.3.1.1
| Installed | Update | 10-04-2014 12:42:PM
Package_for_KB2942844~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 10-04-2014 12:42:PM
Package_for_KB976002~31bf3856ad364e35~amd64~~6.3.1.0
| Installed | Update | 06-12-2013 12:17:AM
The operation completed successfully.
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.
Hi Jaxx,
Microsoft has issued a fix for your error: http://support.microsoft.com/kb/2969339
After you install it, the rest of the updates should download automatically.
Robert,
There are quite a few clues in that output actually.
While the first line of data is very much in keeping with the default at 4.86GB, the Backups and Disabled Features at 1.65GB and the Cache and Temporary Dataat 1.57GB is disproportionate to the norm.
@ Jaxx,
I suggest you perform a disk cleanup by hitting Windows key + R to open the Run command and they type: cleanmgr and click OK. Click Ok in the menu which opens since the C: drive opens by default and then in the following menu check which options represent the greatest space saving. These are likely to be "Downloaded Program Files", "Temporary Internet Files", "Temporary Files", "Recycle Bin", "Thumbnails" and "System Queued Error Reporting".
You can safely delete the first five, but I would tend to leave the "System Queued Error Reporting" since that data may prove useful for troubleshooting.
Also, don't click the "Cleanup System Files" button because that deletes all the data held in the Windows.old folder. Having said that, it's supposedly deleted automatically within 28 days of upgrading. However, it's one of those commands that can't be undone, so I would err on the side of caution and leave it be.
There are a couple of others which appear in the list, but if you delete those files, you lose some data which might be useful in other ways sometime later. You can click each entry to get a description of what it relates to anyway.
I ran the /AnalyzeComponentStore command on my own system a while back purely out of curiosity, but here's the result it produced:
It's possible to schedule a task to reclaim the packages mentioned in the output, but Windows does this automatically, so in my particular case, I didn't bother.
But for future reference, here's an explanation of the output: http://technet.microsoft.com/en-us/library/dn251566.aspx
Ok I'm not sure what exactly do you need me to do??? I didn't really get that
I was practising my Powershell. It may be equivalent to asking you to do this (perhaps in an elevated cmd window, AKA Administrator Command Prompt):
cd /d %windir%\WinSxS
dir/ad amd64*_31bf3856ad364e35_6.3.9600.* | find "Dir(s)"
I'm just curious if this is a way of measuring how your Win8.1.1 is going. You could also do it after doing those DISM commands to see if they change things that way. I should definitely install a virtual machine for my own experiments to understand how this stuff works but I thought a few examples of others' easily obtainable diagnostics might be useful.
There are quite a few clues in that output actually.
@ xircal
Thanks for that. I guess I was hoping for a red flag type message: "Here's the component that's broken:" sort of thing. Perhaps that's something which would show up in the Event log? (Since everybody seems so averse to trying ProcMon. <eg>)
BTW what do you think about Dogtamer's comments about needing /resetbase to avoid corruption?
Here's the message I quoted from in that other thread you referenced:
And most importantly, I think, are ordinary users getting enough warning about backup (and how to use it) in case these experiments go wrong?
TIA
Robert
BTW what do you think about Dogtamer's comments about needing /resetbase to avoid corruption?
Here's the message I quoted from in that other thread you referenced:
And most importantly, I think, are ordinary users getting enough warning about backup (and how to use it) in case these experiments go wrong?
TIA
Robert
Robert,
Bit dodgy that advice because as mentioned on Technet, you can't undo any updates or service packs after running /resetbase. I haven't proposed it myself yet for that reason.
As regards backups, I suppose most users who have upgraded from previous versions of Windows should be well aware of the need to create a backup, but how many do? Most of them just descend on sites like this one instead. To quote an old saying, "You can lead a horse to water, but you can't force it to drink".