This Program Failed to Initialize (0xc0000022)

Amantis · 03-20-2009, 01:52 AM

Ok when I boot in normal mode (it might be a good idea here to let you all know when I boot in safe mode everything works 100%) I get this error "The application failed to initialize properly (0x0000022). Click OK to terminate." on almost every application, at first only a couple of my apps worked at all (being Guild Wars, Pidgin IM, and PowerMenu) so I booted in safe mode so I could access the internet and searched around. Here's what I've tried so far to *little success:
CACLS C:WINDOWS\System32\*.dll /E /G BUILTIN\Users:R
CACLS C:WINDOWS\System32\*.ocx /E /G BUILTIN\Users:R
takeown /f C:WINDOWS\System32\*.dll.
icacls C:WINDOWS\System32\*.dll /grant administrators:F.
And generally a lot of commands like the above.
*Ive noticed slight improvement I got like 2 or 3 more things to run (VLC, ThreatFire)
I've done net user Administrator /active:yes to unlock the real admin account but I still get the error on that. I've done system restore to an earlier date, no help. Its a store bought PC so it didn't come with a Vista disk. I tried booting up with Windows Vista Recovery Disc Download — The NeoSmart Files but it didn't fix anything. Also I can't do geek squad that stuff costs more than my computer did

The problem really is I have no idea what the problem is. I don't know if its even really a permissions problem.

Amantis · 03-21-2009, 02:02 PM

Uh...bump I guess its been a couple days and im on page 3

Amantis · 03-25-2009, 08:16 PM

Um..some more info is at the time that I noticed it starting I had AVG and WinPatrol and ThreatFire running. There was a popup saying a new start up program was detected and I dont remember what it said but I knew I didn't recognize the program and it recommended I stop it from doing the start up thing, could this have been part of a windows update or something?

03-20-2009, 01:52 AM	#1 (permalink)
Amantis Registered User Join Date: Mar 2009 Posts: 3 OS: Windows Vista Home Edition x32	This Program Failed to Initialize (0xc0000022) Ok when I boot in normal mode (it might be a good idea here to let you all know when I boot in safe mode everything works 100%) I get this error "The application failed to initialize properly (0x0000022). Click OK to terminate." on almost every application, at first only a couple of my apps worked at all (being Guild Wars, Pidgin IM, and PowerMenu) so I booted in safe mode so I could access the internet and searched around. Here's what I've tried so far to little success: CACLS C:WINDOWS\System32\.dll /E /G BUILTIN\Users:R CACLS C:WINDOWS\System32\.ocx /E /G BUILTIN\Users:R takeown /f C:WINDOWS\System32\.dll. icacls C:WINDOWS\System32\.dll /grant administrators:F. And generally a lot of commands like the above. Ive noticed slight improvement I got like 2 or 3 more things to run (VLC, ThreatFire) I've done net user Administrator /active:yes to unlock the real admin account but I still get the error on that. I've done system restore to an earlier date, no help. Its a store bought PC so it didn't come with a Vista disk. I tried booting up with Windows Vista Recovery Disc Download — The NeoSmart Files but it didn't fix anything. Also I can't do geek squad that stuff costs more than my computer did The problem really is I have no idea what the problem is. I don't know if its even really a permissions problem.

03-21-2009, 02:02 PM	#2 (permalink)
Amantis Registered User Join Date: Mar 2009 Posts: 3 OS: Windows Vista Home Edition x32	Re: This Program Failed to Initialize (0xc0000022) Uh...bump I guess its been a couple days and im on page 3

03-25-2009, 08:16 PM	#3 (permalink)
Amantis Registered User Join Date: Mar 2009 Posts: 3 OS: Windows Vista Home Edition x32	Re: This Program Failed to Initialize (0xc0000022) Um..some more info is at the time that I noticed it starting I had AVG and WinPatrol and ThreatFire running. There was a popup saying a new start up program was detected and I dont remember what it said but I knew I didn't recognize the program and it recommended I stop it from doing the start up thing, could this have been part of a windows update or something?