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.
 

Your EVE client installation may have modified, damaged or corrupt fil
Author
Previous Topic Next Topic
Maxim Gorkii
A Blessed Bean
Pandemic Horde
#1 - 2017-06-13 12:59:37 UTC
Whatever I do I get the message
"Your EVE client installation may have modified, damaged or corrupt files."
from the EVE launcher.

I have already selected download all files and tried again.

What else can I do?
Maxim Gorkii
A Blessed Bean
Pandemic Horde
#2 - 2017-06-13 13:12:38 UTC  |  Edited by: Maxim Gorkii
Maxim Gorkii wrote:
Whatever I do I get the message
"Your EVE client installation may have modified, damaged or corrupt files."
from the EVE launcher.

I have already selected download all files and tried again.

What else can I do?



I'm running "verify integrity of downloaded files and purge extra files" from the shared cache settings now.
Octavian Nero Gaius
Zealot's
Sigma Grindset
#3 - 2017-06-14 04:25:21 UTC  |  Edited by: Octavian Nero Gaius
BUMP -
My friend is also having this issue currently. Had him do "Traceroute" and he explained that he timed out at the 11th ping to server. I just signed in myself without issue. Anyone have any thoughts on resolving this? Appreciate any help anyone can give.

https://cdn.discordapp.com/attachments/322317156454760448/324409268092534785/unknown.png
Maxim Gorkii
A Blessed Bean
Pandemic Horde
#4 - 2017-06-14 17:25:42 UTC
Maxim Gorkii wrote:
[quote=Maxim Gorkii]Whatever I do I get the message
"Your EVE client installation may have modified, damaged or corrupt files."
from the EVE launcher.




I'm running "verify integrity of downloaded files and purge extra files" from the shared cache settings now.



going into settings and choosing the option described above fixed the launcher issue for me.
it found 3 corrupt files and even though the MS-Windows OS crashed the process before all 70k files were processed
it fixed the problem. I think only about 25k to 30 k files had been processed.