wmvcore.dll Error When Launching

[Quadal]

Came back to play the game today and now I'm getting an error related to a wmvcore.dll file when trying to launch. The exact error is below. I think a Windows update may have caused this and I'm not sure how to fix it. I can see I have a wmvcore.dll file in my system32 folder but the file is 0 kb so I'm wondering if it is corrupted. Does anyone know how I might fix this?

ffxiv_dx11.exe - Bad Image

C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\WMVCore.DLL is either not designed to run on Windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000020.

I've already tried reinstalling FFXIV but that didn't fix the issue.

[worldofneil]

I'm guessing you're using Windows 10 N (which doesn't include media player) so you probably need to install the media feature pack:

https://www.microsoft.com/en-us/down....aspx?id=48231

[Quadal]

I don't believe I have Windows 10 N installed. Checking through apps I already had Windows Media Player installed. Tried installing what you linked and still got an error.

Think the WMVCore.dll file got corrupted somehow. There was another file with the same name in the SYSWOW64 folder so I copied that one over to the System32 folder and am now getting this error:

ffxiv_dx11.exe - Application Error

The application was unable to start correctly (0xc000007b). Click OK to close the application.

Think I'm just out of luck at this point unless I completely reinstall Windows. Really hate how updates can screw up stuff like this.

[worldofneil]

There was another file with the same name in the SYSWOW64 folder so I copied that one over to the System32 folder

You definitely don't want to do that, they're two completely different files.

Your System32 directory has the 64-bit files and SysWOW64 is actually 32-bit files. I know that sounds round the wrong way, but basically both exist so when a 32-bit application runs (FFXIV in DX9 mode for example) then Windows transparently gives it the 32-bit files from SysWOW64 and when a 64-bit application runs (FFXIV in DX11 mode) then it uses the 64-bit files from system32.

You could just try running XIV in DX9/DX11 mode (the opposite of what you're doing now) although that's not a long term solution and you want to be running the DX11 version really.

So I'd suggest running Windows system file checker which, in theory, should find bad files (including the wmvcore.dll you just overwrote) and put working ones back. If it doesn't work it's only cost you a little time anyway.

To do this, on the start menu, find "Command Prompt" and right-click it and run-as administrator.

Then when you get the C:\Windows\system32> prompt come up type:

sfc /scannow

(note the direction of the /)

It might not work, but it's worth a try.

[Quadal]

You definitely don't want to do that, they're two completely different files.

Your System32 directory has the 64-bit files and SysWOW64 is actually 32-bit files. I know that sounds round the wrong way, but basically both exist so when a 32-bit application runs (FFXIV in DX9 mode for example) then Windows transparently gives it the 32-bit files from SysWOW64 and when a 64-bit application runs (FFXIV in DX11 mode) then it uses the 64-bit files from system32.

You could just try running XIV in DX9/DX11 mode (the opposite of what you're doing now) although that's not a long term solution and you want to be running the DX11 version really.

So I'd suggest running Windows system file checker which, in theory, should find bad files (including the wmvcore.dll you just overwrote) and put working ones back. If it doesn't work it's only cost you a little time anyway.

To do this, on the start menu, find "Command Prompt" and right-click it and run-as administrator.

Then when you get the C:\Windows\system32> prompt come up type:

sfc /scannow

(note the direction of the /)

It might not work, but it's worth a try.

I had tried the sfc /scannow but it's unable to repair the files. Wish I could just find a safe way to download the .dll file but MS seems to make that as difficult as possible.