Installer corrupts installation medium (+ bounty for help)

Thank you, I missed this one. This scratches one problem off the list of things I recall on the booted 4.2 installation.

The thread is getting messy with information all over the place, I will try to summarize the current state and will update this post here with problems so we have one dedicated place for it.

Problem list

4.1: Seems to work okay at a first glance when not installing full system right away but doing the graphical install after disabling a problematic PCI device after boot in dom0. See “Error logs/issues from/in 4.1” here: Installer corrupts installation medium (+ bounty for help) - #5 by Minio
(Maybe I just fail to recognize a real problem in these logs though)

4.2-(rc5): A fully verified USB install medium fails built-in verification when installing. After booting into a different system to check the sha256sum of the drive, it did really change. I could not reproduce this anyhow with a reboot, detaching and attaching the drive or anything. It appears to only happen when booting the 4.2 installer/verification.
Just installing the system nevertheless without doing a full installation just like I did with 4.1 in order to run /usr/libexec/initial-setup/initial-setup-graphical after disabling the problematic PCI device fails, see “4.2-rc5 errors finishing install with /usr/libexec/initial-setup/initial-setup-grahic” here and here.
(to be documented in detail, see below)

__________________________________________

What I will do now is creating yet another 4.2-rc5 installation medium and find a way to disable the PCI device during the installation already as the initial-setup-graphic doesn’t work after boot. It would be interesting to see if the installation process itself is fully done then without any error being displayed to me. If I get this to work, I will document the errors I find on the booted system as I did with 4.1.
One additional issue I recall is sudo qubesctl state.highstate giving No Top file or master_tops data matches found. Please see master log for details, which was not an issue on 4.1 too.