Made a support ticket about this, but also wanted to let the community check up on this also.
Digital signed files of CoherentUI_Host.exe and CoherentUI.dll can’t be verified, can be 1 byte or so that is wrong to make the signed file show up as not correct signed.
Easy to check, goto the folder where the GW2 is installed and into the new folder ..\bin\ and right click CoherentUI_Host.exe -> Properties -> Digital Signatures -> click on “Coherent Labs” -> then button [Details]
and you see “The certificate in the signature cannot be verified.” Ok, so this can have 3 reason:
1. Digital Signatures is messed up, double check Anet!
2. File got corrupted somehow, thing is i have checked with other people and they have 100% exact same MD5 or SHA1 checksum so that means we downloaded the expect same wrong file from Anet, if Anet insist that the file is correct, Well then the corrupted file is at Anet or Coherent Labs, easy for Anet, just re-download the files from them again check MD5/SHA-1/Digital signatures
3. Anet dev’s SSD/HDD made a error :‘( can happen to allot of dev’s, but in this type of company ill guess they run there system in raid mirror setup if any of the SSD/HDD brakes there is one of them that is not, unless all brake lose :|
Soo if there is a problem its when someone downloaded the files from Coherent Labs
Have made a gw2.exe -repair and it found 0 errors, checked and in VerifyResults.log
MD5 checksum
E534ACA9F8F35993C863D50BFB38A055 *CoherentUI.dll
935F887F491C6F191DD6767EB554D9FD *CoherentUI_Host.exe
SHA-1 checksum
19d28cce3baafb2a527d3c098e6fb4d238b5fc1a *CoherentUI.dll
b95673522f814468c5b60886f0aa0c5810d2044f *CoherentUI_Host.exe
Best regard
Maxital