@letitbexai_root/lexxit-automation-framework 1.0.4 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@letitbexai_root/lexxit-automation-framework",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "Playwright test execution framework with Express API for test execution and reporting.",
   "publishConfig": {
     "access": "public"

package/scripts/deploy/windows/install-lexxit-agent.ps1

@@ -237,6 +237,21 @@ New-NetFirewallRule -DisplayName "Lexxit Agent" -Direction Inbound -Protocol TCP
 Write-Host "[lexxit] Installing TightVNC..."
 $tvncMsi = Join-Path $env:TEMP "tightvnc.msi"
 Invoke-WebRequest -Uri $TightVncMsiUrl -OutFile $tvncMsi -UseBasicParsing
+
+# Confirmed on a real Windows EC2 AMI: REINSTALL=ALL + REINSTALLMODE=vomus
+# (tried first, see git history) does NOT reliably make TightVNC's MSI
+# reapply VALUE_OF_PASSWORD on top of an already-installed copy - verified
+# by decrypting the backend's actual stored password for a freshly
+# re-registered agent and running it through the real VNC auth handshake
+# directly: still rejected, even with REINSTALLMODE=vomus on the reinstall
+# that supposedly set it. TightVNC's password-setting custom action
+# evidently gates on something REINSTALLMODE doesn't override. An explicit
+# uninstall first removes that "already installed" state entirely, so the
+# following /i is always a genuine fresh install, which does apply every
+# property correctly. /x against the same MSI package is a no-op (not an
+# error) when TightVNC isn't installed yet, so this is safe on every run.
+Start-Process msiexec.exe -ArgumentList @("/x", "`"$tvncMsi`"", "/quiet", "/norestart") -Wait -NoNewWindow
+
 $msiArgs = @(
     "/i", "`"$tvncMsi`"", "/quiet", "/norestart",
     "ADDLOCAL=Server",