There has to be a script to uninstall Defender Beta 2

[Guest]

Please tell me someone has one available. MS should have provided an easier
solution to uninstalling Beta 2 and reinstalling the official version. Going
to add/remove programs on hundreds of computers (don't ask) to uninstall beta
2 is going to suck.

 

[Dave M]

From the release notes "By design, the final release of Windows Defender
removes Windows Defender (Beta 2)."

http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx

 

[Bill Sanderson MVP]

Check the install group--I've published a command-line uninstall that works
a number of times in that group. If you can't spot it--speak up there, and
I'll find it again and re-post it in response.

 

[Bill Sanderson MVP]

msiexec /uninstall windowsdefender.msi /quiet /log uninstall.log

(found it!)

 

[Guest]

Thanks Bill. Now, can someone explain to me why they released 1592? Turns
out this is the version we are having trouble with and not the beta 2
version(s). Luckily this version didn't hit as many computers as first
thought but still annoying none the less.

Thanks again.

 

[Dave M]

Having 1592 (the first RTM non-Beta release) installed is the exception to
the automatic removal of previous versions when 1593 is installed, in that
case a manual un-install of 1592 is required prior to installing the 1593
update. But going from Beta to 1593 directly without having 1592 should
remove the Beta automatically. I imagine that's why they didn't announce
1592 more broadly, as it only was available for a week or two back in
November.

According to Joe Faulhaber (MSFT):
"As you've noticed, there's a new English verison of Windows Defender on
the
Microsoft download site.
In addition to releasing Japanese and German versions this week, we
refreshed the English version of Windows Defender. Version 1593 includes
enhanced sample submission capability for the Japanese and German versions,
and we wanted to make this functionality available to English users as
well.
By collecting more samples from customers, we are able to create improved
definitions, which help to better protect all Windows Defender users.
If you encounter a file the Windows Defender analysts have requested a
sample of, you will get a dialog listing the files requested and you can
choose which files, if any, to submit for analysis from that dialog."
--
Regards, Dave

Beta Max wrote:> Thanks Bill. Now, can someone explain to me
why they released 1592? > Turns out this is the version we are having
trouble with and not the> beta 2 version(s). Luckily this version didn't
hit as many computers as> first thought but still annoying none the less.>

Thanks again.> > "Bill Sanderson MVP" wrote:> >> msiexec /uninstall

windowsdefender.msi /quiet /log uninstall.log>> >> (found it!)>> >> -->> >>
Please tell
me someone has one available. MS should have provided an>>> easier>>>
solution to uninstalling Beta 2 and reinstalling the official version.>>>
Going>>> to add/remove programs on hundreds of computers (don't ask) to>>>
uninstall beta>>> 2 is going to suck.

 

[Bill Sanderson MVP]

There is a post explaining why 1593 was released--which is basically the
answer to your question--search this group on the key [MSFT] I think, to
catch the messages from Microsoft staff. It is probably possible to write
a script that checks the version number of what is installed--in fact, that
may be among the few things exposed in the policy settings for Windows
Defender--but I couldn't tell you how to do that, I'm afraid.

--

 

[Bill Sanderson MVP]

Thanks--that's the message I was thinking of that gives some information
about why 1593 was released.

 

[Bill Sanderson MVP]

(and I've now looked at the policy settings, and the versions of what is
installed are not exposed that way.)

--

There is a post explaining why 1593 was released--which is basically the
answer to your question--search this group on the key [MSFT] I think, to
catch the messages from Microsoft staff. It is probably possible to
write a script that checks the version number of what is installed--in
fact, that may be among the few things exposed in the policy settings for
Windows Defender--but I couldn't tell you how to do that, I'm afraid.

--

Thanks Bill. Now, can someone explain to me why they released 1592?
Turns
out this is the version we are having trouble with and not the beta 2
version(s). Luckily this version didn't hit as many computers as first
thought but still annoying none the less.

Thanks again.

 

[Guest]

Hi Bill,
Could you please advise on the procedure for running this command line, I'm
not sure. Thanks,

 

[Steve]

Thanks Bill - I tried this but which windowsdefender.msi file do I use?
I tried the latest RTM release and it said it was the wrong version.
So I assume I need the version that I used to perform the original
installation which is Beta2. Am I correct here?

If so, where do I find that pesky B2 msi file?

Stevo

 

[Guest]

Hi Stevo,

I think it is pretty risky getting a Microsoft file except directly from the
source--but in an emergency....
from http://www.filehippo.com
Anti-spyware, click on More...on Windows® Defender:v. 1.1.1593.0 click on
More Info.. Now look on the right side for old versions.

For the benefit of the community reading this post, please rate the pºst.

I hope this post is helpful.

Let us know how it works ºut.

Еиçεl