Forum Discussion

john81's avatar
john81
New Member
8 years ago
Solved

Group policy is blocking the installer from running in app data ( due to security) Help!

We cant run go to assist since yesterday, no changes our side, could it be that the installer location has changed to users/appdata ?

37 Replies

Sort By
Show More
  • GlennD's avatar
    GlennD
    GoTo Manager
    8 years ago

    Hi John, all of our software has run from the user's profile since Microsoft introduced that structure in the most recent versions of Windows.


  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago
    The old installer installer was not a .exe. Like others on this forum, our users cannot run exe files. Is there a chance that the launcher will be revered back to the old style? We have hundreds of computers and this is already a nightmare. We are exploring other products at this time as well due to the number of machines that we cannot reach now.
  • GlennD's avatar
    GlennD
    GoTo Manager
    8 years ago

    This is how the paths are changing:

    Install paths

    • Windows: Change from %PROGRAMFILES%\Citrix\Product\ to %PROGRAMFILES%\Product\
    • Windows: Change from %PROGRAMDATA%\Citrix\Product\ to %PROGRAMDATA%\Product\
    • Windows: Change from %LOCALAPPDATA%\Citrix\Product\ to %LOCALAPPDATA%\Product\
    • Windows Start Menu: Change from the product shortcut being within a Citrix folder to not being in a folder

    Temp files and logs

    • Windows per-user: Change from %TEMP%\CitrixLogs\ to %TEMP%\LogMeInLogs\
    • Windows per-user: Change from %TEMP%\CitrixDumps\ to %TEMP%\LogMeInDumps\
    • Windows per-user: Change from %TEMP%\CitrixUpdates\ to %TEMP%\LogMeInUpdates\
    • Windows per-machine: Change from %PROGRAMDATA%\CitrixLogs\ to %PROGRAMDATA%\LogMeInLogs\
    • Windows per-machine: Change from %PROGRAMDATA%\CitrixDumps\ to %PROGRAMDATA%\LogMeInDumps\




  • John A1's avatar
    John A1
    New Member
    8 years ago
    That path is not blocked. Users cannot run exe's from their profile and that is what is blocked. Please fix, go back to the previous launcher
  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago
    The current install path that the opener installed to on my machine is: "C:\Program Files (x86)\GoTo Opener". 
  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago
    Thank you. I will add that path to the cryptolocker exception list as soon as I can see the full path. 
  • GlennD's avatar
    GlennD
    GoTo Manager
    8 years ago

    Hi Derrick, I'm looking into this for you now.


  • AshC's avatar
    AshC
    Retired GoTo Contributor
    8 years ago

    Hi Derrick,
    Were you able to grant access to the path '\Software\LogMeInInc\GoTo Opener' ?

    When the launcher downloads an installer for GoToAssist it first creates the executable as an empty file, then populates it with the data afterwards. Some firewall/proxies will block this request and substitute a common error message instead, but this is not delivered to the end user and instead into the .exe that was created. This causes the .exe to fail with the error when run by the Launcher.

    See if you can also whitelist the following URL *.getgocdn.com in the firewall or proxy.


  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago

    Here is the error: 

    GoTo Opener encountered an error:

    Installer launch error 2001, Method "createprocess" returned Win32 error [1260]. This program is blocked by group policy. For more information, contact your system administrator.

    Error occurred at , endpointtools.cpp:134

    Failed to start GoToAssist.

    Please restart the download or contact Global Customer Support at