This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The company I work for has close to 100 Windows PCs.
All of those run Windows 7 Professional x64
Some of them had different problems with Windows Update (infinite search / never found any updates at all / ... )
For most of them I could solve the problem by following the procedure:
* set windows update to "never check for updates"
* reboot
* manually download and install KB3020369 (sometimes I could skip this step because it was already there)
* reboot
* manually download and install KB3172605
* reboot
* set windows update to "install updates automatically"
After that Windows updates can be searched and installed like they should.
However, there are a few PCs (about 10 ?) where that doesn't work.
All of these have KB3020369 already installed.
Installation of KB3172605 fails with message "the update is not applicable to your computer"
On one of them I tried to install KB3125574, just to make sure that installing updates is still possible.
That installation succeeded.
Another reboot, but KB3172605 still fails.
* Is there another prerequisite apart from KB3020369 that I'm missing?
* Is there something I can check to find out why KB3172605 fails?
* I checked if I could remove KB3020369 and install that again, but that seems not possible (in a normal way).
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.
This happened to me yesterday: fresh install Win7 Home 64bit, no updates. I
Ran and installed kb3020369 just fine, but kb3172605 stubbornly was inapplicable to my system.
I connected to the Internet, ran WSUS offline installer, let it download and install the updates, and restarted the pc. Disconnected from ethernet, ran kb3172605 and...it installed.
Might work for you?
Thanks for replying, CT.
I'm just posting a solution that worked for me, and maybe will work for the OP or others who land here when searching for a solution to this issue.
I don't do remote access, so the 'net access wasn't an issue. Either I can tell Windows to never check for updates, or I can restart the pc offline, I have addressed the slow update 'fix/solution' while offline and after turning off updating.
Also, I did have the correct bit KB, x64 in this case, and the pc still refused to install KB3172605 (inapplicable to this system). Downloaded it on two different pc's, different dates as well. So it wasn't for lack of proper application. :)
Otherwise, in that situation, I follow this procedure, and it works almost all the time:
No luck, still the same message. "The update is not applicable for your computer"
You should follow the Solution:
Note: set Windows Update setting to Never and leave it there.
It is possible that you would get that message if the version of KB3172605 is the wrong bitness (32 or 64) for that particular installation.
That is what I tried (I described it in my opening post)
I leave Windows Updates on 'never' all the way through
It is certainly not a case of wrong architecture: we only have Windows x64 installations: I know for sure because I installed every single one of these computers.
I downloaded a single set of files (the 2 updates KB3020369 and KB3172605) and used that on all the PCs.
The files are not corrupted, when the KB3172605 didn't work, I recopied them from my laptop, and later on re-downloaded them. Both times without success.
Otherwise, in that situation, I follow this procedure, and it works almost all the time:
OK, I'll check if this more extended procedure works.
I'll get back here when I have some results.
You should follow the Solution:
Note: set Windows Update setting to Never and leave it there.
It is possible that you would get that message if the version of KB3172605 is the wrong bitness (32 or 64) for that particular installation.
Otherwise, in that situation, I follow this procedure, and it works almost all the time:
