I have been using GoToMyPC from my home computer for a while. It was working OK until the end of 2019.
I read the forum posts, and I found one that described my problem just about exactly. This was a post dated 09/19/19 by ChristosD titled: "Unfortunately, GoToMyPC couldn't start because it's been corrupted." In early January, I sent ChristosD a private message but have not gotten a response. (This is not surprising because it looks as though this user opened an account around that time, dealt with the issue and likely hasn't logged in again since.)
Here is a brief rundown of my problem for the general forum. I hope someone can help me. (The rest is mostly pasted from my private message to ChristosD.)
I am running Windows XP, and I was able to connect without any problem up through 12/24/19. Then it just stopped working, giving me the "corrupted" error message. I called the support line, and LogMeIn/GoToMyPC was helpful until I told them I was running Windows XP. Then they simply would offer me no help, no thoughts, no further listening to the problem.
But I have some clues about the issues from the log and the changes that apparently were made behind the scenes. The following lines are from the last time it worked correctly; apparently, I'm using build 2329 and application build 473:
========================= 12/24/19, 13:04:37 =========================
C:\DOCUME~1\jsk\LOCALS~1\Temp\LogMeInLogs\GoToOpener.log
13:04:37 204 I: GoTo Opener Application build 473
13:04:37 204 I: C:\Documents and Settings\jsk\Local Settings\Application Data\GoTo Opener\GoTo Opener.exe
13:04:37 204 I: WinINet version 7.0.6000.21376
13:04:37 920 I: [initialize] started
13:04:37 920 logSecurityInfo
OS ver 5.1,
lua=0, virtualization=0, inst-detect=0,
integrity level 0x00000000 (UNTRUSTED)
13:04:37 920 I: Using UI language 0x0409
13:04:37 920 I: [detectMode] started
13:04:37 920 I: [handleUrl] started
.
.
13:04:37 920 configuring request
13:04:37 920 sending request
13:04:37 920 receiving response
13:04:37 920 I: args request took 640 milliseconds
13:04:37 920 I: argumentsRequestMetrics: bytesDownloaded=3485&cscErrorCount=0&displayedAuthUi=false&displayedUi=false&hostName=launch.getgo.com&resolvedHostAddr=67.217.67.141&result=ECError.eNoError&timeBlockedInUi=0&timeToConnect=562&timeToDownload=78&totalTime=640
13:04:37 920 I: effective args,
for DownloaderApp:
allowDowngrade: 0
build: 2329
downloadBaseURL: https://builds.cdn.getgo.com/builds/g2p/2329/,https://builds.getgocdn.com/builds/g2p/2329/
endpointRelativeURL:
fileName: GoTo Opener.exe
launcherInstallerURL: https://launch.getgo.com/launcher2/latest/GoToOpener.msi
persist: 1
product: g2p_viewer
scheme: gotomypc2329
I also noticed that the log's formatting changed. The heading (with all the equals signs) from when it was working correctly has the date in it, and the individual entries give only the time of day (example: 13:04:37). After the problem started, the header line changed to have no date, and the individual lines have both date and time.
When I get to the time that GoToMyPC stopped working, the log has:
2019-12-27 09:28:04.421 -0500 i: [g2o] <FC0> ======================================================
2019-12-27 09:28:04.421 -0500 i: [g2o] <FC0> C:\DOCUME~1\jsk\LOCALS~1\Temp\LogMeInLogs\GoToOpener.log
2019-12-27 09:28:04.421 -0500 i: [g2o] <FC0> GoTo Opener Application build 533
2019-12-27 09:28:04.421 -0500 i: [g2o] <FC0> C:\Documents and Settings\jsk\My Documents\Downloads\GoToMyPC Opener.exe
2019-12-27 09:28:04.421 -0500 i: [g2o] <FC0> WinINet version 7.0.6000.21376
2019-12-27 09:28:04.437 -0500 i: [g2o] <FD0> [initialize] started
2019-12-27 09:28:04.437 -0500 i: [g2o] <FD0> logSecurityInfo
OS ver 5.1,
lua=0, virtualization=0, inst-detect=0,
integrity level 0x00000000 (UNTRUSTED)
2019-12-27 09:28:04.437 -0500 i: [g2o] <FD0> Using UI language 0x0409
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [detectMode] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [loadPatchedArgs] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [parsePatchedArgs] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> effective args,
for DownloaderApp:
allowDowngrade: 1
build: 2329
downloadBaseURL: https://builds.cdn.getgo.com/builds/g2p/2329/,https://builds.getgocdn.com/builds/g2p/2329/
endpointRelativeURL:
fileName: GoToMyPC Opener.exe
launcherInstallerURL: https://launch.getgo.com/launcher2/latest/GoToOpener.msi
persist: 1
product: g2p_viewer
scheme: gotomypc2329
.
.
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [reportStartup] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [enterSingleInstance] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [checkUpdate] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [checkInstall] started
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> checking in HKCU
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> found buildInstalled: 473 (older)
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> checking in HKLM
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> buildInstalled not found
2019-12-27 09:28:04.453 -0500 i: [g2o] <FD0> [downloadInstaller] started
2019-12-27 09:28:04.531 -0500 i: [g2o] <FD0> strip-copy "C:\Documents and Settings\jsk\My Documents\Downloads\GoToMyPC Opener.exe" to "C:\DOCUME~1\jsk\LOCALS~1\Temp\1465E2C1-B2B5-4FCC-B20D-CB61DA5C3A39\GoTo Opener.exe"
2019-12-27 09:28:04.609 -0500 i: [g2o] <FD0> created file 'C:\DOCUME~1\jsk\LOCALS~1\Temp\1465E2C1-B2B5-4FCC-B20D-CB61DA5C3A39\GoToOpener.msi'
2019-12-27 09:28:04.609 -0500 i: [g2o] <FD0> loading https://launch.getgo.com:443/launcher2/latest/GoToOpener.msi
2019-12-27 09:28:04.609 -0500 i: [g2o] <FD8> telemetry data: helperState=Starting
2019-12-27 09:28:04.609 -0500 i: [g2o] <FD0> configuring request
It is clearly installing a new application build, 533, to overwrite 473. Now I don't really know what all this means, but I think it's clearly showing something. And as I pointed out, the formatting in the log has changed, so some part of the program must have changed.
ChristosD was able to get things working again because he had another copy of the older software on a different computer. I don't have any other copies available.
I have found that there is one method I can use to get GoToMyPC to work. (My home computer was previously part of my work intranet, so it has user accounts.) If I log on, not as myself but as "administrator" and if I use Firefox, but not Chrome, the GoToMyPC connection can work. Why I need to go through these steps, and why there's a difference with the browser or the user account is a mystery to me.
I hope that someone is able to shed some light on this. I understand that LogMeIn can't continue to support older systems, but this is not simply a black box with zero indication of what's going wrong. And since I can get a connection by jumping through a couple of hoops, it's clearly not a hopeless case. I just need someone to understand, explain and offer some help.
Thanks very much,
Jonathan Kerman
