Troubleshooting
Errors shown in the sidebar
When a request fails, the sidebar names the problem. Each message has its own page:
| What you see | Code | Page |
|---|---|---|
| You need to sign in | sign_in_required | Sign-in needed |
| Your usage is used up | quota_exhausted | Quota used up |
| Too many requests | rate_limited | Rate limited |
| The assistant service is unavailable | inference_unavailable | Service unavailable |
| The sidebar never answers | none | Service not responding |
| No internet connection | none | Offline |
Install and launch problems
SmartScreen blocks the installer
Symptom: Running OfficeLabs-Setup.exe shows "Windows protected your PC."
Why: This alpha build isn't code-signed yet, so Windows doesn't recognize the publisher. This is expected right now, not a sign of a corrupted download.
Fix: Select More info, then Run anyway. See Install → About the unsigned installer.
Install fails or produces a broken copy
Symptom: The installer shows an error and stops, or (rarely, on older builds) appeared to succeed but OfficeLabs won't start afterward.
Why: The installer copies files into C:\Program Files\OfficeLabs. If a file it needs to replace is locked — most often because a previous OfficeLabs is still running, or your antivirus has the file open for a scan — the install can't proceed. Current builds fail loudly and write a line to %TEMP%\OfficeLabs-Setup.log when this happens, rather than silently leaving a mixed install.
Fix:
- Close OfficeLabs completely. Check Task Manager for any lingering
soffice.exe,soffice.bin, orpython.exeprocesses and end them. - Temporarily allow the installer through your antivirus's real-time scanning, or wait for its scan to finish, then retry.
- If it still fails, check
%TEMP%\OfficeLabs-Setup.logfor the reported reason and include it if you report the issue.
Nothing happens when you launch OfficeLabs
Symptom: You start OfficeLabs from the Start menu or desktop shortcut, and no window ever appears.
Why: The shortcut runs a launcher script that starts two local background services (the agent and app-backend) and waits up to 90 seconds for both to report healthy before it opens the LibreOffice window. If either service fails to start, or the window itself doesn't appear within a further 20 seconds, the launcher gives up and shuts everything back down — with nothing shown on screen.
Fix:
- Open
%LOCALAPPDATA%\OfficeLabs-launcher\launch.login a text editor and look at the most recent run (the log is appended to, so scroll to the bottom). - A line like
FAILURE: Timed out waiting for services to become healthyorService <name> exited unexpectedlypoints at the agent or app-backend, not LibreOffice itself. Check the matchingagent-*.logorapp-backend-*.logfile in the same folder for the underlying error. - A line like
Soffice closed; stopping services.with noFAILUREline before it means the services started fine but the LibreOffice window itself closed or never appeared — try launching again, and report the run if it repeats.
Sidebar opens but never responds
Can't download — the button is disabled
Symptom: The Download for Windows button on the download page is greyed out.
Why: Downloads are gated to a signed-in, subscribed account.
Fix: Sign in first (or create an account and choose a plan if you haven't), then return to the download page.
Collecting logs for support
When you contact support, attach these files so we can see what happened:
- Windows launcher logs: everything in
%LOCALAPPDATA%\OfficeLabs-launcher, in particularlaunch.logand the newestagent-*.logandagent-*.err.log. The launcher keeps the 10 newest per-run agent logs. - Local traces:
~/.officelabs/traces(on Windows,%USERPROFILE%\.officelabs\traces) holds traces of your requests, stored only on your computer. They may contain text from your documents. Open them and review them before sending, and send only what you are comfortable sharing. - Setup log:
%TEMP%\OfficeLabs-Setup.log, if the problem is with installing.
Reach support through the contact page on the OfficeLabs website. Never send your password.