View Single Post
Old March 15th 19, 09:38 PM posted to
external usenet poster
Posts: 9,472
Default Can I install Win 10 like this?

Jonathan N. Little wrote:
Paul wrote:
snip all

Okay, with the Ubuntu version 16.04 the 'Startup Disk Creator' will not
do the Windows ISO. However the following DOES WORK. I just tested it.

To OP follow these steps

1) Go to MS website and download Windows ISO

2) Get a usb key 6 GB or greater. I used a 32GB Sandisk. Insert it.

3) Open a terminal window CTRL+ALT+T and enter one-liner to install WoeUSB:

sudo add-apt-repository ppa:nilarimogard/webupd8 && sudo apt update &&
sudo apt install woeusb

4) You have to discover the device for the USB KEY and you must unmount
it because it auto-mounted via fuse when you stuck it into your USB slot.

cat /etc/mtab

On mine the line started:
/dev/sdb1 /media/jonathan/VOLUME_IDENTIFIER ...

Two things to note the device path without the partition number, in this
case '/dev/sdb' and the mountpoint '/media/jonathan/VOLUME_IDENTIFIER'

5) Unmount the key but leave it in the slot. No sudo needed it's mounted
in userspace.

umount /media/jonathan/VOLUME_IDENTIFIER

6) Now run the woeusb command specifying ISO and filesytem parameters. I
am should full paths in my example for clarity:

sudo woeusb --target-filesystem NTFS --device
/home/jonathan/Downloads/Win10_1809Oct_English_x64.iso /dev/sdb

Booted into Windows setup just fine. Does create two partitions on key
with the probematic UEFI partition that frustrates other methods. Here
is my mtab for the formatted key:

/dev/sdb2 /media/jonathan/UEFI_NTFS vfat
rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0 022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remou nt-ro
0 0

/dev/sdb1 /media/jonathan/Windows\040USB fuseblk
rw,nosuid,nodev,relatime,user_id=0,group_id=0,defa ult_permissions,allow_other,blksize=4096
0 0

We're trusting a .ppa though. I don't
even know the person porting this and what
reputation they have. As some sort of metric.

It is, after all, a fork of another tool. Which
means a miscreant *could* be a malware expert and
not a boot expert, just reusing the boot-making code
and be up to monkey-business.

I don't automatically trust everyone on the Internet.
My methods aren't all that rigorous, or even worth
documenting. Lots of my trust metric is based
on "appearances", "things that defy gravity", and
so on. For example, if someone uses a "packer",
then it could be to save bandwidth. But if they're
on Sourceforge, now their bandwidth is "free", so
that's a danger sign. And if I find a project
which is packed with *2* packers, that's automatically
off limits. The garbage smell from that is... horrible.

For me to test the above, I have to have a reason
to trust them. And a setup where it can't cause
immediate damage.