First, yes! I was able to build successfully after installing Wix and manually adding the Wix binaries to C:\wix311. Awesome work!
I checked the eventlog last night and found where the service is marked as registered, followed by the service timing out in responding to the system. I can get the exact events tonight and will look for any other details.
But all it took was a service restart to get it to check-in. I was wondering if it pertained to setting the auto-update flag but I haven't tested on other machines with different flags (yet)
03/06/2019, 8:46 PM
No clue 🙂
Auto-update enables the auto-update functionality. Which oughtn’t do anything if nothing updates. (and I haven’t pushed an update there)
You could turn up debug logs, and/or run launcher in the foreground for more debugging (see the doc in a PR I linked earlier today)
I’m just installing some windows machines now, so we’ll see what I get
There’s a filenaming bug in autoupdate. It will probably cause an error loop. (In launcher-for-windows, not package-builder). Until it’s fixed, you’ll need to run without autoupdater