How to fix : permanently remove ‘proxmox-ve’ when attempting upgrade Proxmox 6.4 to 7.0

* This post may have affiliate links. Please see my disclosure 

WARNING: permanently remove ‘proxmox-ve‘, learn how I resolved the issue with the warning

I experienced this issue when I tried to upgrade my Proxmox VE from version 6.4.13 to the newest version Proxmox VE 7.0.

It was super frustrating, I spent a good chunk of time trying to figure it out, consulting several forums and Reddit threads, however, many of those articles that  I found didn’t have straight-out directions to solve my issue specifically.

At first, I ran the command “pve6to7 –full, to validate, if the system was presenting any FAILURES or WARNINGS, and the results came out with all zero, which means the system was ready to go within the upgrade.

Then I started to follow the steps described on the official Upgrade Proxmox from 6.x to 7.0 guide.

Evidence of the error: permanently remove ‘proxmox-ve’

When I reached the step Upgrade the system to Debian Bullseye and Proxmox VE 7.0  of the instructions guide, was then when I got  stuck with the following  error:


523 upgraded, 84 newly installed, 34 to remove, and 0 not upgraded.
Need to get 0 B/254 MB of archives.
After this operation, 173 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package ‘proxmox-ve’!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove ‘proxmox-ve‘ from your system, run the following command
W: (pve-apt-hook) touch ‘/please-remove-proxmox-ve
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why ‘proxmox-ve’ would be removed, please verify
W: (pve-apt-hook) – your APT repository settings
W: (pve-apt-hook) – that you are using ‘apt full-upgrade’ to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
root@alpha:/etc/apt# pve6to7 –full


Then, I ran again the  command  and to my surprise, the system started to show  1 WARNING:


ATTENTION: Please check the output for detailed information!


Checking out the warning, by scrolling up the outputs on my console session, the system showed an alert that several packages were pending to upgrade, and from that point, I was not quite sure what the would be the issue, since as I had followed all the steps including the apt update & apt upgrade.


Then, I reviewed my repo directories and confirmed that they all were replaced from the old Debian buster to bullseye, therefore, why were the packages not found to upgrade if all the necessary repo were there?

nano /etc/apt/sources.list

deb http://ftp.ca.debian.org/debian bullseye main contrib

deb http://ftp.ca.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

The Enterprise one:

nano /etc/apt/sources.list.d/pve-enterprise.list

# no production use
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise

Read more: Proxmox web GUI not available but yet SSH works

How I found the root cause and resolved the issue

Well.. the reason indeed was because one of the repo was missing, that’s right!

This one, to be more specific:

deb http://download.proxmox.com/debian bullseye pve-no-subscription

The absence of this distro was spotted by a member of the discord group channel of Proxmox enthusiasts that I’m part of after I shared my struggle with this upgrade, and luckily one of my fellow buddies in the group was able to point me in the right direction.

In conclusion, I solve the issue by adding the distro to the /etc/apt/sources.list.d/pve-enterprise.list

nano /etc/apt/sources.list.d/pve-enterprise.list 
# no production use
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise
deb http://download.proxmox.com/debian bullseye pve-no-subscription

I hope this article was helpful!


Juana Melo

I'm a self-taught security network engineer and blogger, sharing everything I'm learning along the way.

Leave a Reply

Your email address will not be published. Required fields are marked *