I don't have RTM to replicate, but I do have two machines running RC.
I'll blow away Microsoft Security Essentials so Defender will be enabled and
I can test this.
Should be able to manage that by sometime later today.
"shadowman" <(E-Mail Removed)> wrote in message
news:3D3DB7AE-943D-4B8F-91F5-(E-Mail Removed)...
> Hello Bill,
>
> Thanks for your reply.
> I'm running Windows 7 Ultimate (RTM). I have a notebook with only Windows
> Defender,and also there Windows Defender demands a reboot when apply a
> definition update.
>
> Kind Regards,
>
> Guido van Brakel
> System Engineer
> MCP // MCSA // MCSE
>
> "Bill Sanderson" wrote:
>
>> I have to say that I have very few machines running Windows
>> Defender--those
>> that are tend to be servers. That said, I don't recall that definition
>> updates require a reboot.
>>
>> What version of Windows are you running? I wonder whether there is
>> something on your system which is interfering with the ability to restart
>> the service, hence the request for the reboot?
>>
>>
>> --
>>
>>
>> "shadowman" <(E-Mail Removed)> wrote in message
>> news:2C851B66-57DD-4671-9B95-(E-Mail Removed)...
>> > I would like to know why Windows Defender updates demand a reboot?
>> > Commonly,
>> > a system reboot is required because the installer is attempting to
>> > install
>> > a
>> > file that is currently being used. With for example McAfee you don't
>> > have
>> > to
>> > reboot when you install a new definition update. I would be nicer if
>> > Windows
>> > Defender requires no reboot after installing an update, just restarting
>> > the
>> > service should be enough.
>>
>>
|