Windows Defender Beta

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

Guest

I downloaded the beta version, and now I am deluged by "updates are ready
reminders." Is this a problem or what? It seems the same updates arerepeaing.
Any ideas??Thanks in advance.
jackson
 
Copy this text and paste it in RUN box to see if it helps:

Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

To get to run box, START, RUN

Then Launch Defender and from about box you can update it.

hth
 
Agreed. Going to Windows Update and doing an express scan is an alternative
to help, about, check for updates, too.

--
 
Thanks, I tried Anonymous's suggestion and it worked. Program is running like
a top. Appreciate the help!!!!!!
Jackson
 
ANONYMOUS said:
Copy this text and paste it in RUN box to see if it helps:

Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

To get to run box, START, RUN

Then Launch Defender and from about box you can update it.

hth
Click to expand...
 
This solution has not worked for me.

I am on version 1.1.1347.0
Engine 1.1.1303.0
Definition version 1.0.0.0

I have unisntalled, reinstalled, run the above fix and I still get the
message that I am up to date.

I have been on previous version with no problems until 1347 cam eout.

Richard
 
Have you also gone to Windows Update, done an express scan, and applied all
offered updates?

--

Richard said:
This solution has not worked for me.

I am on version 1.1.1347.0
Engine 1.1.1303.0
Definition version 1.0.0.0

I have unisntalled, reinstalled, run the above fix and I still get the
message that I am up to date.

I have been on previous version with no problems until 1347 cam eout.

Richard
Click to expand...
 
Same issue here with 1347 build. All windows updates (except 1.1.1396.12 over
and overand over). Went back to ver 1.1.1051 and now its stuck at sig version
1395 even though Win update indicates 1396.12 successful. Perhaps the new
sigs only work with the 1397 build? Ans for some reason the 1397 build will
not update at all? All posted "fixes" and updates have been done sever al
times. Now the Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} "fix" will
not even completely run complaining the installer package is not there
blah,,blah,,blah. Guess the new beta really hosed up things here. Any ideas
how to proceed?
 
Okay, I ran Microsoft update and now it reads:

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1303.0
Definition Version: 1.14.1396.12

This is bizarre as the first thing I had done on this machine was to install
the automatic update for Defender which did not take.

Thanks for this suggestion. Hopefully, she will stay on track now for
awhile.
 
You're in good shape for the moment. Sometimes there's a prerequisite at
Windows Update which is needed before the automatic updates withing the
program will function. I've not been able to tie it down, but the simple
advice of just going to Windows Update and doing an express scan and
applying everything offered, should cover the bases.

--

Richard said:
Okay, I ran Microsoft update and now it reads:

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1303.0
Definition Version: 1.14.1396.12

This is bizarre as the first thing I had done on this machine was to
install
the automatic update for Defender which did not take.

Thanks for this suggestion. Hopefully, she will stay on track now for
awhile.
Click to expand...
 
I'm not sure this is anything new, but it is messed up.

Usually, I'd recommend downloading and installing the Windows Installer
cleanup utility, and using it to remove --ONLY Windows defender signatures.

However, I'd like to try a variation if I can:

1) Start, control panel, add or remove programs, Windows Defender, click
here for support information, repair.

Follow that up with a visit to Windows Update, express scan, and see if
definitions are offered and install.

If that doesn't work, get the cleanup utility:

http://support.microsoft.com/?scid=kb;en-us;290301

download, install, go to Start, all programs, and run it, and remove just
Windows Defender signatures.

Then do the repair step, followed by an attempt to get defs--you can go
either way--

Give it a little time--sometimes the update succeeds when the same operation
appeared to fail at an earlier time.

--

SBTRS said:
Same issue here with 1347 build. All windows updates (except 1.1.1396.12
over
and overand over). Went back to ver 1.1.1051 and now its stuck at sig
version
1395 even though Win update indicates 1396.12 successful. Perhaps the new
sigs only work with the 1397 build? Ans for some reason the 1397 build
will
not update at all? All posted "fixes" and updates have been done sever al
times. Now the Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} "fix"
will
not even completely run complaining the installer package is not there
blah,,blah,,blah. Guess the new beta really hosed up things here. Any
ideas
how to proceed?
Click to expand...
 
Okay, now that I have this machine happy, happy again, is there any reason to
update to 1347 on my office machines? They are on current signature, so are
they missing anything or should I just let the dust settle and see what comes
along in the future?
 
If you have a reason to touch a machine, you might want to update to 1347.
The only thing I've seen that might be new with 1347 are the complaints of
excessive restore point creation, and I don't have any handle on them at
all--no idea what's going on.

There will eventually be an update auto-notification, I believe.
--
 
OK I had already run the cleanup util before and it did not help either.
However, I did just as you said ran the repair, then windows update and the
1402 defs were there today (were not there last night and the 1396 kept
showing up over and over). Let Windows update download and install. Still did
not show up in Win Defender, but Win Update did not show them again either.
Then downloaded the cleanup util via your link and ran it and deleted the Win
Defender sigs ONLY. Then ran "Check for updates" from the Help About option.
Sigs 1.14.1402.2 now appear:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1372.0
Signature Version: 1.14.1402.2

Just wondering if should attempt up update to 1397 now? At least I have a
working/updated copy running now. Also why would Windows update NOT update
the program? Is that something that will have to be done manually from now on?
 
Well thought I would give it another try and "update" to ver 1397. Failed
with the 1.0.0.0 sigs and none of the previous fixes will make it update the
signatures still. Uninstalled it and reinstalled ver 1051 updated via check
for updates and it updated fine. (Windows update did not offer to update to
1402.2 sig again since already had done so). So apparently ver 1397 is "not
quite ready for prime time". Appears 1051 is a bit more functional at this
point. Actually this is the first version that I have had any trouble with
and been using since Microsoft AntiSpam (Actually Giant Company then MS
then WD and no issues ever until now. :(
Maybe next version may work as it should. Guess I will wait and see
 
SBTRS said:
Defender sigs ONLY. Then ran "Check for updates" from the Help About
option.
Sigs 1.14.1402.2 now appear:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1372.0
Signature Version: 1.14.1402.2

Just wondering if should attempt up update to 1397 now? At least I have a
working/updated copy running now. Also why would Windows update NOT update
the program? Is that something that will have to be done manually from now
on?
Click to expand...


Progress--great! This code increment isn't yet available via the update
process. I believe that the intent is to at least have an automated notice
of availability appear at some future point, but I'm not sure whether the
update itself fill be automatic or not. I don't expect manual updates to
be the rule--but this one is in that category, probably temporarily. I've
left my laptop on 1051 just to see what will happen.
 
My Engine is "stuck" at 1.1.1303.0. Defender is up to date. I have gone
numerous times to Microsoft Updates, downloaded and installed all available
updates yet the latest Defender Definitions fail to install.

I don't know why this is the latest Engine when my other PCs are all up to
1.1.1508.0 and install the latest definitions with no trouble. The PCs are
all in a QA test lab and are a mix of Windows 2000 workstations and servers.
The PCs that install the latest versions are a mix of Windows 2000
workstations, servers and XP Pro workstations. I don't understand what is
preventing me from getting the latest Engine.

I've followed all suggestions in these and other Defender threads, and still
no luck. Now I'm stuck with an old Engine version and *ancient* definitions
 
Back
Top