Installation of Beta 2

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

Guest

I tried to install beta 2 I got an error message to unistall the old version
using Add Remove I unistalled the old version rebooted the computer and went
to install beta2 again it said it was still installed?
 
Robin I went to the proper forum for installation and used the windows
install remover tool found the actual file causing the problem but then it
said that it couldnt insatll it because windows one live was installed. I
unistalled windows one live and it installed ok. Thanks. Dwain
 
What version of Windows Live OneCare was installed? If you were running the
beta of 1.5---that already includes antispyware--I believe equivalent to
Windows Defender.

--
 
Yes Bill, it's using the same core service, MsMpEng.exe behind the OneCare
GUI, it simply disables Defender's GUI. The files are also installed in the
OneCare Antivirus folder.

Bitman
 
Thanks--I don't have one to look at, but that's what I'd expect--didn't want
to say it outright!
--
 
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on Vista
RC2 to see what's been included and what hasn't and also what happens when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here to
post a link once I've posted the results.

Bitman/OneCareBear
 
Bill i am a vb.net programmer and have a thought abut this isnt that like
the old vb days DLL HELL pardon the expression. Maybe they should rename it
or put it in a different namsspace that would prevent this from happening in
the future. That was the whole reason for designing dot net framework I
thought. Anyway why couldnt they be run togheter yes probably counter
productive but a whole lot of less headaches for Microsoft. Thanks for your
input yes I was using the latest version of One Care

Bitman said:
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on Vista
RC2 to see what's been included and what hasn't and also what happens when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here to
post a link once I've posted the results.

Bitman/OneCareBear

Bill Sanderson MVP said:
Thanks--I don't have one to look at, but that's what I'd expect--didn't want
to say it outright!
Click to expand...
Click to expand...
 
FWIW, I've just removed OneCare 1.5 from my laptop running Vista RC2, in
disgust.

It was continually locking up the firewall, telling me that I was connected
to an unknown, untrusted network, while at the same time, it pointed out
that I was connecting to my own WPA2 encrypted AP in my own house!

And there seemed to be no easy way to prevent this behavior. Back to the
Microsoft Beta I was using previously, which didn't muck with the firewall.
--

Bitman said:
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on Vista
RC2 to see what's been included and what hasn't and also what happens when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here to
post a link once I've posted the results.

Bitman/OneCareBear

Bill Sanderson MVP said:
Thanks--I don't have one to look at, but that's what I'd expect--didn't
want
to say it outright!
Click to expand...
Click to expand...
 
It'd be nice if the error was a little clearer. I think the big picture is
great--Microsoft has a coherent strategy for antimalware protection--they
are giving out Windows Defender for free, and they have a couple of packages
that incorporate antivirus capabilities as well, that aren't free: Windows
Live OneCare, and Microsoft Forefront Client Protection. These packages
differ significantly in their user interface and details, but they use
common components and definitions to get the job done.

--

DwainS said:
Bill i am a vb.net programmer and have a thought abut this isnt that like
the old vb days DLL HELL pardon the expression. Maybe they should rename
it
or put it in a different namsspace that would prevent this from happening
in
the future. That was the whole reason for designing dot net framework I
thought. Anyway why couldnt they be run togheter yes probably counter
productive but a whole lot of less headaches for Microsoft. Thanks for
your
input yes I was using the latest version of One Care

Bitman said:
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on
Vista
RC2 to see what's been included and what hasn't and also what happens
when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here
to
post a link once I've posted the results.

Bitman/OneCareBear

Bill Sanderson MVP said:
Thanks--I don't have one to look at, but that's what I'd expect--didn't
want
to say it outright!
--

Yes Bill, it's using the same core service, MsMpEng.exe behind the
OneCare
GUI, it simply disables Defender's GUI. The files are also installed
in
the
OneCare Antivirus folder.

Bitman

:

What version of Windows Live OneCare was installed? If you were
running
the
beta of 1.5---that already includes antispyware--I believe
equivalent to
Windows Defender.

--

Robin I went to the proper forum for installation and used the
windows
install remover tool found the actual file causing the problem but
then
it
said that it couldnt insatll it because windows one live was
installed.
I
unistalled windows one live and it installed ok. Thanks. Dwain

:

funny, I installed it directly over the beta2 and had no problems
on 2
computers
robin
I tried to install beta 2 I got an error message to unistall the
old
version
using Add Remove I unistalled the old version rebooted the
computer
and
went
to install beta2 again it said it was still installed?
Click to expand...
Click to expand...
Click to expand...
 
Bill that was the main reason I removed one care from my system because it
disabled the firewall all together. I coild not enable or disable it because
it was all greyed out. I am greatful for Microsofts kind initiative I really
like Windows Defender had it since it first came out in beta and never
experienced any problems and the price is excellent.

Bill Sanderson MVP said:
FWIW, I've just removed OneCare 1.5 from my laptop running Vista RC2, in
disgust.

It was continually locking up the firewall, telling me that I was connected
to an unknown, untrusted network, while at the same time, it pointed out
that I was connecting to my own WPA2 encrypted AP in my own house!

And there seemed to be no easy way to prevent this behavior. Back to the
Microsoft Beta I was using previously, which didn't muck with the firewall.
--

Bitman said:
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on Vista
RC2 to see what's been included and what hasn't and also what happens when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here to
post a link once I've posted the results.

Bitman/OneCareBear

Bill Sanderson MVP said:
Thanks--I don't have one to look at, but that's what I'd expect--didn't
want
to say it outright!
--

Yes Bill, it's using the same core service, MsMpEng.exe behind the
OneCare
GUI, it simply disables Defender's GUI. The files are also installed in
the
OneCare Antivirus folder.

Bitman

:

What version of Windows Live OneCare was installed? If you were
running
the
beta of 1.5---that already includes antispyware--I believe equivalent
to
Windows Defender.

--

Robin I went to the proper forum for installation and used the
windows
install remover tool found the actual file causing the problem but
then
it
said that it couldnt insatll it because windows one live was
installed.
I
unistalled windows one live and it installed ok. Thanks. Dwain

:

funny, I installed it directly over the beta2 and had no problems
on 2
computers
robin
I tried to install beta 2 I got an error message to unistall the
old
version
using Add Remove I unistalled the old version rebooted the
computer
and
went
to install beta2 again it said it was still installed?
Click to expand...
Click to expand...
Click to expand...
 
DwainS, It's supposed to disable the Windows Firewall, since that is repaced
by the OneCare firewall which is managed within the OneCare GUI.

Bill, Read your post and replace the words OneCare v1.5 with Defender, then
imagine you're reading this sight unseen as the moderator.

I understand your backing out to get back in operation, though I experienced
exactly the same issue with today's update and had no apparent real effects,
at least relating to Internet access. This was the same even if I manually
changed the network back to Private from Public, which was the actual effect
of the change. I don't know exactly what effects this would have on sharing,
so maybe you can shed some light on this, over in the WLOC v1.5 Beta forum
would be best. I haven't posted about it yet myself because I haven't
determined any real effects other than the unrequested change from Private to
Public in my case, since I don't use sharing.

As I mentioned here earlier, I've performed a couple simple tests in
response to some questions about the Antispyware components in Windows Live
OneCare v1.5 Beta, though I still have more to test. Heres the link to the
thread containing my post if you're interested.
http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=855966&SiteID=2

Bitman

DwainS said:
Bill that was the main reason I removed one care from my system because it
disabled the firewall all together. I coild not enable or disable it because
it was all greyed out. I am greatful for Microsofts kind initiative I really
like Windows Defender had it since it first came out in beta and never
experienced any problems and the price is excellent.

Bill Sanderson MVP said:
FWIW, I've just removed OneCare 1.5 from my laptop running Vista RC2, in
disgust.

It was continually locking up the firewall, telling me that I was connected
to an unknown, untrusted network, while at the same time, it pointed out
that I was connecting to my own WPA2 encrypted AP in my own house!

And there seemed to be no easy way to prevent this behavior. Back to the
Microsoft Beta I was using previously, which didn't muck with the firewall.
--

Bitman said:
Though it uses the same core as Defender, the file versions are wildly
different, so they're obviously compiled specifically for the features
supported [or not] by the WLOC GUI.

I'll be doing some testing of [test] malware and the Defender GUI on Vista
RC2 to see what's been included and what hasn't and also what happens when
the Defender GUI is enabled, which I assume now is a bad thing.

I'll be postiung this in the WLOC v1.5 Beta forum, but I'll return here to
post a link once I've posted the results.

Bitman/OneCareBear

:

Thanks--I don't have one to look at, but that's what I'd expect--didn't
want
to say it outright!
--

Yes Bill, it's using the same core service, MsMpEng.exe behind the
OneCare
GUI, it simply disables Defender's GUI. The files are also installed in
the
OneCare Antivirus folder.

Bitman

:

What version of Windows Live OneCare was installed? If you were
running
the
beta of 1.5---that already includes antispyware--I believe equivalent
to
Windows Defender.

--

Robin I went to the proper forum for installation and used the
windows
install remover tool found the actual file causing the problem but
then
it
said that it couldnt insatll it because windows one live was
installed.
I
unistalled windows one live and it installed ok. Thanks. Dwain

:

funny, I installed it directly over the beta2 and had no problems
on 2
computers
robin
I tried to install beta 2 I got an error message to unistall the
old
version
using Add Remove I unistalled the old version rebooted the
computer
and
went
to install beta2 again it said it was still installed?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top