Winpe_amd64

[Vangele Ioannidis]

Ican run the amd64.bat file from the 'Deployment and Imaging Tools Environment' command line, but it only runs the first command, in this case: copype amd64 C:\winpe_amd64. After that no commands will be launched, even though the first command was successful.

Some notes:If I have the color changed, this will work, same like the 'title' option.It simply runs the first command. The whole package is 30 commands long (this will grow with the growing amount of drivers to be added)

I have installed Microsoft WAIK and the supplementary package. I have on the first technician machine created a winpe bootable image with a set of custom drivers and away i went mounted it added drivers commited the changes and created the .iso. Well I must of done something to the installation afterward by trying to mount and inject another set of drivers...now it will not mount the image and fails at 3 percent and the command line window freezes. The process cannot be killed (Have to log or reboot). It does mount something as there are files in the mount folder. So i thought ill launch another instance and try to inject drivers. It gives me an error about it is an unsupported windows Vista RTM image??? i did imagex cleanup commands dism cleanup commands, uninstalled Windows AIK and the supplentary package and reinstalled it all again. Created a new winpe install directories, used other directories all with the same problems. It always freezes and gives that vista error. On another computer entirely i just installed MS WAIK and the supplementary packaged walked through the MS tech net install and setup walkthroughs and the using DISM the mount fails and freezes again at 3% on this machine ... i googled the hell outta this for over a week. I need help. I am new to this but game to try anything..

I created the winpe_ia64 directories and used this architecture instead of winpe_amd64 and it mounts and unmounts and injects as it should. Seems like i just picked the wrong arch. for 64bit. Wish i tried this weeksago.

Okay on another machine i reinstalled Windows AIK, installed the supplementry package, cereated the winpe_amd64 folders copied winpe.wim and created the \ISO\ folders etc. I my first dism command to mount the winpe image and it stalled again on 3% and hanged the cmd gui. Here is the dism log.

Okay got the same crap happening with ia64 uninstalled and deleted all directories and fully reinstalled winaik and supplementry and cant mount freezes at 3 or 4 or 5% will unmount however. Also compelted blasted it away again and tried with amd64 same crap... i am pretty sure its just a flakey program and i have wasted enough time on it. Back to Norton Ghost i suppose.

Bare metal restore for Windows 7 and 8--------------------------------------Authors------- Wai Keong Phan: First completed a bare metal restore on Windows 7 and wrotethe first draft. Graham Keeling: Edits to the original draft, with help from Wai Keong Phanand Michael Da Cova. Peter Maloney: First completed a bare metal restore on Windows 8, updatedthe instructions and converted them to the wiki.Prepare-------Install burp on the admin boxInstall one of these on an admin box ADK (Windows 8) -us/download/details.aspx?id=30652 AIK (Windows 7) =en&id=5753You should use the latest one. The Windows 8 version works for win8 or older(win7, xp, etc.).Maybe another boot CD will do also. Basically all that is requires is that ithas: diskpart burp(It has been suggested that a Linux CD would work. It will not, because Linuxdoes not know how to restore Windows VSS files)The other things needed (eg. "bootrec /rebuildbcd") can be done from theWindows install CD.Create and mount the winpe boot CD on the admin box, run "Deployment andImaging Tools Environment" with administrator rights.> copype.cmd amd64 c:\winpe_amd64> cd c:\winpe_amd64> copy winpe.wim media\sources\boot.wim> dism /mount-wim /wimfile:media\sources\boot.wim /index:1 /mountdir:mountPut burp on the CD (this assumes you have the burp client installed on theadmin box)> cd \Program FilesBack up the old burp client, so a burp restore can be built in the defaultlocation (workaround for hardcoded paths)> xcopy /E Burp BurpClient Does BurpClient specify a file name or directory name on the target (F = file, D = directory)? DPrepare the BurpRestore directory (currently named Burp)> cd Burp> del ssl_cert*> del CA\*> notepad burp.confMake sure the burp.conf has the right user name and password that the serverwill accept for a restore.(burp-server.conf has a line like "super_client = restore").Set cname/username to "restore"> bin\burp -a l This will generate the SSL keys.If there are problems here, you can go on the server in the /etc/burp/CAdirectoryrm restore.* Edit index.txt to remove the "restore*" lines. Retry.> cd ..> move Burp "C:\winpe_amd64\mount\BurpRestore"Put the old burp client back where it goes.> move BurpClient BurpFinish the BurpRestore setup by setting the correct paths as they are when youare booted on the CD.> cd "C:\winpe_amd64\mount\BurpRestore"> notepad burp.conf sC:/Program Files/BurpX:/BurpRestore> cd ..\..Unmount and create iso.> dism /unmount-wim /mountdir:mount /commit> oscdimg -n -betfsboot.com media burprestore2_amd64.isoBurn the iso to a CD to use it in physical machines, or test it in a virtualmachine.Remember this CD has the restore user password and private keys on it, so keepit secure.Backup------Obviously for a bare metal restore to work, you should include the wholeoperating system volume.Here is an example client file.include = C:/# temp stuffexclude_regex = "[A-Z]:/Users/[^/]+/AppData/Local/Temp"exclude_regex = "[A-Z]:/Documents and Settings/[^/]+/Cookies"exclude_regex = "[A-Z]:/Documents and Settings/[^/]+/Recent"exclude_regex = "[A-Z]:/Documents and Settings/[^/]+/Local Settings/Temp"# iometer test fileexclude_regex = "[A-Z]:/iobw.tst"# system stuff that is not important in a restored systemexclude_regex = "[A-Z]:/RECYCLER"# swap file (Windows XP, 7, 8)exclude_regex = "[A-Z]:/pagefile.sys"# swap file?? (Windows 8)exclude_regex = "[A-Z]:/swapfile.sys"# note that we are backing up C:/System Volume Information"Restore-------Boot the CD.Create file system.> diskpartDISKPART> select disk 0DISKPART> create partition primaryTESING: select partition 1DISKPART> activeDISKPART> assign letter=CDISKPART> format fs=ntfs quickDISKPART> detail diskDISKPART> exitRun restore.> x:> cd \BurpRestoreJust a test.> bin\burp -a l -c burp.conf -C $nameRun restore (the -f is optional; if it fails, try without).> bin\burp -a r -f -c burp.conf -C $name -d / Be patient... this takes a long time.> c:> cd \windows\system32> shutdown /r Takes very long to actually shut down... put in the regular Windows CDwhile you wait.Run from regular Windows install CD in repair mode "command prompt".> diskpartDISKPART> select disk 0DISKPART> select partition 1DISKPART> activeDISKPART> exit> bootrec /rebuildbcd(In Windows 8) close the command prompt by clicking X, then click "continue toyour OS" or something like that, and it will reboot. When testing win8 final 64 bit, I forgot to do "bootrec /rebuildbcd" and ran repair instead, which seemed to work.For Windows 7 and 8: Run the install CD's automatic repair 2 times, then rebootto your OS. Don't run it from the same boot as the "bootrec" stuff above or itwon't properly detect Windows to repair it; it will fail saying it can't fixthe problem "Missing BootMGR".Test install: firefox (probably only file config, plus default browser set) burp (includes scheduled task) .... (something that relies on the registry...)I found this works well. It seemed like a perfect restore on Windows 7 and 8.Only Windows 8 preview had issues.If something goes wrong: (for when the OS does not work properly, but it boots).Try this backup plan which creates an incomplete but pretty good system (OSworks, but some apps relying on the registry need reinstall).In my testing with Windows 8 release preview, the system would crash and rebootevery few minutes, but worked fine with Windows 8 final. So for win8 preview, Ineeded to fix with these steps.The fix: Boot the installer disk. Run repair mode "refresh" (consider this the 'rebuild the registry and delete all your installed stuff' mode). Boot into OS to finish the "refresh", boot again until you have thelogin screen. Log in, and wait for the process to complete. Boot the BurpRestore disk again. Repeat the restore without using the "-f" option. This might be quicker than a full restore. Ideally it would onlyrestore OS stuff (Windows, Program Files) without overwriting otherlarge files on your disk. Reboot into OS.

I'm attempting to get a Windows Preinstallation Environment to boot over PXE from a Linux server. The end goal will be to install Windows but that's pretty easy once I can get WinPE to start up (I've got the samba share with the windows OS disk etc.). I'm using ESXi and attempting to get a VM to PXE boot the winPE but also have access to a physical machine for testing. I followed the steps on a few tutorials ( -pxe-server-to-install-windows-on-centos/ mainly) and I've reached an interesting place:

However, if I mount the winpe iso on the VM's disk drive it works fine (I reach the winpe and can install windows). From what I've read of the "Cannot boot from CD - Code 5" error it is most commonly associated with BIOS firmware/hardware incompatibilities, but were that true the iso shouldn't work when mounted either.

I've tried both with and without appending raw with the same result. I have already copied the memdisk binary to the tftproot. The iso seems to be found when PXE booting because the iso is being read in some capacity, the ISO is placed inside the tftproot at windows/winpe_amd64.iso.

When you "mount" winpe_amd64.iso on a VM and boot from it the ISO sees itself booting from a CD/DVD drive (either real or virtual).When you boot winpe_amd64.iso from memdisk the ISO sees an "emulated" (created by memdisk) disk environment.

The "map" process is implemented using INT 13h - any disk emulation will remain accessible from an OS that uses compatible mode disk access, e.g. DOS and Windows 9x. The emulation via INT 13h can't however, be accessed from an OS which uses protected mode drivers (Windows NT/2000/XP/2003/Vista/2008/7, Linux, FreeBSD) once the protected mode kernel drivers take control. If the OS contains drivers for accessing this mapped ISO, or knows how to find the ISO on the disk, there is no booting problem of course.

3a8082e126