forums.wsusoffline.net

Is there a way to clear the RAM as it gets locked up? Much of my work is on netbooks and entry level laptops, and there usually is a notable slowdown toward the end of the updates. Currently I'm on a a 2GB laptop and with the RAM at 99% usage I've gotten several Low Memory warnings. The last (#138) Win7 update has alone taken 25m so far. I even opened task manager and killed what few unneeded processes were there, and set the desktop to a plain color.

Is there a command I can invoke manually in a separate CMD window to clear RAM, or would it be a good idea to write such a command into the WSUS code to execute periodically automatically?

Thanks.

138 updates, down the drain. After I wait an equally long time for them to revert, I will go online and update in batches.

MS is to blame for this odd/buggy behaviour/memory lock. Not much we can do about. For fresh installs it helps to have only the OS installed and updated with neither MS Office nor Dotnet 4.6 installed. This saves a lot of updates in the first run.

On Windows 7 it currently helps to install the following updates BEFORE connecting to the internet or trying to update the system in any way:
- WindowsUpdateAgent-7.6 (from .\client\w61(-x64)\glb)
<reboot>
- KB3078601
- KB3087039
- KB3102810
- KB3104002
- KB3109094
<reboot>

Now use wsusou or Windows Update to update your computer. The searching time in a virtual machine decreased from many hours to about 15-25 minutes.

Thanks, I've noted that and might try it next time. Decreasing installation speed toward the end of the run is always present, but not always critical. Here, after an hour on the last update, I hit ctrl-c and hoped for the best - and lost. In this case, I had installed .NET 4.2, in order to run an activation preserver; usually I save that until afterward.

I also had a 2GB SD card in as ReadyBoost (this is Win7 x64), but it didn't make a difference. I've now upped the RAM to 3GB and am trying WSUSo again.

Surprise, I found the machine had gone through the updates again, this time successfully. Sometimes I do my best work while I'm sleeping!

Also, I did install Office first on this machine, next time I will hold off for sure.

I also found that the RAM in this machine was PC-8500 rather than PC-10600, which will affect performance, and changed it before the reboot.

I'm not sure, how big the effect of Office is, as the memory bug is caused by TrustedInstaller.exe, which just handles Windows updates; but excluding .NET in the first round should help a little bit.