Conversation
Notices
-
@hobbsc no matter how inefficient you may be: you're still more efficient than Windows Vista figuring out which updates to download ;-)
- ghostDancer likes this.
-
@hobbsc a have a Windows Vista box sitting here for 1 week "computing which updates to download" at 100% (celeron) cpu load. Not uncommon...
-
@yvolk you still get updates for Vista and W7 if you don't skip updating for too long.
-
@yvolk Otherwise svchost.exe will run for hours-days at 100% cpu *without* network or disk activity, "meditating" what updates are needed
-
@nakal rumour says MS's update-searching method has become a lot more "complicated" in April & the auto update client went very inefficient
-
@nakal I recently re-installed Vista on a notebook and after SP1 & SP2 the auto update client meditated for 3 days "searching for updates"…
-
@nakal … without any network or disk activity, but finally coming up w "there are xxx updates", so really just needed the cpu time of 3 days
-
@nakal to be a bit more precise: there is disk and network activity within the first 10... minutes – the 3 days after are meditation, though
-
@nakal @axmen so, either !MS is just incapable with their update method, or rather than stupidiy they're mining bitcoins on ppls computers
-
@nakal I havent noticed crashes but some people claimed the svchost allocating 4 GB or so RAM . Not here though.
-
@nakal I gave up on my recent case of Vista auto update meditating for >12 days. I upgraded to Win7& got all updates completed within a day
-
@nakal I use Vbox a lot and it rarely crashes. When it did crash it was never reproducible. From my experience you need >=1.3GB RAM for win7
-
@nakal regarding the update problem you can try the winfuture.de update pack.Installing their updates may work but it won't fix MS's updater
-
@nakal I think you can also disable Windows update in the system control ui, or stop & disable "Windows Update" in services.msc
-
@andersbateva thx, I know. I have a Windows 10 testing VM, disconnected from the internet, but I hate it and do not use it. @nakal