Windows to USB - Windows to Go

UFD is using Bootmgr (Works)
Host is using Bootmgr.efi (fail)

Use x64 version windows 7 which supports using bootmgr.efi

+++
Since JFX confirmed, I will let WinNTSetup add things to "my Win81x64 boot manager" for vhd and report back here...

Tested and failed, my stupid bood manager 

To me not critical,
 I learned some new stuff,
  Tested Wintousb,
   I first time practiced WinNTSetup for such goal which I found better,
    I will prepare a Win7x86 vhd on my usb disk, which would work side by side with Gena and Win7PESE,
      Not perfect but Life is good with working options

@JFX,
maybe another WinNTSetup topic around 

I have to learn PLC now, See You 

You could use UFD - Single NTFS  Partition using bootmgr > booting multi VHD's

X86 will not work with your Host bootmgr.efi

UFD is using Bootmgr (Works)
Host is using Bootmgr.efi (fail)

Use x64 version windows 7 which supports bootmgr.efi

I am also sure Win7x64 will work,
 There are lots of unupdated drivers for some devices where Win7x86 works nicely,
  Well all idea how to bypass this limitation to boot secondary none efi os,
    In the end legacy mode enabled but bootmanager gives the headache.... (It should be "boot manager"  )
     Anyway, booting a 2nd disk is not perfect, but it will suit 
      I wish card reader worked (so no need to plugin a 2nd device from usb), I feel "boot manager" won't let plop to workaround and I don't have time (and will) to test anymore....

Life is good 
 Time to play some with WinNTSetup Win7x86 VHD

ps: Still project idea is good 

you could convert Host to MBR and use Bootmgr
be able to Boot both x86 and x64

4 partition limit - BUT you are using VHD's - so non-issue

 

On the other hand it is always tempting to face new difficulties and discover how to overcome ... 
 And more important, I have too many stuff on my host which I don't want to mess up. 
  I am "very" user,
   And also, I am able to live with current conditions  and there will be solution to that

Life goes

Just did this with x86

Select your UFD as boot partition - so bootmgr and boot files are on ufd

And edit BCD to select your D drive for VHD

Booting from ufd directs boot to D:\VHD

Rather then loading vhd from ufd

Yes KYHI 

The idea of using 1GB sd card with a cardreader was same 

++
To workaround,
Since I have internal card reader, I tried (with a 1GB :) card,
 but figured out Asus bios does not let internal card as boot device (updated bios to 2.17 without change)
 Also "my Win81x64 boot manager" do not provide such device to boot. (other devices list...)
   --> ps: with legacy mode, other devices list there is ufd etc. which I can boot from...

ps: Asus N56VZ S4402H http://www.asus.com/Notebooks_Ultrabooks/N56VZ/HelpDesk_Download/

If cardreader worked here,
 only advantage is leave and forget it there.

Well it is nice we have workarounds at hand

would not boot GPT disk partition

edit the drive letter changed as I was using M

Had no luck booting x86 VHD on secondary HDD > no matter where I choose to write the boot files..
Using UEFI W8.1Core x64 host GPT partitions

For GPT you have to create the 100MB system partition yourself and select this one a boot drive.

Hi JFX,

well WinNTSetup can not do like WinToUsb,
shortly WinNTSetup fails with Win81x64-gpt

Longly:
after I create 100MB fat32 (E:) and rest NTFS (F:)  (first format and remove all, than convert to gpt )
I select Boot Drive -- 100MB fat32
installation drive (vhd)
after all done, "Efi Part" remains X , and tested I can not boot..

On explorer I see E: with files.....


WinUSB on GPT act different :
ESP
and
Boot Partition
see reply 7 picture http://theoven.org/index.php?topic=1232.msg14476#msg14476

After I do same with Wintousb, E: lost
 --> there is "You need to format drive E: during operation,
      later there is no E: around,
      and on disk manager there is now "100MB Healthy (EFI System Partition)"
       unlike WinNTSetup where E: remained as a regular drive with FAT32

I guess KYHI case similar..

@JFX,
maybe another WinNTSetup topic around 

We definately need a topic to gather things about WinNTSetup 

Hi KYHI,

With WinNTSetup I installed Win7x86 on a basic disk (usb), all went fine here,
 As I wrote above, There seems to be missing about gpt on WinNTSetup for now 

Well we need a WinNTSetup topic by JFX 

btw KYHI,

do you know ramdisk to use rams beyond 4GB,

 I had read these stuff on topics in past, but since I always use x64 (since XPx64) I ignore,
  but now I am on labs with old devices where they like x86 more, mostly Win7x86

@JFX,

btw, is it ok to add 2k3x86 VHD, better ask before trying...   

Hi KYHI,

Here is a v2 candidate to your plugin
https://www.dropbox.com/s/f5zvfec2xdf6mh0/WinToUSB_M_201503100100.7z?dl=0

I updated Plugin_Creator_Innounp to v32 for such multiarch case ;) (for now on Gena Server)
Utils\PC Innounp ->
1) WinToUSB_Setup_2.1_Beta.exe
2) WinToUSB.exe
(or 2) bin\WinToUSB.exe but I like WinToUSB.exe more for reasons... )

plugin above have a special iniwrite unicode
 (which I had used once on Opera8, I simply copy and paste when this rarely required ;) and always forgot creating a macro... )
  well you may find interesting to practice with PC Innounp , with the created one comparing with the working one, figuring out steps... 



edit:
it is easier to update such plugins once established nicely 
 only difference with .iss and minor modifications....

I use > Diskpart > Dism or imagex > Install.wim > BCDboot

x86 to USB works fine because USB is MBR legacy format and only needs to have one partition (system and windows partition = shared)

x64 to USB works fine because USB is MBR legacy format and only needs to have one partition (system and windows partition = shared)

99.9% of USBs can not be partitioned to contain more then one partition - non issue for legacy x86 and legacy x64 boot

You can boot x64 VHD files placed on a GPT disk (x64 supports GPT)

>> Limitations

You can not boot x86 VHD files placed on a GPT disk (unsupported)

You can not share the system and windows partition in UEFI Boot mode, which also requires GPT disk format

x86 does not support UEFI or GPT disk format (with 2 known exceptions)

>>> Portable Drive Considerations

Generic USB Flash Drives seem to have much slower read/write times

External HDD connected via USB seems to have a faster read/write times - but may require additional power source - may get flagged as removable drive..

Logic tells me - an Internal SSD in a cheap external enclosure would be the best option for portable windows (faster read / write times with much lower power consumption requirements)

Hi KYHI,
Here is a v2 candidate to your plugin
https://www.dropbox.com/s/f5zvfec2xdf6mh0/WinToUSB_M_201503100100.7z?dl=0

There is something wrong with the v2 plugin... When the program launched from script - it does not proceed without errors and/or stops responding. although did recover and finish.. But, Windows Disk Management also fails to populate and thus can not detach VHD..



I will also Note that program uses Legacy MBR Boot Option (as expected)
The programs > legacy vs. VHD selection option < = > File Folders vs. VHD File

>>
Here is the WinToUSB download > http://www.easyuefi.com/wintousb/downloads/WinToUSB_Setup_2.1_Beta.exe
which proceeds all through the VHD file creation without question (k=USB, L=VHDx64)



The three issues I have with WinToUsb - are it always wants to format usb before creation, selecting ISO and 14GB Min VHD

With WinNTsetup you can select wim and use existing usb boot manager (bcd).. A small issue is having the windows format option popup after vhd creation - for which you just have to cancel

The Problem with WinNTsetup is Booting VHD (k=USB, L=VHDx64, X=VHDx86) VHD creation process is quick - Boot code is wrong to boot vhd files (only seems to see attached vhd and detects prior VHD boot code as usual )


To be honest I did not detach the WinNTsetup VHD(s) prior to running > bcdedit /store k:\boot\bcd
To be honest unsure I did not detach the wintousb VHD prior to running > bcdedit /store k:\boot\bcd

But instead ran bcdboot commands to try and fix and no change until I closed VHD's (Prior untested Failure) (to late now)




Lance, have you accessed your usb's bcd after using WinNTsetup??

Just using WinNTsetup (formatted usb) without prior use of wintousb vhd creation on Host 8.1 core x64 (as above)
VHD is created on usb, BUT


Hope all this helps.. a lot of time testing this morning..
Kyhi

I use > Diskpart > Dism or imagex > Install.wim > BCDboot

Hello

Does Windows to go work on Windows XP ?
Just try and dont launch.

Kare
--

KYHI, it's your topic, but if you want you can also use this new WinNTSetup topic.

As for this error, it may not mention windows 8 Pro, but it will accept this one.

You currently have a windows 8 Core edition selected, this one does not support VHD boot.

Host 8.1 Core OS booted VHD yesterday..

Hello

Does Windows to go work on Windows XP ?
Just try and dont launch.

Kare
--

We in testing phase... To soon to pull that trigger.. But it seems to reason that WinToUSB does not support XP or Vista and has some known issues with Win 7

http://www.easyuefi.com/wintousb/index.html