Skip to content

v1.8.1 - TESTING ONLY - Visible attended launcher fix

Pre-release
Pre-release

Choose a tag to compare

@pupontech pupontech released this 08 Oct 10:52

v1.8.1 — visible attended launcher (TESTING ONLY)

TESTING ONLY - attended console visibility fix. Owner live acceptance remains required.

  • Removed -WindowStyle Hidden from the foreground battery-check invocation:
    it shares the elevated runner console and could hide that whole window while
    the run continued at an unseen approval prompt. The separately started
    keep-awake helper remains hidden. Battery confirmation and cancel behavior
    are otherwise unchanged.
  • Added a harmless native Windows console-visibility regression with the old
    Hidden flag as a negative control, plus continue/cancel stub paths. CI runs
    it under PowerShell 5.1 and 7 and repeats it against the extracted ZIP.
  • Do not resume old hidden cleanup sessions blindly. Before retrying, close
    only the identified old ScreenConnect cleanup/stub runs, or reboot after
    saving work. Do not terminate unrelated cmd.exe processes.
  • Post-AV persistence and its separate typed approval are unchanged. The
    agents do not run the real cleanup; actual UAC consent and battery dialog
    acceptance remain owner-live tests.

Verified Windows result

The harmless native fixture confirmed the reported failure and this fix:

Case Before After Exit
Old foreground Hidden flag (negative control) Visible Hidden 0
Fixed foreground invocation, continue Visible Visible 0
Fixed foreground invocation, cancel Visible Visible 1; no continuation

Both Windows Server 2022 and 2025 passed under PowerShell 5.1 and 7, and the tests were repeated against the extracted ZIP. The actual native window state was measured with GetConsoleWindow/IsWindowVisible; these are not just source-marker assertions. The old control restores its window before exiting.

Before retrying

Save your work and reboot, or close only positively identified old ScreenConnect cleanup/stub sessions. Do not bulk-end cmd.exe or PowerShell processes. This release cannot close the owner machine's elevated hidden runs remotely.

Verify the checksum, extract this NEW ZIP into a fresh folder, then run START-HERE.bat. Do not use a previously downloaded v1.8.0 ZIP. Do not approve Step 5 removal if the detected ScreenConnect client is your own required remote-access client.

The agents ran no real cleanup, scanner, installation or live malicious sample. Actual UAC consent and the battery dialog on an unplugged owner machine remain untested by CI; full live collection/removal/rollback acceptance also remains pending. Mandatory post-AV persistence and the separate typed REMOVE gate are unchanged.