FIXED!! Windows 7 sp1 never ends searching for updates

[xorbe]

Well EOS (End of Sales) for Windows 7 Pro OEM is set to the 31st of October, so after that is only what's in stock.

For home users, plenty of Win7 options that can't be discussed on this forum.

 

[stinger608]

@Solaris17 your frigging awesome man!!!!!!!!!!

 

[Solaris17]

@Solaris17 your frigging awesome man!!!!!!!!!!

thanks buddy hope it proves useful for ya!

 

[stinger608]

thanks buddy hope it proves useful for ya!

Oh yea, it will!!!!!

I have several clients that wish to go back to Windows 7 so this will sure as heck speed up that process.

 

[Solaris17]

haha I do appreciate it, dont hold it in high regard just yet, you do need to manually deal with the occasional box. I cant interact with them in batch. So hitting "Close" is still something the user needs to handle.

I lied about this @Kursah I might actually have a trick up my sleeve yet. I will check on a fresh VM that isnt patched tomorrow after I get some sleep. Might have a final update for you guys that enables super laziness.

 

[Kursah]

My bench guy will be forever thankful to get Win 7 deployments off of his bench!

My testing has been successful with what you already have shared, much appreciated and I look forward to testing your future release(s).

 

[Solaris17]

Here is the latest, I cant modify my post anymore for the other one.

Changes:

-Added quiet flag to installers so you dont need to interact with them.

-Fixed numerous text formatting/spelling issues

-Fixed condition were script was copied to startup even on systems that dont support it.

-Added progress check to the beginning of the script so you dont need to read the beginning and interact for a script thats already in progress.

You will still need to allow administrator privileges of the script with each concurrent reboot because I write my staging data to the root of C:

Pretty sure this will be the last edit. I dont plan on working on it anymore, there isnt much else to do unless someone runs into a bizarre issue that I need to address.

 

[rk3066]

See I install Windows7 again cause Windows update wasn't working but now I updated to where it just searching&searching but I went to bed and by next morning...

 

[Jetster]

rk3066 run that patch in the post above you

 

[rk3066]

I already did that once before but the reinstall worked. I stood up till 11 then I went to bed

 

[Melvis]

Worked a treat Solaris17 THANK YOU!

 

[Solaris17]

Worked a treat Solaris17 THANK YOU!

NP buddy your very welcome!

 

[P4-630]

Well, I've finally installed Windows7 from a cloned recovery partition on SSD, installation went fine!

I have managed to install the first updates and SP1 without a problem.
After that it kept searching for updates, tried your patch @Solaris17 but it could not find updates right away after that.
Then I've tried this:

https://support.microsoft.com/en-us/kb/3172605
"The July 2016 update rollup includes some new improvements and fixes including the improvements from June 2016 update roll upKB3161608 for the Windows 7 SP1 and 2008 R2 SP1 platform. We recommend that you apply this update rollup as part of your regular maintenance routines."

restarted the laptop after that and I had pouring in a huge amount of updates and was able to fully update it with a few restarts in between.

I'm a happy camper and this Asus laptop is going to my dad now.

 

[rk3066]

What laptop is it? Windows7 is still a great OS and so is Windows Vista if you know how to mod it

 

[Solaris17]

Well, I've finally installed Windows7 from a cloned recovery partition on SSD, installation went fine!

I have managed to install the first updates and SP1 without a problem.
After that it kept searching for updates, tried your patch @Solaris17 but it could not find updates right away after that.
Then I've tried this:

https://support.microsoft.com/en-us/kb/3172605
"The July 2016 update rollup includes some new improvements and fixes including the improvements from June 2016 update roll upKB3161608 for the Windows 7 SP1 and 2008 R2 SP1 platform. We recommend that you apply this update rollup as part of your regular maintenance routines."

restarted the laptop after that and I had pouring in a huge amount of updates and was able to fully update it with a few restarts in between.

I'm a happy camper and this Asus laptop is going to my dad now.

The patch downloads this as part of MSU number 2 (STEP 4)

bitsadmin.exe /transfer "KB3172605" https://download.microsoft.com/down...67F-C713F7821374/Windows6.1-KB3172605-x64.msu C:\Win7qUD\2nd.msu

Are you sure it made it all the way to step 6? I know that the script prompts for UAC after reboot but Windows itself will close all security requests after a few min, if you went to get coffee or something you probably came back to a blank screen. When the script finishes it will literally tell you.

 

[P4-630]

The patch downloads this as part of MSU number 2 (STEP 4)

bitsadmin.exe /transfer "KB3172605" https://download.microsoft.com/down...67F-C713F7821374/Windows6.1-KB3172605-x64.msu C:\Win7qUD\2nd.msu

Are you sure it made it all the way to step 6? I know that the script prompts for UAC after reboot but Windows itself will close all security requests after a few min, if you went to get coffee or something you probably came back to a blank screen. When the script finishes it will literally tell you.

No blank screens, I think I've just restarted the laptop after it, I have let it do it's thing.

 

[Solaris17]

No blank screens, I think I've just restarted the laptop after it, I have let it do it's thing.

You shouldn't need to manually reboot. The script reboots the machines by itself. after each reboot UAC will prompt for admin. When the script is complete it will pop up and tell you (step 6 of 6). Also while people have been having luck with updates showing immediately this shouldn't be expected.

Atleast you got it working, the script does however download that update if left to its own devices.

 

[P4-630]

What laptop is it?

Asus N53JQ

With i7 740QM , upgraded the ram to 8GB and it has a GT425M.
It's a nice laptop and I'm impressed by it's sound (Bang & Olufsen).

 

[cdawall]

Thanks @Solaris17

 

[bogmali]

Stick'd for easy access

 

[Ithanul]

Best thing to do to avoid crap like this is to make a iso that has all the updates inside it. Saves a whole lot of time when doing a fresh install.

If you curious about the updates and such or even want isos set up nice. There an awesome guy over on OCN with a thread showing all updates and what they are for. He even made isos with the updates integrated into them.

 

[Solaris17]

Thanks @Solaris17

NP man hope it helped you out!

 

[SimJett]

Wish me luck. I've a laptop and a desktop afflicted by this never ending search for updates. Neither of which was after a fresh install / reinstall, but "months" later, when things had been going well.

 

[SimJett]

The KB3172605 - July 2016 update rollup for Windows 7 SP1 is supposed to include the fix from the KB3161608 - June 2016 update rollup for Windows 7 SP1, KB3161647, which is supposed to help fix the long search time for updates problem.

https://support.microsoft.com/en-us/kb/3172605 - July 2016 update rollup for Windows 7 SP1

This July 2016 roll up is what worked for me. Just make sure to have the prerequisite SP1 and April 2015 servicing stack kb3020369. Before installing, go to Windows Update and set to never check for updates. Then via control panel / admin tools / services, stop windows update if it's running. Install the patches and then go back to Windows Update and change the setting back to the desired method.

ps

soz for double post.

 

[stinger608]

Okay, a recent issue has arisen in these issues:

I recently had 2 different systems finally update Windows 7, however, both systems rebooted with errors showing several different .dll files missing!!! After doing a bit of research I found this solution:

Start the command prompt as administrator. (Note, this will not work if you do not run the command prompt as an administrator!)

Run the "sfc /scannow" command (Note: There is a space between sfc and /scannow.)

It will take awhile to scan. Probably around 15 to 30 minutes. Once it reaches 100% it will just sit there for another 5 to 10 minutes.



Both systems that I ran this command on have been repaired and working flawlessly.


Figured I would post this up for anyone that might have this newest issue.

Seems to be an issue lately with Windows 7 update service from good ole Microsoft. Imagine that.