I been looking into it since I am also working on a laptop unit need to reinstall but not urgent so I got time to test. What Windows 10 version did you install since v1903 giving me that app association break unlike v1809? UPDATE: I reread your post sorry, it seems you working at Windows 10 v1903 @AnarethoS When I am using the Recommended UEFI partition scheme, the sysprep script failed to create WinRe so after sysprep script done and reboot, I got stock on Capture. Did I do something wrong? UPDATE: My bad, I mess up the ResetConfig.xml. Sorry
Hey ! Here a little fix for Update - Windows 10.cmd, if the user don't want AddOn, the original script install AddOn... Code: ECHO ************************************* ECHO Check if AddOn was installed. Please wait ... ECHO ************************************* if exist C:\Recovery\OEM\Menu\AddOn GOTO INSTALL SET Setting=%CD%\Recovery\OEM\Menu\Settings.ini if exist "%CD%\Recovery\OEM\Menu\AddOn" RD /S /Q "%CD%\Recovery\OEM\Menu\AddOn" if exist "%Setting%" powershell -Command "(gc '%Setting%') -replace 'AddOn=1', 'AddOn=0' | Out-File -encoding Unicode '%Setting%'" :INSTALL ECHO ************************************* ECHO Removing previous files. Please wait ... ECHO *************************************
My created recovery drive didn't boot on dell laptop it created then I tried to boot it on other computer and it working. I used 4.2.0 for recovery Windows 10 v1909 Dell Inspiron 3442 This is really weird.
hello thank you for the video and your time would be possible to make another one for copy of the files on usb key thank you
Hi In 4.2 version manual there is no step-by-step demonstration for Windows 7. can anyone upload this (windows 7 ) pdf file which have it. thanks
It is possible to select which internal disk to restore from the created recovery usb drive since it always selects disk 0. I encounter an m.2 nvme ssd as disk 1 where this disk is supposed to be OS installed and cannot change the way it is behaving on UEFI settings. A temporary fix is just to remove all storage media except where you want to restore the OS.
If this is an Intel based system then you could try integrating the Intel Rapid Storage Drivers into your wims using dism. I find having the driver installed makes the M.2 disk 0.
Its been some time but spending more time at home these days..... getting around to updating my install disks and was wondering......How would one go about creatinng the "Autounattend.xml" for a new install that would provide a choice to choose from an mbr or a gpt scheme? Or is this even possible? thought process is I have a usb flash-drive that is capable of booting into both legacy or uefi bios. therefore being able to choose or automatic detection would be awesome. Currently i just do not autounattend and run dispart.txt to acomplish the step. maybe i'm just dreaming of a much easier LOL 'lazier way to do things'. any thoughts?