Installation hangs in 'Running post-installation scripts' on new Framework 13

I’d like to install Qubes 4.2.3 on my new Framework 13 laptop, but I can’t seem to get it to finish the installation. It keeps hanging when the horizontal blue line is about halfway across the screen. The notation above it says ‘Running post-installation scripts’. I’ve attempted to install multiple times and waited hours to see if it would progress, but so far it consistently stops at this point.

Is there a way to see where in the installation process it hangs so I can provide a better report?

I can partially start the OS, but it appears there is still some configuration left to do. Once I start the OS I am presented with the Templates configuration page. It indicates the Whonix is not available. The drop-down for the default template is blank. Does this indicate a similar issue to earilier reports of configuration issues with Qubees 4…1

My hardware has an Intel core Ultra 7 165H CPU, uses the Insyde KFM30.03.01 BIOS, has 65 GB RAM and has a TPM 2.0 device onboard, along with 2TB of SSD disk.

I have successfully installed Ubuntu and FreeBSD on the laptop.

Any suggestions would be appreciated. Qubes looks like a great system and I’d like to give it a go.

Did you check that your installation media is not corrupted?
Is media test successful when you boot it from the Qubes OS Installer?


So you use the whole disk for Qubes OS installation or just some part of it? If it’s a part then how much disk space do you use?

Thanks for your suggestion.

I copied the ISO image to a Samsung EVO 64 GB micro SD card using Balena Etcher on my Mac… It verifies the image after copying it, so I figured the chances of it being corrupt was very small. I’ve used the same setup to install several different OSs to my Frame.work and they have been successful.

Answering your question about disk space, I have a 2TB SSD drive in my laptop. Each time I attempted an installation I deleted all partitions on the drive so the installer had access to the entire disk and could partition it as needed.

I should also mention that I do NOT get the Unsupported Hardware nastygram on startup.

I took your advice and used this option in one of my attempts, but it ended up at the same place.

I also tried to install with the latest kernel via the troubleshooting install, same result. The latest kernel provided a much better experience since it accommodated the screen resolution much better than the stable kernel and I could read my display without using a magnifying glass.

In all cases, I waited until the laptop fan quieted and the flashing light on the USB went to solid on, indicating little to no activity, then waited a few minutes and rebooted. In earlier attempts I have waited as long as overnight for this part to complete. This seems to result in a partial installation.

On multiple occasions I rebooted into the partially installed Qubes OS and was presented with Initial Setup page with template configuration options for the Debian template only. In one instance I had the Debian and Fedora options. I attempted to continue from there, but the process never completed successfully. Sometimes I had messages that Whonix was not available.

I would really like to run Qubes on my laptop, but I seem to be at an impass. I have not successfully completed the installation, but the process does not give me feedback to determine what is failing.

I realize I’m trying to install Qubes on a “niche” system and I may be the first to try on this particular configuration. I expected some challenges, but not quite to this extent.

I seem to have a memory from years ago, when graphical installers were becoming the rage, of being able to press a function key or multiple keys to bring up the console output. Does this exist for Qubes? I don’t recall seeing it mentioned in the documentation.

Try to change the Storage mode from RAID to AHCI/NVME and disable the Intel Volume Management Device (VMD) in BIOS.

Ctrl+Alt+F2 to switch to the shell TTY.
Ctrl+Alt+F3-6 - some of them are the log TTYs
Ctrl+Alt+F7 or Ctrl+Alt+F1 - back to the GUI

The problem seems to be the micro SSD media. Thanks for the keys to show the terminal output. Examining the log showed errors reading files from the media, even though it passed previous tests. I switched media and everything seems to be working.

I appreciate the quick responses. I’m looking forward to exploring Qubes.