18 replies to this topic

[Malzel]

I run Windows 7 x64 Home Premium and have more RAM than necessary, so I was thrilled to hear that a 64-bit client was being released. Unfortunately, I haven't been able to get the x64 client to run since it came out. As a computer savvy individual, I've been working on it for a few days, doing research and trying fixes, but I'm completely stumped, so here I am asking for other eyes and minds to think of anything I've missed.

The 32-bit client works as normal, but when I try the x64 version, it spits out a "XINPUT1_3.dll is missing." error. I've run the DX runtime installers that Microsoft offers; the web installer simply says all DX components are present and won't run, where the offline installer runs, but at the end throws an error log, which says DX is already installed. I've located Xinput1_3, it's very much where it needs to be. If I copy the dll into the game's directories, as some online help sites suggest, the error changes to a 0xc000007b error, which has the same suggested troubleshooting steps as the XINPUT error.

I've checked and re-checked DX9 and 11. I've run CHKDSK. I've re-installed the MWO client. I've actually re-installed all of Windows, and am posting this from a freshly reformatted HDD, but I can't get the x64 client to run on this machine, and I can't figure out why to save my life. I've gotten it to run on my laptop with zero trouble, and other games that use DX9 and 11 appear to run with no issue. The problem appears to be solely with MWO, and solely on this computer. Web searches imply that I'm apparently the only person on the internet having this issue, so I'm at my wit's end.

If anyone can think of absolutely anything I might try, (That's legal and won't turn my HDD into Typhoid Mary) I'd love to hear it. No measure is too drastic!

[Malzel]

Bumped in hopes that someone is smarter than I.

[SnowBalls]

Move (Copy and delete) xinput1_3.dll from C:\Windows\SysWOW64 and C:\Windows\System32 to any folder. Then reinstall DirectX and install update

[Tarl Cabot]

As noted, make sure Windows has the newest updates.

This is the redistribution file. I use it to update any new machines I receive as well as to re-install if I suspect file corruption or unsure if a system has all required DX9c files.

http://www.microsoft...ls.aspx?id=8109

Never download directx components from a 3rd party site, tis be like playing Russian Roulette with the system.

Before switching to 64bit, were you running dx9 or dx11? Go back into 32bit and switch it to the other dx.

[crustydog]

This is exactly the same error I have on my new 8.1 machine

Nothing has fixed it so far - and I'm not going to reinstall Windows... Windows is fine.

I did try reinstalling the game - but the game is fine also

Directx is fine.

Everything is fully up to date.

There is no unknown code running in memory.

I am running everything correctly on my end - and there is no corruption on this machine.

The problem is some kind of bug in the game code itself - with how it handles directx.

Malzel - the fault is not on your end.

[Malzel]

SnowBalls, on 22 December 2014 - 08:01 AM, said:

Move (Copy and delete) xinput1_3.dll from C:\Windows\SysWOW64 and C:\Windows\System32 to any folder. Then reinstall DirectX and install update

I ran the updater, and my copy of Win7 is up to date.

I deleted the dll and re-ran the DirectX updater, but each time I get an internal system error, which references the DirectX.log, which says simply:

Quote

12/23/14 18:18:15: infinst: Installing C:\Users\Eric\AppData\Local\Temp\DX856A.tmp\d3dx9_25_x64.inf [DefaultInstall]
12/23/14 18:18:15: infinst: Installed file C:\Windows\system32\d3dx9_25.dll

It didn't replace the deleted xinput1_3.dll, I had to restore that file from deletion, myself.

Is there any reason that an un-activated copy of Windows would be the issue? This is a clean install, and I haven't dug out my CD key yet since I have 30 days to do so.

[Claviger]

http://pcsupport.abo...ssing-error.htm

[Event Horizon]

64-bit DX11 is working great for me. Are you in DX11 or DX9?

[Dirk Le Daring]

Did you also run this... https://www.microsof...s.aspx?id=14632 ?

Also, you may want to try the repair tool.

Edited by Dirk Le Daring, 23 December 2014 - 04:17 PM.

[TyGeR STD]

Hate to hear someone having issues with the 64bit client. I just started using it and saw that my fps stopped dipping and are running at a steady 120.

Hope you find a fix

[Grendel408]

Odd thing to think of... but have you tried running MWOx64 in Compatibility Mode set to "Run as Admin" ? I notice the 64bit OS tend to be rather picky when it comes to programs running correctly when not setup that way. Hell, I even got MechCommander2 and MW4 Mercs to run using this option.

[Malzel]

Claviger, on 23 December 2014 - 03:53 PM, said:

http://pcsupport.abo...ssing-error.htm

Done.

Eugenics, on 23 December 2014 - 04:09 PM, said:

64-bit DX11 is working great for me. Are you in DX11 or DX9?

I've tried in both.

Dirk Le Daring, on 23 December 2014 - 04:11 PM, said:

Did you also run this... https://www.microsof...s.aspx?id=14632 ?

Also, you may want to try the repair tool.

Done and done.

Something tried in desperation was copy/pasting the xinput1_3.dll into the System32 folder (instead of the SysWOW64 folder) caused the error to change to "D3DCompiler_42.dll not found". Copy/pasting that file into the System32 folder caused all errors to disappear, but then the MWO client just silently self-terminates when run. I don't usually tamper with system files like that, but it's the most progress I've made on the issue.

I hate to be the special case, but I'm completely baffled by this. If a complete reformat/reinstall/update of Windows can't fix it, I honestly don't know what to do.

[vetal l]

Malzel, on 23 December 2014 - 06:35 PM, said:

I hate to be the special case, but I'm completely baffled by this. If a complete reformat/reinstall/update of Windows can't fix it, I honestly don't know what to do.

You are not alone. I have the same issue on one of my PCs. The other one works great with MWO x64.
PC that wouldn't run MWO x64 have MS Windows 8.1 Pro in domain infrastructure. I've tried all the steps you mentioned above. So still using 32 bit version.

[crustydog]

That's three different warriors - on three different machines - with three different operating systems

Hmmm - I wonder if we have anything in common

FRR?

NOooooo - it couldn't be... That would be tin foil thinking for sure:)

and yet - here are all of these clan warriors

No, no way - not even possible....


Merry XMAS my friends:) Seasons greetings and good cheer to all !!!

[9erRed]

Greetings all,

For the Dx install to run and not be rejected by windows, stating that a newer version is installed.

- Try downloading the file instead of 'run' from the Ms site.
- Once you've downloaded the file, right-click, select run as Administrator may solve the issue.

Additionally with some attempts of just moving the Dx files around it generates a different 'stop' error.
(should only be done in safe mode normally, then rebooting)
By reinstalling Microsoft Visual C++ Redistributable Package it will stop the normal error of C++ is not properly configured and it may cause 0xc00007b error.
- Windows may want or need to be updated after this change.

Make sure that the C++ is the 64bit version, find here:
http://www.microsoft...s.aspx?id=14632
- C++ has 32 and 64 bit versions.

Just some ideas,
9erRed

Edited by 9erRed, 24 December 2014 - 08:44 AM.

[Event Horizon]

Hope you get it to work fellow MechWarrior.

[Malzel]

I finally got this resolved this morning. I couldn't tell you exactly how or why, but I'll recount my exact steps just for the sake of posterity.

• I upgraded from Windows 7 Home Premium to Win7 Professional and performed a clean install. (Long story, but MSFT wouldn't accept my old Win7 HP key)
  
• I installed my updated video card drivers, which installed the 2012 Microsoft C++ x64 Redistributable package.
  
• I installed MWO before any other program and patched it. (Usually, I installed Steam and several other DX-using applications first.) Trying to run it returned a 0xc000007b error, which was frustrating, but that was different from the xinput1_3 error so I called it progress.
  
• I ran the DX Runtime Web Installer. This installed the DX9 files that don't come with Win7. Where usually the installer failed, this time it succeeded. (I have to assume it's because I hadn't installed Steam, which does install DX9)
  
• I ran the Microsoft 2010 C++ x64 Redistributable package installer.
  
• Tried the x64 MWO client again, and to my shock, it ran. Then installed Steam, anti-virus, Java, all the other applications I use. Tried MWO again, to see if any of those applications were the issue, it booted up and ran fine.

Bottom line, I couldn't really tell you why it worked this time, but I have to assume 1 of 2 possibilities:

1) There was something fundamentally wrong with my edition of Win7 Home Premium. This doesn't make any sense to me, because I never had any trouble out of it for 10 years, but the issue evaporated with the fresh install of Win7 Pro.
2) Installing Steam or other DX-using apps may not configure DirectX in the best possible way, so using MSFT's web installer instead of letting a game install DX for you might be the key.

#2 sounds more reasonable to me, but that's purely conjecture. I wish I could shed more insight than that, but this has all been beyond my comprehension to begin with. I hope that anyone else suffering at the hands of the x86 client can break free and enjoy the 64-bit goodness. It is truly the promised land.

Edited by Malzel, 24 December 2014 - 12:58 PM.

[Wing 0]

Malzel, on 24 December 2014 - 12:57 PM, said:

I finally got this resolved this morning. I couldn't tell you exactly how or why, but I'll recount my exact steps just for the sake of posterity.

• I upgraded from Windows 7 Home Premium to Win7 Professional and performed a clean install. (Long story, but MSFT wouldn't accept my old Win7 HP key)
  
• I installed my updated video card drivers, which installed the 2012 Microsoft C++ x64 Redistributable package.
  
• I installed MWO before any other program and patched it. (Usually, I installed Steam and several other DX-using applications first.) Trying to run it returned a 0xc000007b error, which was frustrating, but that was different from the xinput1_3 error so I called it progress.
  
• I ran the DX Runtime Web Installer. This installed the DX9 files that don't come with Win7. Where usually the installer failed, this time it succeeded. (I have to assume it's because I hadn't installed Steam, which does install DX9)
  
• I ran the Microsoft 2010 C++ x64 Redistributable package installer.
  
• Tried the x64 MWO client again, and to my shock, it ran. Then installed Steam, anti-virus, Java, all the other applications I use. Tried MWO again, to see if any of those applications were the issue, it booted up and ran fine.

Bottom line, I couldn't really tell you why it worked this time, but I have to assume 1 of 2 possibilities:







1) There was something fundamentally wrong with my edition of Win7 Home Premium. This doesn't make any sense to me, because I never had any trouble out of it for 10 years, but the issue evaporated with the fresh install of Win7 Pro.
2) Installing Steam or other DX-using apps may not configure DirectX in the best possible way, so using MSFT's web installer instead of letting a game install DX for you might be the key.

#2 sounds more reasonable to me, but that's purely conjecture. I wish I could shed more insight than that, but this has all been beyond my comprehension to begin with. I hope that anyone else suffering at the hands of the x86 client can break free and enjoy the 64-bit goodness. It is truly the promised land.

I was just having the same problem you had when you did a clean install but this is how i fixed mine. First off the DirectX setup in MWO's Main Folder only extracts files that it came with from the start. It does not do an Internet Update on Direct X files and sadly NOT ALL the Direct X files are in use anymore. Note 64bit Clients cant use 32bit components and switching them around will not work around it.

Heres how i fixed my on a new machine.

Install MWO fresh and Clean using the 60MB file you downloaded to install MWO. Once the installing is done, Open MWO and let the patching do its work. After that is taken care of, Close the Client. don't worry. you will be back.

Next:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=35 "DirectX End-User Runtime Web Installer" You need to get Direct X here that connects and updates. When i did this on a BRAND NEW PC WITH Windows 8.1 64bit, there were about nearly 90 mbs of components that never got installed that MWO's 64 Bit client side needs.


Never had to do this step:

The Microsoft Visual C++ 2010 Redistributable Package (x64 isnt needed since it does install it for you when you open the 60 mb installer for MWO before opening the patcher but if you are having issues outside there i would do a manual download and install.


Open MWO:

Open the patcher like you all always do and set it for the 64bit client. Play and you should be rid of that error and able to play on the 64bit client.

Advice:

Update Graphics Drivers

Update DirectX Once a Month.

Keep Windows Up to date.

Hope this Helps.

[Tarl Cabot]

Wing 0, on 25 December 2014 - 12:07 AM, said:

I was just having the same problem you had when you did a clean install but this is how i fixed mine. First off the DirectX setup in MWO's Main Folder only extracts files that it came with from the start. It does not do an Internet Update on Direct X files and sadly NOT ALL the Direct X files are in use anymore. Note 64bit Clients cant use 32bit components and switching them around will not work around it.

Heres how i fixed my on a new machine.

Install MWO fresh and Clean using the 60MB file you downloaded to install MWO. Once the installing is done, Open MWO and let the patching do its work. After that is taken care of, Close the Client. don't worry. you will be back.

Next:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=35 "DirectX End-User Runtime Web Installer" You need to get Direct X here that connects and updates. When i did this on a BRAND NEW PC WITH Windows 8.1 64bit, there were about nearly 90 mbs of components that never got installed that MWO's 64 Bit client side needs.


Never had to do this step:

The Microsoft Visual C++ 2010 Redistributable Package (x64 isnt needed since it does install it for you when you open the 60 mb installer for MWO before opening the patcher but if you are having issues outside there i would do a manual download and install.


Open MWO:

Open the patcher like you all always do and set it for the 64bit client. Play and you should be rid of that error and able to play on the 64bit client.

Advice:

Update Graphics Drivers

Update DirectX Once a Month.

Keep Windows Up to date.

Hope this Helps.

Just FYI, the dxwebsetup only installs files that were associated with that setup at the date of its creation. You can go back to a different and older dxwebsetup.exe (small initial download) and you will not get all of the files that are associated with the 2010 version. Also, once used on newer OS, it may flag the system and on the next attempt install the webdxsetup it usually informs you that the system already has a newer dx installed (iirc), thus it will not even attempt to re-install/overwrite any dx9c files.

And the last time directx 9c was updated/last configured was back in June 2010, repackaged 4-18-2011. I have noted the dates so that later on if someone else reads this that they double check the dates, since they may have been installing an older version that does not have the last set of dx 9c DLL.

OP, I did not see you posting that you had downloaded (large download)/unpacked and ran the dxsetup the redistribution directx 9c package, only the webupdater. This has everything in it that is initially downloaded/installed by the webdxsetup.

Edited by Tarl Cabot, 25 December 2014 - 07:31 AM.