Skip to content
AIPC UPAIPC UP

Troubleshooting

After reading this page you will be able to: work through common symptoms, collect useful details, and find the next support step.

Before Contacting Support

Section titled “Before Contacting Support”
  1. Check antivirus software: Ensure core components are not blocked or quarantined; exit antivirus software and reinstall, or add the app to exclusions if necessary.
  2. Restart the app.
  3. Click Check token in Settings -> Required Setup.
  4. Check the network, proxy, firewall, and local ports.
  5. Check for updates in Settings -> About.
  6. Open Settings -> System -> Log Directory, use the displayed path and the folder button to locate or select the directory, then collect logs and record the version, operating system, and reproduction steps.

For each scenario below, do the table check first, then follow the steps.

App Will Not Open or Stops Responding

Section titled “App Will Not Open or Stops Responding”
SymptomFirst check
Startup screen hangs, the window is blank, or the app does not respondLook for leftover AIPC UP processes, startup errors in the log, and antivirus quarantine status
  1. End leftover AIPC UP processes and start the app again. If it still fails to open, exit your antivirus software and reinstall, or add the app to the antivirus whitelist.
  2. Confirm the configured work and log directories exist and are accessible.
  3. If the log points to GPU or rendering issues, update the graphics driver and try disabling hardware acceleration.
  4. Submit a diagnostic report with the exact error if it still fails.

Required Setup Check Fails

Section titled “Required Setup Check Fails”
SymptomFirst check
“Check token” fails, the token is invalid, or HuiAI cannot be reachedToken completeness and access to HuiAI services
  1. Re-paste the token in Settings -> Required Setup without leading or trailing spaces.
  2. Confirm it has not been revoked and that account resources are available.
  3. Check the proxy, firewall, and system clock.
  4. Save the token and run the check again.

Model 401 or No Response

Section titled “Model 401 or No Response”
SymptomFirst check
401, authentication failure, timeout, or no response after sendingSelected model, API key, Base URL, and provider status
  1. Confirm the intended model is selected in Settings -> Models.
  2. Check the key, Base URL, and model name. A HuiAI token is not a model API key.
  3. Check provider quota, regional restrictions, and proxy settings.
  4. Retry with a short message and record the response status.

Agent Is Not Ready

Section titled “Agent Is Not Ready”
SymptomFirst check
An Agent cannot run, reports that you are signed out, or fails to startRequired Setup status and the repair page
  1. Sign in, then check the token again.
  2. Open the Agent repair page and complete its dependency instructions.
  3. Close and reopen the current session.
  4. For migration or incomplete-installation errors, update or reinstall the latest build and keep the logs.

Voice Input Does Not Work

Section titled “Voice Input Does Not Work”
SymptomFirst check
Clicking the microphone produces no transcription or says setup is missingMicrophone permission, HuiAI token, and network
  1. Allow AIPC UP to use the microphone in system privacy settings.
  2. Check the token and confirm voice resources are available.
  3. Close other apps using the microphone and retry.
  4. Check the input device and network, and record recognition-service errors.

Floating Window Does Not Appear

Section titled “Floating Window Does Not Appear”
SymptomFirst check
The floating-window control is clicked but no window is visibleOther display edges, the taskbar, and windows positioned off-screen
  1. Check the taskbar area and every connected display.
  2. Toggle the floating-window control again.
  3. Disconnect an external display and restart the app.
  4. Record the display layout and app version if it remains missing.

File Manager Shows a Read-Only Banner

Section titled “File Manager Shows a Read-Only Banner”
SymptomFirst check
The file manager is read-only and cannot writeDirectory permissions, filesystem mount state, and workspace status
  1. Confirm the directory exists and the current user can write to it.
  2. Check disk space and whether the filesystem is mounted read-only.
  3. Switch to a known writable directory to identify the scope.
  4. Confirm permissions in the operating system file manager, then reopen the project.

Browser Automation Cannot Connect

Section titled “Browser Automation Cannot Connect”
SymptomFirst check
Browser automation cannot connect to ChromeChrome remote debugging and the debugging port
  1. Open Chrome and visit chrome://inspect/#remote-debugging.
  2. Follow Chrome’s instructions to enable remote debugging and open the target page.
  3. Check the AIPC UP browser settings and ensure the port is not in use.
  4. Run connection detection again, then test with a low-risk action.

Desktop Automation Service Is Not Running

Section titled “Desktop Automation Service Is Not Running”
SymptomFirst check
Windows desktop control reports that client.exe is not runningWhether client.exe exists and the local service port is available
  1. Confirm Windows is the current operating system and check whether security software quarantined the helper. If features cannot run normally, please exit your antivirus software and reinstall, or add AIPC UP and client.exe to your antivirus whitelist.
  2. Confirm client.exe is running in Task Manager.
  3. Check that the local service port is not used by another process.
  4. Restart AIPC UP and run a low-risk diagnostic.

Remote Access Fails

Section titled “Remote Access Fails”
SymptomFirst check
A WebUI page will not open on the LAN or through the public tunnelPort, firewall, tunnel state, and public quota
  1. For LAN access, put both devices on the same network and check port 25808.
  2. Allow the app’s local port through the firewall.
  3. For public access, restart the tunnel and confirm its quota is available.
  4. Do not publish the public URL. Record the network and error page if it still fails.

Chat Platform Does Not Receive Messages

Section titled “Chat Platform Does Not Receive Messages”
SymptomFirst check
A configured bot does not receive or reply to messagesPairing approval, credential expiry, and bot permissions
  1. Confirm the credential is current and save the configuration again.
  2. Review and approve pending pairing requests.
  3. Confirm the bot can send messages in the target group or conversation.
  4. Send a short test and inspect the gateway log.

Update Fails

Section titled “Update Fails”
SymptomFirst check
Update checking, downloading, or installing failsNetwork, disk space, app processes, and installer log
  1. Retry and confirm the proxy or firewall allows the update server.
  2. Close the app and processes that may lock the install directory.
  3. Record the version, error text, and failed phase from the log.
  4. Download the official installer, run it manually, and check the version again.

Logs and Support

Section titled “Logs and Support”

The default log location varies by operating system and installation method. In Settings -> System -> Log Directory, use the path displayed by the app; click the folder button to locate or select the log directory, and restart when prompted after a change. After collecting the required logs, use Settings -> About -> Report a problem when available. Whether diagnostic events or log reports are sent depends on release configuration and trigger conditions; review the content before submitting. For further help, visit Contact and Support.

Section titled “Related”