Error: MSASCui.exe 0xc0000022 when starting Defender Beta 2

[Guest]

MSASCui.exe The application failed to initialize properly (0xc0000022). Click
on OK to terminate the application. This error seems to be user related. User
is not an administrator. I read that Defender Beta 2 can be run by any class
of user.

 

[Guest]

Hi Eddie

I believe this error is a security one and is caused by a file permissions
issue. At a guess I would think MSAScui.exe is calling a system file which
does not have the the correct permissions assigned to it. Question is. Which
one? File Monitor from Sysinternals would tell you.

http://sysinternals.com/

Download, start logging and then launch Defender. Once you have found which
DLL is failing, you need to fix it by either reinstalling the DLL if it has
been deleted, or changing the file permissions so that you have read access
to it.

Alternatively, maybe the experts on here (Bill Sanderson) have a simpler
solution.

Hope this helps

Stu

 

[Guest]

Thanks for the help Stu,
I run W2K Pro on all these work machines. File Monitor is a neat tool,
however i have not been successful running it from a User or Power Users
account because they do not have debugging rights. In 2000, i have not found
a way to give the users debugging rights without administrative rights.
Still searching for the fix.
Eddie

 

[Guest]

I've had this problem, too. There is no solution on the Internet, nor any
enlightnment from Microsoft (you'd think the error code would provide some
information), so the only solution I see is to uninstall the program. That's
after wasting 4 hours getting it installed in the first place (because it
continually asked for files that I didn't have and needed to track down and
install). Much worse than Beta 1, which worked fine. I guess I'll have to buy
a commercial anti-spyware now, and I won't be trying Windows Defender again,
that's for sure.

Randy.

 

[Guest]

MSASCui.exe The application failed to initialize properly (0xc0000022). Click
on OK to terminate the application. This error seems to be user related. User
is not an administrator. I read that Defender Beta 2 can be run by any class
of user.

I solve the problem in win2k changing the security properties of the
gdiplus.dll file (in system32 folder) used by windows defender to allow the
full control by the user that make the login.

 

[Guest]

I solve the problem in win2k changing the security properties of the
gdiplus.dll file (in system32 folder) used by windows defender to allow the
full control by the user that make the login.

It also works if you grant just the Read and Execute permissions to the
Everyone group for the gdiplus.dll file. Thanks for the tip!

 

[Guest]

You are exactly right. Any user who doesn't have read and execute rights to
\...\system32\gdiplus.dll (the file that Windows Defender said you had to
install to run it under Windows 2000) will get the error you describe. If you
COPIED the dll into system32, the dll should be assigned the correct rights,
but if you MOVED it into system32, it will carry along the existing rights it
had (maybe you were logged in as administrator and decompressed the dll to
your desktop where only the admin had read-execute rights and then MOVED it).
If you read-execute to everyone, all users will be OK. I hope that helps.

Tom Albright
Indiana University