Windows 10: Booting from USB stick or DVD

I am sorry but you are getting totally confused between win2usb and Macrium. they are totally unrelated and fulfill totally different functions.

 

Are you trying to build a second Windows installation that you can boot from another drive, or are you trying to make a backupof your existing installation that you can boot into if your primary one fails?

For the former, you can use WintoUSB. For the latter, you're better off at looking at making a .VHD of your existing system in order to be allowed back into it, or else look into Macrium's other features whereby you can boot one of their images directly.

See Macrium Reflect Free | Macrium Software fro more information about being able to boot Macrium backups via their own PE, under the restore section.

EDIT:I do not believe that this will allow you to boot the image itself, but rather, that you will be able to restore the image from the bootable PE environment that Macrium can make.

 

Yes, why are you trying to use an image file to create a Live W10 usb stick ????

Just use the link given in reply #11


Your best backup plan would be to create an image file of Windows 10, as already suggested.

And just use a live linux distro as a rescue device.

 

Hi folks

The live Linux Distro idea is actually very good --especially if you have an older SSD with a SATA-->USB connector.

What you can then do is create a Windows virtual machine on your Linux device - SAMBA etc will ensure that you can get access to any HDD's you need on your main computer. With an external SSD even on USB2 the response of the Windows VM will be perfectly OK. Loads of people have older 128 GB SSD's around -- ideal for this purpose.

You can also use the Windows VM as a tool for repairing / recovery of your main Windows installation. Don't worry about activation of Windows if you are simply using the VM as a recovery tool -- a W7 installation gives you 30 days and W10 will work for long enough to fix any problems before giving those activation nags.

The advantage of this is that the Windows VM will run on ANY machine !! - Linux boots easily and the overhead is very small.

Use VMWARE PLAYER or VBOX for creating the VM's.

If you merely want a bootable copy of your existing Windows system simply create the Macrium bootable media and either save the backup image on the same device or when running Macrium .

I think there's also an option to make the image file itself bootable so you can recover that way.

When creating the Linux system though I'd suggest ensuring it works in MBR mode --that way it will boot both on older machines and newer UEFI ones. Some Linux installs will give you the option but others will use the boot system it finds on the machine used to install the OS.

I have W10, W7 and XP as 3 VM's on a 250 GB SSD with CENTOS 7 as the Linux distro. On USB3 I can run these 3 VM's all concurrently with decent response even on an 8GB laptop.

The W7, W10 X-64 VM's only need 2 GB and XP will run easily in 1 GB.

Very useful tool .

Cheers
jimbo

 

IMO this is a sledgehammer to crack a nut.

If you want a rescue enviroment, use Kyhi's tool

Windows 10 Recovery Tools - Bootable Rescue Disk - - Windows 10 Forums

If you want to boot from a usb with full windows, use tutorial in tutoria section or use wintousb (Web Server's Default Page). I do not know why OP says it does not accept isos as that is exactly what it does.

Running Windows 10 in a VM does not use native drivers of pc and no matter what anybody thinks, you do get a performance hit.

You state "The advantage of this is that the Windows VM will run on ANY machine !!".

Unless pc can be enabled for virtual technology, then this is not accurate. I believe it is possible to run vmware on pcs not vt-x enabled but they will run so slowly on old devices to make it almost impossible to use.

Also older devices may not have enough RAM and may not be possible to add extra RAM.

A "windows to go" install will run on any pc, provided there are suitable drivers.

 

Hi there

actually any 32 Bit OS can run as a Virtual OS on a machine - even if not VT enabled -- if VT enabled a 64 bit VM OS can also run on a 32 bit HOST. Note though if running a 64 bit GUEST on a 32 BIT HOST max RAM that can be allocated for Host + Guest is 4GB regardless of how much physical RAM is installed on the machine.

Running VM's on older hardware will of course present a challenge if the hardware isn't up to the job - but then so was running some base native apps like VISTA. Lack of RAM and really poor I/O (HDD's even today can be terrible performers) usually were more of a hindrance than actual CPU power. I doubt you'd want to run say a Windows 2012 server VM on a 1GB old Netbook for example !! even if you could find a way to do it.

As to performance -- I think if you wanted to repair a system performance isn't the first objective when trying just to fix a machine so it will boot.

If a machine is broken the first thing is to get it to BOOT --the VM can fix your machine (in nearly all cases ) so it will boot. Then you can install all the other stuff you need including new drivers which you can use the VM or external Linux system to download for you if the "Broken machine" doesn't have Internet access at that point..

Meanwhile the VM option - or even a Linux base system can help you browse the internet and look for solutions while the other PC is inoperative.

The VM idea could be regarded as a "Sledgehammer" to crack a nut with - but it's nice having 7 or 8 different Language versions for Windows and even more languages for Office --- If you work in as many different countries and locations as I do then it's a perfect solution. (I have office 2016 --VL version so no re-activation required when booted up on to a different machine).

There's no way I would be allowed to boot an "Unofficial" Windows to go from any sensible corporate network - especially if you are working as an external consultant.

All these solutions just give people the option of more choices - and actually the overhead of running a VM from an OS booted from a USB 3 device is pretty minimal compared with a HOST OS running from a typical spinner !!!!!

Like most of these things there's no "One size fits all" --that's what's great about these Forums - there's loads of ideas around people can read up about --some better than others of course but a great place as an "Ideas Factory".

BTW the wintousb nethod fails on the latest CU update (1703) with the extra updates applied -- I haven't tried creating a new ISO --I'll have a go with that later.

Note also the wintogousb while a good get around is an unofficial non Ms supported system so if you use it there's no guarantee it will keep working -- especially with the whole slew of fixes / updates and releases Ms has in the pipeline.

Creating a WINPE environment seems probably the most stable way of getting a decent bootable external Windows system - but that's for recovery --it wouldn't be any good for running applications like say OFFICE.

Cheers
jimbo

 

Interesting theory ...

 

I have a wintousb install of 1703 on a flash drive with all the updates installed - works fine.

Obviously winpe can only run truly portable apps.

I doubt wintousb will ever stop getting supported in near future. It now can create uefi installs on a standard removeable flash drive which annoyingly the official Windows To Go will not do despite it now being possible as you can read multiple partitions on drives without the "fixed drive" bit enabled.

I do not see that you would be allowed to run linux drives with windows in a vm any more than windows on a usb on a corporate network. Most big companies i deal with lock down usb drives so you cannot boot from them - many will not even let you read from them.

You are comparing oranges and apples when you say running vm from usb3 would be faster than running a host from a slow spinner. Running a host OS from usb3 will be faster than running a vm from usb3, and running vm from a slow spinner will be slower than running host from a slow spinner.

However, you are totally correct about different ideas. But I still subscribe to the KISS principle where possible.

 

Windows to go creator has been suggested. Sounds like what you were asking for. *Confused


It also is possible to create an install.wim of your current installation ( with all your programs and files ) and apply that to another drive. Probably be able to apply that to usb, you would need to fix the drive letter after applying the image.

Have you tried applying a macrium image to usb? Aomei can do it, I expect macrium can.

 

Hi there

Agree with the KISS principle wherever possible.

Fortunately at a lot of my gigs I don't have trouble with a Linux VM.

Every workplace has different protocols -- and it's probably a HIDEOUS nightmare for admins if the "Bring your own Device (BYOD) " model is implemented everywhere --

What does work though in a load of places is that on your own laptop you can usually connect to a Wireless or even a LAN network that isn't connected to say a production system but has more access than standard "Guest" or "Visitor" network. Saves the company from having to supply laptops to external consultants and being an external network any problems aren't the fault of the company -- as it's always Use at Own Risk as it's provided for convenience just like customers going to an Internet Cafe.

Corporate Networks with access to Production systems (or even a decent QA Pre Prod for final testing one) are usually for very good reasons locked down of course.

Cheers
jimbo

 

I prefer BYOB to BYOD ;-).