Safe Mode

  • Thread starter Thread starter Ira
  • Start date Start date
I

Ira

I find many instances where to solve a problem with MSAS it is advised to
restart in safe mode. I think that this is really not an acceptable
solution. To do this means that one is unable to set a scheduled run. Safe
mode should be removed and the problem should be fixed and not having to run
in safe mode. I think that this is a very good example of why open source
is necessary otherwise MSAS can never be run in Automatic Mode as long as
Safe Mode is a fix.
Ira
 
I believe that if there is "Open Source" then not only would MS be able to
send changes but users would have the ability to fix problems themselves. I
know that this would lead problems but after almost a year of reporting the
identical problems from many many users some help is overdue. For every new
user the same problems are reported again and again and the answer is always
the same--wait for Beta 2. I for one am tired of reading "no fix yet. I no
longer care if there are more beta releases.At the least some problems would
be fixed. Presently I think that MS is driving new novices away. It
appears to them that MS can't or wont fix problems.
Ira
: How does "open source" solve this problem? (I don't think it is going
: away...)
: --
:
: : >I find many instances where to solve a problem with MSAS it is advised to
: > restart in safe mode. I think that this is really not an acceptable
: > solution. To do this means that one is unable to set a scheduled run.
: > Safe
: > mode should be removed and the problem should be fixed and not having to
: > run
: > in safe mode. I think that this is a very good example of why open
source
: > is necessary otherwise MSAS can never be run in Automatic Mode as long
as
: > Safe Mode is a fix.
: > Ira
: >
: >
: > --
: > Ira
: >
: >
:
:
 
You can, of course do the scans in normal mode, and if anything is found you
can try and have MSAS remove it in that mode. The reason why when something
is found, the recommendation is to scan in safe mode, is because often the
malware will be loaded and running in normal mode, and MSAS (and other
removal tools) cannot access the file(s) to delete or quarantine them. In
safe mode only the basic set of Windows processes is loaded, hence removal of
malware files is easier and more complete.
 
This issue is tied to the System Startup thread below......
It was (and still is) an update issue ..... remember the can connect to the
update server issue last week .... All your coders start there ..... i did
it already...
microsoft needs to patch XP first and stop trying to intergrate Vista code
into XP so soon ... dont test this on us as a beta issue ... it causes
problems all around...
the WHOLE issue lies in the MSAS update you guys released last week...
heres a hint...... think about how MSAV writes files to reload on restart
after an update is fired .... good luck!
 
There is no Vista code in beta1.

The problem with updates has nothing to do with either the .701 code update
for beta1 or with any particular definition update.

--
 
Beta1 has been a relatively static product--It has a number of
idiosyncracies (bugs!) that are annoying, but don't prevent the program from
doing very useful work--cleaning many, many bugs.

The need for safe mode when cleaning some malware does not seem to me to be
connected at all to the above. I do believe that beta2 will do a better job
of cleaning some bugs, but I also suspect that safe mode will continue to be
a necessity. Certainly Symantec recognizes this, in terms of virus
cleaning.
 
Back
Top