A
Adam Albright
Microsoft's "Defender" is a laughing stock. Not only won't it defend
you it often blocks perfectly fine applications from working. Defender
(DEP) is suppose to "protect" you from some unseen Virus and other
threats. I guess the idiots of Redmond didn't think to protect Vista
users from the biggest and most nasty virus of all... sloppy Windows
code that infests Vista itself.
Let me explain...
Prior to SPI I Data Execution Prevention at least did no harm. Now it
can interfere with all kinds of things if you change options from the
default. Why would you want to change settings? Because Windows being
such a poorly written pile of crap, some applications, including
Windows own crap built into Windows can't have DEP "watch" it. I
mostly had trouble with media files throwing COM Surrogate errors.
The fix was simple enough or should have been. Go to System
Properties, Settings, Advanced Data Execution Prevention. Click "turn
on DEP for all programs and services except those I select:" I had COM
Surrogate in this list along with a couple others. The laughingly
stupid thing was even telling Vista to not use DEP for COM Surrogate
it still would anyway, but in the exclude mode at least this error
didn't pop up as often as when it wasn't checked.
Now one thing the idiots of Redmond often do with a Service Pak is
once it is installed it reverts many system changes you might have
made back to their defaults. So in effect DEP was set for essential
Windows programs and services only. This way I got COM Surrogate
errors like crazy, so I set it back to what I had prior to SPI, to
skip DEP for the listed applications, ie COM Surrogate.
Were things better? Hell no, the buffoons of Redmond made things
worse. Now my spelling checker was considered a "threat" by DEP and
moronic Windows told me at boot since the spelling checker is a TSR
application that it had to shut it down for unknown reasons. Ok fine I
don't use it much anyway.
Yesterday I needed to access some Excel spreadsheets, Vista the
steaming pile of dog shit it is said they were in use by another user,
they weren't, but trying to reason with Windows is useless so I said
to myself, screw it, I'll do that job tomorrow.
Well it is tomorrow and a new day. So soon as I boot DEP (Defender)
still nags about the spelling checker and shuts it down. I go to open
a Excel Spreadsheet, Vista nags it has to shut the application down
because it isn't working. I try to open some Word documents. Same mind
numbing stupid DEP message that it needs to shut Word down too. So now
I can't access any spreadsheets or Word documents or my spelling
checker.
I go back to Data Execution Prevention, return it to it's default
setting where it runs for only essential Windows programs, I reboot
and now I can use my spelling checker and Vista no longer thinks Excel
or Word is a threat and lets me run those too.
So instead of being an improvement SPI if I elect the option to bypass
DEP so it won't nag about COM Surrogate errors, stupid in itself now
crashes Word and Excel in this mode. So to use these two applications
I have to accept constant Com Surrogate errors.
What have I proved. The same story, just a different chapter.
Microsoft does not test the crap it releases, often new versions or
patches are worse than the prior version.
Microsoft should be so ashamed, yea right that will happen some day.
Sure it will.
you it often blocks perfectly fine applications from working. Defender
(DEP) is suppose to "protect" you from some unseen Virus and other
threats. I guess the idiots of Redmond didn't think to protect Vista
users from the biggest and most nasty virus of all... sloppy Windows
code that infests Vista itself.
Let me explain...
Prior to SPI I Data Execution Prevention at least did no harm. Now it
can interfere with all kinds of things if you change options from the
default. Why would you want to change settings? Because Windows being
such a poorly written pile of crap, some applications, including
Windows own crap built into Windows can't have DEP "watch" it. I
mostly had trouble with media files throwing COM Surrogate errors.
The fix was simple enough or should have been. Go to System
Properties, Settings, Advanced Data Execution Prevention. Click "turn
on DEP for all programs and services except those I select:" I had COM
Surrogate in this list along with a couple others. The laughingly
stupid thing was even telling Vista to not use DEP for COM Surrogate
it still would anyway, but in the exclude mode at least this error
didn't pop up as often as when it wasn't checked.
Now one thing the idiots of Redmond often do with a Service Pak is
once it is installed it reverts many system changes you might have
made back to their defaults. So in effect DEP was set for essential
Windows programs and services only. This way I got COM Surrogate
errors like crazy, so I set it back to what I had prior to SPI, to
skip DEP for the listed applications, ie COM Surrogate.
Were things better? Hell no, the buffoons of Redmond made things
worse. Now my spelling checker was considered a "threat" by DEP and
moronic Windows told me at boot since the spelling checker is a TSR
application that it had to shut it down for unknown reasons. Ok fine I
don't use it much anyway.
Yesterday I needed to access some Excel spreadsheets, Vista the
steaming pile of dog shit it is said they were in use by another user,
they weren't, but trying to reason with Windows is useless so I said
to myself, screw it, I'll do that job tomorrow.
Well it is tomorrow and a new day. So soon as I boot DEP (Defender)
still nags about the spelling checker and shuts it down. I go to open
a Excel Spreadsheet, Vista nags it has to shut the application down
because it isn't working. I try to open some Word documents. Same mind
numbing stupid DEP message that it needs to shut Word down too. So now
I can't access any spreadsheets or Word documents or my spelling
checker.
I go back to Data Execution Prevention, return it to it's default
setting where it runs for only essential Windows programs, I reboot
and now I can use my spelling checker and Vista no longer thinks Excel
or Word is a threat and lets me run those too.
So instead of being an improvement SPI if I elect the option to bypass
DEP so it won't nag about COM Surrogate errors, stupid in itself now
crashes Word and Excel in this mode. So to use these two applications
I have to accept constant Com Surrogate errors.
What have I proved. The same story, just a different chapter.
Microsoft does not test the crap it releases, often new versions or
patches are worse than the prior version.
Microsoft should be so ashamed, yea right that will happen some day.
Sure it will.