Does this QubesOS being vibe coded actively, or actively maintained by people who are very good at programming, Because I faced an issue like 2 months ago , Where I couldn’t get QubesOS to install on my Machine, Where it gets stuck and only installs the dom0 components and skips the other, If things return to normal I’d give it a try again, Based on my experience QubesOS wasn’t stable, it somehow breaks A long time ago it had an issue with disk password and booting into OS, Not hating QubesOS, I Hate the devs for not properly testing
Hi fewonfk - and welcome to the forum. 
I’m pretty sure the devs tests the system, as good as they can, with the amount of hardware they have access to - but the combinations of hardware (eg. CPUs, GPUs, netcard, …) and how manufacturers design/configures/construct each release of their machines are orders of magnitude larger than what will ever be available for testing. 
I have no clue about the design/configuration of your “Machine” – but a wild guess is, that it is a combination of hardware and configuration from the
manufacturer, that isn’t available to the developers. In this case, you might be the only person interested in Qubes, trying to run on that hardware - and then reports about what works and what fails can help the community to learn how to install Qubes on that “Machine”.
Since this should be your first post to the forum, I assume you didn’t post descriptions of how the Initial Setup failed to install the templates … and just dropped you in a system with dom0 running (if I read you post correctly). If that was the case, then you should be able to run:
sudo /usr/libexec/initial-setup/initial-setup-graphical
from a dom0 terminal and collect any error messages for the community.
1 Like