9 replies to this topic

[CH4CH]

Got portal crash now! I just played the game last week, it still run.
The MWOClient.exe is missing, while MWOClient.exe_fresh is showing. I tried running the repair tools but it can't fix the issues as result.

-bin64\mwoclient.exe_fresh
-mwoupdate\mismatch\bin64\mwoclient.exe

Any files downloaded for the FE will be cleaned.

The shader cache will be cleaned out.

Starting to fix issues
Fixing mismatched files.
Caught an exception while fixing mismatched files!
Access to the path is denied.

Terminating repair process.


Issues fixed!

The problems still not fixed.

Edited by CH4CH, 08 September 2024 - 07:07 PM.

[Tarl Cabot]

If the exe was renamed, possibly infected with a virus. Run your usually antivirus then also run Free Malwarebytes. For mismatched files, the files may have been fine, or corrupted due to hard drive issue or/and unstable ram, giving erroneous errors. Even if the files were fine, the check may have read them as bad due to defective or unstable components.

[Ekson Valdez]

This thread was moved to Workarounds

[CH4CH]

I have checked the virus and malwares already. I found the mwoclient.exe in the subdirectories of mwoupdate/mismatch/bin64. I can't run that file. I already do 5 hours reinstalling the game already before I post this issue.

Edited by CH4CH, 11 September 2024 - 06:01 AM.

[CH4CH]

When I push the play button the pop-up is show like this.

Failed to launch C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin64\MWOClient.exe - The system cannot find the file specified
Stack Trace:
at MWO_Portal.ReleaseProfile.Play(Boolean a_bRun64Bit)
at MWO_Portal.ViewModel.PortalViewModel.onPatchPlayInstallClick()
at MWO_Portal.ViewModel.PortalViewModel.<initialize_Task>b__91_5(Object param)
at WpfUtil.RelayCommand.Execute(Object parameter)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at MWO_Portal.App.Main()

->Inside that:
The system cannot find the file specified
Stack Trace:
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at MWO_Portal.ReleaseProfile.Play(Boolean a_bRun64Bit)

[CH4CH]

The latest good news is that I run the repair tools again, this time the issue is fixed. I can launch the game right now. Thank you for replied.

[StraferXTG]

Hello! Seems like I got it too!. Neither Malwarebytes nor AVAST see the file as bad.

Turns out, on 9/11/24 my AVAST saw MWOClient.exe and immediately put it into quarantine as a IDP.Generic threat. The MWOClient.exe_FRESH showed up as modified on 9/12 (today).

I sent that non-working file to quarantine. Then sent to AVAST to analyze. I then sent the quarantined MWOClient.exe to AVAST to analyze as possible false positive. Then deleted .exe_FRESH but it did not get deleted from the bin64 folder, so I did it manually. I restored the MWOClient.exe and made it an exception for AVAST.

Then I checked regedit. the .exe_fresh (note the case change) is in HKEY_Local_Machine in two places ... both in an Avast folder. I left them alone.

Now with MWOClient.exe back in place, I opened the game and got in!!!! It seems to work but the initial splash takes a while to start and the "exit game" takes a while too.

SO, please check your antivirus programs for any quarantined file of MWOClient.exe, restore it, and get rid of the .exe_fresh or .exe_FRESH file you got. GAME ON!

But, it would be good to know why the good .exe is seen by AVAST as an IDP.Generic threat.

Hope this helps,
StraferXTG

P.S.: If the good file is not in quarantine, then manually delete the .exe_FRESH (or _fresh) file, run repair tool, it might(????) work.

[CH4CH]

Same here, I think the problem that came from Avast detection. Thanks for replied.

[Robinhood78]

Had exactly the same problem and sure enough I found MWOClient.exe was quarantined by AVG so I restored the file and it all works now.

[Tarl Cabot]

Robinhood78, on 25 October 2024 - 08:35 PM, said:

Had exactly the same problem and sure enough I found MWOClient.exe was quarantined by AVG so I restored the file and it all works now.

It is almost always Avast that does that after a game patch, and it does not matter the game. Options is to have Avast ignore the game directory that is patch often, ie an online game, or create a separate game folder for all of your games, or at least your online games then the Avast to ignore the general game directory and sub-directories..