Windows 7 still not updating

[RandyL]

Note: tried the recomendations from the July 27th thread

I've got 3 systems with clean installs of Win 7 sp1 that will not update. Tried all recomendations from here and from google searches. Going on second day of running the updator.

Have a very important client that needs a clean Win 7 install next week. Starting to panic.

Any additional advice ?

Thank you,

R

 

[PBComputer]

Wsus offline on a USB drive network connection disabled. It's just took me 2 days to fully patch a machine

 

[Markverhyden]

I'm working on a brand new Dell, x64, W7Pro. Same symptom. In the past I installed, with no network connection, the below, in order, reboots between each one.

kb2775511
kb3020369
kb3138612
kb3172605

On the new machine it took 2775511, then reported the next two were installed, then installed 3172605, reboot and update is working fine.

 

[AlexCa]

I've recently re-installed and updated two Windows 7 SP1 systems by following the steps described in the thread:
https://www.technibble.com/forums/threads/win-7-update-process-as-of-7-28-16.71277/#post-561749

The only difference was that i skipped the Convenience Rollup and the June 2016 Update Rollup. You need to make sure that you have your internet connection disabled during the process. Afterwards, i was able to run Windows Update and install the remaining updates without problems.

 

[kwisher]

I cannot believe PC Techs still install Windows from install media. You should learn how to use a VM to make a sysprepped image and learn to use some sort of cloning software to save and restore when you need to do a N/P.

 

[trevm999]

I cannot believe PC Techs still install Windows from install media. You should learn how to use a VM to make a sysprepped image and learn to use some sort of cloning software to save and restore when you need to do a N/P.

Some techs might like to follow the rules, since chances are their client does not have re-imaging right. If they don't care about the rules, then yes, using an image updated already is the way to go.

 

[kwisher]

Some techs might like to follow the rules, since chances are their client does not have re-imaging right. If they don't care about the rules, then yes, using an image updated already is the way to go.

You totally lost me with your response. What do you mean by "rules"? There is nothing illicit in the way I restore my images as you still have to input the Windows key to validate.

 

[johnrobert]

I just put a new HD in a desktop I thought I would install win7 since that's what it had
then I thought nightmare of days of updating, decided to reinstall win10 job done in 30 mins.
with classic shell people are comfortable

 

[trevm999]

You totally lost me with your response. What do you mean by "rules"? There is nothing illicit in the way I restore my images as you still have to input the Windows key to validate.

Just because Windows activates does not mean you are compliant. In order to use a single Windows image to re-image multiple computers there needs to be re-imaging rights. This comes with a volume licensing agreement. If all there is is an HP OEM licence, for example, you are not supposed to load it with a custom image, you are supposed to use the original OEM image. If you build PCs and purchase OEM licences, sure you can use your own standard image for the computers. Same for refurbisher licences.

Brought to you by the world of Microsoft licensing. It's a PITA, but if you're supporting businesses, then it should always be your goal to not do something that might cause problems in the event of a Microsoft audit. And if you are a MS refurbisher, you should make sure your practices would pass a Microsoft audit.

 

[nlinecomputers]

Limits on the method to install Windows is nowhere listed on this license that I can see:

https://www.microsoft.com/en-us/Useterms/OEM/Windows/10/UseTerms_OEM_Windows_10_English.htm

Once the end user has possession of the unit they may remove and completely reinstall windows in any method they see fit. Or hire anyone to assist them in doing so. There ARE limits if you SELL PCs new or used but not in repair of them.

 

[Markverhyden]

Just because Windows activates does not mean you are compliant. In order to use a single Windows image to re-image multiple computers there needs to be re-imaging rights. This comes with a volume licensing agreement. If all there is is an HP OEM licence, for example, you are not supposed to load it with a custom image, you are supposed to use the original OEM image. If you build PCs and purchase OEM licences, sure you can use your own standard image for the computers. Same for refurbisher licences.

Brought to you by the world of Microsoft licensing. It's a PITA, but if you're supporting businesses, then it should always be your goal to not do something that might cause problems in the event of a Microsoft audit. And if you are a MS refurbisher, you should make sure your practices would pass a Microsoft audit.

Yes, it depends on the version, OEM, Retail, etc,etc. Refurbisher and OEM actually have two licenses. One with M$ and one with the OEM/Refurbisher. All of the others have just one, with M$. Of course there are country specific things as well. Been a while but have read several different EULA's over the years. They reference things like "this software" but I have yet to see them make a reference specifying the type of source, such as ISO, disk, etc. I see this as being a bit of a grey area.

In the case of OEM's, like HP and Dell, they reference the software they provide so it's pretty cut and dry in my book. You can use an image provided by the OEM and, as long as the COA/license on the OEM machine matches the OS version, you can do what you want. Back when I was at CompUSA we used to get HP recovery disks and included in them were disks with just the OS, no bloatware. I seem to remember HP saying something about not modifying the software which implies you cannot go in and strip out OEM stuff to build a minimal image.

 

[trevm999]

Limits on the method to install Windows is nowhere listed on this license that I can see:

https://www.microsoft.com/en-us/Useterms/OEM/Windows/10/UseTerms_OEM_Windows_10_English.htm

Once the end user has possession of the unit they may remove and completely reinstall windows in any method they see fit. Or hire anyone to assist them in doing so. There ARE limits if you SELL PCs new or used but not in repair of them.

The reimaging rights brief
https://www.microsoft.com/en-us/licensing/learn-more/brief-reimaging-rights.aspx

There was also a report somewhere on the forums here where a registered refurbisher was audited by Microsoft and they were told they could not use their custom images for customer's PCs that came in for repairs

 

[trevm999]

Yes, it depends on the version, OEM, Retail, etc,etc. Refurbisher and OEM actually have two licenses. One with M$ and one with the OEM/Refurbisher. All of the others have just one, with M$. Of course there are country specific things as well. Been a while but have read several different EULA's over the years. They reference things like "this software" but I have yet to see them make a reference specifying the type of source, such as ISO, disk, etc. I see this as being a bit of a grey area.

In the case of OEM's, like HP and Dell, they reference the software they provide so it's pretty cut and dry in my book. You can use an image provided by the OEM and, as long as the COA/license on the OEM machine matches the OS version, you can do what you want. Back when I was at CompUSA we used to get HP recovery disks and included in them were disks with just the OS, no bloatware. I seem to remember HP saying something about not modifying the software which implies you cannot go in and strip out OEM stuff to build a minimal image.

I bet it is a grey area legally, and thus why it isn't clarified more in the EULA. But the volume licencing and refurbisher licencing teams seem to take it to heart, so unless there is a court case over it, it probably won't be clarified.

 

[nlinecomputers]

The reimaging rights brief
https://www.microsoft.com/en-us/licensing/learn-more/brief-reimaging-rights.aspx

There was also a report somewhere on the forums here where a registered refurbisher was audited by Microsoft and they were told they could not use their custom images for customer's PCs that came in for repairs

That is the terms UNDER volume licensing. They have NOTHING to do with the terms for an individual end user. That is covered under the terms of the End User License Agreement. Volume License terms do not apply to people who are NOT in a volume license agreement. You have misinterpreted that document.

 

[trevm999]

That is the terms UNDER volume licensing. They have NOTHING to do with the terms for an individual end user. That is covered under the terms of the End User License Agreement. Volume License terms do not apply to people who are NOT in a volume license agreement. You have misinterpreted that document.

That is because the end user agreement does not come with the rights to make an image intended to be deployed to multiple PCs. What gives you this right?

 

[nlinecomputers]

What gives you this right?

What doesn't?

 

[trevm999]

What doesn't?

From the Windows 10 EULA you posted

"c. Restrictions. The manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:
(ii) publish, copy (other than the permitted backup copy), rent, lease, or lend the software;"

 

[mraikes]

I'm working on a brand new Dell, x64, W7Pro. Same symptom. In the past I installed, with no network connection, the below, in order, reboots between each one.

kb2775511
kb3020369
kb3138612
kb3172605

On the new machine it took 2775511, then reported the next two were installed, then installed 3172605, reboot and update is working fine.

This worked perfectly, thank goodness.

I had an HP desktop that the client factory restored, and then brought to me because "nothing worked" (Also known as "What happened to all my stuff?!!"). I restored personal files from a recent backup and attempted to install updates. As usual, it sat there for two days not accomplishing anything. I decided to just wipe it and reinstall from scratch. When ready again to try updating, I followed Mark's suggestion above, and everything went swimmingly. I can finally finish this thing and get it back to the customer.

 

[MikeLierman]

Just wanted to chime in here and say we've had the same problem on a deployment of 10 Windows 7 workstations. I found that if I let the updater run doing the "checking for updates" overnight with sleep turned off. It does do it. I don't know if it's a new bug introduced in Windows 7 or if Microsoft's servers are getting hammered so they moved resources to Win 10 update servers, and now Win 7 updates slowly. The latter is our guess here at the shop, after continually seeing this issue. Even had the issue on Sever 2012 R2.

I also open up a command prompt and run "net start bits" that's the service that connects to the update servers, and sometimes it's stopped.

Sent from my Nexus 6 using Tapatalk

 

[RandyL]

Just wanted to thank you guys for the suggestions and advice. I ended up trying Wsus offline per PBComputer. Had found some other positive info online re Wsus...It worked very well. Only down side is, you have to monitor the installation process, which takes awhile.


R