Left taskbar bug not fixed in MSAS 1.0.613

  • Thread starter Thread starter Leo Feret
  • Start date Start date
L

Leo Feret

After installing MSAS 1.0.613 over 1.0.509, I was pleased to see most
floating notification windows do not automatically float anymore from
bottom to top of the screen so fast they cannot be read. However, when
the program invoked auto-update the first time (to get signature file
5727 which was already manually installed), ZoneAlarm Pro flagged this
as a process from a new program and asked if I wished to accept it,
which I did. Then the unreadable MSAS blue screen swept by from top to
bottom as it's been doing since January.

However other MSAS screens have not shown this behavior and work as
expected; e.g. allowing me to click on a choice, so the bug is mostly
fixed.

--
Leo Feret - "I'm not always at the keyboard;
·|Ô¿Ô¬|· sometimes I use the trackball."
____________________________________________
"When we get injured, all it says is 'one soldier wounded.' Not that a
soldier has lost an arm or a leg, or how hard that is." - Specialist
Robert Acosta
 
I'm afraid I only tested the red threat dialog's in the minimal amount of
testing on this issue I've done.

I'll see if I can run some installs with a vertical taskbar soon to check
out the blue dialogs as well.

Thanks for this report.
 
I'm afraid I only tested the red threat dialog's in the minimal amount of
testing on this issue I've done.

I'll see if I can run some installs with a vertical taskbar soon to check
out the blue dialogs as well.

Thanks for this report.
Click to expand...


I experience the same situation, no matter if upgrade or fresh/clean
install, install with taskbar verticaly or horizontally, taskbar locked or
not - always after the installation and setting the taskbar vertically
"toast" fly off..
Even upgrade to 1.0.614 did not repair this.
Is there anything I can do to help to resolve this problem?
 
Can you clarify which dialogs are flying? I've only tested with a red
threat dialog, so far.

These are my steps:

On 613 or 614:

Drop to a command prompt, and cd to the %windir% (winnt or windows,
depending)

MD winlogon.exe <enter>

Watch for the dialog. Respond clean threat.

RD winlogon.exe <enter>

This is a harmless test, and this dialog doesn't fly for me.

--
 
Can you clarify which dialogs are flying? I've only tested with a red
threat dialog, so far.
Click to expand...

The first "test" is the alert informing about the new signatures (as
1.0.613 and 1.0.614 overwrite the last 5727 with 5725 version)
These are my steps:
On 613 or 614:
Drop to a command prompt, and cd to the %windir% (winnt or windows,
depending)
MD winlogon.exe <enter>
Watch for the dialog. Respond clean threat.
RD winlogon.exe <enter>
Click to expand...

Made this test (on 1.0.614) - and all seems to be OK - this alert does not
fly!

This is a harmless test,
Click to expand...

Yes, I know :)

and this dialog doesn't fly for me.
Click to expand...

For me to, so the problem for now is surely with new signatures alert.
I will try to find a way to make green, yellow and blue dialogs tests.
 
Can you clarify which dialogs are flying? I've only tested with a red
threat dialog, so far.

These are my steps:

On 613 or 614:

Drop to a command prompt, and cd to the %windir% (winnt or windows,
depending)

MD winlogon.exe <enter>

Watch for the dialog. Respond clean threat.

RD winlogon.exe <enter>

This is a harmless test, and this dialog doesn't fly for me.
Click to expand...

The test for the blue threat dialog is a try to modify the
%SystemRoot%\system32\drivers\etc\hosts file (for example adding current IP
address and computer NetBIOS name) - this should be captured by MSAS (if the
MSAS System Agent has this checkpoint enabled, of course) and signalized
with blue dialog box.

And this dialog box does not fly off the screen, "glued" as the the red one
:-)
Again - only the info about new definitions appears to run away.
 
That's very helpful--looks like they missed one kind of dialog (well--maybe
more--there are the ones about new code versions being available that are
very infrequent.)

I don't know what the chances are of this getting fixed--rather low, I
suspect, before beta2.

--
 
That's very helpful--looks like they missed one kind of dialog
(well--maybe more--there are the ones about new code versions being
available that are very infrequent.)

I don't know what the chances are of this getting fixed--rather low, I
suspect, before beta2.
Click to expand...

You are maybe right.. Let's wait for Beta 2, then :-)
 
Back
Top