HomeAssistant update failed -> rollback! (2025.12.0)

[lomtas]

Hi there,

since a few month now I have the problem that Home Assistant Core Updates fail. Often the second try led to success, so that this problem was not really serious for me.
Now with Home Assistant 2025.12.0 I am at a point where I can’t install Home Assistant sucessful and really searching for a solution.

In the logfiles from Home Asisstant Supervisor I can find the following entries when trying to install:

2025-12-04 13:53:35.702 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2025.12.0
2025-12-04 13:53:35.703 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2025.11.3 to ghcr.io/home-assistant/qemux86-64-homeassistant:2025.12.0
2025-12-04 13:53:35.704 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2025.12.0.
2025-12-04 13:53:43.362 INFO (SyncWorker_4) [supervisor.docker.manager] Stopping homeassistant application
2025-12-04 13:53:47.247 INFO (MainThread) [supervisor.api.proxy] [491eb00d_hamh] Home Assistant WebSocket API closed
2025-12-04 13:53:47.251 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API closed
2025-12-04 13:54:45.476 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Home-Assistant-Matter-Hub is failed, restarting...
2025-12-04 13:54:45.496 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_491eb00d_hamh application
2025-12-04 13:55:21.787 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/t0bst4r/home-assistant-matter-hub-addon with version 3.0.2
2025-12-04 13:56:17.594 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning homeassistant application
2025-12-04 13:56:26.329 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-12-04 13:56:41.766 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2025.12.0
2025-12-04 13:56:41.767 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-12-04 13:59:42.338 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-12-04 13:59:42.339 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2025-12-04 13:59:42.356 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2025.11.3
2025-12-04 13:59:42.358 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2025.12.0 to ghcr.io/home-assistant/qemux86-64-homeassistant:2025.11.3
2025-12-04 13:59:42.359 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2025.11.3.
2025-12-04 13:59:46.096 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping homeassistant application
2025-12-04 14:00:00.526 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning homeassistant application
2025-12-04 14:00:04.286 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-12-04 14:00:15.245 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2025.11.3
2025-12-04 14:00:15.246 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-12-04 14:03:15.843 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-12-04 14:03:23.972 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-12-04 14:03:27.498 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-12-04 14:12:22.478 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2025-12-04 14:12:22.909 INFO (MainThread) [supervisor.api.proxy] WebSocket access from 491eb00d_hamh
2025-12-04 14:12:23.038 INFO (MainThread) [supervisor.api.proxy] [491eb00d_hamh] Home Assistant WebSocket API proxy running
2025-12-04 14:13:57.073 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize

It is true - my home assistant installation takes a long time to startup, even without doing an update. Perhaps due to the high amount of plugins and addons used in this installation. Can it really be that the supervisor is doing a rollback because of long startup times?

These are the plugins used in my installation:

• AdGuard Home
• Alexa Devices
• Alexa Media Player
• Android TV Remote
• Anycubic Cloud
• Aqua Temp
• Arbeitstag
• Backup
• Bluetooth
• Bring!
• Browser mod
• Deutscher Wetterdienst
• Deutscher Wetterdienst (DWD) Weather Warnings
• DLNA Digital Media Renderer
• DLNA Digital Media Server
• Dreame Vacuum
• DWD Pollenflug
• Einkaufsliste
• ESP Home
• evcc Solar Charging
• Fritz!Box Tools
• Fritz!SmartHome
• Fully Kiosk Browser
• Fusion Solar
• Generische Kamera
• Google Calendar
• Google Cast
• Google Gemini
• Google Translate text-to-speech
• Govee lights local
• Home Assistant Supervisor
• Home Connect Alt
• Homematic(IP) Local for OpenCCU
• Huawei Solar
• iBeacon Tracker
• InfluxDB
• Internet Printing Protocol (IPP)
• Local Tuya
• Logitech Harmony Hub
• Lokales To-do
• Material Symbols
• Matter
• Microsoft Familiy Safety
• Mobile-App
• MQTT
• MQTT Room Presence
• Music Assistant
• Network Scanner
• Nintendo Switch Parental Controls
• Open-Meteo Solar Forecast
• Oral-B
• Samsung Smart TV
• Scrape
• Shelly
• Sonne
• Sonos
• Spook
• Spotify
• SpotifyPlus
• SSH
• Synology DSM
• System Monitor
• Telegram Bot
• Thread
• Tuya
• Twinkly
• UPnP/IGD
• Volkswagen Connect
• Web Untis
• Xbox
• Xiaomi Home

And then there are also some Add-Ons:

• AdGuard Home
• Cloudflared
• ESPHome Device Builder
• Grafana
• Home-Assistant-Matter-Hub
• InfluxDB
• Matter Server
• Mosquitto Browser
• MQTT Explorer
• Music Assistant
• Samba share
• Studio Code Server
• Terminal & SSH
• Zigbee2MQTT

All in all that leads to ~6700 Entities.

Is that installation a problem for Home Assistant? What would be a way to find out what really is the problem here and why the installation fails? Can anybody help?

[stiefenm (Marek Stiefenhofer)]

Same problem for me. Core Update is rolled back 3 minutes after starting the new release.
I never experienced the same problem before (maybe because I do have fewer add-ons and entities), but also my instance takes a long time starting up. I am using Virtual Machine Manager on Synology for hosting the supervised image, which is basically qemu. And I already found other users running on Synology experiencing the same issue. Any hints how to further analyze the root cause?

[ravaoo]

I have also problems after update to 2025.12.0
My is HA is not starting or i can’t connect to it.
It is running on synology nas virtual machine

I made a backup before updating. How do ik go back to this back up? I made the backup in HA. Unfortunaly not in virtual machine.

Please help. My lights are not working now!!!

[ravaoo]

In virtual machine i see the home assistant instance using CPU (1,5%) should i wait?

[lomtas]

I am also using Home Assistant in a Synology Virtual Machine. Forgot to mention this before.

[Edwin_D]

@lomtas

Can it really be that the supervisor is doing a rollback because of long startup times?

Yes, I had it happen to me when tere was an integration taking a huge amount of time due to incompatibility with the new version. Addons themselves should not be a problem, but any correcponding integrations might. Maybe check which integrations have long startup times and see if they have updates, or temporarily disable those?

Make sure you have backups before trying anything.

ps. I think AMP is notorius for problems, so I’s start there.

[pimseb]

Hi,
Same problem here, using also Home Assistant in a Synology Virtual Machine.

2025-12-04 19:49:56.240 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2025.12.0
2025-12-04 19:49:56.241 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-12-04 19:52:57.000 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-12-04 19:52:57.002 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2025-12-04 19:52:57.025 INFO (MainThread) [supervisor.resolution.module] Create new issue update_rollback - core / None
2025-12-04 19:52:57.027 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2025.11.3

I tried the install process 3 times

[Frank_Beetz]

If you go to repairs, you can check how long each integration needs for start-up:

[lomtas]

Taht takes really long… Anything I can do about this? Is it only bad hardware?

[Edwin_D]

Could be one of them is making others slow as well. As I said earlier, AMP is the most likely candidate. Disable it and check again. Also good to know what hardware this runs on / what respurces are allocated to the VM. How much memory?

[lomtas]

It runs on an Synology DS918+. The VM has 4GB of RAM and can use all 4 Cores.

[Edwin_D]

Lots of addons might be tight on 4 GB. Remember each addon is an application of its own, with their own memory requirements. You cannot see that from the outside, you’ll need to look from withing HA to see how much is used, from the system integration and the (disabled by default) entities of the supervisor integration.

[lomtas]

This is what Home Assistant Hardware Monitor is saying?

After all this I am really thinking about moving the installation to a raspberry pi 5. Would that enhance the situation? What do you think?
Thank you for all your responses. Just got to understand my problem a bit better.

[pimseb]

Here are my startup times

I’m on synology 916+
The VM has 8GB dedicated to HA.
It’s the first time I can’t install an update, I’ve been using home assistant for years on this machine

[ravaoo]

For me is it workin again. I restarted the virtual machine. It was slow but came on line. I saw a problem with integrations not starting and de update was not installed. After dublicating de vm in virtual machine (i am learning ) i tried to install 2025.12.0 again with succes. It is fast again and everything is working.

[pimseb]

so do you think I should restart the VM and try to install the update again ?

[ravaoo]

it worked for me. no garanties. But no working ha is nothing.

[EGDimitrov (E.Dimitrov)]

Same problem here. Home Assistant runs under a virtual machine on a Sinology DS220+. I’ve been updating with every new release for years and for the first time the installation fails and rolls back to the previous version. I turned the virtual machine off and on, but that didn’t help either…

[pimseb]

Rebooting the VM machine and then reinstalling 2025.12.0 did the trick for me. I’m now on the newest version. Thanks for the advice

[ZachPL (Zach)]

Happening to me with synology vm homeassistant. I shut down and restarted tried to install it makes it all the way to 100% I get a server disconnect and when it comes back up the update is still there to install.