• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Can't update Windows 7 installs

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
Do you see how ridiculous this is.
Why is there no easily located full download from a Microsoft-owned site, not third party articles/blog links that seem to be the only links to Win7 "SP2".
 
After installing all of the updates listed in satrow's link and the above link from Pinky (infoworld link), one of my PC's (with a fresh install done yesterday) magically found 234 updates.

Microsoft, seriously, WTF? Why was it necessary for me to manually install all these updates before the updater started working again on it's own?

Thanks to both Pinky and satow for the help. Hope I can get this method to work on my other PC that's also hung up on this step.

This is straight up weird, it wouldn't install any of those manual updates unless I attempted to install them within the first few minutes of booting the PC up, no idea why.

This is the bane of my existence at work right now. Every computer that I have fresh wiped and reinstalled Windows 7 Enterprise on has needed the same type of treatment - each time a different set of updates has been required. You're not alone. Glad I caught this thread because right now I have a machine that isn't updating despite installing both July and August roll ups, 5 or 6 other updates I had on hand that worked on other machines... and I've been constantly clearing the distro folder and caroot2 folder to manually reset updates history.

Messed up thing is I am past the point where you get the 234 updates. I had to install all 234 updates ~20-25 at a time because the first time it failed on 49 of them and reverted back. However, it failed on a few more updates after it reverted so it chose the restore point before all 234 updates were installed. Such a pain - wasted at least 3-4 hours of time and I have been going at this since noon yesterday.

Going to try some of the updates mentioned in this thread and hope it works out. Right now I can't even install Office 2016 because the update service hangs. :mad:

Oh and IE doesn't work at all. Trying to navigate past MSN.com just comes up as a blank page or indefinitely attempts to query the website you type in.
 
This is the bane of my existence at work right now. Every computer that I have fresh wiped and reinstalled Windows 7 Enterprise on has needed the same type of treatment - each time a different set of updates has been required. You're not alone. Glad I caught this thread because right now I have a machine that isn't updating despite installing both July and August roll ups, 5 or 6 other updates I had on hand that worked on other machines... and I've been constantly clearing the distro folder and caroot2 folder to manually reset updates history.

Messed up thing is I am past the point where you get the 234 updates. I had to install all 234 updates ~20-25 at a time because the first time it failed on 49 of them and reverted back. However, it failed on a few more updates after it reverted so it chose the restore point before all 234 updates were installed. Such a pain - wasted at least 3-4 hours of time and I have been going at this since noon yesterday.

Going to try some of the updates mentioned in this thread and hope it works out. Right now I can't even install Office 2016 because the update service hangs. :mad:

Oh and IE doesn't work at all. Trying to navigate past MSN.com just comes up as a blank page or indefinitely attempts to query the website you type in.

This is more of a "for my information" question/post but ....Would making a generic system image like described here be useful for your situation? It was the first thing I thought of when reading your post, but I am just not sure if it would apply to that issue.
 
I need to do something similar. Unfortunately the model of laptops in my company vary user to user. I need to use the DISM Command-Line tool to inject updates manually into my flash drive build. I got hired at this company about 3 months ago and the support specialist before me was using CD based images and doing everything from scratch so I didn't have anything to base myself off of.

My solution in the time being is to just apply as many updates manually as possible - I was able to install a few that seems to have pushed it over the edge finally. After installing KB3109094 it finally wanted me to Shutdown to install updates and it "magically" decided to do 22 updates after that. The user is connected on WiFi so sadly I can't use Wake on LAN to reboot the PC and I'm stuck waiting until they notice to turn the laptop back on to see where this goes from here.
 
I need to do something similar. Unfortunately the model of laptops in my company vary user to user. I need to use the DISM Command-Line tool to inject updates manually into my flash drive build. I got hired at this company about 3 months ago and the support specialist before me was using CD based images and doing everything from scratch so I didn't have anything to base myself off of.

My solution in the time being is to just apply as many updates manually as possible - I was able to install a few that seems to have pushed it over the edge finally. After installing KB3109094 it finally wanted me to Shutdown to install updates and it "magically" decided to do 22 updates after that. The user is connected on WiFi so sadly I can't use Wake on LAN to reboot the PC and I'm stuck waiting until they notice to turn the laptop back on to see where this goes from here.

Yeah but isnt that the point of the link? Make a "generic image" by following the steps and add whatever custom drivers and updates you like. In your case you could/would make your master/generic image and apply all updates to it, then apply chipset and manufacturer drivers to individual machines after you ghost a fully updated image to them?

Like I said I was really more curious to know if I was heading in the right direction in case I ever have to do a mass deployment like that (probably never). Also I tried a fresh install on a home machine the day after Win10 AU and had the same issue, so thanks for all the ueful advice guys :)
 
I honestly don't know if you could configure the image on the fly with this method. To me this sounded ambiguous how well that would work for different systems.

It's talking about going through the OOBE... which in my head means you're setting up an image for laptop model X. So the computer you're using to create the image is the base that it resides on. I think it's a one trick pony in the end - meaning that it will only work for one specific type of laptop.

This means I would have to create individual images for each new model of laptop we acquire. That just isn't convenient enough in the long run. I don't mind downloading and configuring drivers every time Windows installs because there are always newer updates than what Windows has in it's index. As for programs there are very few we use so installing them only requires having the .exe's ready on separate media for quick access. I keep a flash drive with the updated versions of the programs so I always know the latest version is installed when I have to reformat someone or build them a new image.

What I need to create somehow is an image that has critical updates streamlined into the installer. I found a guide that shows what I plan to do here.

This may be out of date I'm not sure yet, it was posted back in May and you know how Windows likes to create multiple new updates quite often. I'll have to test the guide out myself to see how well it works - or if I'm going to have to add additional updates that precede the guides post date.

-Edit-

Basically the goal I'm trying to achieve is having a bootable Windows 7 Ent flash drive that contains all the media I need for anyone's computer at a moments notice. As for drivers, that one I'm just stuck with sourcing myself each time. Drivers are almost always picky and I do not like to rely on Windows' index because sometimes it will install generic drivers that cause issues in the long run. So about the only thing I want to have to archive is drivers for the different models - creating individual images will just take up too much space and leave more room for error.
 
Last edited:
It's talking about going through the OOBE... which in my head means you're setting up an image for laptop model X. So the computer you're using to create the image is the base that it resides on. I think it's a one trick pony in the end - meaning that it will only work for one specific type of laptop.

I read it to mean that it took you outside the OOBE to make a completely vanilla and updatable image to build multiple systems on. If it works the way I think it amounts to the same end product as the link you listed , so ...great minds think alike! :thup: :D
 
I don't know man :(

I read through the article 3 or 4 times now looking if I was missing something, but it looks like it uses the machine you're creating the image on as its template - so it will expect whatever system it is used on to be the same architecture in terms of hardware. If that's the case then jumping from model to model will cause either buggy or unstable installations. I could be wrong though, I'll try it out and see what happens.
 
Just a note, I did a fresh install of win7 sp1 on my old laptop (atom cpu). It took almost 4 days before the updates showed up, (about 225 of them). So it can take a ridiculously long time. I have read this is a flaw in win7 updater.

I had previously tried various partial installs of the updater, IE11 but nothing seemed to help but waiting.
 
Just a note, I did a fresh install of win7 sp1 on my old laptop (atom cpu). It took almost 4 days before the updates showed up, (about 225 of them). So it can take a ridiculously long time. I have read this is a flaw in win7 updater

Yep, there is a flaw in the updater... as well as some of the services I suppose because even when I attempt to "update the updater" it fails at that sometimes. This laptop I'm currently working on has been by far the worst offender, but each install I've done thus far has run into its own different assortment of issues with updates.

I was able to fix the service registration - now I just have to solve update error 0x80070057... sigh.
 
I don't know man :(

I read through the article 3 or 4 times now looking if I was missing something, but it looks like it uses the machine you're creating the image on as its template - so it will expect whatever system it is used on to be the same architecture in terms of hardware. If that's the case then jumping from model to model will cause either buggy or unstable installations. I could be wrong though, I'll try it out and see what happens.

Are you using the OEM disc? I was talking about using an iso from MS. You get a vanilla install then without any of the chipset or proprietary drivers (which can be added on individual machines later from the manufacturer website) and then add all updates to THAT image? You would still have to handle each machine individually to add the chipset and other drivers later, but that is a quicker process than fixing updates on each machine. Thats my thought process any way. Let us know how it turns out in any case. Good luck :)
 
Yes, I have an OEM image from the VLSC.

I just didn't think the process in the article you linked created an image free of drivers - I thought it would create an image of the Windows 7 installation you just put on that specific machine. I'll find out later this week when I get the time to play with it at work.
 
Bah, I don't even know what to try anymore.

I finally got to a point where I only have 1 important update failing and 8 optional that won't download.

I was able to install Office 2016, but now Outlook hangs when attempting to add a profile with automatic settings. I'd configure them manually, but I do not have the manual configurations available, nor does my profile display any settings information since it auto discovers. I tried to use the Office 365 Recovery Assistant, but that hangs too.

There is definitely something screwy with this laptop and I have no idea what it could be. Event Viewer is clean. It's a brand new Samsung EVO 256GB SSD to replace a failing HD that was throwing bad block errors in EV. A completely brand new clean install from a fresh iso of Win 7 Ent 64-bit on my laptop.
 
Back