Problems with updating Defender Beta 2 to latest version

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I seem to be having two problems with the Beta 2 updates. First, I get
messages every second or third day telling me a newer version is available.
I run the update, which appears to work appropriately, telling me the program
engine and the database have been appropriately updated. However, the
version number being updated to each time is 1.1.1347. Somehow the update
engine is not catching that I already have the latest version. Second, when
the update is performed, it deletes all the icons from my QuickLaunch area on
my task bar. Although the update process says nothing about rebooting, I
have to reboot to get my icons back. These are both only minor irritants,
but I'd appreciate any information that might help me avoid them.
 
This does sound as though the program update is not completing correctly--I
think that the loss of system tray icons indicates an Explorer crash.
Windows recovers from this, but each individual icon provider must provide
the right code to have their icon reappear in such a situation, and I know
from personal experience that not very many of them do this.

I would suggest shutting down real-time protection in your antivirus
application, and as many other third party applications or drivers as you
can easily manage, and then running an update install of the 1347 code you
have in place: start, control panel, add or remove programs, Windows
Defender, change, update.

See whether that completes without the crash--and eliminates the repeated
update notices. Note that there is a definition and engine update
today--but I believe we are talking about the UI update involving a separate
download, in this message.
 
Thanks. I'll give that a shot if something I just discovered doesn't solve
the problem. It turns out that Beta1 (labelled Microsoft Antispyware, not
Defender) was still loading and running in my system tray. So Beta 2 was
having to load on top of Beta 1. I've removed Beta 1. If getting rid of
that potential impediment doesn't solve the problem, I'll try your "clean as
possible update" procedure.
 
There may be some common factor in the non-removal of beta1 and incomplete
install of the new beta2 build--simplify things and see if you can get it to
behave. I'd tend to look at antivirus and other malware-protection type
apps.

--
 
Back
Top