Application failed to initialize 0xc0000022

Question

Application failed to initialize 0xc0000022

I'm stuck to using this bloody PC at work. I had Safari running just fine until one morning as I came back from vacation and booted my machine and try to run Safari, I get the error message. I've tried checking permisions with all the DLLs and googleing for help all over the net. Nothing seems to help. I seem to have administrative privilages but I certainly can't perform any re-installs etc. I can't even re-install Safari as safarisetup.exe gives me an error Extraction failed - cannot open output file. Anyone have any idea? Every other software is running fine. I installed firefox 3 just fine.

Joshua.

17" iMac, Mac OS X (10.4.9), 1.83GHz Core Duo - 1GB RAM

Posted on Jul 7, 2008 5:00 AM

Reply

Answer 1

Jul 7, 2008 7:39 AM in response to Joshua Kaijankoski

Update:

I tried on another workstation with a previous working Safari installation. Didn't work anymore and couldn't re-install.

I tried the Safari+Quicktime install file and this time it started installing Safari but ended up crapping out on SafariTheme.dll. It said it had no permission to write it and I've made sure the permissions on the given folder and drive are correct. Blah...

Joshua.

Reply

Answer 2

Jul 7, 2008 8:43 AM in response to Joshua Kaijankoski

Try downloading the setup file again. It sounds corrupted.

Reply

Answer 3

Jul 7, 2008 9:11 AM in response to Reverse_Parn

Done that many times. Got my workmate to download it as well on his workstation. He got the same error installing it. If you mean to try download from a different location, I'll give that a shot.

Reply

Answer 4

Jul 7, 2008 9:31 AM in response to Joshua Kaijankoski

I tried to edit my previous post but was unable to.

Update: I downloaded the setup file from another location and got the same error so I guess that rules out the corrupt file.

Obviously something in our computers is preventing the installation. I'm wondering if there's something I can do about it. I don't know if it's a bug on Apple's part... frustrating...

Reply