These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Unable to patch client (raised privileges)

Author
Synical Isu
Caldari Provisions
Caldari State
#1 - 2013-02-10 04:40:14 UTC  |  Edited by: Synical Isu
Hey all,

When attempting to launch EVE for the first time after downloading/installing the client, I receive the follow 2 errors, starting when the patcher reaches approximately 50%;

"An error has occurred while patching, the launcher will now try to apply the patch safely with raised privileges."

And upon relaunching with "raised privileges":

"Unable to apply patch. It is recommended that you restart your computer and then run the EVE online launcher again"

Naturally rebooting does nothing...

Steps taken so far:
- Running as administrator (no difference)
- Rebooting (no difference)
- Re-installation, after downloading a fresh client installer/patcher thingo (long download, but no difference)
- Running the repair tool as admin (no difference)
- Running EVE in compatibility mode (no difference)
- Changing permissions on the EVE executable to allow full control for all users (no difference)
- Reverting permission to their 'normal' state (no difference)
- Disabling AV and adding EVE directory to exception list (no difference)
- Forwarding port 26000 (no difference)
- Just for the hell of it, removing my router and switch all together and bridging my modem directly to my PC (no difference)

System Specifications:

Intel i5 3470
Nvidia GTX 660 (driver revision 310.90)

I'm at a loss here, the launcher's log file indicates that the local and remote game client/launcher versions match but it then tries to download an update for the launcher (launcherupdate_1_320.dat) and the client (EVE_Online_476047-476047_win.patch) anyway, which fails with the following;

Quote:
ApplyPatchError: FailedFiles: ['resDX9Scene.stuff']


So any ideas?

Cheers :)

//EDIT

Ok so I think I've sorted it out, simply deleting (or renaming) the dodgy file that showed up in the launcher's traceback (resDX9Scene.stuff), running the repairer twice and launching the client as admin seemed to fix it.