Building a custom Windows machine image fails due to incorrect NSSM and GOSS exe files
search cancel

Building a custom Windows machine image fails due to incorrect NSSM and GOSS exe files

book

Article ID: 337593

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
When creating a custom Windows machine image it fails with the below error
 
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher, Win32 ErrorCode 216

If the NSS.exe file is downloaded from the Control-plane and locally executed with Powershell, you would see a pop up error message "Unsupported 16-bit Application".  Same issue occurs with the goss-alpha-windows-amd64.exe file.


Environment

VMware Tanzu Kubernetes Grid 2.1.0

Cause

Incorrect version of the NSSM and GOSS exe files on the control plane.

Resolution

This issue will be fixed in the next TKG 2.1 release

Workaround:
As a workaround, instead of using the NSSM and GOSS links to the control plane IP, you can use the exe links from internet. 
Replace the following exe links in the windows.json
"goss_url": "http://CONTROLPLANE-IP:30008/files/goss/goss-alpha-windows-amd64.exe"   "nssm_url": "http://CONTROLPLANE-IP:30008/files/nssm/nssm.exe"
internet exe links:
"goss_url": "https://github.com/goss-org/goss/releases/download/v0.3.21/goss-alpha-windows-amd64.exe"
"nssm_url": "https://upstreamartifacts.azureedge.net/nssm/nssm.exe"