F
Frank Haber
I'm saying goodbye to this beta/preview. I just can't support a product I
can't believe in - there are absolutely no controls in this thing, no user
options. I can see that there's a market for that, a big mass market. It's
just that I wouldn't use it, and I don't recommend what I won't use. Insofar
as the experienced-user/word-of-mouth/early-adopter mini-segment (my segment)
still counts in a dumbed-down world, you have my vote - a vote with my feet.
Update flakiness and confusion were only minor irritations. The percieved
speed hit of running full-time protection was trivial compared with (shudder)
Symantec's. I can't speak to detect/remove capability, because I didn't have
any infections.
I guess the tipping factor was a quite bothersome 0x8DDD0018 WinUpdate problem
I had on one of my main machines, SP2, vanilla 3.2 Dell, no new software
recently, iTunes and MS Live Meeting wrapper the only recent uninstalls. I
keep this machine pretty lean and crisp.
None of the elaborate svcs-fiddling (autoupdate, event), reregistrations, or
COM+ reinstall* seemed to help. Instead of deleting the update history db, I
uninstalled Defender, ran MSI cleanup2 (nothing untoward), then tried System
Restore. This time Restore was good to me, restoring Update functionality and
completely eliminating a 1-2 minute period of unusabilty after turnon and
reboots. (This "thinking delay," which had only a moderate amount of disk
activity, had been getting longer and longer.)
I can't really coherently single out Defender for sole blame (interaction?),
but combined with the bad taste in my mouth, I'd reached the tipping point. I
never had a lick of trouble with Beta 1/Giant, and I gather I'm not alone in
this. Sorry.
* had to reinstall COM+ twice. The first time I got this peculiar errmsg:
"Sub-component COM+ raised an exception while processing the
OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\src\complussetup\comsetup\ccompluscore.cpp (line 565) Error
Code = 0x80040206 An unexpected internal error was detectedThe COM+ event
classes could not be registered"
can't believe in - there are absolutely no controls in this thing, no user
options. I can see that there's a market for that, a big mass market. It's
just that I wouldn't use it, and I don't recommend what I won't use. Insofar
as the experienced-user/word-of-mouth/early-adopter mini-segment (my segment)
still counts in a dumbed-down world, you have my vote - a vote with my feet.
Update flakiness and confusion were only minor irritations. The percieved
speed hit of running full-time protection was trivial compared with (shudder)
Symantec's. I can't speak to detect/remove capability, because I didn't have
any infections.
I guess the tipping factor was a quite bothersome 0x8DDD0018 WinUpdate problem
I had on one of my main machines, SP2, vanilla 3.2 Dell, no new software
recently, iTunes and MS Live Meeting wrapper the only recent uninstalls. I
keep this machine pretty lean and crisp.
None of the elaborate svcs-fiddling (autoupdate, event), reregistrations, or
COM+ reinstall* seemed to help. Instead of deleting the update history db, I
uninstalled Defender, ran MSI cleanup2 (nothing untoward), then tried System
Restore. This time Restore was good to me, restoring Update functionality and
completely eliminating a 1-2 minute period of unusabilty after turnon and
reboots. (This "thinking delay," which had only a moderate amount of disk
activity, had been getting longer and longer.)
I can't really coherently single out Defender for sole blame (interaction?),
but combined with the bad taste in my mouth, I'd reached the tipping point. I
never had a lick of trouble with Beta 1/Giant, and I gather I'm not alone in
this. Sorry.
* had to reinstall COM+ twice. The first time I got this peculiar errmsg:
"Sub-component COM+ raised an exception while processing the
OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\src\complussetup\comsetup\ccompluscore.cpp (line 565) Error
Code = 0x80040206 An unexpected internal error was detectedThe COM+ event
classes could not be registered"