New
#21
Very strange. I don't have 3083324. It's not in my hide list or my don't install list.
Plus it not offered.
Very strange. I don't have 3083324. It's not in my hide list or my don't install list.
Plus it not offered.
That probably means that the KB was reworked - that same KB number was used.
I installed that KB on 03 Sept. on a test computer. It was not offered again today for that test computer. It was probably just an error that MS put the current version out there on 03 Sept. It probably would have been better if MS had not pulled the update - especially if the same update was to be released today. Pulling the update just fed the tin foil hat crowd. That article has been quoted in many a forum - including this one.
It's not in my hidden list or list of updates to avoid either. It showed up as "important" - not sure why it's not offered to everyone.
EDIT: Okay it has now made it's way onto my list of updates to avoid and I've removed it.
Code:kb:2660075 kb:2726535 kb:2876229 kb:2902907 kb:2923545 kb:2952664 kb:2970228 kb:2976978 kb:2990214 kb:2994023 kb:3021917 kb:3022345 kb:3035583 kb:3044374 kb:3050265 kb:3065987 kb:3068708 kb:3075249 kb:3075851 kb:3075853 kb:3080149 kb:3083324 kb:3083325
Last edited by Callender; 09 Sep 2015 at 21:49. Reason: add info
I haven't seen KB3083324 yet not on 9/3... or today
Of course I haven't been offered any updates yet though :)
I downloaded KB3075851 using my browser.
My 1st attempt to install KB3075851 failed.
Once I stopped the BITS and WUA services, KB3075851 installed.
It instantly fixed the RAM and CPU issues (mostly).
There is still a bit of CPU churn (25%) but RAM usage has dropped from 2GB+ to ~200MB.
It still (apparently) took over 2 hours to generate the update list.
When I tried to install a few updates my VM behaved normally.
After a few minutes it had downloaded them and after another few minutes they were installed.
Last edited by lehnerus2000; 08 Sep 2015 at 20:38. Reason: Additional
WU may be working now so a bit of CPU and mem is expected until updates are done for. On my machines CPU and mem dropped to normal values.There is still a bit of CPU churn (25%) but RAM usage has dropped from 2GB+ to ~200MB.
What I had noticed though, have seen this a couple of times, WU won't search for updates when set to notify (waits and waits with no action) and only starts to download and install if set to automatic. TrustedInstaller runs with 25% to 50% in this case until updates are finished.
Agreed.
If there are still updates to be installed (not including Hidden or Optional) it will keep using CPU power. :)
Once all of the updates (not including Hidden or Optional) were installed, the CPU usage dropped to 0 and the RAM usage dropped to ~20 MB (a significant improvement on 2GB+).
A weird thing I've noticed is that once I click "Install updates", it takes a certain amount of time before it actually starts downloading them.
The time seems to be equal to ~0.8 minutes per update selected (on my PC).
I selected today's 11 updates and it took ~9 minutes before WU actually started downloading anything.
Last night, my VM took ~16 minutes to start downloading 20 updates.
The 3 updates before those took ~2 minutes to start.
TrustedInstaller does an integrity check on all downloaded files, correlates results, and works out the order of install, before allowing the install of the first update.
Did you mean "... does an integrity check on all system files, ..."?
I meant before WU starts to download the chosen updates.
That is to say, no network activity is detected until after the mysterious delay.
After the update downloads have finished, there is almost no delay before the installation begins (on my PC).
It must be a VM "thing".
My "real" W7 install only suffers a delay of a few seconds per update (before downloading begins).
I don't believe my "real" W7 is 20x faster than my W7 VMs (since I notice no performance differences apart from boot time).
I have to say I have never noticed this Note at the bottom of the settings page :/
Attachment 371050
Last edited by ThrashZone; 05 Oct 2016 at 21:50.