[German version]Here I have described, how to create a Windows 8 To Go installation on a USB hard disk. The solution had a few disadvantages. First of all, it requires an old Windows 8 Build (I used Portable Workspace Creator, which was removed from Build 8102). And I wasn’t able to test my procedure with an 16 GB USB thumb drive, because the minimum is a 32 GB USB memory stick. Now I found a simpler way, to bring the Windows 8 Developer Preview as Windows 8 To Go-Version to a 16 GByte USB-Stick (work’s also with USB hard disks).
Werbung
Wrong paths …
My first approach was, to install Windows 8 in a virtual machine, using a 16 GB virtual disk. Then I tried to clone this virtual disk to a 16 GB USB thumb drive using the Linux-Tool GParted. But I failed, because GParted terminated during copy operation with errors. The USB memory stick was bootable, but Windows 8 couldn’t load.
One other idea, I have had, was: create a 350 MB boot partition and a 2nd 5,3 GB Windows partition using GParted and format that as NTFS drives (diskpart won’t support that). This approach offers the possibility to use the WAIK (Windows Automated Installation Kit)program imagex.exe to copy the Windows files to the 2nd Windows partition. But I also failed.
At least I discussed my toughts about imagex on German forum WinVistaSide.de. User hoschi80 cited the following from a BUILD presentation.
The same APIs used to deploy desktops and laptops can be used with Windows To Go
imagex /apply N:\Images\my-windows-partition.wim 1 W:\
Bcdboot.exe w:\windows /s X: /f ALL
After reading that cite, I rembered this arcticle, that should point to the right direction. A few hours later, user hoschi80 directs me to a second article, that confirmed my thoughts.
Step by Step: Windows 8 To Go on a 16 GB USB memory stick
First of all, we need to boot the Windows 8 Developer Preview (for instance in a virtual machine). Then it is mandatory, to mount the ISO file of a Windows 8 Developer Preview (I have used the 32 bit version). We also need the Windows Automated Installation Kit (for Windows 7), because the WAIK file imagex.exe from the Tools folder is required. I have copied the recommended 32 or 64 bit version to my Windows 8 machine.
After connecting the USB memory stick to Windows 8, we need to create a NTFS-formated primary partition on the USB memory stick. This can be done using Computer Managment-Console (branch disk management). Or you can invoke the command prompt windows using Run as administrator. Then you can use the following diskpart-commands to create the ntfs partition.
diskpart
select disk 1
select partition 1
delete partition
create partition primary
format fs=ntfs quick
active
exit
You can use list disk to query all drives, and list partition shows all partitions on a drive. The select command selects the drive and the required partition. Above I used disk 1 and then I deleted an existing partition on the memory stick. Afterward I created a primary partition and formats it with ntfs. The active command made the stick bootable.
After terminating diskpart, we need to copy Windows files to the USB thumb drive using imagex.exe. This can be done, using the following command in a administrative console window.
imagex.exe /apply d:\sources\install.wim 1 f:\
Here I launched imagex.exe from the currect directory of my Windows 8 drive. D: was the DVD drive (containing the setup media with the file install.wim) and F: was the drive letter of my USB memory stick. The number 1 defines, that only on Windows 8 edition should be copied.
After copying Windows successful to the thumb drive (on my system it took nearly 3 hours to finish), we have to copy also the boot files to the media. This can be done using the following command:
bcdboot.exe f:\windows /s f: /f ALL
within an administrative console windows. Drive f: is my USB memory stick. The command writes the boot files from the current Windows directory to the boot area of the target media.
Executing the commands above sucessfully, the USB memory stick should contain the files shown below. After unmounting the USB thumb drive the media can be used to boot a system.
To force a boot from USB memory stick (pen drive), it is required to invoke the BIOS boot menu (pressing a key like ESC, F8, F11, depends on BIOS version and vendor) and select the boot device. After selecting the USB media as boot device, Windows 8 should boot and starts configuring the system. The screen below shows the setup page to enter the computer’s network name.
During first setup, some reboots are necessary. Keep your attention to invoke the BIOS boot menu and select USB media to boot (otherwise the OS installed on the system disk will be booted). After configuring your Windows 8 To Go, the login screen should be visible. Below is my MSI Wind 100 netbook, showing Windows 8 start screen (I have used Windows 8 To Go on a 300 MB USB 2.0 hard disk).
Remarks: Using the steps described above brings Windows 8 Developer Preview to a 16-GB-USB thumb drive (or a USB hard disk) as Windows 8 To Go. The advantage against my 1st solution: we don’t need a Windows 8 Build containing Portable Workspace Creator, and we can keep existing partitions on a USB hard disk. The disadvantages are: We don’t have a 2nd partition “system reserved”, that is needed to set up bitlocker.
For my tests I have had only a 16 GB USB 2.0 thumb drive. I was able to boot my system with this memory stick. But the solution wasn’t really useable. Whilst I was able to use my USB 2.0 hard disk with Windows 8 To Go in a reasonable way, the USB 2.0 thumb drive took a long time to boot – more than 5 minutes – and setup the system for the first time. After entering the password in login screen, I waited 10 minutes. I could see activities on the USB thumb drive, but I still have had a black desktop with mouse pointer – and no start-screen. This is too long and I terminated my test.
Recommendation: If you intent do experiment a bit with Windows 8 To Go, I strongly recommend a 32 GB USB 3.0 thumb drive (or USB hard disc) and a computer with USB 3.0 support.
Schlagworte: USB-Stick, Windows 8 To Go
If you mean with this the imagex install then yes.
I: is the 32GB USB stick and I did imagex from a virtualCDrom drive to this I: USB stick.
I also tried with an 40GB external usb drive and got exactly the same problem.
@Sawyer: I have used the approach several times – it worked. If you try to use the command in Windows 7, I get the same issue. Here are a few questions:
- Did you invoke your command prompt windows unter Windows 8?
- Did your command prompt windows runs with administrator privileges?
- Is your target drive NTFS formatted and the partition is active?
Some “basic requirement” to execut the command successful is obviosly missing – but I can’t see what it is.
If you have the opportunity, to access M2 or M3 build 7989 – try pwcreator.exe – maybe that works.
Installs OK using W8 in Virtualbox. Target is 16GB Kingston. Booting for a while, get first startup screens. Then stops with error UNMOUNTABLE BOOT VOLUME.
Tried twice. This stick used to have ubuntu and was working OK. Cleaned and installed all according to this instructions.
No I did it under Windows 7.
I guess thats the mistake then.
On a side note.
I managed to install windows 8 on my USB hard drive with the other method where you first install the old leaked version of windows 8 witch has a portable workspace creator, then you just change the CD for the development build. Its running great now.
However I really like to have Windows 8 on my small USB key so I guess I will try again under 8 now.
Yeah I did the above steps under Windows 7 :\
Tried it now under 8 and it works there just fine.
I also made my first portable disk with the other leaked build method.
But Since my USB stick is little bit to small for that method 14GB I will try yours again now. Already copying.
@Sawyer: Thanks for feedback.
BTW: Here is a YouTube video showing Windows 8 To Go on a slate (but my comments are in German).
Worked fine on my small usb 14GB which wouldnt work with Portableworkspace creator. It also worked fine with my stupid 32GB Jetflash 3.0 key which also doesnt work with pwc.exe due to it being incompatible.
However the USB key version is slow like hell but my 40GB old portable USB 2.0 hardware version is suprisedly fast. Almost native speeds.
@Sawyer: Thanks for feedback – you confirmed my personal experience. As far as I understood, the USB key Microsoft handed out at BUILD 2011 was a modified one (it is identified as a hard disk from firmware).
[...] 8 on flash it is still possible with a little work. Despite being aimed at enterprise users, Born city has step-by-step instructions that will guide you through the process of creating a “Windows to Go” setup that will use your [...]
[...] 8 on flash it is still possible with a little work. Despite being aimed at enterprise users, Born city has step-by-step instructions that will guide you through the process of creating a “Windows to Go” setup that will use your [...]
Update: At least I found a thread [1] in MyDigitalLife-Forum, where Windows 8 To Go is also discussed.
1: http://forums.mydigitallife.info/threads/29248-Running-Windows-from-an-external-USB-drive-with-Windows-To-Go/page2/
Can you use a 8gb flash drive?
@Brian: I fear 8 GB is far below the space Win 8 needs as a minimum. Also I wrote that USB 2.0 thumb drives are to slow for practical use. A USB 2.0 hard disk up and above 32 GB will be a good choose. Here I use a 320 GByte USB 2.0 hard disk, that contains two primary partitions, each 40 GB in size, hosting a 32 and a 64 bit Windows 8 To Go. I’m using dual booting to switch between both versions.
Thanks for this guide! Helped me alot.
In the steps there are a few minor things missing:
- When you are in diskpart you have to call “assign” to assign a drive letter to the created partition (At least I had to do that)
- You have to use the bcdboot.exe from the Windows 8 installation (call it from c:\Windows\System32), the bcdboot.exe from the WAIK folder doesn’t support the /f option.
@Chis: Thanks for your comments. Assign is right, if the volume isn’t associate with a drive letter (I guess, I have made this in computer management).
The bcdboot.exe thing: thought it will be clear, because I’m stating that you have to boot with Windows 8 and execute the commands. But thx too for clarification – maybe it will help others to be succcessful.
Have fun with Windows 8 To Go
I have a 32 GB Corsair USB 3 flash drive. It’s very slow to load the system and it’s pratically unusable (also on USB 3 motherboards). The drive is rapid for reading/copying files, but slow for boot Windows 8. What can i do?
@Andrea: Thx for feeback. I havn’t USB 3.0 enabled hardware, so your information is new for me. My suggestion: Just use a cheap USB 2.0 hard disk – these drives seems to be fast enough. I run Windows 8 To Go from a 320 GByte USB 2.0 hard disk – and it’s fast enough.
HTH
What I’ve read (after I published the article) is, that Microsoft has used a modified USB 3.0 flash drive handed to the BUILD participants. The firmware of this stick was modified in a way that it reports a hard disk to operating system.
@Günter Born: Do you know if there are some tricks to run faster Windows To Go in my USB stick?
Another thing: Windows To Go created with Portable Workspace is the same of extracting install.wim?
@AdreaR: I don’t know a trick how to run Win 8 To Go faster on a USB stick.
Concerning to your 2nd question: Yes, Portable Workspace creator do the same trick as I described it in my article using imagex.
Hello again
It is not sure at all that this Windows To Go feature is going to be present in the beta (by end of february 2012) and in the final ‘client’ versions of Windows 8.
That’s what a lot of well informed people think, like said here:
http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/5c4ff9ac-65a6-49f5-a87d-33851746effe
The expiring date of the actual Windows 8 Developer Preview is 3/11/2012 (as shown in winver.exe)
So I think that this means that the USB drives that we created with WTG will stop fonctionning on the 12th of march 2012 !
Is this correct ?
So if this feature is not anymore in the future client versions (beta, RC, RTM, …) it means that experimenting with WTG will be finished for the “grand public” and reseved to Enterprise versions.
What a pity !
That destroys most of my intesterest in Windows 8 as a new OS … Because I am no going to play with my fingers and the tiles of Metro
@franz99: I agree with your thoughts – but in moment, it is a nice feature I’m using to run test drives of Windows 8 on different machines (slates, desktops, netbooks). No need, to set up Windows 8 on a foreign machine – just boot up my USB 2.0 disk on a machine let me do my tests.
Concerning “it is not sure …” we have to wait, what the beta will bring (I have seen screen shots of further Win 8 builds containing portable workspace creator again).
Concerning “an in the final ‘client’ version” – well, my guess is, that according to licensing issues this feature will be available only in Windows 8 Enterise clients at all.
But we have to wait and see – also with the metro stuff
.
Has someone had good results with a USB 3.0 stick?
@AndreaR: My last comment “What I’ve read (after I publihed the article) is, that Microsoft has used a modified USB 3.0 flash drive handet to the BUILD participants. The firmware of this stick was modified in a way that I reports a hard disk to operating system.” is still valid.
Using a USB 2.0 hard disk gives me reasonable results.
“ The firmware of this stick handed out by Microsoft to the BUILD participants was modified in a way that I reports a hard disk to operating system “
Do you know WHY is it important to have this modified firmware on a USB stick so it reports a hard disk to operating system ?
Does this modification influence :
- the booting capability
- the speed of the booting
- or the way it operates AFTER re-booting and getting all the nexessary drivers ?
@Franz99: Unfortunately I haven’t any information, why Microsoft decided it this way. Booting capability should bei (in my opinion) no issue – also the speed of booting should not be influenced – because this depend in my opinion on read access speed. I guess it has something to do with “after boot process and driver loding” – but I’m not really sure.
For my own, I enjoyed my USB 2.0 disk with the Windows 8 To Go dual boot configuration (32/64 bit) I have set up. But we have to wait and see, if Windows 8 To Go remains in Beta (my information is, that the portable workspace creator wizard was removed in the last pre-beta builds).
i tried the steps on usb 2 16gb memory disk and there is mountable boot disk error can you please let me know how to solve that
@vasu: Sorry, I have no clue, what went wrong.
bcdboot.exe f:\windows /s f: /f ALL
I see the letter f three times here is there something wrong
@krish: I don’t now, whether there is something wrong. The /f All is an option, whilst f: is a drive letter (could also be D: or G: – depends on your system).
I found also another article at [1] which seems that the author already has tried out. Most of the other articles dealing with Win 8 To Go (like [2]) are copy cats of my article above.
1: http://www.intowindows.com/how-to-run-windows-8-from-usb/
2: http://techeblog.in/tag/bcdboot-exe-fwindows-s-f-f-all/
Cris !
+100 REP Dude
After i used you`s advice all finished 100 %
I have working USB HDD booting Win 8
**********************
Christiaan Veeningen sagt:
2. Dezember 2011 um 12:32
Thanks for this guide! Helped me alot.
In the steps there are a few minor things missing:
- When you are in diskpart you have to call “assign” to assign a drive letter to the created partition (At least I had to do that)
- You have to use the bcdboot.exe from the Windows 8 installation (call it from c:\Windows\System32), the bcdboot.exe from the WAIK folder doesn’t support the /f option.
************************
@Niksavoy: Thanks for feedback – it has been a while since I tempered with Win 8 To Go. Hope it will be supported in Consumer Preview at all.
Has anybody reached good results with USB sticks?
[...] Fuente ¿Recomiendas Cómo instalar y ejecutar Windows 8 desde un pendrive? Tweet ¿Te gusta Planeta Red? Tags Manuales y tutoriales Windows Windows 8 Categorias [...]
[...] and here I’ve discussed, how to use Windows 8 Developer Preview to create a Windows 8 To Go installation [...]
I’ve managed, almost by accident, to install using a simple method , Windows 8 on a usb drive. I did it using the installer.cmd at the WAIK files , using my laptop with windows7. I didn’t have to install windows 8 on a virtual machine. It works just fine. At first it didn’t work at a normal usb startup, so , because I have Chameleon bootlodaer, I decided to choose the usb drive from the menu and it works great.
@António: Thanks for the tip. It seems that installer.cmd contains the commands to setup Windows 8. I’m curious and will inspect the installer.cmd later, because the bcdboot.exe command won’t work unter Windows 7 in the way, I’ve presented it in my article.
So I guess, instead of Cameleon bootloader we can use also Plob bootloader (from EasyBCD) for USB boot. Will give it later a try.
Update: I now found also an article here – that describes, how to use the install.cmd to bring Windows 7 to USB devices.
@Gunter: I’m glad you liked my tip . That article is precisely the article I’ve based my work to have Windows 8 running on a usb drive, but , as I said, at first it didn’t start by itself. Then using a bootloader problem was solved. Thanks also for your support and keep the good work
Hello, do you have a way to create a Windows To Go drive able to boot on a MacBook? I’ve sow that the official usb drive created by Microsoft runs well on macbook but i’ve created one using your tutorial that works well on a acer but im not able to boot on macbook. Thank you.
@Alexandru: I don’t have a MacBook nor I will have in Future. So I can’t say what to modify – maybe the To Go Drive need to be set up in GTP instead of MBR.
I also got yesterday a 32 GB USB 3.0 Stick from Kingston as a test sample. Somehow I was not able to create a bootable To Go Version on this thumb drive using my tutorial – the best I got was an error, that Windows was broken and I should fix it, using repair environment. At least I used Portable Workspace Creator from a M3 build to create my Win To Go on USB 3.0 Stick. I haven’t have the time yet to investigate, because I’m writing a book about Win 8 CP.
If you find a few free space and want to write some tips for trying to set it in GTP instead of MBR I could try this for you and let you know.
@Alexandru: If you have a few tipps to install Win 8 To Go on a GPT disk, maybe you can leave it here as a comment – I will have a look at it and will publish it as a guest article.
BTW for all reader: Currently I’m testing a Kingston 32 GB USB 3.0 Memory Stick. It is recognized as a “hard disk” in Windows – and I was able to create a Windows 8 To Go version on it. But – the solution isn’t too reliable. First of all, I had no luck, to create Win To Go using my instruction given above. The best I could get, was a Blue Screen telling me, that winload.exe was missing. And automatic repair failed – I have had not the spare time to investigate it in details.
Then I used portable workspace creator from M3 Build to create Win To Go on that stick. The thumb drive worked from scratch, but I have had some issue. The USB stick was booteable on my MSI Wind U100 netbook – but it refused to boot on a WeTab (Petagron) slate. The USB 2.0 hard disk version doesn’t have this issues.
After I finished my Win 8 book project, I will investigate it a bit more.
I ran imagex.exe from \Program Files\Windows AIK\Tools\amd64 and that’s okey. The problem is that this directory has an old (Win7) version of bcdboot.exe. So when I ran bcdboot.exe from the same directory the old version was used. I changed directory to C:\ and everything was fine. Just a warning to others.
@Oyvind Eriksen: Thx for feedback. Maybe it was also the problem I have had a few days ago during a test with a 32 GB USB 3.0 thumb drive – because I run out of time, I used at least the Portable Workspace Creator from M3 to create my Win 8 To Go CP.
Overall I’m going away from Windows 8 To Go. As described here [1] (only in German), I run in serious issues with a WeTab slate and a MSI Wind U100 netbook.
- The graphic adapter was not recognized properly – only a Microsoft Basic VGA-Graphic adapter driver was installed
- As a consequence, my netbook’s display resolution was fixed to 800 x 600 pixel. The slate display resolution was fixed at 1260 x 768
- I was not able to find Updates through Windows Update
- I was not able to install separate graphic drivers (error: the driver isn’t compatible with this Windows)
- Also PC refresh and PC restore won’t word (a message says that this wasn’t supported)
At least I did a native Windows 8 install on the WeTab slate and the screen resolution was 1366 x 768 out of the box. Also on my MSI Wind U 100 I was able to install Intel Mobile 945 driver and came to 1024 x 600 (and with a trick to 1152 x 864 pixel.
So Windows 8 To Go (Consumer Preview) is good for first experiments – but not for in deepth analysis (as I need to write my Windows 8 books).
1: http://www.borncity.com/blog/2012/03/16/windows-8-grafikauflsung-beim-msi-wind-u-100-teil-1/
@franz99: I’m getting a bit lost with your comments. To keep things a bit updated for my English language readers (my German readers got the insights at all in several To Go articles) here a brief compilation, what I found out so far.
The USB-Stick problem
I’ve mentioned in the comments above, “The firmware of this stick handed out by Microsoft to the BUILD participants was modified in a way that it reports a hard disk to operating system “
@franz99 asked on 24. January: Do you know WHY is it important to have this modified firmware on a USB stick so it reports a hard disk to operating system ?
Does this modification influence :
- the booting capability
- the speed of the booting
- or the way it operates AFTER re-booting and getting all the nexessary drivers ?
Answer: Well, after discussing the topic with a German reader of my blog – the pieces fellt into the right order to fit the puzzle. The problem with USB sticks is, that the USB filter driver for Windows just supports one partition during boot. Whilst it isn’t a problem, to create multiple partition in Linux, an ordinary USB stick created with Portable Workspace Creator comes with two partitions (one 350 MB “system reserved”, containing the bootmanager, and one system partition containing the Windows 8 files). Using the method described above, creates just one partition, but some USB sticks refused to boot (for unknown reasons).
Kingston just has created a series of USB 3.0 DataTraveller Ultimate Sticks, that comes with a controller with a modified firmware – that will be recognized as a “hard disk” from Windows 8. I discussed it in my German article Windows 8 To Go und USB 3.0-Sticks – Teil I. I got one evaluation sample from Kingston – but the USB 3.0 thumb drives are not available to the public (only samples for customers with a need for a huge amount of sticks will get a chance to place an order – as far as I understand some corespondence held by another reader with Kingston).
So, overall: USB 3.0 thumb drive will do the trick in future – current thumb drives are not coming with this modified firmware.
Trouble with Windows To Go created from Windows 8 Consumer Preview
After releasing Windows 8 Consumer Preview I begun experimenting with Windows To Go (using Portable Workspace Creator and the steps discussed obove). I used a USB 2.0 hard disk, containing several partitions with 32-/64 Bit Windows To Go (Developer Preview and Consumer Preview) in a multi boot environment. Whilst Win To Go in Developer Preview ends in good results, I completely failed with Consumer Preview versions of Windows To Go.
Of course, Windows TO Go boots and I was able to use it. But there are a few big issues, I haven’t noticed in Developer Preview:
- The graphic card wasn’t detected in a proper way on a MSI Wind U100 netbook and on a WeTab slate. The Microsoft Basic Graphics adapter driver was installed, and screen resolution war limited to 800 x 600 (on a netbook) and 1024 x 768 on a slate (tablet pc), althought both devices comes with a much higher screen resolution.
- As a consequence I was not able to use metro apps on my netbook and I couldn’t use split-view on my slate. Because Windows To Go doesn’t allow to install driver, I was not able to update the Intel mobile graphics display driver (got an error, that the driver isn’t compatible with this version of Windows).
- Also Updates was blocked and PC refresh and PC reset was blocked as well.
Overall, in consequence, Windows To Go in Consumer Preview isn’t useable! I switched to native install, to write my book about Windows 8 Consumer Preview.
Concerning the question raised from @franz99 about Virtualbox install on a usb thumd drive: In prinziple it should work (I have never used it). But I use Virtualbox portable here on my desktop system. What you need to know using portable Virtualbox is:
- During launch, some profile information will be written into the user profile of the host. So there is no “indian approach” (come in and leave without traces) possible.
- You need a working host OS on the computer that is compatible with Virtualbox on the USB thumb drive.
- Virtualbox portable comes with a few issues: sometimes USB is faulty (I was several time in need to install virtual USB driver on the host manually to invoke USB devices). Also bridged networking isn’t available in portable Virtualbox. The best you can use is NAT – and this causes here the effect, that my local network devices will not be listed in network environment. I need to enter a UNC network path \\rom7 to access my shares on computer Rom7.
Overall: it’s a messy situation. Windows To Go could be a huge thing, if MS improves it. In the mean time between now and a possible improved version, my proposal is: use a native install (maybe on a virtual disk (.vhd file) – or stumble with android and linux (both OS supports USB boot out of the box – and run fine on ordinary thumb drives or SD cards – and also the foot print is much smaller
.
HTH
Thanks a lot Günter for wrtiting this summary !
I think that all we have to do now is to wait next June for the RC version of Windows 8 and hope for a « real return » of Windows To Go with a integrated feature like « PW Creator » found in the early M3 leak of Windows 8.
I remember that this « PW Creator » used to force the creation of 2 partitions (one system reserved and one with the Win 8 files) on the targeted USB device. So in case of using a USB stick we will have to take care to use one of these special sticks recognized as a hard drive by Windows (like the USB 3.0 DataTraveller Ultimate)
I agree that the actual situation is messy :
WTG created with DP was more or less working (at least booting), but the Windows To Go created with Consumer Preview is not useable !
If Microsoft does not improve it, we will have to forget about a « mobile Windows » and this does still not answer the central question :
in which commercial SKU will this feature be available legally ?
Any SKU available to the individual customer or only for enterprise and volume licensing ?
I mean which is going to be the price we will to have to pay every time to active WTG on a USB stick ?
Will it really boot as a full OS on any computer running Vista or above as Sinofsky said in the presentation made at the Conference BUILD ?
Or are we going to run in never ending driver problems ?
And at the end what is going to happen when we will clone with Ghost.exe such mobile Windows ?
I am very disappointed every time I create a Windows To Go derivated from a Windows 8 version using the method described above.
All I get IS an incomplete OS without Start Menu and without the software I am used to.
I would prefer a « Windows 7 To Go » if possible !
So my question: is it possible to deploy Windows 7 on a USB device using this command line :
imagex.exe /apply d:\sources\install.wim 1 f:\
on a computer with Windows 7 installed.
I do not really understand the meaning of the number 1 in the command line.
Above your statement :
« The number 1 defines, that only on Windows 8 edition should be copied »
Should the 1 be omited in case of a Windows 7 deployement ?
And then:
bcdboot.exe f:\windows /s f:
without /f ALL
should be sufficient to copy also the boot files to the media
So is it possible to create a Windows 7 To Go with the same method one can create a W8 To Go ?
I something going to fail in the procedure or be locked in the result ?
@franz99: I never tried Windows 7 “To Go”, because this OS loads the USB driver in a different manner (compared to Windows
during boot process. AFAIK, in Windows XP we have had to use a 3rd party USB driver to get a booteable version on SD/USB (I was never able to get it to run).
But within the comments I published some links to an alternate website, that quotes “a solution for all Windows version”. For my own, I’m sceptical, because of the USB driver issue mentioned above (and I never tried to waste my time). Unfortunately it seems also, that the site:
http://techeblog.in/tag/bcdboot-exe-fwindows-s-f-f-all/
reached it’s traffice limit verry often. So, overall, you need to test by yourself, if it’s important for you – I don’t have the time to investigate this issue (especially, because I still have some hope, that MS will add portable workspace creator wizard in upcoming RC).
Thx for commenting – I will publish also an article about the “USB thumb drive” issues coupled with “Windows 8 To Go” (maybe first in German, but probably later in English). One of my German readers brought a few missing pieces of the puzzle and I was able to put it into the right position – so, now the image becomes visible. Using USB thumb drives together wie Windows 8 is a “nasty thing” at all.