Unable to boot after update.

[AnnaRenee87]

Hello,

New here, registered to report this, I'm running on the latest Proxmox and OPNsense has been running fine for like... 5ish months?

When updating to the latest version of OPNsense I'm getting this error in the console and it never boots. (In Screenshot)


The version I tried to install is 25.7.8 (November 26, 2025)

I have backups of the VM so I just restored the VM.

I've attached a screenshot of what Plugins are installed too.

Thanks

EDIT/PS, VM has 6 Cores/Threads assigned to it and it's got 8GB of RAM.

[AnnaRenee87]

Figured it out, Gonna leave this here in case someone Gogoles this one day and comes across this and no one ever responded or gave an answer.

Uninstall the "os-cpu-microcode-intel" plugin.

Booted right up.

[Patrick M. Hausen]

That plugin is useless inside a VM, anyway. Any microcode updates for your CPU need to be done on the hypervisor host.

[kweetwel]

I have the same issue on a Qotom box Q1076GE. On bare metal, so no VM's.

Uninstalling the 'os-cpu-microcode-intel' plugin fixed it. Thanks for the suggestion @AnnaRenee87!

Now searching for logs to see why it failed with the plugin installed... hmmm...

[meyergru]

Do not look any further...

Let me guess: UFS install, 25.7.x installed, not having read or followed the advice here: https://forum.opnsense.org/index.php?topic=42985.0, point 23, or more specifically: https://forum.opnsense.org/index.php?topic=48343.msg244891#msg244891

The microcode updates by themselves do no harm, but rather help. There are known instabilities with newer FreeBSD kernels with certain Intel generations (i.e. Alder Lake, Twin Lake and Nxxx).

The problems turn up mostly on UFS installs. They can be avoided by certain tuneables that are explained in the postings above.

And this thread was about a VM install where microcode updates have been applied inside the VM - which is wrong and will probably not work (or cause problems). All of this is mentioned in the READ ME FIRST post as well.

[HourWithHobbit]

Yeah, I should have looked more into the update before jumping in and updating.

I am running this in hardware but do not have the plug in mentioned installed. Instead, I needed to completely remove the WAN interface and reconfigure. After that, internet returned.

I work in IT I know I should have looked into issues! Oops. Thankfully its my home lab!