Bug Report v1.0.615

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

Guest

I see in the list here that v 1.0.701 is riddled too! Yikes.

Anyway, on this older version...when it runs it seems to take command of the
background. Anything on the active screen is unaffected. However, when the
scheduled scan finished, the task bar and anything in the backgound is
unaccessible.

I will try to find the other version later.
 
Find the newer version here:

http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en


However, note that we know of no code changes other than the expiration date
between these versions. You want the new version, because the older version
expires at year end, but don't expect changes in the behaviors.

I think that I've seen what you are experiencing myself--there seems to be a
significant lag--minutes, perhaps--between the time the results screen
appears on the screen, and the time you can actually do anything with it to
dismiss it or move to other parts of the UI.

This will change in beta2, but build .701 is not beta2.
 
There are the changes needed to change the expiration date. What do you see
that is inconsistent with that description? Of course all the pieces have
new version numbers, and new digital signatures.

--
 
Hi Bill,

I think Olivier is trying to get the point across that the Shell Execute Hook is again
showing as an Unknown Shell Execute Hook with this latest update.

This was fixed once before but has been broken again since updating to build 701.

Microsoft.AntiSpyware.ShellExecuteHook.1
"This is an unknown Execute Hook."

Donald Anadell
 
I did understand that. Each piece of code gets recompiled with a new
version number and a new digital signature--that makes it different as far
as the detection mechanisms, and so it is going to show as unknown unless
they get it together to provide the signatures before the code gets out
there--which clearly they didn't this time!

I'll be checking after today's expected definition updates to see whether
they've fixed that yet.

--
 
Bill Sanderson said:
I did understand that.
Click to expand...

Bill, I also understand your point but do not quite agree with what you said:
... but don't expect changes in the behaviors.
Click to expand...

It all depends how much the general behavior depends on the 'right' version
numbers being reported. You can expect anything...
 
Bill Sanderson said:
I'll be checking after today's expected definition updates to see whether
they've fixed that yet.
Click to expand...

Fix verified in 5781 (MSAS ShellExecuteHook is known).
 
So I see! I agree with you that the code is, in fact, different. I don't
believe there is any functional difference except for the version number and
the expiration date, but bugs are bugs--and we could see some other
differences, I suppose.

--
 
Hi Bill,

Thanks for the response. I guess it's moot point now, looks like it's fixed again
with the 5781 defs update:o)

Donald Anadell
 
The remaining issue is whether we'll see new bugs or behaviors from the
program that weren't seen with the previous builds. My understanding is
that we should not, but I'm watching the groups here and trying to keep an
open mind.

--
 
Back
Top