What happens to Proxmox when AtlasPVE is uninstalled?

Proxmox keeps running. Virtual machines, containers, storage, backups and snapshots stay in place. The uninstall removes only the files and services AtlasPVE installed itself and the records it added to Proxmox under its own name. Nothing that existed on the machine before the installation is removed.

How to uninstall

In the AtlasPVE panel, Settings › Diagnostics › Remove Atlas is opened and confirmed.

If there is a licence, it is released in the portal first and the server leaves the list.

The uninstall continues on the server as a separate service; the panel closes within a few seconds.

Completion is visible in the Proxmox shell with this command:

If the panel does not open at all, the same script is run in the Proxmox shell. On this path the licence is released manually in the portal.

What is not touched

Virtual machines and containers, together with their disks.

Storage pools, datasets and storage definitions.

Backups and snapshots.

Network configuration: bridges, bonds, VLANs.

Proxmox's own settings and users. The only exception is the records AtlasPVE created under its own name.

What is removed

All AtlasPVE services. The list is not kept by hand; it is read from the machine, so a service added later is removed too.

The monitoring services AtlasPVE installed (Prometheus, Alertmanager, exporters), the file browser and the configuration service.

Application, settings, data and log directories: /opt/atlas, /opt/atlas-core, /etc/atlas, /var/lib/atlas, /var/log/atlas.

Scheduled tasks and the log rotation rule. No task is left trying to run a script that no longer exists.

The atlas@pve API user created in Proxmox and its tokens, and the notification endpoints AtlasPVE added.

The module setting written for graphics card passthrough.

The system links of the bundled Node runtime. If the machine has its own Node installation, it is not touched.

What is left on purpose

Services that existed before installation

If a monitoring service was on the machine before AtlasPVE, the installation records this with proof and the uninstall does not touch it.

Shared system services

avahi-daemon, smartd and openvswitch-switch are Debian packages. AtlasPVE only enables them; the uninstall does not remove them.

The IOMMU setting on the kernel command line

If it was added for graphics card passthrough, it stays in place. Removing it would mean touching how the machine boots.

Uninstalling in a cluster

The atlas@pve user is a shared cluster record. Uninstalling from one node removes only that node's tokens. If another node in the cluster uses AtlasPVE, the user and roles stay in place, because removing them would cut the other nodes' connection.

The one point to watch

If graphics card passthrough was set up with AtlasPVE, the card returns to its normal driver on the first boot after the uninstall. The virtual machine that uses that card cannot see it until passthrough is set up again in Proxmox by hand.

Frequently asked questions

Do virtual machines stop when AtlasPVE is uninstalled?
No. The uninstall does not touch virtual machines or containers; running ones keep running.
Does the uninstall change Proxmox configuration files?
No. Only the API user and notification endpoints AtlasPVE created under its own name are removed, with Proxmox's own tools.
Are any services or scheduled tasks left behind?
No. AtlasPVE services are removed by reading them from the machine; scheduled tasks are deleted too.
What happens to the licence?
When uninstalling from the panel, the licence is first released in the portal. A later installation on the same server uses one return right.
Can the uninstall be undone?
No. AtlasPVE files and settings are deleted. A reinstall is done like a new installation; nothing is lost on the Proxmox side.