Code: - Windows 10 1709 x64 EFI - "Default with Data partition" - Using version 4.0.8 of recovery Tools - Booted without Network - Installed 4 software using Ninite (Notepad++, WinSCP, Putty and Filezilla) - Installation of all patch - Sysprep (no generalize, no dism reset base) - First boot + OOBE - Local recovery - Creation of recovery drive - Full restore in a new Virtual machine Still not working. Next try : WIndows 10 clean install + no drivers + no update + no sysprep + default partition layout to check if problem is in Windows 10 or else where.[/CODE]
Thank you. Now I know im not the only one to experience it. But your last test "WIndows 10 clean install + no drivers + no update + no sysprep + default partition layout" scenario is I not yet experience it.
In this test I not capture anything. Basically I tes recovery scenario that an end user which installed a clean Windows 10 wouldnhave done. Creating the recovery media right now.
Code: - Windows 10 UEFI - Default partition - No Autounattend.xml file used - No audit mode - No drivers or update - Local recovery - Recovery drive creation - Barr metal recovery Not working. Looks like a Windows 10 (or at leat 1709) bug. Can someone test with previous version? I will think about something. Maybe use push-button recovery for local recovery and bring back WIM image for media creation, at the choice of the system builder.
Hi everyone, I just want to let you know on what I'm working right now. For Windows 10, during the execution of the Sysprep script, the "computer technician" (basically, you), will be asked if a full image is needed or only push-button support. If push-button support is used, it will be exaclty what it is right now. - Always the lates version of Windows 10 will be used - Apps will be kept - Drivers will follow - Creation of recovery media is using Windows 10 Tools (with known bug of recovery image after recovery not working) If a full image is choosed : - A full Windows image (WIM) will be captured - Local recovery will still use the push-button feature (latest Windows, current drivers) - When creating a recovery media, it will use my tool to create a new recovery media (USB) with the WIM file. This will reinstall the ORIGINAL version of Windows 10 with the ORIGINAL drivers. This means that is the end user had changed hardware it may cause problem. At the same time, is a new version of Windows create problem, this may solve it. - The WIM file will be kept between each "local" reset option because it will be in C:\Recovery\OEM folder.
If push-button support is used, it will be exaclty what it is right now. - Always the lates version of Windows 10 will be used - Apps will be kept - Drivers will follow - Creation of recovery media is using Windows 10 Tools (with known bug of recovery image after recovery not working) For SSD, to not take too much space on the disk. If a full image is choosed : - A full Windows image (WIM) will be captured - Local recovery will still use the push-button feature (latest Windows, current drivers) - When creating a recovery media, it will use my tool to create a new recovery media (USB) with the WIM file. This will reinstall the ORIGINAL version of Windows 10 with the ORIGINAL drivers. This means that is the end user had changed hardware it may cause problem. At the same time, is a new version of Windows create problem, this may solve it. - The WIM file will be kept between each "local" reset option because it will be in C:\Recovery\OEM folder. For HDD, it is not the space that most often misses on these disks.
That's why you will be able to choose which option you prefer. Testing the manual script right now. Will let you know how it goes.
Hi, For those of you who have "non working" recovery drive created by Windows, can you add the following line to the ResetConfig.xml file? Code: <RestoreFromIndex>1</RestoreFromIndex> It should look like this : Code: <?xml version="1.0" encoding="utf-8"?> <Reset> <Run Phase="BasicReset_AfterImageApply"> <Path>Scripts\Restore.cmd</Path> <Param></Param> <Duration>2</Duration> </Run> <Run Phase="FactoryReset_AfterImageApply"> <Path>Scripts\Restore.cmd</Path> <Param></Param> <Duration>2</Duration> </Run> <SystemDisk> <MinSize>80000</MinSize> <DiskpartScriptPath>ReCreatePartitions.txt</DiskpartScriptPath> <OSPartition>4</OSPartition> <WindowsREPartition>1</WindowsREPartition> <WindowsREPath>Recovery\WindowsRE</WindowsREPath> <RestoreFromIndex>1</RestoreFromIndex> <Compact>False</Compact> </SystemDisk> </Reset> Curiously, the recovery drive I am currently creating was giving me the same error as the one created by Windows but adding this files seems to fixed the problem. So maywa adding it to Windows could fix the problem also.
Hum.... I tried to apply, using DISM, the WIM file created by the recovery drive Tools from Microsoft and the file is corrupted. I don't know if the problem is my USB drive or the fact I do it through VMware. Anyway, I'm still working on the new version. Basic script are done. I have to create a new gui to create the recovery media.
When restoring from USB, it will be the same thing. I will just use the full image and not the "rebuilt" one. For the GUI in Windows, if there is not full image, nothing will be changed. Otherwise, just a file dialog box to select the destination drive, a warning that everything will be deleted on the drive, a waiting message and confirmation. Nothing really new. The recovery form USB is using the orfficial method from Microsoft. BAsically a boot drive with WINRE + install.wim (or multiple install.swm) in sources folder + recreate partition script + resetconfig file. That's it. Should I give the end-user the choice to delete the image from the computer once the recovery media is done or just put an hidden script for those ointerested, like the one with the apps update ?
@AnarethoS this is great work. have used it for several years now. First time with windows 10 though. I followed all the instructions but for some reason i cannot get the autounattend to create the partitions. It keeps giving me errors. what am i missing?
@AnarethoS I have tried both the default and recommended uefi gpt autounattend. Windows 10 x64 platform. Drive has been cleaned with diskpart, so essentially blank. The error msg that I get is : Windows could not creat a partition on disk 0. The error occurred while applying the unattend answer file's <DiskConfiguration> setting. Error code:0x80042565 I'm almost certain that this is something simple. Probably overlooking some small detail that is different with Windows 10. What I've done is grabbed the project and the required files. Copied required files into place. On my usb I have the iso extracted and the autounattend.xml, along with the ei.cfg. I also have the recovery folder which will be copied into place after the initial install.
I would sugest you to boot to Windows 10 installation media (without autounatted.xml file) and open a command prompt (F10 or Shift+F10) and launch DISKPART to check what is the disk 0. Maybe the number are worng (USB drive 0 and HDD 1) or similar.
Hi everyone. I would like to let you know hos 4.0.9 is going 1- Capture Full image of Windows 10 - Done 2- Create recovery media - Done 3- Recover from recovery media - Testing in progress 4- Update script - To do 5- Update documentation - To do Once part 3 is done I will give access to my beta code. Also, please note that the new version is no mot digitally signed anymore. My code signing certificated expired and StartCom whent out of business and I was not able to find any code signing certificate for 50$. Thanks.