'Sticky' Core version: Unable to downgrade

Since I have problems with the latest version of HA Core: 0.110.1, I would like to downgrade to 0.109.6.
When I enter the command

core downgrade --version=0.109.6

in the cli, the process starts and ends successfully.
When I login to the GUI of home assistant, the developer info still shows 0.110.1 as running version.
The OS log shows the following:

20-05-22 09:11:45 ERROR (MainThread) [supervisor.homeassistant] Home Assistant has crashed!
20-05-22 09:11:45 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-05-22 09:11:45 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.1
20-05-22 09:11:45 INFO (SyncWorker_2) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.109.5 to homeassistant/qemux86-64-homeassistant:0.110.1
20-05-22 09:11:45 INFO (SyncWorker_2) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.1.
20-05-22 09:11:46 INFO (SyncWorker_2) [supervisor.docker.interface] Clean homeassistant application

Any help?

I believe this might be due to how Home Assistant handles it’s internal config files. When an upgrade is done, things might change, as it’s doing some upgrade actions. I noticed a PR pass by during the beta phase of the 0.110 release, which should fix this issue in future releases:

This however does not help your current case, as mentioned in the PR, it can’t prevent the update of the current release, it can only ensure that future releases can be downgraded correctly again…


This has put me in the right direction.
I’m restoring a HyperV snapshot and copy only my config files instead of the config directory including the .storage.