q-ry
New Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Can't login on Fresh Windows 7 install
AshCAs stated, I had already contacted support and they could not find the source of the problem and directed me to GoToRescue which turned out to be rather useless. So here's the thing: the machine that I have been running g2a on until last month is a Windows XP machine. Yes, really. So I respect that at some point you might release a new version that would no longer support that OS, but it was in fact the old version that I had used before that gave me the cripled login screen. So I started a Windows 7 image which I'd rather not do because this requires more resources, but this failed to run GoTo Opener with the following message: The timestamp signature and/or certificate could not be verified or is malformed. The Windows 7 image was fully patched all the way to where Windows 7 went into transition support - the image dates back to November 2017 and I think the last update available at that time was from June that same year. Reading Assaf's message I checked whether it could be possible that updates were still being released and indeed there were some updates, including certificates, but one required dependency (KB4490628) not being offered and requiring manual download an installation. This did not change the behaviour of GoTo Opener. In the end I copied the 1544 binaries from the original (XP) support machine over to the Windows 7 machine, started it, was able to login and received the update to 1673 which installed and started without issues. So at least now I can start and use g2a. But, that's not the end of it. I have this unattended client acting as a dial-in machine. Doesn't do anything, shouldn't do anything, just allow me start an RDP session with another machine on the network. You probably already guessed this is also a virtual XP machine and when I logon to it using the virtualization agent console it instantly starts updating the g2a client which then fails with a "file authentication failed" on uninshlp.dll and then uninstalls the whole product instead of falling back to the original installation. Obviously I can revert the snapshot, but this is really bad. As I mentioned earlier, the login screen on the Windows XP machine showed the missing image icon. I found that if I point Internet Explorer (8) to https://get.gotoassist.com it tells me it cannot display the page, even after manually adding the corresponding root certificate. When I however use Firefox from that same machine, I have no issues displaying the page. When I registered to this community I noticed a message stating that LogMeIn requires at least Internet Explorer 11 to be installed and my guess is that you have in fact just recently reconfigured your web servers to actively bounce requests containing user agent strings that are sent by older versions of Internet Explorer. Why? For God sake, why? This is so pointless...2.3KViews0likes2CommentsRe: Can't login on Fresh Windows 7 install
Exactly. And there is more, because apart from breaking my original installation I can in fact not start g2ax installer from the website on a clean Windows 7 machine. There is some mumbling about a certificate and next the opener that is supposed to fetch the actual installer fails to start due to some kind of corruption. I've been online with support and they hinted that I could use go2rescue as well. That didn't work out particularly well also. First time I connected with the customer I received his screen condensed to about the size of a 5" phone screen. After he changed his screen settings and I reconnected, I got a workable view (still only part of my screen) and he could see me move the mouse. I could however not click any object, nor input any commands using the keyboard. I ended up using an unlicensed product from a different vendor that required me to reconnect every 5 minutes or so.6.1KViews0likes5CommentsRe: Can't login on Fresh Windows 7 install
I am experiencing the same issue, but in my case I did not reinstall the OS. I run g2ax from a dedicated VM that is returned to its original snapshot after every use, unless I apparently am required to update the g2ax version and I create a new snapshot before doing any online stuff. The last time this was done was on July 3 and was related to an attempt to fix the saved credentials on the 1610 build. As I found out yesterday, with a customer waiting, which annoyes the hell out of me, I am no longer able to log in with that very same build and it seems to me this must be related to the updated login service v1.23.0 from October 10. An interesting fact here is that the logo in the top of the login screen is missing and this seems to indicate some bad html/css/js coding in that page or at least ask for internet explorer features that were not in the previous version. The only version I can still login with is the 1544 build but this instantly upgrades me to the 1673 build that asks me to enter my credentials again on the crippled login page.6.1KViews0likes7Comments