Jump to content

Mwo Patcher Fail


2 replies to this topic

#1 Rick Oshay

    Rookie

  • Bridesmaid
  • Bridesmaid
  • 5 posts

Posted 17 April 2015 - 04:58 PM

So I went to log onto MWO this morning and I get -
Failed to launch MWO PATCHER,exe - Access is denied this tool will now close.

Tried to run the repair tool I get -
Windows cannot access the specified device,path or file. You may not have permissions to access the item. (even when run as admin)

Uninstall MWO.

Reinstall MWO and I get -
Failed to launch MWO PATCHER,exe - Access is denied this tool will now close.

wtf...

So after 12 hrs the patcher actually started up and I downloaded MWO then halfway through..
"The download file is corrupt the MD5 hash of the local file doesnt match that of the file on the server would you like to retry"...

So a further 2hrs later it actually downloaded... GG piranha

Edited by Rick Oshay, 18 April 2015 - 04:51 AM.


#2 Jonathan Hoag

    Member

  • PipPip
  • Bad Company
  • Bad Company
  • 22 posts

Posted 06 May 2015 - 08:29 PM

I am not having any luck. I'm getting the same error message: "Failed to launch MWOPatcher.exe - Access is denied". It's been running fairly smoothly, up until now. And, since that won't launch, I can't run the repair tool. And if I try to run the repair tool .exe file directly, I get: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item".

WTF??

I _did_ use the "sbdinst" shortcut to make all the .exe files playable without having to enter my admin PW every freakin' time I wanted to play the game. Like I said, it's been running fairly smoothly, up until now, so what changed??

V/r,

JH

#3 Jonathan Hoag

    Member

  • PipPip
  • Bad Company
  • Bad Company
  • 22 posts

Posted 09 May 2015 - 10:21 PM

Okay.. I don't have the link to it, anymore, but the instructions for using "sdbinst" to grant access to the game on a standard Windows account without having to enter the admin PW was my cure. Everything was already in place, I just had to redo the CLI "sdbinst {whatever file name}.sdb" command, and I got it up and running to the point where I could patch it. So, I'll patch it, reboot, and see if I can still play the game.

V/r,

JH





3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users