Thank you very much for this. There's an *awful* lot of stuff going on in those logs, with the errors pointing every which-way. If half of that's to be believed, you've got some nasty corruption going on. But....I'm not certain I do believe it quite.
First off - have you been running in Safe Mode recently? There are some entries in there indicative of service errors. However, those service errors could have been caused if you booted into Safe Mode recently. If you haven't though, we need to get digging. If you have, we can put those to one side.
Next, how much free space do you have on your disk drive? And have you ever had a low space condition recently? First, 643 itself can be caused by free space issues. Second, errors pointing every which way can indicate a free space issues: the installation gets to a slightly different point each time before running out. Third, .net updates are infamous for requiring a good couple of GB of free space. Fourth, free space issues are becoming more common with the rise of SSDs taking drive letter C:\. So please let me know precisely how much you have on drive C:\ at the moment and whether you've had this issue recently.
...
However, saying all that, my personal belief is that you don't have a free space issue, and you never have had one. But I want to check the obvious things first lest we look very silly if it turns out to be them
The next thing I want to note though is that this installation is actually failing during the initial extraction and setup stages - not during the actual installation. This in fact is usually a good sign: failure during installation means corruption on components which already exist on your PC (bad). Failure during extraction means free space issue (I don't think that's the case here but I'll check anyway), or a cache corruption - i.e. by some bad luck the installer downloaded/extracted a file incorrectly first time round, and now keeps on re-using those bad files,
or something more complex is going on. In fact, I think it's actually the latter - you appear to be running into a known issue. I've seen it once before, although back then it manifested itself in a very slightly different way to your PC. However, there's plenty of information online I've dug out now and for the one other time I've seen this, so let's get started.
First up, let's try the Microsoft solution for their own problem. Install this update:
http://support.microsoft.com/kb/3000988
restart your computer and re-try Windows Update.
If that doesn't do the job, uninstall (
Removing an update - Windows Help) all of the following updates:
KB2918614
KB3008627
KB3000988 (the one you've just installed
if it wasn't installed already EDIT: clarification: I mean for you to uninstall this update regardless of whether or not it was already installed. That wasn't very clear initially.)
Then restart your computer, refresh Windows Update and retry KB3001652 and KB2901983. Then, if they install, restart your computer again and re-install any further updates which are offered to you (including any of the ones we've just uninstalled - if I've diagnosed the issue right, you've got v1 of those updates. Microsoft have re-released them now, so there's no harm in reinstalling them, we just needed to get the stuck and broken ones off your system before installing a nice clean copy of the new versions.
Really good luck with this - fingers crossed! :)
Richard
