Unable to install R3.1 / media check failure

[Cory Nelson]

Hello,

I'm attempting to install Qubes 3.1 but am having an issue during the media check. It fails at 4.8% every time on two different laptops (Lenovo E540 and Dell Inspiron 7548) and two different flash drives, so I figure I must be doing something wrong. Install, as expected, also fails.

I've built the flash drives using Rufus in DD mode as described on the Qubes install guide, and have verified the checksum of the ISO. Beyond that, I'm not sure the best way to diagnose the issue, I have unfortunately not developed for Linux for several years and most of my in-depth knowledge has faded. But, I am able to follow instructions.

Thanks in advance for any help.

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Cory Nelson:

It sounds like you've done everything right. Is it possible that
there's some misconfiguration with Rufus? (Can you try Unix dd
instead, just to be sure?)

Are both flash drives the same brand/model? If so, can you try a
different one?
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXG1ZDAAoJEJh4Btx1RPV8J7UQAMonUdUEThHnUpJo4TugG6NI
nRp7hIBfxlDz79Ksa6r/c2S9pu0XB0MEc4wUGQYnY3PdNHOoaQYrUn7qCZKKN0KM
RdBTbLEBTNQqxG+40uZjxyZ/ykTDXwsw9fzhGNJ0sBEUiF8Myk096bSoWbT885St
OCGJ7HzTl6Hg3gAgi0N0fV/FzrXf3UmQYkyu2tlCelPZQIGs6Yh5N848Fme6bPxV
lgTVpGO2Z9OZTYpg82SjZ94rhxoBKLQEogAIKd/v+nEcEvWsq5Q657MHQlOj/hgN
uSD71htciDQXNcMIsSyOH5bvFuGEBbieKghnF1eYTcugseEeYnL5XB/nntM6W71z
jMfkKGhqCOfUMxEPnXQQsbCfZkNgfOuG3suiTMZ9AryqXUjJs5ja6rwm/qtNuhRU
u2KimWgxo4LycqM14UJ7FqBDfe5G3mQGdMWx1ocUk76SLn3OZJRgxH7t7R/SvmTo
bjA38kd/dDds5f8ZupEUIex/pVTF7KyKf01FyV0T+2Yto+9sG/nD/dPVfNUWDIrh
IocSc3HwzlFuBVzVLSTbL+rmgGgzzxS36S/iZl52W56AeXj4Q8UoZgdMRiTuq3uF
weF6TEp40VjYJJfvw0pOhIBSRiR0J0baCRX8LSdhDW0uIqsMJI50ZcbXYneyzSCn
6+i5oGh1ZHJkUKUt5WiC
=rrzg
-----END PGP SIGNATURE-----

[raah...@gmail.com]

I don't even know what rufus is. if you are doing this from linux just use normal dd command on a usb 8gb or bigger.

[raah...@gmail.com]

if doing it from windows i use a program called rawrite32.exe from netbsd.
https://www.netbsd.org/~martin/rawrite32/download.html

[raah...@gmail.com]

On Saturday, April 23, 2016 at 10:20:35 AM UTC-4, raah...@gmail.com wrote:
> if doing it from windows i use a program called rawrite32.exe from netbsd.
> https://www.netbsd.org/~martin/rawrite32/download.html

also see if there is boot mode in the bios maybe.

[Cory Nelson]

Interesting... looks like Rufus has an issue. Ended up juggling a few
USB drives to get into an Ubuntu live session and run proper dd for
Qubes. Media check works now.

--
Cory Nelson

[dbo...@gmail.com]

It seems I had also issues with Rufus.in another thread I was advised to us f2f in Linux. So doc seems wrong, can somebody correct it, the process is a bit too involved for me.
I will try rawrite as suggested in this thread.

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

dbo...@gmail.com:

> It seems I had also issues with Rufus.in another thread I was
> advised to us f2f in Linux.

If you're on a Unix-like system, I recommend just using dd (as the
docs recommend). That's what worked for Cory (as reported in the
message you're replying to), as well as everyone else, as far as I can
tell.

It could be that there was a recent change to Rufus, or that there are
other system-specific compatibility issues.

> So doc seems wrong, can somebody correct it, the process is a bit
> too involved for me.

Which part seems wrong?

> I will try rawrite as suggested in this thread.

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXHHpBAAoJEJh4Btx1RPV8T3UQAJ1awh+JWbltEkVy36Xh1cGX
yWKCVFCRNjp5lW9lUitb/Suci2breuT2h0eEjlhdBjYMQ8wJJeuitqvtEH89H1Og
NntInPERRXRBDS/ZzdRcol1NlKDQTga2Pr6breuCkXhJ5Tg7LxkPLHaJ0xyZfF79
RAlDsciBZNjSPvTwogPK8ChOS7m74ZHC+vgX9a6qj7Adm4TNE4KN0gRu8CziEqyh
SyN1vEzs8XOIDGb3fgDlpwaagVEu9sc2SgsLoOv7ZaPZEijClyQOtPneNDYZ2abz
a2Sv9OOhn0jBJ5FPMIBO2a7Gd4chkgIlhGtwrx79jrjDN+30YjkvfJZ1kirA1UeF
UqUJVVnOhqn/uT+i3ol4DntsuL8iNKgqWMeLy6uffIW5XFpMe5ZWPHrDrBqtMVTQ
RXYavcqYpv1Wyl23d2nszScxMjPw6R5612FEZry+ycUHQ23Y5Y2suNUCR8vkDzCc
9YiHFbUus93yeePCSIMS5frhHCHQfDERDFoxHm8tJjpJZhE2WdvJ6wzEIjYPvSgs
SryZ0MToQd8ikVQ4GC8AGEKAMk0UhFXu90A/NEWmweoA4Ca/El9HiZDjijABY3bK
XcA2BzvapRyEZQnNQcCja4xwrme+iYHuUfb0vFkRwqyM6Pm0gHRuxvI89NM6hbTt
xTpHcqZWGlBbwlASGpcx
=U2t0
-----END PGP SIGNATURE-----

[dbo...@gmail.com]

The part about Rufus... it is a pity as this is the only installation path from windows.

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

dbo...@gmail.com:

> The part about Rufus... it is a pity as this is the only
> installation path from windows.
>

Is there something specific in the section about Rufus which is
incorrect, or are you proposing that we delete the entire section?
What would we replace it with?

If Rufus is still working for *some* users, then I would be hesitant
to remove it when we have nothing to replace it with it.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXHILoAAoJEJh4Btx1RPV8wXQP/j//IAhz71x72qnL1rcnrDT9
7uomg+8KYl0/N9d78jVmVpOtVkDyVW/a01S3XI9S7lNdwFurL8DH/crCj/84Pp/P
Bqh93GiaBDwGzkqNJDSkhhxLRd8PbgaXHt2PZyh6JKk8RQCOSWZQXMxrC9uuAbOs
md6TlvOz4MHAw+uPrnQ3jb7X7ZkR+2u/Y3Nw0mxmcWQzv9YXvoPF9erjHO/kp3wF
k48LVFar86w3dmLaJIj7otIg0cZQxjRUBk6dilr5bIQ9HCm1eP/SK/01XfUy7cQ7
gO3bQ4LWTK9NoghsnKqqq6+2W6uhaiRElWas3utCklZuOeK70xGW2q2t8z0UdhXa
8OS4NWh90sgJ7+ji7oRI0tIYSHSZD0/j2EPkUxj6eLA31Tsxxec+Fpw7M5xWTAyK
vGR55SoKxK1wjbOfOyR4jFnp3ekbm6e6yrbYwdtWaZ9IlnowRNQQ0d0N7TcfAvZN
mtHOS5Y4bw2RJfBrojW7ZgESV4C5ofgLZ43l3a/CXPrTm8bUMknT2Ak/o4AlABHk
5ixEk9Z/fDuKUT5KiIz+5dY9AxzuRNK6ka8QBGUHP+skBoow+q1yMEa1pbWzVi0q
oW3gxPH+huRu8ezS0c9QA+wNk10X9F5d2NmGwNTTfk6OqNDttH4stbKJtDC8pJ2+
II+RdKBKem+IfGGYImul
=nGNM
-----END PGP SIGNATURE-----

[dbo...@gmail.com]

Agreed, if it works for some people the Rufus must be left as the only option from Windows. For me (X220tablet) it definitely does NOT work, and from cygwin ("linux on windows") dd does not work either.
With rufus (v2.7 and v2.8) I tried two different USB sticks (one brand new) and DD mode, as well as DD and ISO mode to check. Nothing works. I am preparing an ubuntu 16 multi boot USB with YUMI, to do the dd thing as per the doc un ubuntu 16, hope it works from a LiveUSB.

It this last thing does not work, I'll start thinking that some BIOS boot parameters are wrong in my x220t... Any thoughts?
I could install the 3.1RC2 from a USB disk, it is the 3.1 release which bothers me.
Qubes OS slowly, slowly starts to drain my patience!!!

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

dbo...@gmail.com:

Some thoughts:

* Make sure that you're copying the ISO to the device, not to a
partition on the device (e.g., /dev/sda, not /dev/sda1).

* If you've been using USB 3 ports and you have USB 2 ports available
(or the ability to control such settings in your BIOS), try using USB
2 ports.

* If possible, try creating the bootable USB drive using a different
computer.

* If both of the USB drives you've tried are the same brand/model, try
a different one.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXHNSlAAoJEJh4Btx1RPV8stgP/3w/4FdmSZXREL8MLNUdLkbD
HlYD8Ggamxv9QKzvSx+nR0YY/16OBAHZsg6o/4Fa++ABxUsSDcdvF0i9Mc0EPCoh
i6LG/Ln1W3GZAEtdgGCeCujjkmMPxHV4tUstso+zhvJsC37Le0Jg9v+LU3JQKkW1
tHudx3sfhhCJekTS7lp1rdai/7wkXy2HzVxebLMXtBsFKEf+RULAthwqhN0XyF6G
a4K+ei1jLW101OF5hmXvnXNPaTirBYYbhnZ8LfNv7G2RaLSlMt6YvcqMIWWh3+JN
KQM85O8UNvr6/J+A3BB3DCo1r2Oz/IIq2Vp8eO8RTknWa1jcwPz6UM1yqXkknfC1
Ns2ZjwlTV2r9mlUD+cDR27x8Uch041bUBC0XS+giX0sCOq4bYJ+ueFZ+7AFZ3KEx
ueI7QgK6FtxB2ydQZ8bBEyjRYYqdF62DDdWprVM1t2nFjc48Ndu4YNdH5XQO+N0R
QDiWQ5OJ4N7QoplzuZCZ4LEdIiqqxoJiSSxqJdXWEdQNqslGTy9RpdMU7HaE9XLm
mjCzZvcLSR7EQ9BeREpd4UZJKKfd4VJDjcDd3ZfsX+WbUQn1ZZ1JKKQFF/CyTLzg
b6wBcEG9Ym3cGTE3Qt+/b1YkfEGRxUKCGllaEOpt7/xPUFlFl2R5eNa+uh1POZT+
ctwFrK21PtSqPwqlyVTm
=0Oro
-----END PGP SIGNATURE-----

[raah...@gmail.com]

I used a program called rawrite32.exe from windows with no problems, you could give it a sot.

[dbo...@gmail.com]

Thanks Raah... Rawrite had the same issue for me.

[raah...@gmail.com]

On Monday, April 25, 2016 at 9:16:12 AM UTC-4, dbo...@gmail.com wrote:
> Thanks Raah... Rawrite had the same issue for me.

then maybe you need a diff brand usb stick, or you have to change your bios mode to legacy, or also try diff usb 2.0 ports on your computer.

[Cory Nelson]

There appears to be something unique about the Qubes ISO that causes
these tools to fail when writing from Windows. I wonder if Windows
reads the partition table and tries to correct something it thinks is
an error.

For me, multiple PCs (one Win8.1, one Win10), multiple drives (one usb
3.1, one usb 3, one usb 2), all failed when written from Windows, but
then succeeded in Linux.

--
Cory Nelson

[raah...@gmail.com]

weird, rawrite always worked for me, but i might not have done it since 3.0 not sure. i have windows 7 and legacy bios. the one time i had any issues burning to usb from windows. it was baffling. everyting installed, was working ok, my first qubes install... I'd have to find my original first thread to remember what the heck was not working right. was brainstorming on the forum and someone told me that my usb was probably too small. this was with 3.0 when I had a 4 gb. and sure enough the media check failed on it and that was the issue. it was slightly over 4 gb. everything installed I remember now but it was missing a kernel i wanted to install that should of been installed by default lol.

[raah...@gmail.com]

axon makes a good suggestion to do it from a diff pc maybe over tor.

[Gabriele Bini]

Hello,
I have exactly the same problem. This is what I did:
1. I downloaded the Qubes-R3.1-x86_64.iso ISO from the Torrent.
2. I checked the signature and the hash values in the DIGEST file (I checked just the hash values in a second PC) and everything was fine.
3. I used dd to copy the ISO in a USB flash drive (Sony 8Gb)
4. When I booted from the USB I tried the “Verify and Install” option but, exactly at 4,8% (as for Cory Nelson) the check failed. There was a message of this type (copied by hand):
Failed to start media check on /dev/sdc
See 'systemctl status checkisomd5@-dev-sdc.service' and 'journal.ctl-xn' for details
5. I couldn't check anything because the system was halted

What can I do?
Thank you in advance!

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Did you use Rufus or Unix dd?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIbBAEBCgAGBQJXrsJsAAoJENtN07w5UDAwvrsP+OhECR1mnbk5xO+b35beNxJV
RpuPrSYZ3PSEjwPgvIVJCee6s2MwzUTjQnjVuGx8yLsPC7VdnAwcUceNyySAL9ST
HXyJZErgEXkFnR9QK5VNl0RFqHPuiUmTmOPkfpZm7rgE1xVDFQk5E3ZCI60493i6
8yL3xz2eqhG4UfuvN665LDEwqvg7KSRUzbq0fQlrqLVLN8qucUKAijTTa31ea6Rk
8ea+KncQtN8RL6jMFG6guN+lpQnx2klHyU//bbNrjUnFQ/XzPV0N8C6HZbWpAItP
RYdCZABDzrtYBgPGg/K0cxWfX4gvOPVA027fb8jJT7WgRVNaqwA0mdq3Vdzk3Xek
0SPMAfGlWGamrlpGqFrx1R7v+qHlYTfedrREgwp8pzP1Ey47Pt/XRt3PZScIwd1t
G+vj83+X8Ochk8KDfVY5JrIo4vcK208xOXfkkRcCuZrR8PlGECdLjJFqPqXPr3mr
DghrWdO0kTEKYI6slkt6EosG4OeCCKAj3+EbFOz1hPdohZZpGts4nuEpOqquhiIC
YmbYhwT/JjefB4/EugdYH0pTBIqkgWXNKs+SMJ/s7Md8vFqhIdZJrh4Gp83DY1nv
XKAiWOyBAv6O+Y2oYtzco9IpzB+3Ua+06/gx/UkDdamfZkt2nfJVcOwt1/2mPLKJ
s7B1nmIeoCvuab4sHcU=
=jY+z
-----END PGP SIGNATURE-----

[Gabriele Bini]

I used dd: my current system is a Linux Mint 17.

--

Asperges me hysopo et mundabor

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-13 01:25, Gabriele Bini wrote:
> I used dd: my current system is a Linux Mint 17.
>

Ok, then this might be a different issue. The previous one was due to Rufus
and has already been fixed (or so we thought). However, given your new
information, it's possible there's actually a common root cause. Tracking your
new issue here:

https://github.com/QubesOS/qubes-issues/issues/2246

P.S. - Please avoid top posting.

iQIcBAEBCgAGBQJXrvTEAAoJENtN07w5UDAwsjQP/3HCP2/UGL+zD+ReofLTDlh9
WNwwdochWNmVLIP02XQxM4HNj+WsR+8tzZrjkQZeTV0Z4sr+Ks+5lc/3l2RYKQhD
5wO/ja5Vfl/imizct8CPc01JTB1brHXeFlrT1MJtweXQAgHPuGapdhasFnvbPjPB
Or6EtmQ+xNnHFSe2eND6V4Eu9dmOeonjCNEoUi6sbKdNMWakL4bE/xWyaTYGRBQR
g0Va7h+MAG/EyuE0FtvHapV9yWgComIuRJNJwfBwK21NOVCv9ycxnGBXPMoyl+v0
JAv4H9sIQFtVMXk2wUB3Ww6PhoyMKX+aZWc0IuZDcNaNnyQIPwWR0iY3K2mNh4t/
cOGlWQ9/Cov0u4KmcQGupI5+HMmo/6T44SpGwx4CwQSXpKf1sRlvmANCsmBB13CO
o2pbrV+QMXryX7si3kNte6m1g6MlcI5SAmHiGl00rRp3idT/pe9Wb5QY96vEF6Xm
ZXxit9v5xk5xEc5hTttMnRi3JMNq8ZrrDBOzHi8p5ubZT840h/fPeYtBZoYOiALJ
hHXlXLAngEMcdAxxyb92APkKQVQm7vGqA6WxY31s8R2pPXy91Lfxcuigdju6L7Ce
TUkpPnBnNxeYn6A1PWz67s84vrMzF9jm8ucywY8T9pIiwve2WuQfuRFoud4Xb0i1
t1O/t7l05RFQ9sGy6Qld
=je12
-----END PGP SIGNATURE-----

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-13 07:28, Gabriele Bini wrote:
> Il giorno sabato 13 agosto 2016 12:22:04 UTC+2, Andrew David Wong ha

> Thank you! I will follow the issue on github: let me know if I should try
> some experiments (I was thinking of copying the ISO on a different USB
> flash drive and using dd from a different computer...)

If you don't mind trying that, it would indeed be helpful to know whether you
can reproduce the problem on different hardware.

> Sorry for the "top posting": i have never used Google Groups before and I
> assumed it works like a forum. I used "reply" the first time and "reply
> all" the second time (and I guess this is "top posting" because it involves
> all qubes-users users, right?).

No, top posting is when you place your reply on top of the quoted message rather
than on the bottom or interleaved:

https://en.wikipedia.org/wiki/Posting_style#Top-posting

(My reply to you right now is an example of interleaving.)

> For now I use "reply to author", just to be sure...
>

If you don't mind, please keep the list CCed (unless there's a special need
for privacy). This increases the likelihood that a greater quantity of useful
information will be available to everyone in the future.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXrzFZAAoJENtN07w5UDAww80QAKTnpwcxqvXmO0dVkebIchg3
D369WaEe3tOizFtR9rNna6Q+zgGZ38+LQtl87J2/R7W7cm+Nq6RKc3mKQlnRlKxs
JN2RwXhtQtcp0b//i0WmNGQuCgLeWqitUezngbleGMgd9LNrm0jqy5sNAdw9yvZZ
3vJmE5vltNnzI2yxpXK7Wqh27xyXN65wiiCRjZA9p8mdMaLv5l0Wrs7uT9Gcyqz4
X1K98hptTV4cXpnjhZ5lDuD3y6G4jvZfnYcLLdX0uBHPJD9Nnmv3AJAaRp9y8K8T
YhoZr4kOd8DhL+91g/l2Wo6k1rpU+HHxh9HsW8WV/wkJftmeCUEWaNW+CQeeF4rt
+YRb4/vJcFuxXBZaaoUuosFRLUOL3sQWt6ZYqFhX4Rr/p7DQ60D9q1WehAJYE/6I
m9nT+3s+TDg22m87QPrWlatmrUApd8HqVUObdsbIGXD1uO8qlCvYj1TR+E6xrK3n
t/uo2uBVuYRRkB9N3c/4NgWVeIOiGDCE+DJ42rwiBGGc1nbr7glu0/w+jAW78eRK
H33bwXLRF4bRIy713xOZOzIjYoZHE3snY9jGep+XB7ZSnPYrlNlXheNgzeLPkqE4
Bo2cibSkoIoSgSX1A16fWj1o5zQCyso1xs405WrkPZyRuW1v6XHzP/IdLpdCiyut
hML54gG1ape3pfsoKqC7
=+nUR
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, Windows do break installation image:
https://github.com/QubesOS/qubes-issues/issues/2051
Some excerpt:

the core of the issue is that the default modern Windows behaviour is
that, whenever you plug a disk with a file system that Windows can
recognize, it creates a System Volume Information\ directory on that
file system, that contains a single file called IndexerVolumeGuid.

So the problem is that, after a Windows user writes the Qubes image in
dd mode, the FAT32 ESP gets mounted by Windows, which results in the
creation of the directory and file above.

Of course, this means that the FAT32 index gets modified and fails the
byte comparison...

As you can see in the issue history, we're trying to prevent this by
providing those files in installation image. It is in R3.2-rc images,
but not R3.1. So hopefully should be better in new release.
Unless Windows create the other file ("WPSettings.dat")...


- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXr5n0AAoJENuP0xzK19csbVQH/3pFl8ZuWxtwtLMTQRWBmGlo
IoRc0v6tT2m4BGYm2CAeApLSl7BjFf6MfpzvFbASNxJYLGPM4Eid2lXVpSbVD5CN
8PzDBsMe2hXToidLr3WWN2D9Eb0B6lbDUha+EsB07X8K9kTiMjiIRydVGs3Tygxg
9+JngNfWl7MGP6NkgdH7Y9B6cw8hA/5GYEnVunHYwRI6ZQKyiUrR7YTCBbVuWAjW
Mbz6PHun3O5CfHWcY5G1JljgKLxsNR2y9H/zVTYPomicOIYviqgZwGgB/gias7Dm
kDjyqL+5Sbf+2nSy6GCckepBvio7y4LmGCU8xOyqXrkZDZSW2tezKTsIQLWIEGQ=
=PrvF
-----END PGP SIGNATURE-----

[Benson Muite]

Buringn and iso to a DVD and installing using the DVD tends to be more
reliable than USB stick.

[Gabriele Bini]

Il giorno domenica 14 agosto 2016 07:50:45 UTC+2, Benson Muite ha scritto:
> On 8/12/16 9:24 PM, Gabriele Bini wrote:
> > Hello,
> > I have exactly the same problem. This is what I did:
> > 1. I downloaded the Qubes-R3.1-x86_64.iso ISO from the Torrent.
> > 2. I checked the signature and the hash values in the DIGEST file (I checked just the hash values in a second PC) and everything was fine.
> > 3. I used dd to copy the ISO in a USB flash drive (Sony 8Gb)
> > 4. When I booted from the USB I tried the “Verify and Install” option but, exactly at 4,8% (as for Cory Nelson) the check failed. There was a message of this type (copied by hand):
> > Failed to start media check on /dev/sdc
> > See 'systemctl status checkisomd5@-dev-sdc.service' and 'journal.ctl-xn' for details
> > 5. I couldn't check anything because the system was halted
> >
> > What can I do?
> > Thank you in advance!
> >

I made another test: I copied the same ISO on another USB Flash drive (8Gb Kingstone) from a different computer (Mint 17.1), then I tried again the installation on the previous computer: this time it worked!

However, I don't know if it is relevant, I noticed that the text in some windows of the installation wizard are wrong (a lot of missing characters): see attached image.

I also tried to compare the content of the two USB: their file structure (I just compared the result of ls -lR) is the same. Should I try to compare the images extracted from the USB with dd? Is there a smart way to do it (I am not very good)?
Thank you!

[Ben Wika]

Worth noting that, even though I had the same issue with Rufus, I could still install Qubes-OS from the USB when I bypass the media check.

[wilberth...@gmail.com]

Hi,
I had the same issue with Rufus, then I used Etcher and it did work perfectly.
Check: https://etcher.io/
Hope it works for all!