New
#121
One could create the macrium boot option
and then replace the marcium boot.wim with my Boot.wim
I created a 1GB partition and copied the files from the ISO to the partition
Used EasyBCD to add the boot.wim entry
@Cliff S
Here's the code I use to dual boot Macrium Version 5 when it was not available until version 6. Just copy the content of Jimmy's Winpe to the HD. Change the path in GREEN to point to it, use one of the line in RED. One for MBR, one for UEFI. Save the code to .bat then run from Admin Command.
Code:@echo off echo Configuring Dual boot Win 10 Recovery Tools bcdedit.exe /CREATE {ramdiskoptions} /d "Ramdisk Options" bcdedit.exe /SET {ramdiskoptions} ramdisksdidevice partition=C: bcdedit /set {ramdiskoptions} ramdisksdipath \macrium\boot\boot.sdi for /f "tokens=2 delims={}" %%g in ('bcdedit.exe /create /d "Win 10 Recovery Tools" /application osloader') do (set guid={%%g}) echo GUID = %guid% created !!! bcdedit /set %guid% device ramdisk=[c:]\macrium\sources\boot.wim,{ramdiskoptions} bcdedit /set %guid% osdevice ramdisk=[c:]\macrium\sources\boot.wim,{ramdiskoptions} bcdedit /set %guid% systemroot \windows REM use the next line for UEFI style installation bcdedit /set %guid% path \Windows\system32\winload.efi REM For MBR, use the next line bcdedit /set %guid% path \Windows\system32\winload.exe bcdedit.exe /set %guid% winpe yes bcdedit.exe /set %guid% detecthal yes bcdedit /set %guid% nx OptIn bcdedit /displayorder %guid% /addlast bcdedit /timeout 5 echo "Done... Reboot your PC" pause
Do you mean a one click option that you can setup dual boot as in Macrium ? With Macrium, you have to do while Windows is running so it can create a Ramdisk entry in BCD and create neccessary files/folders.Thanks to both for your answers:). But I wasn't thinking for myself, I was thinking of an automated-one-click option, with the download, for people that don't even know, that such an option exists.
You can use the same procedure I posted to boot Macrium Rescue Disk on an external/Internal drive. Instead of copy the content of Macrium Rescue Disk, copy the content of Jimmy's WinPese:
Solved FYI: Setup Macrium Rescue to boot from an Internal/External USB HD/SSD - Windows 10 Forums
I recommend creating a 1.5GB partition (G:) and copied the ISO contents to that G:\ partition....
Note: Edit the G: in the code box to match your partition drive letter
Save the Proper *.cmd and run as admin - to add PESE Boot Option to Host Boot Menu
PE_MBR_BOOT.cmd
PE_EFI_BOOT.cmdCode:@echo off echo. echo Configuring MBR Boot Option for WinPE Recovery Tools echo -------------------------------------------------------------------------- for /f "tokens=2 delims={}" %%g in ('bcdedit.exe /create /d "WinPE Recovery Tools" /Device') do (set deviceid={%%g}) echo -------------------------------------------------------------------------- echo DEVICE ID = %deviceid% echo -------------------------------------------------------------------------- bcdedit /set %deviceid% ramdisksdidevice partition=G: bcdedit /set %deviceid% ramdisksdipath \boot\boot.sdi for /f "tokens=2 delims={}" %%g in ('bcdedit.exe /create /d "WinPE Recovery Tools" /application osloader') do (set guid={%%g}) echo -------------------------------------------------------------------------- echo GUID = %guid% echo -------------------------------------------------------------------------- bcdedit /set %guid% device ramdisk=[G:]\sources\boot.wim,%deviceid% bcdedit /set %guid% osdevice ramdisk=[G:]\sources\boot.wim,%deviceid% bcdedit /set %guid% systemroot \windows bcdedit /set %guid% path \Windows\system32\boot\winload.exe bcdedit /set %guid% winpe yes bcdedit /set %guid% detecthal yes bcdedit /displayorder %guid% /addlast bcdedit /set {bootmgr} displaybootmenu True bcdedit /set {bootmgr} timeout 10 echo. echo DONE... Reboot your PC pause
The main reason I created the partition - is for testing PESE without having to constantly write to USBCode:@echo off echo. echo Configuring UEFI Boot Option for WinPE Recovery Tools echo -------------------------------------------------------------------------- for /f "tokens=2 delims={}" %%g in ('bcdedit.exe /create /d "WinPE Recovery Tools" /Device') do (set deviceid={%%g}) echo -------------------------------------------------------------------------- echo DEVICE ID = %deviceid% echo -------------------------------------------------------------------------- bcdedit /set %deviceid% ramdisksdidevice partition=G: bcdedit /set %deviceid% ramdisksdipath \boot\boot.sdi for /f "tokens=2 delims={}" %%g in ('bcdedit.exe /create /d "WinPE Recovery Tools" /application osloader') do (set guid={%%g}) echo -------------------------------------------------------------------------- echo GUID = %guid% echo -------------------------------------------------------------------------- bcdedit /set %guid% device ramdisk=[G:]\sources\boot.wim,%deviceid% bcdedit /set %guid% osdevice ramdisk=[G:]\sources\boot.wim,%deviceid% bcdedit /set %guid% systemroot \windows bcdedit /set %guid% path \Windows\system32\boot\winload.efi bcdedit /set %guid% winpe yes bcdedit /set %guid% detecthal yes bcdedit /displayorder %guid% /addlast bcdedit /set {bootmgr} displaybootmenu True bcdedit /set {bootmgr} timeout 10 echo. echo DONE... Reboot your PC pause
(I write to the G:\ Partition instead) and PESE is selectable via my host boot menu
I tweaked @topgundcp commands to better suit the purpose of BCD Entry Descriptions
Last edited by Kyhi; 05 Dec 2015 at 02:09.
Hi Jimmy.
Yes, the script is for dual boot. However, If you want to boot from another drive from boot menu. Just create the partition big enough for WinPeSe, format with FAT32, copy the whole content of WinPeSe and set the partition to Active and it should work either with MBR or GPT.
Personally I don't like dual boot of anything so that's how I test mine.
The selected disk is not a fixed MBR disk.
The ACTIVE command can only be used on fixed MBR disks.
My disks are all GPT
And I boot multi-OS, multi-VHD and PESE
All from the Host boot menu
To Boot legacy - I have to use USB
Hi everyone and Kyhi!
I am new to the forum and my Win 10 is experiencing some sfc /scannow errors.
Tested in Powershell and also cmd with the same error.
After reading the posts #61 and #62 at Sevenforum thread 'Windows 7: How do you fix corrupted files found by SFC /SCANNOW?', also I tried to use the following comand (after sfc /scannow in elevated cmd) to extract only the SR rows from the CBS.log:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"
But while it actually works in Windows 7 , under Windows 10 simply continues to blink and the sfcdetails.txt is empty.
How to fix that findstr command, please?
P.S. Screnshot shows the txt file out of the desktop because I tried to generate it also in C:\ but without results.
Thank you,
Butterfly