Microsoft Antispyware Beta 1 Crashing

  • Thread starter Thread starter Kevan Brown
  • Start date Start date
K

Kevan Brown

I hope no one else has a post on this, as I can't check
since the search feature of this site is currently
disabled.

I've installed Microsoft Antispyware Beta 1 on several
machines running Microsoft Windows XP Professional with
Service Pack 2. All have DEP enabled for all
applications. The product installs fine, and runs fine
under multiple user profiles (both administrative and
limited users) on all machines.

However, on one machine, any time a limited user logs in,
Microsoft Antispyware crashes with the following dialog
box and error message while trying to load:

Title: "gcasServ.exe - Application Error"
Message Text: "The application failed to initalize
properly (0xc0000022). Click on OK to terminate the
application."

If you try to manually launch the application you receive
the following very similar dialog box and error message:

Title: "GIANTAntiSpywareMain.exe - Application Error"
Message Text: "The application failed to initialize
properly (0xc0000022). Click OK to terminate the
application."

The only unique aspect of this machine's configuration is
that it has the following applications installed which the
other machines do not:

Microsoft Visual Studio 6.0 with Service Pack 6
Microsoft Visual Studio.NET 2003

I'm guessing it has something to do with Microsoft Visual
Studio 6.0, since I see some of the executables for
Microsoft Antispyware use the default Visual Basic 6.0
form icon.

Any ideas or workaround?

Thanks,

Kevan Brown
 
We have a couple of fixes for VB runtime issues that are both cosmetic and
functional, but don't run to crashes.

The older fix, now deprecated, was to apply a VB6 runtime SP, currently SP6
SP
http://www.microsoft.com/downloads/...61-7a9c-43e7-9117-f673077ffb3c&DisplayLang=en

KB article about SP
http://support.microsoft.com/default.aspx?scid=kb;en-us;290887

However, Microsoft has suggested an easier fix for the range of issues
covered by this one--typically missing system explorers--here's the new
workaround:
-------------------------------
We believe we have a workaround which is better than installing the VB6 SP.
Can we have users who experience this problem try the following:

1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll" (without the quotes).
3) Close and re-open Windows AntiSpyware

Please let me know if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
As it turns out, all applications written in VB6 which are
on this machine do not run under the profile of a limited
user. This appears to be some sort of bug with Visual
Basic 6.0. They all crash during initialization with the
same error code: 0xc0000022.

There must be some way to correct this. ...and re-
registering the VB6 VM doesn't fix it; if that were broken
I'd have all kinds of other issues.

Thanks,

Kevan Brown
-----Original Message-----
We have a couple of fixes for VB runtime issues that are both cosmetic and
functional, but don't run to crashes.

The older fix, now deprecated, was to apply a VB6 runtime SP, currently SP6
SP
http://www.microsoft.com/downloads/details.aspx? FamilyID=7b9ba261-7a9c-43e7-9117-
f673077ffb3c&DisplayLang=en

KB article about SP
http://support.microsoft.com/default.aspx?scid=kb;en- us;290887

However, Microsoft has suggested an easier fix for the range of issues
covered by this one--typically missing system explorers-- here's the new
workaround:
-------------------------------
We believe we have a workaround which is better than installing the VB6 SP.
Can we have users who experience this problem try the following:

1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll" (without the quotes).
3) Close and re-open Windows AntiSpyware

Please let me know if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
----------------------------------------
Each of these seems reasonably likely to be benign and easy to try out, at
least--so they may be worth trying but I can't say I have high hopes.

Are you getting dumps of any kind for these crashes?

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
I hope no one else has a post on this, as I can't check
since the search feature of this site is currently
disabled.

I've installed Microsoft Antispyware Beta 1 on several
machines running Microsoft Windows XP Professional with
Service Pack 2. All have DEP enabled for all
applications. The product installs fine, and runs fine
under multiple user profiles (both administrative and
limited users) on all machines.

However, on one machine, any time a limited user logs in,
Microsoft Antispyware crashes with the following dialog
box and error message while trying to load:

Title: "gcasServ.exe - Application Error"
Message Text: "The application failed to initalize
properly (0xc0000022). Click on OK to terminate the
application."

If you try to manually launch the application you receive
the following very similar dialog box and error message:

Title: "GIANTAntiSpywareMain.exe - Application Error"
Message Text: "The application failed to initialize
properly (0xc0000022). Click OK to terminate the
application."

The only unique aspect of this machine's configuration is
that it has the following applications installed which the
other machines do not:

Microsoft Visual Studio 6.0 with Service Pack 6
Microsoft Visual Studio.NET 2003

I'm guessing it has something to do with Microsoft Visual
Studio 6.0, since I see some of the executables for
Microsoft Antispyware use the default Visual Basic 6.0
form icon.

Any ideas or workaround?

Thanks,

Kevan Brown
Click to expand...


.
Click to expand...
 
I suspect you may get better information in a developer-related
newsgroup--or at least one related to VB6, rather than this app-specific
group. VB6 is largely G(r)eek to us.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
As it turns out, all applications written in VB6 which are
on this machine do not run under the profile of a limited
user. This appears to be some sort of bug with Visual
Basic 6.0. They all crash during initialization with the
same error code: 0xc0000022.

There must be some way to correct this. ...and re-
registering the VB6 VM doesn't fix it; if that were broken
I'd have all kinds of other issues.

Thanks,

Kevan Brown
-----Original Message-----
We have a couple of fixes for VB runtime issues that are both cosmetic and
functional, but don't run to crashes.

The older fix, now deprecated, was to apply a VB6 runtime SP, currently SP6
SP
http://www.microsoft.com/downloads/details.aspx? FamilyID=7b9ba261-7a9c-43e7-9117-
f673077ffb3c&DisplayLang=en

KB article about SP
http://support.microsoft.com/default.aspx?scid=kb;en- us;290887

However, Microsoft has suggested an easier fix for the range of issues
covered by this one--typically missing system explorers-- here's the new
workaround:
-------------------------------
We believe we have a workaround which is better than installing the VB6 SP.
Can we have users who experience this problem try the following:

1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll" (without the quotes).
3) Close and re-open Windows AntiSpyware

Please let me know if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
----------------------------------------
Each of these seems reasonably likely to be benign and easy to try out, at
least--so they may be worth trying but I can't say I have high hopes.

Are you getting dumps of any kind for these crashes?

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
I hope no one else has a post on this, as I can't check
since the search feature of this site is currently
disabled.

I've installed Microsoft Antispyware Beta 1 on several
machines running Microsoft Windows XP Professional with
Service Pack 2. All have DEP enabled for all
applications. The product installs fine, and runs fine
under multiple user profiles (both administrative and
limited users) on all machines.

However, on one machine, any time a limited user logs in,
Microsoft Antispyware crashes with the following dialog
box and error message while trying to load:

Title: "gcasServ.exe - Application Error"
Message Text: "The application failed to initalize
properly (0xc0000022). Click on OK to terminate the
application."

If you try to manually launch the application you receive
the following very similar dialog box and error message:

Title: "GIANTAntiSpywareMain.exe - Application Error"
Message Text: "The application failed to initialize
properly (0xc0000022). Click OK to terminate the
application."

The only unique aspect of this machine's configuration is
that it has the following applications installed which the
other machines do not:

Microsoft Visual Studio 6.0 with Service Pack 6
Microsoft Visual Studio.NET 2003

I'm guessing it has something to do with Microsoft Visual
Studio 6.0, since I see some of the executables for
Microsoft Antispyware use the default Visual Basic 6.0
form icon.

Any ideas or workaround?

Thanks,

Kevan Brown
Click to expand...


.
Click to expand...
Click to expand...
 
Found the fix. Either the original install for Microsoft
Visual Studio 6.0 or the install for Service Pack 6 for
Microsoft Visual Studio 6.0 is changing the default
permissions on "%SYSTEMROOT%\System32\msvbvm60.dll".

The default permissions include "Read & Execute"
and "Read" for the built-in "Users" group. However one of
these installations are removing that ACL entry.

As an added FYI, the version of "msvbvm60.dll" included
with SP6 for Visual Studio 6.0 is newer than that included
with Windows XP SP2 (or MSIE60SP1): 6.0.9782 vs 6.0.9690.

Thanks,

Kevan Brown
-----Original Message-----
I suspect you may get better information in a developer- related
newsgroup--or at least one related to VB6, rather than this app-specific
group. VB6 is largely G(r)eek to us.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
As it turns out, all applications written in VB6 which are
on this machine do not run under the profile of a limited
user. This appears to be some sort of bug with Visual
Basic 6.0. They all crash during initialization with the
same error code: 0xc0000022.

There must be some way to correct this. ...and re-
registering the VB6 VM doesn't fix it; if that were broken
I'd have all kinds of other issues.

Thanks,

Kevan Brown
-----Original Message-----
We have a couple of fixes for VB runtime issues that are both cosmetic and
functional, but don't run to crashes.

The older fix, now deprecated, was to apply a VB6
Click to expand...
runtime
SP, currently SP6
SP
http://www.microsoft.com/downloads/details.aspx? FamilyID=7b9ba261-7a9c-43e7-9117-
f673077ffb3c&DisplayLang=en

KB article about SP
http://support.microsoft.com/default.aspx?scid=kb;en- us;290887

However, Microsoft has suggested an easier fix for the range of issues
covered by this one--typically missing system explorers-
Click to expand...
-
here's the new
workaround:
-------------------------------
We believe we have a workaround which is better than installing the VB6 SP.
Can we have users who experience this problem try the following:

1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll"
Click to expand...
(without
the quotes).
3) Close and re-open Windows AntiSpyware

Please let me know if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Click to expand...
have
high hopes.
Are you getting dumps of any kind for these crashes?

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I hope no one else has a post on this, as I can't check
since the search feature of this site is currently
disabled.

I've installed Microsoft Antispyware Beta 1 on several
machines running Microsoft Windows XP Professional with
Service Pack 2. All have DEP enabled for all
applications. The product installs fine, and runs fine
under multiple user profiles (both administrative and
limited users) on all machines.

However, on one machine, any time a limited user logs in,
Microsoft Antispyware crashes with the following dialog
box and error message while trying to load:

Title: "gcasServ.exe - Application Error"
Message Text: "The application failed to initalize
properly (0xc0000022). Click on OK to terminate the
application."

If you try to manually launch the application you receive
the following very similar dialog box and error message:

Title: "GIANTAntiSpywareMain.exe - Application Error"
Message Text: "The application failed to initialize
properly (0xc0000022). Click OK to terminate the
application."

The only unique aspect of this machine's configuration is
that it has the following applications installed which the
other machines do not:

Microsoft Visual Studio 6.0 with Service Pack 6
Microsoft Visual Studio.NET 2003

I'm guessing it has something to do with Microsoft Visual
Studio 6.0, since I see some of the executables for
Microsoft Antispyware use the default Visual Basic 6.0
form icon.

Any ideas or workaround?

Thanks,

Kevan Brown


.
Click to expand...
Click to expand...


.
Click to expand...
 
Thanks - that's helpful!

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
Found the fix. Either the original install for Microsoft
Visual Studio 6.0 or the install for Service Pack 6 for
Microsoft Visual Studio 6.0 is changing the default
permissions on "%SYSTEMROOT%\System32\msvbvm60.dll".

The default permissions include "Read & Execute"
and "Read" for the built-in "Users" group. However one of
these installations are removing that ACL entry.

As an added FYI, the version of "msvbvm60.dll" included
with SP6 for Visual Studio 6.0 is newer than that included
with Windows XP SP2 (or MSIE60SP1): 6.0.9782 vs 6.0.9690.

Thanks,

Kevan Brown
-----Original Message-----
I suspect you may get better information in a developer- related
newsgroup--or at least one related to VB6, rather than this app-specific
group. VB6 is largely G(r)eek to us.

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Kevan Brown said:
As it turns out, all applications written in VB6 which are
on this machine do not run under the profile of a limited
user. This appears to be some sort of bug with Visual
Basic 6.0. They all crash during initialization with the
same error code: 0xc0000022.

There must be some way to correct this. ...and re-
registering the VB6 VM doesn't fix it; if that were broken
I'd have all kinds of other issues.

Thanks,

Kevan Brown

-----Original Message-----
We have a couple of fixes for VB runtime issues that are
both cosmetic and
functional, but don't run to crashes.

The older fix, now deprecated, was to apply a VB6 runtime
SP, currently SP6
SP
http://www.microsoft.com/downloads/details.aspx?
FamilyID=7b9ba261-7a9c-43e7-9117-
f673077ffb3c&DisplayLang=en

KB article about SP
http://support.microsoft.com/default.aspx?scid=kb;en-
us;290887

However, Microsoft has suggested an easier fix for the
range of issues
covered by this one--typically missing system explorers- -
here's the new
workaround:
-------------------------------
We believe we have a workaround which is better than
installing the VB6 SP.
Can we have users who experience this problem try the
following:

1) Open up a command prompt (start -> run -> cmd)
2) Type in the following "regsvr32 msvbvm60.dll" (without
the quotes).
3) Close and re-open Windows AntiSpyware

Please let me know if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and
confers no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
responses to this
message are best directed to the newsgroup/thread from
which they
originated.
----------------------------------------
Each of these seems reasonably likely to be benign and
easy to try out, at
least--so they may be worth trying but I can't say I have
high hopes.

Are you getting dumps of any kind for these crashes?

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I hope no one else has a post on this, as I can't check
since the search feature of this site is currently
disabled.

I've installed Microsoft Antispyware Beta 1 on several
machines running Microsoft Windows XP Professional with
Service Pack 2. All have DEP enabled for all
applications. The product installs fine, and runs fine
under multiple user profiles (both administrative and
limited users) on all machines.

However, on one machine, any time a limited user logs
in,
Microsoft Antispyware crashes with the following dialog
box and error message while trying to load:

Title: "gcasServ.exe - Application Error"
Message Text: "The application failed to initalize
properly (0xc0000022). Click on OK to terminate the
application."

If you try to manually launch the application you
receive
the following very similar dialog box and error message:

Title: "GIANTAntiSpywareMain.exe - Application Error"
Message Text: "The application failed to initialize
properly (0xc0000022). Click OK to terminate the
application."

The only unique aspect of this machine's configuration
is
that it has the following applications installed which
the
other machines do not:

Microsoft Visual Studio 6.0 with Service Pack 6
Microsoft Visual Studio.NET 2003

I'm guessing it has something to do with Microsoft
Visual
Studio 6.0, since I see some of the executables for
Microsoft Antispyware use the default Visual Basic 6.0
form icon.

Any ideas or workaround?

Thanks,

Kevan Brown


.
Click to expand...


.
Click to expand...
Click to expand...
 
Back
Top