Engel,
My Good and Dear Friend
Why do you think I wait for your link with Bated Breath?
One of the main reasons is that your link DOES NOT CREATE A SYSTEM RESTORE
POINT !!!
I've pointed this out before but I will reiterate.
The Defender Update itself DOES NOT CREATE A RESTORE POINT!!!
It is the Method of downloading that triggers the creation of an SRP.
AU {WU/MU} BY DESIGN trigger the creation of an SRP. Most of the time this
is a Good thing as it involves Patch Tuesday and Major changes to the system.
It is however unnecessary for something as minor a definition update.
The UI of Defender [Check for Updates] also creates an SRP as it "invokes"
in someway, shape, or form, AU .
I believe that it works the same for the Portal [i.e. No SRP] but I only
tried it once when it was first introduced. The full download from the
Portal is just too time consuming for my modem to do on a daily basis.
Of course this is my experience with XP, it could be different with Vista.
Hope this answers the question.
And I Thank as always for the links,
and Now you know why
Tim
:
Hello Tim,
Please confirm. Regards Restore Point
Using my link, you don't get a Restore Point ??
What about the Portal ??
TIA
Tim Clark said:
Well,
One difference between your method of updating and mine is that using the AU
method causes the creation of a System Restore Point. So when you give
permission to install Two things are happening in Succession.
1. A System Restore Point is created [which I'm sure is using the CPU as
well as doing a lot of writing to the disk].
2. The Update itself is immediately applied after that.
My question for you is How Long does this take.
If it's a High CPU usage for 3-5 seconds I would not care.
If it's a High CPU usage for 20-30 seconds then I might care.
It could also be that I generally Don't Do Anything during an update of
Anything except allow the update to occur so I don't notice anything else
being affected.
Tim
--
If you set a Vista disk in the CD tray upside down,
you can hear SATANIC VOICES!
But that isn't the worst of it,
if you set it the right way IT INSTALLS VISTA!
:
This is definitely an installation delay. I'm notified that an update exists
by windows update. I give permission for the update to be downloaded (but not
installed) over a broadband (or T1) connection. Sometime later I give
permission for the update to be installed. At that time, the total
consumption of all CPU resources occurs and the length of time depends on the
speed of the CPU. No other update of any other definition-type data
(Symantec, Spybot S&D, ...) or even updates of windows components or
installed programs is nearly so effective at pigging up the CPU as are the
Windows Defender updates. Even Adobe's updates behave better and they have
never played nice on Windows machines.