All right. Is there anyone here who has successfully updated their system using the rollup download and if so how did you do it, after applying what pre-requisites exactly on your system?
It's completely random and varies machine to machine, at least in my experience so far I have found minimal consistencies. Today I applied the Windows Readiness Tool first - KB947821. You know this is successful when it takes a bit to install. On some machines it applies within 15-30 seconds, but does absolutely nothing. You restart and you can apply the patch over and over again with zero results. After I applied the Readiness Tool I ran the Updater Troubleshooter because I could tell already Updates were timing out. It came back and told me it had fixed previous failed installs (even though none had failed yet) and that it had fixed the service registration from being corrupt or missing. Then I restarted and Windows found 161 updates and went fairly smooth from there. It took all day to install that section of updates so I don't know if there are any more updates being found after this point yet until tomorrow, but I feel confident that this one might be okay from here on out.
Other machines like I've previously posted about are a total nightmare. I was purely in a state of troubleshooting the "current update" issue at hand when I was applying these so I was still playing whack-a-mole with what was wrong. This particular machine would install some updates - then go back to an infinite loop searching for updates.
This is what I have been using mostly for
Windows 7 Enterprise 64-bit - I used a few (4 or 5) on my own PC which is running Windows 7 Professional 64-bit.
Here is the list of patches I had to manually install by date of release. This first is important despite its contents.
Windows6.1-KB2506143 - Description of Windows Management Framework 3.0 for Windows 7 SP1 - This is an update that enables developer/IT related tools (PowerShell, WIM, OData IIS Extension, etc) I think it is necessary for Framework 3.0 to function properly. It has a lot of requirements check out the page for the details - there are a lot. Ain't nobody got time for that. 1/4/2013
Windows6.1-KB947821 Windows Readiness Tool (also info about DISM tool in there) October 2014
Windows6.1-KB3020369 April 2015 Service Stack Update - This one is definitely key/Important.
Windows6.1-KB3078601 Security Patch from 8/18/15
Windows6.1-KB3102810 This is supposed to be a fix for slow installing/searching of updates. From October 2015 - last revised in Nov 2015.
Windows6.1-KB3109094 Security Update 12/8/2015
This is where I usually find anywhere between 160-230+ updates available for install after a restart. I install those updates and sometimes it breaks again after this point.
Windows6.1-KB3138612 Windows Update Client from May 2016
Windows6.1-KB3161608 June 2016 Roll Up - Important, but gets removed later on to some extent. See July 2016 Roll Up.
Windows6.1-KB3164033 June 14 2016 Security Update
Windows6.1-KB3172605 July 2016 Roll Up - Fix for Bluetooth drivers, removes June Roll Up to an extent. There was
an article posted about this that is in this thread already.
Windows6.1-KB3179573 August 2016 Roll Up
After manually patching these I finally got that one nightmare laptop fully updated and was able to install Office 2016.
-- Diagnoistic Tools I used--
There are also these guys which have helped me troubleshoot (kind of, if you can call what they do actual diagnostics/troubleshooting you could have fooled me).
WindowsUpdateAgent-7.6 - This has only worked for me on one computer, my own personal PC with Windows 7 Pro.
WindowsUpdateDiagnostic.diagcab Supposdly diagnoises what could be wrong with your updates. Was really only useful for letting me know the service registration was missing or corrupt.
This is a walk through for resetting update components. This helped unfreeze the updater sometimes. There is a
FixIt that does the same process, but I find it isn't very useful (it does nothing most of the time) and you are better off going the manual route.
To reset the services I would type this in cmd prompt (
Run as Administrator or you'll get permission errors):
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
Then start them again.
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
Doing this will also help you see if a service is the issue and you can try to troubleshoot getting that working again prior to throwing random updates at your machine.
I have yet to try this, but this is the method I will be using to slipstream the updates into my installer to hopefully avoid this issue in the future. This might prove helpful in creating a better installation so in the event of needing to reformat you can do so without the pain.
How to Slipstream Updates into Windows 7 Installation
Credit for this guide really belongs to everyone in this thread mentioning updates and diagnostic tools. I wouldn't have gotten as far as I did as quickly as I did without the suggestions I found here.
I hope this helps those of you still stuck.
My father says its working well with he's Win7 Pro 64bit but he's the type that installs, updates and then doesn't check for updates for months/years in a row (said it's been 8 months since last time he installed, so that might have something to do with it 
