Skip to main content
The troubleshooting steps below apply to AgentOS running as a Windows service. For standalone mode on macOS or Linux, check the terminal output for errors.

Logs

Service logs are stored at:
C:\Windows\System32\config\systemprofile\.askui\logs
Use these for troubleshooting startup, crash, or connectivity issues.

Common Issues

Service won’t start

  1. Check the logs at the path above for error details.
  2. Verify the install completed successfully — look for errors in installer.log if you used /l*vx installer.log during installation.
  3. Ensure no other process is using the configured ports (default: 26000 for service, 23000 for execution engine).

SDK still uses standalone mode

The SDK auto-detects the service. If it falls back to standalone:
  1. Verify the service is running in Windows Services (services.msc).
  2. Check that the service port (default 26000) is reachable.

RDP session drops break automation

Ensure SERVICE_TRANSFER_SESSION_ON_DISCONNECT is set to 1 (default). This keeps the desktop alive when an RDP session disconnects. See Configuration.

Agent can’t press CTRL+ALT+DEL

The login/lock screen cannot be automated unless the local security policy allows services to simulate a Secure Attention Sequence (SAS). To enable it:
  1. Open the Group Policy Editor (gpedit.msc).
  2. Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Logon Options.
  3. Set Disable or enable software Secure Attention Sequence to Enabled.
Also verify that SERVICE_ENABLE_SAS is set to 1 (default) in the Silent installer parameters.
The service includes a windows.forceSas option that overrides group policies. This is not recommended as it may trigger system integrity checks. Configure the GPE policy instead.

Need to reinstall or remove

Do not stop or remove the service from Windows Services manually. Always uninstall the full AskUI AgentOS application via Windows Add/Remove Programs. This ensures proper cleanup so the SDK falls back to standalone mode.