Linux HowTo: How can I create a Windows bootable USB stick using Ubuntu?

Original Source Link

I have erased the entire HDD and I’m trying to install a dual boot of both Ubuntu and Windows.

  1. First I made one bootable USB drive using an Ubuntu .iso file. I set the boot order in BIOS correctly. After restarting my machine, I correctly sees setup steps for Ubuntu. I installed Ubuntu successfully.
  2. On the second step, I made another bootable USB drive using a Windows 7 .iso file. I set the boot order correctly. When I restarted my machine, I couldn’t see anything but Missing Operating System. Then Ubuntu starts to boot and load.

Can anyone help me here to solve this issue of installing Windows?

Although you don’t have Windows 7 installed yet, you can also create a bootable USB flash drive for installing Windows 7 from Ubuntu using a USB flash drive. WoeUSB is a tool for creating a bootable USB flash drive used for installing Windows. Native UEFI booting is supported for Windows 7 and later images. WoeUSB is an updated fork of the WinUSB project.

Some third-party installers feature Windows installation images (/sources/install.wim) greater than 4GB making FAT32 as target filesystem impossible. NTFS filesystem support has been added to WoeUSB 3.0.0 and later.

Installation

To install WoeUSB (GUI+CLI) in Ubuntu 14.04/16.04/17.10-20.04:

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

This will install the WoeUSB graphical interface and the WoeUSB command line tool. WoeUSB supports both UEFI and BIOS for FAT32/NTFS/ExFAT USB flash drives.

To install the WoeUSB command line tool snap package in all currently supported versions of Ubuntu open the terminal and type:

sudo snap install --edge woe-usb  
sudo snap connect woe-usb:removable-media

To launch the woe-usb snap package command line tool run the following command:

/snap/bin/woe-usb.woeusb

If you get a permission denied error click the Permissions button on the woe-usb screen in Ubuntu Software and toggle the permissions options from OFF to ON as shown in the below screenshot.

woe-usb Permissions

The WoeUSB GUI is easier to use than the WoeUSB command line tool. Click the radio button to the left of where it says From a disk image (iso), browse to the location of the Windows .iso file, under Target device select a USB flash drive, open Disks application and check that the Device name in Disks matches the Target device in WoeUSB (it should be something like /dev/sdX where X is a letter of the alphabet), and click the Install button to install to create a bootable Windows installation media on the USB flash drive.

enter image description here

Windows USB drive from Ubuntu failing repeatedly
WoeUSB Issues

  1. If using rufus:

    • Make sure partition scheme is MBR (for BIOS or UEFI)
    • NTFS file sytem

Like as shown below

enter image description here

  1. Probably the better to create a Windows (7) bootable disk, is using the tool from MicrosoftWindows USB/DVD Download Tool

or directly from codeplex: Windows USB/DVD Download Tool

The second option has no hassle as the setup is straightforward needing no extra configurations as with rufus.

enter image description here enter image description here

enter image description here enter image description here

According to onetransistor.blogspot.co.uk

Before starting, let’s mention that there are two types of boot
methods. There is the MBR code type where the bootable executable is
stored in a reserved section at the beginning of the storage device.
And there is the EFI type, where the boot loader executable file is
stored at a standard path in an FAT32 filesystem.

You must decide in advance what you will use. There are some variables
for each boot type. If you have no idea what to use, the most common
setup that works with unmodified Windows sources, is msdos partition
table with fat32 filesystem and flag the partition with boot
. In this
way you will get both an MBR and UEFI bootable drive.
USB Boot flags MBR/UEFI mods/gpt

  1. Format USB drive

You must re-create the partition table by going to the Device menu
then select Create Partition Table. Choose msdos (or gpt if you want
an UEFI only bootable drive) and click Apply.

  1. Copy Windows files
  2. Make it bootable

If you used NTFS filesystem and MSDOS table, only method A is
available. If you used FAT32 and MSDOS table, you can apply method A,
B or both. If you used GPT partition table, only method B should be
followed.

  • A. MBR bootable

GRUB will be used for that. Open a Terminal and run:

sudo grub-install --target=i386-pc --boot-directory="/media/<username>/<drive_label>/boot" /dev/sdX

Now, create a text file and write the following in it:

default=1  
timeout=15
color_normal=light-cyan/dark-gray
menu_color_normal=black/light-cyan
menu_color_highlight=white/black

menuentry "Start Windows Installation" {
    insmod ntfs
    insmod search_label
    search --no-floppy --set=root --label <USB_drive_label> --hint hd0,msdos1
    ntldr /bootmgr
    boot
}

menuentry "Boot from the first hard drive" {
    insmod ntfs
    insmod chain
    insmod part_msdos
    insmod part_gpt
    set root=(hd1)
    chainloader +1
    boot
}

That’s it. The USB drive is now bootable from BIOS and can be used to
install Windows on your PC. The first time you boot from it in MBR
BIOS or CSM mode select Start Windows Installation.

  • B. UEFI bootable

Not all Windows versions are supported. Windows 7 on 64 bits, Windows
8 and newer versions should work.

After the copy process is finished, look in the USB root folder for
the efi/boot directory. If there’s a bootx64.efi or bootia32.efi file
there, then you’re done. You can boot from your USB in UEFI mode.

If the OS you are making a bootable USB for is Windows 7, browse the
efi/microsoft folder and copy the entire boot folder from this path
one level up in the efi folder. Merge folders if boot already exists.

Here is what to do if you don’t have the bootx64.efi file in efi/boot
folder. Browse the mounted Windows ISO image into the sources folder.
Open install.wim (or install.esd) with your archive manager (you will
need 7z installed). Go to the path ./1/Windows/Boot/EFI and extract
the file bootmgfw.efi anywhere you want. Rename it to bootx64.efi and
put it on the USB drive, in the efi/boot folder. If you can’t find
bootmgfw.efi in install.wim then you probably have a 32 bit Windows
ISO or other types of images (recovery disks, upgrade versions).

You can now boot from your USB in UEFI mode.

I quote the original website for reliability, But the website is way better in style and details, So use it unless you force not to.

Tagged : / / /

Making Game: How can I create a Windows bootable USB stick using Ubuntu?

Original Source Link

I have erased the entire HDD and I’m trying to install a dual boot of both Ubuntu and Windows.

  1. First I made one bootable USB drive using an Ubuntu .iso file. I set the boot order in BIOS correctly. After restarting my machine, I correctly sees setup steps for Ubuntu. I installed Ubuntu successfully.
  2. On the second step, I made another bootable USB drive using a Windows 7 .iso file. I set the boot order correctly. When I restarted my machine, I couldn’t see anything but Missing Operating System. Then Ubuntu starts to boot and load.

Can anyone help me here to solve this issue of installing Windows?

Although you don’t have Windows 7 installed yet, you can also create a bootable USB flash drive for installing Windows 7 from Ubuntu using a USB flash drive. WoeUSB is a tool for creating a bootable USB flash drive used for installing Windows. Native UEFI booting is supported for Windows 7 and later images. WoeUSB is an updated fork of the WinUSB project.

Some third-party installers feature Windows installation images (/sources/install.wim) greater than 4GB making FAT32 as target filesystem impossible. NTFS filesystem support has been added to WoeUSB 3.0.0 and later.

Installation

To install WoeUSB (GUI+CLI) in Ubuntu 14.04/16.04/17.10-20.04:

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

This will install the WoeUSB graphical interface and the WoeUSB command line tool. WoeUSB supports both UEFI and BIOS for FAT32/NTFS/ExFAT USB flash drives.

To install the WoeUSB command line tool snap package in all currently supported versions of Ubuntu open the terminal and type:

sudo snap install --edge woe-usb  
sudo snap connect woe-usb:removable-media

To launch the woe-usb snap package command line tool run the following command:

/snap/bin/woe-usb.woeusb

If you get a permission denied error click the Permissions button on the woe-usb screen in Ubuntu Software and toggle the permissions options from OFF to ON as shown in the below screenshot.

woe-usb Permissions

The WoeUSB GUI is easier to use than the WoeUSB command line tool. Click the radio button to the left of where it says From a disk image (iso), browse to the location of the Windows .iso file, under Target device select a USB flash drive, open Disks application and check that the Device name in Disks matches the Target device in WoeUSB (it should be something like /dev/sdX where X is a letter of the alphabet), and click the Install button to install to create a bootable Windows installation media on the USB flash drive.

enter image description here

Windows USB drive from Ubuntu failing repeatedly
WoeUSB Issues

  1. If using rufus:

    • Make sure partition scheme is MBR (for BIOS or UEFI)
    • NTFS file sytem

Like as shown below

enter image description here

  1. Probably the better to create a Windows (7) bootable disk, is using the tool from MicrosoftWindows USB/DVD Download Tool

or directly from codeplex: Windows USB/DVD Download Tool

The second option has no hassle as the setup is straightforward needing no extra configurations as with rufus.

enter image description here enter image description here

enter image description here enter image description here

According to onetransistor.blogspot.co.uk

Before starting, let’s mention that there are two types of boot
methods. There is the MBR code type where the bootable executable is
stored in a reserved section at the beginning of the storage device.
And there is the EFI type, where the boot loader executable file is
stored at a standard path in an FAT32 filesystem.

You must decide in advance what you will use. There are some variables
for each boot type. If you have no idea what to use, the most common
setup that works with unmodified Windows sources, is msdos partition
table with fat32 filesystem and flag the partition with boot
. In this
way you will get both an MBR and UEFI bootable drive.
USB Boot flags MBR/UEFI mods/gpt

  1. Format USB drive

You must re-create the partition table by going to the Device menu
then select Create Partition Table. Choose msdos (or gpt if you want
an UEFI only bootable drive) and click Apply.

  1. Copy Windows files
  2. Make it bootable

If you used NTFS filesystem and MSDOS table, only method A is
available. If you used FAT32 and MSDOS table, you can apply method A,
B or both. If you used GPT partition table, only method B should be
followed.

  • A. MBR bootable

GRUB will be used for that. Open a Terminal and run:

sudo grub-install --target=i386-pc --boot-directory="/media/<username>/<drive_label>/boot" /dev/sdX

Now, create a text file and write the following in it:

default=1  
timeout=15
color_normal=light-cyan/dark-gray
menu_color_normal=black/light-cyan
menu_color_highlight=white/black

menuentry "Start Windows Installation" {
    insmod ntfs
    insmod search_label
    search --no-floppy --set=root --label <USB_drive_label> --hint hd0,msdos1
    ntldr /bootmgr
    boot
}

menuentry "Boot from the first hard drive" {
    insmod ntfs
    insmod chain
    insmod part_msdos
    insmod part_gpt
    set root=(hd1)
    chainloader +1
    boot
}

That’s it. The USB drive is now bootable from BIOS and can be used to
install Windows on your PC. The first time you boot from it in MBR
BIOS or CSM mode select Start Windows Installation.

  • B. UEFI bootable

Not all Windows versions are supported. Windows 7 on 64 bits, Windows
8 and newer versions should work.

After the copy process is finished, look in the USB root folder for
the efi/boot directory. If there’s a bootx64.efi or bootia32.efi file
there, then you’re done. You can boot from your USB in UEFI mode.

If the OS you are making a bootable USB for is Windows 7, browse the
efi/microsoft folder and copy the entire boot folder from this path
one level up in the efi folder. Merge folders if boot already exists.

Here is what to do if you don’t have the bootx64.efi file in efi/boot
folder. Browse the mounted Windows ISO image into the sources folder.
Open install.wim (or install.esd) with your archive manager (you will
need 7z installed). Go to the path ./1/Windows/Boot/EFI and extract
the file bootmgfw.efi anywhere you want. Rename it to bootx64.efi and
put it on the USB drive, in the efi/boot folder. If you can’t find
bootmgfw.efi in install.wim then you probably have a 32 bit Windows
ISO or other types of images (recovery disks, upgrade versions).

You can now boot from your USB in UEFI mode.

I quote the original website for reliability, But the website is way better in style and details, So use it unless you force not to.

Tagged : / / /

Linux HowTo: Can I move Linux from running on a USB to a hard drive partition?

Original Source Link

I’m working on helping my brother with a project. He has been running Lubuntu Linux from a USB drive while he was setting up some server and web projects (proof of concept). Now that he has the official OK from his company to roll it out, he would like to transfer the OS that resides on the USB to a partition on his hard drive, so he can avoid having to reconfigure everything on a clean install. Neither of us has cloned a Linux install before, so I’m not sure where to start or if this type of clone/move is even possible.

Linux is easily cloned because it doesn’t depend on hard drive sector placements to boot. What you will need:

  1. Backup your computer AND your USB drive.
  2. Create your partition table with at least one Linux-compatible file system
  3. Boot from a live CD and rsync your system from the USB drive. (Don’t boot from the USB in question).
  4. Edit your /etc/fstab to reflect your new drive configuration.
  5. chroot into your new system and set up grub as your boot manager.
  6. Reboot.

I won’t go into detail on each of these steps because it’s a risky procedure and you need to do your research on this yourself. At any rate, do your backups! Did I mention you need to create backups first?

Tagged : / / /

Making Game: Can I move Linux from running on a USB to a hard drive partition?

Original Source Link

I’m working on helping my brother with a project. He has been running Lubuntu Linux from a USB drive while he was setting up some server and web projects (proof of concept). Now that he has the official OK from his company to roll it out, he would like to transfer the OS that resides on the USB to a partition on his hard drive, so he can avoid having to reconfigure everything on a clean install. Neither of us has cloned a Linux install before, so I’m not sure where to start or if this type of clone/move is even possible.

Linux is easily cloned because it doesn’t depend on hard drive sector placements to boot. What you will need:

  1. Backup your computer AND your USB drive.
  2. Create your partition table with at least one Linux-compatible file system
  3. Boot from a live CD and rsync your system from the USB drive. (Don’t boot from the USB in question).
  4. Edit your /etc/fstab to reflect your new drive configuration.
  5. chroot into your new system and set up grub as your boot manager.
  6. Reboot.

I won’t go into detail on each of these steps because it’s a risky procedure and you need to do your research on this yourself. At any rate, do your backups! Did I mention you need to create backups first?

Tagged : / / /

Linux HowTo: Tails on live USB flash drive freezes

Original Source Link

I’m testing Tails 4.6 on a Terra USThree 32 GB USB 3.0 flash drive. The host system is an IBM ThinkPad R60 with 3 GB RAM.

When loading multiple script-heavy websites on the bundled Tor browser or editing moderately-sized images with the bundled Gimp editor, the system quickly slows down, often to a point where it gets stuck in a permanent “overload cycle” indefinitely (mouse cursor gets stuck for a few seconds, moves again, gets stuck again etc.) or even slows down to a complete and permanent freeze, both usually requiring a forced reboot.

How can this be allowed to happen? I understand that the USB connection can be a bottleneck between Tails running on the stick and the host’s CPU, RAM etc. that it uses. But shouldn’t system stability have absolute god-like priority over any possible app that might be running?

FWIW, I’m experiencing a similar behaviour with the Android Tor browser on my mobile phone. It frequently consumes most of the CPU/RAM (heavy lagging when scrolling etc.) – until I simply cut the data connection, which immediately frees up CPU/RAM. Is this normal behaviour or could this be malware-related?

Tagged : / / / /

Making Game: Tails on live USB flash drive freezes

Original Source Link

I’m testing Tails 4.6 on a Terra USThree 32 GB USB 3.0 flash drive. The host system is an IBM ThinkPad R60 with 3 GB RAM.

When loading multiple script-heavy websites on the bundled Tor browser or editing moderately-sized images with the bundled Gimp editor, the system quickly slows down, often to a point where it gets stuck in a permanent “overload cycle” indefinitely (mouse cursor gets stuck for a few seconds, moves again, gets stuck again etc.) or even slows down to a complete and permanent freeze, both usually requiring a forced reboot.

How can this be allowed to happen? I understand that the USB connection can be a bottleneck between Tails running on the stick and the host’s CPU, RAM etc. that it uses. But shouldn’t system stability have absolute god-like priority over any possible app that might be running?

FWIW, I’m experiencing a similar behaviour with the Android Tor browser on my mobile phone. It frequently consumes most of the CPU/RAM (heavy lagging when scrolling etc.) – until I simply cut the data connection, which immediately frees up CPU/RAM. Is this normal behaviour or could this be malware-related?

Tagged : / / / /

Making Game: Security difference in using Linux by live USB vs. by VirtualBox?

Original Source Link

Can an expert please explain me which of following three methods working with an OS is technically considered more “secure” – and why (pros/cons)?

Security I mean aspects like:

  • preventing any malware to “swap” over to the other drives of the computer
  • web browsing
  • preventing traces of data from being read by the other OS drives of the computer

Here are the methods:

  1. Booting Linux from Live USB
  2. Dual-Booting – two OS systems on the same computer
  3. One Main OS on the computer, but using other OS via VirtualBox (or any other provider of virtual drives)

BTW, can virtual drive software like VirtualBox theoretically monitor everything you do when web browsing? is it just our trust in the provider, or is there solid “evidence”?

Tagged : / / /

Linux HowTo: Security difference in using Linux by live USB vs. by VirtualBox?

Original Source Link

Can an expert please explain me which of following three methods working with an OS is technically considered more “secure” – and why (pros/cons)?

Security I mean aspects like:

  • preventing any malware to “swap” over to the other drives of the computer
  • web browsing
  • preventing traces of data from being read by the other OS drives of the computer

Here are the methods:

  1. Booting Linux from Live USB
  2. Dual-Booting – two OS systems on the same computer
  3. One Main OS on the computer, but using other OS via VirtualBox (or any other provider of virtual drives)

BTW, can virtual drive software like VirtualBox theoretically monitor everything you do when web browsing? is it just our trust in the provider, or is there solid “evidence”?

Tagged : / / /