MSI install ended prematurely

Support / Troubleshooting
1

Keep getting “Setup Wizard ended prematurely because of an error” when trying an MSI install.

First tried via PowerShell: msiexec /i TwingateWindowsInstaller.msi /qn

Removed /qn switch to see what was going on.

Getting this window:

Twingate 1.0 2023-06-13 at 12.57.52 PM.31 23340 Setup & Downloads

2

hi @mitchatavail,

what version of Windows are you trying to deploy the Client on?

3

Windows 11 22H2 (x64), fully patched.

It actually does install, despite that error, when I spin up a new fully patched VM to test. :man_shrugging:

4

thanks @mitchatavail, strange indeed. I’ll pas the info to our QA team in case they can reproduce.

5

I had the same issue: Using a console with admin privileges will allow for the install, but the client doesn’t seem to work then (win10 at my side). See Headless Win10 client won't connect

6

Did you ever get this resolved? I am facing the same issure with both the exe and MSI on a windows 10 laptop with the latest Windows Updates installed. All I Can see in the logs is that the service failed to respond in time.

7

Was this ever resolved? We are facing the same issue here at my company. We have Windows 10 22H2 machines fully patched. We also ran this command for the msi install msiexec /i “[path]\TwingateWindowsInstaller.msi” /L*V “[path]\twingate.log” and the log is below:

=== Verbose logging started: 9/18/2023 11:18:47 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (78:4C) [11:18:47:755]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (78:4C) [11:18:47:755]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (78:B4) [11:18:47:766]: Resetting cached policy values
MSI (c) (78:B4) [11:18:47:766]: Machine policy value ‘Debug’ is 0
MSI (c) (78:B4) [11:18:47:766]: ******* RunEngine:
******* Product: .\TwingateWindowsInstaller.msi
******* Action:
******* CommandLine: **********
MSI (c) (78:B4) [11:18:47:768]: Machine policy value ‘DisableUserInstalls’ is 0
MSI (c) (78:B4) [11:18:47:775]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (c) (78:B4) [11:18:47:775]: Note: 1: 1324 2: . 3: 1
MSI (c) (78:B4) [11:18:47:775]: MainEngineThread is returning 2
=== Verbose logging stopped: 9/18/2023 11:18:47 ===

We have done these troubleshooting steps:

  1. Ran install as Administrator
  2. Ensured the Windows Installer Service is enabled
  3. Clear the Temp folder
  4. Re-Register VBScript.dll and the Windows Installer Service
  5. Turn On .NET Framework 3.5 and 4.8
8

Hey folks :wave:

Unfortunately, we don’t have a complete solution for all users experiencing this issue of installation ending prematurely. For some, the below works a charm and not at all for others.

  • Uninstall the Client

  • Open regedit and review entries in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles and look for any Twingate Profiles, and delete them

    networkprofiles
    networkprofiles824×590 41.3 KB

    • Note that this is a sensitive task, and you must click into individual profiles to verify the ProfileName value is Twingate before deleting. Deleting the incorrect NetworkProfile is dangerous.

  • Open CMD As Administrator, and run: mofcomp %windir%\system32\wbem\cimwin32.mof (per this KB)

  • Restart

  • Reinstall the latest Client

  • Verify the service, per this KB

If this fails to resolve the issue, we may want for folks to submit a support ticket via help.twingate.com so that we can review Event Viewer logs, per:

We would be looking for Application events, that speak to potential .NET related errors, or otherwise. Please be mindful of sharing sensitive PII that EV logs might elevate here in this public space.

9

The above steps worked for me, Thanks Neth!

1 Like