The Error DLL INIT FAILED is a rather common error and it has to do with the msxml.dll file. The error means that the DLL failed to initialize, or start, due to some reason with the most likely possibility being that the DLL is corrupt or has been moved. This DLL is primarily for XML applications, which is what Windows Update uses in order to send information back and forth from its servers. That is the average application for this error.
Method 1: Scan For Corruption
The most common problem that occurs with a dll is that the file becomes corrupt. The developers at Microsoft understand this very well and have built in the sfc tool to allow users to scan for corrupt files, and have Windows automatically correct the ones that are corrupt without needing to do very many complicated tasks.
Hold the Windows Key and Press X and choose Command Prompt (Admin) if you are using Windows 8 or 10. Else, Click Start -> type cmd and choose run as adminsistrator.
In the Command Prompt (Window) type sfc /scannow and press ENTER. Wait for the scan to finish, if the scan results return no corruptions or violations, then you’re system files are ok, but if they return or report corruptions then repair them using the following command:
Dism /Online /Cleanup-Image /RestoreHealth
After the process has finished, reboot PC and test.
Method 2: Copy & Re-register the DLLs
Copy the following DLL files from a working computer with the same operating system as you. The files that you need to copy are located in C:\Windows\System32 and are
msxml3a.dll, msxml3r.dll, msxml6.dll, msxml3.dll and msxml6r.dll
Once the files have been copied, save and copy them to the system in question in the same directory (C:\windows\system32) and then type the following command for each dll file.
Method 3: For Developers
If you’re a developer and are experiencing this error, it has a different cause. If this happens while you are developing, then it usually means that the component the error is coming from failed to install correctly.
Reinstall the component.
Test to see if this issue occurs with elevated permissions on. If the issue occurs on this elevated level, you have a permissions issue.
Contact the vendor of the component to ensure that the application you are developing is not including a module that interacts with the desktop. This error occurs due to a permissions error that ASP.NET gives when it tries to access something on the desktop as ASP.NET is built not to interact with the desktop.