TWO THUMBS DOWN

G

Guest

all they've done is talk to you about crap totally unrelated to this thread. :)

just like family
 
G

Guest

The article about the updates doesn't help.

Besides, I had the update problem BEFORE I uninstalled this product.

Steve Dodson said:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
has the answer you are looking for - :)

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Test0r said:
by the way thanks for responding :)

Test0r said:
If that KB you're working on has a fix on it, wanna just give us a couple
things to try here?

I'm scared, Microsoft Person! Hold me! :-D

you're an insider man help us out!

:

We are aware of the signature update issue and will have a KB shortly.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
yeah I mean this is beta software? I can't even find an area anywhere
that
has a "report bug" link or anything.....

Where do we officially report this issue? Anybody know? Let's flood
these
guys with this issue
 
G

Guest

I see no answer here. . . Problem existed from the very start. Was unable
to update from the get go. No other issues listed here apply to the problem
we are having. Nice try. Care to try again?

Steve Dodson said:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
has the answer you are looking for - :)

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Test0r said:
by the way thanks for responding :)

Test0r said:
If that KB you're working on has a fix on it, wanna just give us a couple
things to try here?

I'm scared, Microsoft Person! Hold me! :-D

you're an insider man help us out!

:

We are aware of the signature update issue and will have a KB shortly.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
yeah I mean this is beta software? I can't even find an area anywhere
that
has a "report bug" link or anything.....

Where do we officially report this issue? Anybody know? Let's flood
these
guys with this issue
 
G

Guest

And Linuxgirl was the one btchn about "Flooding the group". All I want is a
solution. Don't have any suggestions as I have tried all that I have read.
Like Linusgrl, I have install this beta on upwards of 10 systems but am only
having problem with one (so far). But one compromised system is all it takes
for me to make other suggestions to my clients about protection.
 
G

Guest

he doesn't care to try again

Just_wing_n_it said:
I see no answer here. . . Problem existed from the very start. Was unable
to update from the get go. No other issues listed here apply to the problem
we are having. Nice try. Care to try again?

Steve Dodson said:
http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
has the answer you are looking for - :)

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Test0r said:
by the way thanks for responding :)

:

If that KB you're working on has a fix on it, wanna just give us a couple
things to try here?

I'm scared, Microsoft Person! Hold me! :-D

you're an insider man help us out!

:

We are aware of the signature update issue and will have a KB shortly.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
yeah I mean this is beta software? I can't even find an area anywhere
that
has a "report bug" link or anything.....

Where do we officially report this issue? Anybody know? Let's flood
these
guys with this issue
 
G

Guest

Me too! I had it on for about 24 hours and it totally crashed XP. I got the
fabled blue screen saying my computer was stopped. It lost everything, took
3 reboots to get halfway back to where I was. I am now trying to figure out
why IE no longer understands Java ... I had to use FF to write this message!

As far as I am concerned, this thing is pure crap!

Niteowl
 
B

Bill Sanderson MVP

Thanks for posting your experience anyway. Can you say more about what
happened? Did you get definitions updated? Did you do a scan? Was
anything removed? When did you start having problems?

--
 
G

Guest

I followed the download path and installed the whole thing ... standard
install. I let it run all the scans it wanted to ==> no results. Apparently
it thought my system was OK. (EMachines T3265 Athalon 3200, 1.5 G of RAM and
XP home) A while later (?hours) I suddenly got a blue screen that said my
computer had been halted by some dll. And it was totally dead. It accepted
no further input of any sort. I had to shut off power to reboot. It took a
few reboots to get going. Then I noticed that I no longer had Java
capability. I checked add/remove programs under control panel and found
there were 2 Java runtime environments installed ?????????

So, I downloaded a fresh copy of the Jave runtime environment installer,
removed the 2 copies of Java in add/remove, reinstalled Jave and rebooted.
Will see how things run now.

But I want no part of that beta software! Let me know when it is ready for
prime time. Until then, it is on my S*** list.
 
B

Bill Sanderson MVP

I've got Windows Defender running on a machine very similar to that--maybe
it's a 3260, not sure. Haven't seen this on any of the 50 or so machines I
work with.

The multiple java's installed is "the way it works." (according to Sun,
anyway.) However, it isn't the way you should allow it to work--java
versions are replaced largely because of discovered security
vulnerabilities. Sun's own knowledge base articles state that unless the
older vulnerable versions are removed, the system remains vulnerable--far
less so than if the vulnerable version is the default, but still. So the
recommendation, by both Sun and other computer professionals, is to remove
the older versions unless you know them to be required for specific software
that you depend on. This isn't done by the install or update process--you
have to go back and do it manually.

About the only forensic thing I can imagine might still be available would
be to check the System Event log back at the time of that blue-screen crash
to see whether there were any details recorded--sometimes there will be the
name of a driver. Additionally, there might be a minidump. If we can
really tie this occurrence to Windows Defender, a minidump would be of
interest to the development team.

--
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top