8 replies to this topic

[TheTriforceKid]

Sooo..I'm getting kind of butthurt here. The latest patch has been REAL buggy as far as the front-end goes.. When I go to log in, it asks me to patch...which doesn't make sense..so I close it, re-open the program, activate the repair tool, wait for it to do it's thing, restart, play a couple matches..oorrr..it just says "nope" and spits out an error and the following line of information regarding the crash. it says it can't find the mechwarrior exe file, which doesn't make sense at all, because the patcher knows it's there or I couldn't even open the damn thing.

A little help would be appreciated..I would like to win my mechs and premium time..

************** Exception Text **************
System.Exception: Failed to launch C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin64\MWOClient.exe - The system cannot find the file specified ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at PatchBot.PatchBot.launchExe()
--- End of inner exception stack trace ---
at PatchBot.PatchBot.launchExe()
at Patcher.GamePatcherForm.launchGame()
at Patcher.GamePatcherForm.buttonPatchPlay_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MWOPatcher
Assembly Version: 1.7.7.0
Win32 Version: 1.7.7.0
CodeBase: file:///C:/Program%20Files%20(x86)/Piranha%20Games/MechWarrior%20Online/Bin32/MWOPatcher.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
PatchTarget
Assembly Version: 1.0.0.0
Win32 Version: 1.7.7.0
CodeBase: file:///C:/Program%20Files%20(x86)/Piranha%20Games/MechWarrior%20Online/Bin32/MWOPatcher.exe
----------------------------------------
VersionDll
Assembly Version: 1.0.0.0
Win32 Version: 1.7.7.0
CodeBase: file:///C:/Program%20Files%20(x86)/Piranha%20Games/MechWarrior%20Online/Bin32/MWOPatcher.exe
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[TheTriforceKid]

sooo..nobody can help me?

Tried running th epatcher again, same spiel..says it repairs, then when I try to run it, it comes back as being unable to load a PAK file...I've uninstalled and reinstalled this game once already this week..=/

[Viking520]

Having the same issue. They say a windows update fixes the issue. I updated windows and restarted my computer and it worked. However, I come back to log on later this afternoon and I'm having the same issue again.

- Repair tool usually makes the problem worse
- I've tried to run in 32 and 64 bit
- I've deactivated my firewall
- I've uninstalled and re-installed

Still nothing.

Edited by Viking520, 17 January 2015 - 03:37 PM.

[Khujjo]

http://mwomercs.com/...ing-patch-cycle

Try this. I had this happen too, and the last step of total uninstall and fresh install finally worked for me.

[Milax]

I have had the same problem for the past 3 days....I have followed the list of things to do...uninstalled everything to do with the game(at least 4 times)...even the test server...yesterday I did a total uninstall after I deleted the client off the computer just in case it was corrupt. REBOOTED, Then downloaded the client again....and freshly installed game. It worked after that. Today I try to run the game and now it wants to patch again...so it is back where it started 3 days ago and several uninstalls and reinstalls later. I am not going to run the repair tool..because it will just be missing some pak.file that has to be there somewhere...has been for 2 years(yes I am a founder). So do I have to repeat this process to play this game I have been playing since early beta? And do I get my premium time and an extension of the event that I cannot compete in with my clan, because I spent all the time redoing the game steps, and patching, so i can get a tiny bit of time in before the wee hours of the morning? I am sure that all the $$ have invested in the game(founders/Phoenix,both clan packs and some funds thrown at MC could perhaps warrant a hot fix or something....Some of this have waited to play this extraordinary game for 10 years now..and in its awesomeness it is broke and needs some loving care.

[Impossible Wasabi]

The Space Pope has tried all the fixes he has found, both official and unofficial on the forum, however over the last week he has discovered all of them are at best temporary in nature as the "patch bug" will return after X amount of time.

[Gremlich Johns]

Considering that this is not our problem, but theirs, they need to fix this and give us something free for putting up with what still amounts to a minimally viable game in BETA status.

[Kajoran]

I've been suffering the same problem. Running the mwo repair tool 4X (yes four) will fix it temporarily. Make sure that all of the options are checked on it and restart your computer after the fourth time. Good luck.
-K

Update. The 4x repair is no longer working for me. Going with the DNS fix. Thanks to Wing O.

Edited by Kajoran, 18 January 2015 - 06:58 PM.

[Wing 0]

Check here

http://mwomercs.com/...ing-patch-cycle

Several of the guys I had played with had that too. They did a DNS flush through CMD, Restarted the PC and were able to log back into MWO. Obviously this issue needs to be addressed since a lot of ppl are having issues out of nowhere