Process Monitor is a handy tool that we use sometimes when we need more information about what is happening on a computer when an Autodesk product is throwing an error. It can be a bit daunting because Process Monitor captures TONS of information, so it's challenging wading through thousands of lines of information to find the one line that actually pertains to the error. But sometimes Process Monitor is a lifesaver, particularly when we encounter an error that none of us has seen before.
I encountered one such error earlier today. The error message is "The application was unable to start correctly (0xc0000022). Click OK to close the application."
That error is similar to "The application was unable to start correctly (0xc0000142)" so I immediately guessed it was related to the AppInitDLLs registry key. However, in this particular case, that registry key was completely empty. Event Viewer had absolutely nothing related to the error, so I turned to Process Monitor to try to get some idea about what was going on.
One of the first things I search for in Process Monitor is "ACCESS DENIED". That's the message it will give if there are any problems accessing files/folders/registry keys. Lo and behold, there was an ACCESS DENIED message pointing to C:\Windows\System32\mfc140u.dll. Checking the Security tab for that file showed this lovely message:
Well that certainly didn't seem right, so I ended up having to take ownership of the file so I could fix the permissions. Once Full Control permissions had been granted to the current user for that file, the error went away. And now we have this lovely knowledge article in case we ever encounter this error again:
The application was unable to start correctly (0xc0000022). Click OK to close the application.
Digging through a Process Monitor capture isn't anybody's idea of a good time, but sometimes it's the only thing that will help you find that needle in the haystack.
Subscribe