If these simple fixes cannot help you, you can try the following solutions to troubleshoot the error 0xc0000022.

Well then how to fix the error 0xc0000022? Before we go, you can try some simple fixes such as restarting your PC, temporarily disabling antivirus software on your PC, reinstalling the application and so on. Third-party antivirus software interference.Generally, the Windows application error 0xc0000022 can occur due to the following reasons: What Causes Application Error 0xc0000022? All the information you want to know will be shown below. What causes “the application was unable to start correctly 0xc0000022”? How to fix it? You may be confused about the error. The application was unable to start correctly (0xc0000022). When you try to launch an application, you may receive the following error message with error code 0xc0000022. What Causes Application Error 0xc0000022?.If you encounter the same error, check out this post now. This post from MiniTool will show you how to fix the application error with top 3 solutions. Note: to commit this change your machine will need to reboot (twice I think).0xc0000022 is a Windows application error that you may encounter in Windows 10/8/7. I’m including this tidbit to clarify that the empty value for “Current edition is” doesn’t seem to have any relevance here. Only “Current Edition” had a value for me: “ServerStandard”. One other thing I found confusing is that if you run DISM /online /Get-CurrentEdition, there is a “Current edition is” and a “Current Edition” parameter in the response. So I ran the command with “ServerStandard” and it worked, as follows.ĭISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula That revealed an option for “ServerStandard”. Poking around a bit more I found the DISM TechNet reference and the DISM.exe /Online /Get-TargetEditions command. Unfortunately, it didn’t mention anything about MSDN licenses, and in principle my edition wasn’t changing, so I didn’t really know what to do for the Set-Edition parameter that he speaks to in:ĭISM /online /Set-Edition: /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula. I had vague recollections that this may not be possible, but the best information I found was this Blain Barton post on converting evaluation editions. Off to my favourite search engine I went, but I found surprisingly little about this. It basically tells you the same thing about struggling with the edition. Running that slui.exe command doesn’t get you very far though. “Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC004F069’ to display the error text” If you’re running an evaluation version of Windows Server 2012 R2 and want to activate it with an MSDN license, you may find that you get an error like this:

Slui.exe 0x2a 0xc0000022