• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win7 HP SP1-U x64 - more update madness

VirtualLarry

VirtualLarry

No Lifer
Yes, I know that the "minimum recommended" RAM for 64-bit Windows 7 is 2GB. Oh well. The rig I just installed it on, has 1GB, because that's all I had lying around to use.

Anyways, it wanted to install 130 updates or so, and when it got to installing update 120 or so, it said "Windows is running out of memory, oh noes!". Apparently, with 1GB RAM and a 40GB SSD, it had allocated nearly all of it's maximum 5020MB VM space.

The update install process just got slower, and slower, and slower. So I clicked "Stop Updates". Who knows what that does... does it simply stop, after the current update, and let you reboot (sane option), or does it attempt to roll-back all 120 updates that it applied (insane option, given the memory pressure issues)?
 
After some of my updates that were cut due to connection problems the update service installed as much as it could (I think). Then on resume connection it just continued.
Install updates manually, a few at a time.
 
Manually doing a few at a time will definitely help, but even though it says it's running low on memory, at least when it showed up on my VM with 1.5GB of RAM the other day, it actually turned out to be running out of HDD space as I had promptly shut down the VM and assigned 4GB and still got the message when doing all updates in one shot. When Windows Update unpacks updates, they take up quite a lot of space and since MS killed the idea of a second service pack, there is certainly a lot of them...
 
Last edited:
The minimum recommended is actually 4GB minimum in practice, if not 8GB if you want a box to last. 2GB is a phone (and an average one at that).
 
escrow4 said:
The minimum recommended is actually 4GB minimum in practice, if not 8GB if you want a box to last. 2GB is a phone (and an average one at that).
Click to expand...
Have to argue with this assertion.

If that were true, why would "they" release the 32 bit version that can't even address more than ~3 Gigs?

Art
 
If you have a bunch of updates to install, after a fresh install, it won't install them all at once. Some will fail. You need to do it multiple times. I installed on a 1.5GB memory machine with an SSD and it worked fine, but it did need multiple reboots. SSD makes a huge difference when you have 2GB or less.
 
ArtShapiro said:
Have to argue with this assertion.

If that were true, why would "they" release the 32 bit version that can't even address more than ~3 Gigs?

Art
Click to expand...

Because of creaky outdated 1995 era software that doesn't need that much RAM? Who even clean installs 32 bit Windows now anyway beyond tablets?
 
Sorry for not (updating, arg!) this thread.

After clicking "Stop Updating" and waiting for three hours, without any notable CPU usage, I closed the window. Went to Control Panel, opened Windows Update, and lo and behold, it was still stuck on update 120, and this time, "Stop Updates" was lit up again.

So I clicked Start, Restart, and it took some time to finally shut down Windows, but then it applied the updates that had gone through, then I was able to reboot and apply the rest.
 
They wont make a SP2 for 7,this is unreal,all they care about is 10.Peoples will get piss off and switch to the Crappy 10D:
 
A friend of mine stopped by this weekend with a used Dell first gen i3 laptop that he picked up cheap. I did a clean install of Win7 HP on it for him and then ran Windows Update after loading the hardware drivers. It said that there were 199 updates available and so I put it to work. It downloaded everything and ran updates fine until it hit #183 where it just sat, grinding away at the hard drive. The laptop has two gigs of ram in it but eventually the 'running out of memory' message popped up. I canceled the install and after more grinding away at it I was able to eventually reboot the system and resume the updates.

I had to laugh when it said that there were 31 updates available because we all know that 199 - 182 = 31, right? 😉
 
escrow4 said:
Because of creaky outdated 1995 era software that doesn't need that much RAM? Who even clean installs 32 bit Windows now anyway beyond tablets?
Click to expand...

unfortunately, we have to keep a few laptops with it at work.
i work for a yarn manufacturer. the equipment may have another 10-15 years of life, but as far as software support for the PLCs is concerned, vendors consider it EOL already so....no windows 8, no 64 bit. windows 7 32 bit is it. it blows.

most other stuff is supported up to windows 7 64 bit. im kinda peeved that people are supporting windows 8/server 2012 better but im not really surprised.
 
DrDoug said:
A friend of mine stopped by this weekend with a used Dell first gen i3 laptop that he picked up cheap. I did a clean install of Win7 HP on it for him and then ran Windows Update after loading the hardware drivers. It said that there were 199 updates available and so I put it to work. It downloaded everything and ran updates fine until it hit #183 where it just sat, grinding away at the hard drive. The laptop has two gigs of ram in it but eventually the 'running out of memory' message popped up. I canceled the install and after more grinding away at it I was able to eventually reboot the system and resume the updates.

I had to laugh when it said that there were 31 updates available because we all know that 199 - 182 = 31, right? 😉
Click to expand...

Some updates only appear after pre-requisites are installed. This is extremely typical.

It always takes several rounds of updates (and multiple system restarts) to catch up completely.
 
VirtualLarry said:
Yes, I know that the "minimum recommended" RAM for 64-bit Windows 7 is 2GB. Oh well. The rig I just installed it on, has 1GB, because that's all I had lying around to use.

Anyways, it wanted to install 130 updates or so, and when it got to installing update 120 or so, it said "Windows is running out of memory, oh noes!". Apparently, with 1GB RAM and a 40GB SSD, it had allocated nearly all of it's maximum 5020MB VM space.

The update install process just got slower, and slower, and slower. So I clicked "Stop Updates". Who knows what that does... does it simply stop, after the current update, and let you reboot (sane option), or does it attempt to roll-back all 120 updates that it applied (insane option, given the memory pressure issues)?
Click to expand...

I now typically don't select more than about 50 updates at a time to install.

Even on powerful systems running through the 170-some updates after initial install consumes hours as the memory usage skyrockets.

I used to give people computers with 2gb ram because that was all that was needed to run a business-purpose machine fast. In recent months Windows Update decided this was no longer sufficient, consuming up to and over 1.4gb just for the corresponding svchost.exe process! Let alone trustedinstaller.exe which consumes up to & above 1gb during installs of 100+ updates.
 
You should consider using Windows' DISM utility to build and maintain your Windows images. Eliminates downloading and installing hundreds of updates for each PC. I add each month's updates to my images so a clean install is always up-to-date. You can also remove updates that have been replaced by newer ones.
 
cubby1223 said:
I now typically don't select more than about 50 updates at a time to install.

Even on powerful systems running through the 170-some updates after initial install consumes hours as the memory usage skyrockets.

I used to give people computers with 2gb ram because that was all that was needed to run a business-purpose machine fast. In recent months Windows Update decided this was no longer sufficient, consuming up to and over 1.4gb just for the corresponding svchost.exe process! Let alone trustedinstaller.exe which consumes up to & above 1gb during installs of 100+ updates.
Click to expand...

Some of the services (like indexers and Superfetch) are designed to use more memory when there's more available. So SVCHOST.EXE will always balloon to fill up the unused space. Superfetch should improve system performance when loading applications. It's low priority, so it pushes the cache out when you need more memory for other things.
 
wsusoffline works great for reinstalls.
install the os
install drivers
run wsusoffline, come back in the AM
WU only had 29 updates to do in the AM
I pop 128gb ssd into any PC Im refreshing, then ghost it back to the original drive before giving back to the customer, saves me time,plug then I have a backup image 'as delivered'
 
this all changed when MS decided to use RAM not as only as cache for updates, but as a storage for downloading (and extracting) updates
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top