Not installing new update

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

Guest

Downloaded and installed the new update of Defender (beta 2) about 5 times
already this morning, and its just not registering that it has downloaded and
installed it and it keeps coming up on automatic updates that i need to
install it... how do i get it to install and register that it has?
 
I have that problem too. I've been trying for a few days to update. I seem
to connect as it get's a "no new engines or components" (or similar
statement), but then the update is not recognised???
Anyone have any ideas why?????
 
Or put Beta 1 back in place until the Beta 2 mess gets sorted out in a few
months.
 
Hi

WD works but need som more trouble shooting then Beta 1

I cannot see any reason to run Beta 1, old scan engine,
old definitions.

Compare it with Sunbelts Counterspy, new engine and up to date
definitions.

http://www.sunbelt-software.com/CounterSpy.cfm

So MSAS beta 1 must be placed in the Recycle bin and rest in peace.

regards
plun
 
Check "About Windows Defender" and if think you will find that it did not
really update to 1.13.1276.16. If it didn't update, run the Windows
Installer Cleanup Utility and remove the Windows Defender Definitions only
(not the Windows Defender program). Then run WD update - either Help,
About, Check for Updates or use Microsoft Update to download and install the
new definitions.

If you don't have the Windows Installer Cleanup Utility, you can download it
from:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

I don't know what causes the failure to update, this method seems to fix the
problem.
 
I had a similar problem yesterday. I waited for 5 min and it updated
automatically. Try pressing autoupdate and wait a couple of min.
 
FWIW, I did a fresh install of beta1 from filehippo today, just to update a
VPC, and to have it handy to see the answers to questions folks may have.

I agree with your thoughts, though.

--
 
I followed that which basically tells you to run
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}
and it said it couldn't find my E:\ drive (which is my USB hard-drive)

I reattached it... ran it again and voila! Signature 16 hurrah. So
there's something in my registry about msiexec which wants e:\ to be present
:(
 
Back
Top