Windows Defender Error when Disabled through Hardware Profiles

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

Guest

I recently created two Hardware Profiles, Default (with no service changes) ,
and one for Gaming (one of which services I disabled was Windows Defender).
When I restarted under the Gaming profile, right after logon I received a
Windows Defender error message along with a numeric code. I don't recall the
exact error message or code number (though if necessary I can provide them).
I receive no error messages from all the other services I've disabled
(McAfee, etc). Anyway, after closing the error box, the computer works
perfectly fine.

I'm aware that this program is in BETA, so I'm not going to get into a hissy
fit about it. Has anyone else had this issue? If so, is Microsoft planning
on some sort of fix? When I went restared to my Default Hardware Profile I
did not receive the error message, but I did get the "Error 0x80004003
Invalid pointer" error (mentioned on the boards for the first time), and I've
been using Windows Defender for the past 45 or so days. It may just be
coincidental of course, though perhaps they're related?

Anyway, thanks in advance for any help/advice you'd be able to provide.

Operating System: Windows XP Home Edition Service Pack 2
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1353.2
 
The invalid pointer error is a bug which is not yet fixed in code
distributed to us. There's a Microsoft post from Joe Faulhaber which says
this will require a rev to the UI code, which has not yet happened, I
believe.

Personally, I'm pleased that theres an error message when the Windows
Defender service is disabled. This is the service that provides real-time
protection, and services during scans.

Under Vista, the absence of this service would be called out by the Security
Center. Posts here have indicated that Microsoft is considering how to
handle this under XP.

So--I hear you when you say "that's a bug"--but I'm not sure I agree. I
think if you kill the service, you should also kill the auto-start for
MSASCUI.exe--and presumably make sure that there's no scheduled scan job
that will attempt to run, as well.

I'm not sure what the "right way" to do what you are trying to do is--Anyone
else want to take a stab at it?
 
Back
Top