Bat File Bug (for Developers)

[Mike Lareau]

Hello, I physically invoked a DOS bat file containing the
following command, repeated about 15 times for different
dlls:
%SystemRoot%\system32\regsvr32.exe c:\LMS\some
dll.dll /u /s

The Microsoft anti-spyware app caught the bat file
execution and presented a dialog that allowed me to
indicate whether to block or allow execution and to
remember the action via a checkbox at the bottom of the
form.
I dismissed the dialog by clicking the allow button and
leaving the "remember..." checkbox checked. Howevever,
the dialog came-up over and over in an endless loop--I
stopped at over 50 cycles having to kill the 2
antispyware processes!
Afterward, I checked the application agent script
checkpoint and saw that it had not "remembered" my bat
file exemption.
This appears to be a very obvious bug.

Thanks,

M. Lareau

 

[Andre Da Costa]

From Steve Dodson:
This is a known issue when running in an enterprise. I wrote the following
KB to describe this...

http://support.microsoft.com/default.aspx?scid=kb;en-us;892375

 

[Bill Sanderson]

One serious bug in this situation is that the directory context in which the
batch file executes in the situation in which you've just answered the
prompt--is%windir%\system32.

This happens only when the prompt comes up--if you succeed in having your
preference remembered, the next execution goes normally.

However--in your case, it looks like full paths are given for everything, so
I don't see that bug as the issue.

I'm not sure whether there's a bug in Microsoft Antispyware not remembering
your preference--not a fair test--you bombed out in the middle! There are
reports here of individual installs which fail to remember various user
choices/preferences, though.

I don't know what to think about the looping behavior. Can you simplify the
batch file down to one command or so, and see whether you can get that
accepted and remembered as good?

 

[Mike L.]

Steve, I previously invoked the bat file via Windows
Explorer--the bat file is on a Novell network share (I
have full rights there) so Systems Management Server
doesn't really come-into play in my environment as
mentioned in your KB. Afterward, I copied the bat file
locally and invoked it getting the same looping result
(XP Pro SP1, admin rights).

-Mike