Lansweeper’s auto‑update engine keeps your environment current, but when something goes wrong, the experience can feel sudden and disruptive. A silent service failure or a stalled backup can leave your console dark at the moment you need it most. This guide highlights the most common auto‑update issues seen across customer environments and gives you clear, practical fixes.
What is going on
Admins report failures after updates, missing web consoles, stalled IT Agent updates, and C: drives filling to the brim. These problems usually involve services not restarting, backup folders growing unchecked, LocalDB conflicts, or application behaviors outside Lansweeper’s control.
Auto‑update touches several moving parts at once: services restart, IIS reloads, and a full database backup is created. Any delay or conflict in these steps can interrupt access to the console. Large backups strain storage. LocalDB behaves poorly in multi‑server setups. Some third‑party apps redownload installers endlessly. These conditions often converge during the update window.
How can I fix this
Web Console Unavailable After Update
The server may complete the update but fail to bring IIS or Lansweeper services back online fast enough.
- Open services.msc.
- Restart the Lansweeper Server service.
- Restart IIS Express or IIS.
Insufficient Disk Space for Auto‑Update
Large databases produce large backups. The auto‑update process stores them in C:\ProgramData\Lansweeper\Backup and does not clean them automatically.
- Delete old backups after confirming the update succeeded.
- Expand the C: drive so it has at least twice the size of your database available.
- If you already rely on external backups, continue using them until automated cleanup is introduced in a future release.
Repeated Download Failures Filling Disk
Adobe Reader often redownloads its .msp files when its own updater fails, creating the false impression that Lansweeper is the cause. Lansweeper does not retain deployment packages.
- Disable the application’s built‑in auto‑update.
- Use Lansweeper deployments as your single update mechanism.
- Manually clean any leftover installer files.
IT Agent Discovery Not Auto‑Updating
The “Pause auto‑update” switch often causes confusion. When it is enabled, updates stop entirely.
- Go to Discovery → Discovery Groups and confirm Pause is turned off.
- Verify the maintenance window is set correctly and that the system appears in the group.
- Restart the Lansweeper IT Agent Discovery service to refresh configuration.
- The next maintenance window will trigger the update.
Auto‑Update Fails to Start and Service Will Not Start
When LocalDB coexists with SQL Server, conflicts occur. LocalDB does not support remote or multi‑scanner environments.
- In services.msc, stop and disable the Lansweeper LocalDB service.
- Optionally uninstall Microsoft SQL Server LocalDB.
- Confirm that your SQL Server instance is reachable and healthy through SSMS.
By following these steps, you can restore stability quickly and keep your environment ready for future updates.
