New WD definitions 1.14.1325.6

  • Thread starter Thread starter Pat Willener
  • Start date Start date
P

Pat Willener

Just got the newest definitions 1.14.1325.6 for Windows Defender via
automatic updates. No problems with the update.
 
Good to know and lucky you. I had to manually remove the old 1314 with KB
Article 915105 and Run
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} for the new 1325 to
update. If I don't do it manually it falls into a loop with 1325. I think
this happens only in the very old original Defenders betas.
 
Hi

Yup, no problems.

It would be really interresting if users with problems also
running any Symantec/Norton NIS product ?

regards
plun
 
*****************************
No problems with WD update on three PC's
PC1 WIN XP PRO, Norton (Symantec) AV corporate version, Windows Firwall
PC2 WIN XP HOME, Norton (Symantec) AV, Windows Firewall
PC3 WIN XP HOME, NOD32, Windows Firewall
In fact Plun I have had NO problems with any of the WD installs or updates
from the start.
*****************************
 
plun said:
Hi

Yup, no problems.

It would be really interresting if users with problems also
running any Symantec/Norton NIS product ?

regards
plun
Click to expand...

I had the repeating loop problem but WD updated after the
http://support.microsoft.com/?kbid=915105 temporary fix. No Norton here (I
took the pledge) but I am also running (just not at same time) Spybot 1.4,
Zone Alarm Internet Security Suite, SpySweeper 4.5 in addition to WD.

2.8GHz, 1GB RAM, two 120GB HDDs, XP Home SP2.
 
Hi

Well, it´s the NIS version I suspect, have seen several users with
NIS 2005 with this problem.

Firewallrules or script blocking.... ??
Or blocked Live Update ?

regards
plun
 
For the second update in a row the update installed successfully first time
from Microsoft updates :-). I have NAV 2005, ZA free, XP SP2.
 
I be laughing when you guys can't get Vista to work!

I am having this problem.

Windows Defender definitions haven't been updated in 18 days..

Have manually updated a dozen times, and WD says downloads complete,
WD is now up-to-date. BUT, problem persists.

AND WD shows in the tray ALL THE TIME, with at little orange exclamation mark!

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1286.1

WinXP SP2
---------------------------------------
ZoneAlarm version:6.1.737.000
TrueVector version:6.1.737.000
Driver version:6.1.737.000
Free Version
--------------------------------------------
AVG 7 Free Version
Ewido Networks (14 trial guard, then free scanner)
--------------------------------------

If I did inadvertently block the update module with ZA I wouldn't know as MS
probably has some nonsense abbreviation for the program.

That goes for anything, when ZoneAlarm pops up and says.. Billy Bob
X654241575m3 demands access to the internet, then who the hell is Billy Bob
X654241575m3?
 
At least two executables need Internet access:

MSMPENG.exe--the scanning and real-time protection engine--this provides the
Windows Defender service.

mpcmdrun.exe -- this does updating and scanning.

Updates are done via AutoUpdate--does AutoUpdate work on your system?

You can also get updates by going to Windows Update--which is what I'd
recommend that you try next--your system has clearly updates at least once,
but is not current.

It's possible that what is wrong is that the current definitions in place
are not completely installed. The usual fix for this is to use the
resolution steps in this article:

http://support.microsoft.com/?kbid=915105

--
 
If your signature version is 1.13.1286.1, you have a problem The current
one is 1.14.1325.6. Try running Windows Installer Cleanup - remove Windows
Defender Signatures - then update Windows Defender.
 
NO GO - Kaput

mpcmdrun.exe
msmpeng.exe
msascui.exe

All added to Zonealarm and given ALL permissions..

Zonealarm lists them as.

service executable
user interface
command line utility

Which makes them hard to ID.

Also ran disk cleanup. Shut down and restarted WD. I have been using WD
from the 1st time available and had previously been using MS anti spyware
(Beta 1)

So, no problems until about 3-4 days ago..

May be best to ditch it - and - get another download. Try that.
 
http://support.microsoft.com/?kbid=915105

RESOLUTION
To resolve this problem, follow these steps: 1. Remove the current signature
file. To do this, click Start, click Run, type Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}, and then click OK.
2. Open Windows Defender. To do this, click Start, click Programs, and then
click Windows Defender.
3. Check for new definitions. To do this, click the Help options arrow next
to the Windows Defender Help icon, click About Windows Defender, and then
click Check for Updates.


URGENT TO EVERYONE WHO POSTED EVERYWHERE.................

**THIS FIXES THE PROBLEM***

*Thanks to .:Bill Sanderson:. for posting
Sorry I missed this at 1st trying to muck around with Zonealarm.

*Now have..*
Little green tick on WD, and it disappeared as should be.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.14.1325.6
 
Its easy to get scared by the appearance at first glance in the newsgroups
that "everyone is having a problem."

This really isn't true--the majority of users are not having problems, and
don't even know about the newsgroups.

And, for those that are, that article provides quick relief for most, but
not all. If you read a bit more, there's a second article that usually
takes care of the remaining few.

Glad that worked!
 
Yes, I see, turn automatic updates on.. some people may have this off.

I suppose..
1. Click Start, click Run, type wuaucpl.cpl, and then click OK.
2. Click Automatic (Recommended), and then click OK
works faster than..

Start> control panel> security center> automatic updates > ON (recommended)

as some people may have 'classic view' set.

Sometimes I also wonder that with Windows, why not name programs say -
Windows Defender.exe, Windows Defender Updater.exe and Windows Defender
Command Line.exe.

I made a little program in Delphi many years ago and it's named
'Graham`s Fabwriter.exe' exactly like that including * `s *. Seems to work
OK with that name, but I could have named the exe GfabWri.exe. I know what
that means, but if it was in wide distribution, would other people?
 
John

Problem solved. Look at second furball under Bill Sanderson; he solved the
problem for me. Or gave me the MS link to delete the installed update. I did
not think disk clean-up would work because I don't think WD team think their
updates are 'junk' files. Besides I have crap cleaner or CCleaner to run on
every PC start.

Article: http://support.microsoft.com/?kbid=915105

CAUSE
This problem occurs because after Windows Defender Beta 2 has been
reinstalled, it does not automatically obtain new definitions until the next
definition update is published on the Windows Update Web site.

RESOLUTION
To resolve this problem, follow these steps: 1. Remove the current signature
file. To do this, click Start, click Run, type Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}, and then click OK.
2. Open Windows Defender. To do this, click Start, click Programs, and then
click Windows Defender.
3. Check for new definitions. To do this, click the Help options arrow next
to the Windows Defender Help icon, click About Windows Defender, and then
click Check for Updates.

Mine was not reinstalled, problem just happened 3-4 days ago.. Had MSAS
(Beta 1) from the start, uninstalled it and downloaded WD (Beta 2) Worked
perfectly - up until 3-4 days ago.

Anyway, all fixed now. Thanks
 
In a corporate LAN, autoupdate may not connect to Microsoft. There are at
least three Microsoft-supplied solutions it can connect to, and a number of
third-party ones as well. This gives rise to a good many of the "never
updates" threads here. The administrators of such networks want control
over what software is run and what updates are handed out--and lots of
Microsoft Antispyware installs got by under the radar--but Windows Defender
tries to play by the rules.

--
 
Back
Top