Thanks for the hard work. Waiting for stable release for "adding some apps +recapture . Will not update for now on my other laptops. My desktop which just updated to 1709 got upgraded its recovery tool to the latest beta version. I will try to reset it later. Anyway thanks. By the way, some setting like system restore option i set during audit didnt capture and other i dont remember and i used the lated beta version to date of this post.
Hello thank you for your work if possible review the script to windows 10 for the partition recovery she is no longer in autouunattend.xml know why it is removed I know there is usb key or external hdd but partition bootable! I test your beta versio is you go back the info is waiting for you impatiently your final version 4.08 bonjour merci pour votre travail si possible revoir le script a windows 10 pour la partition recovery elle n'y est plus dans autouunattend.xml savoir pourquoi elle est retirée je sais qu'il y a des cle usb ou hdd externe mais sur partition bootable ! je test votre version beta est vous remonte les infos est vous attendont avec impatience votre version final 4.08
Windows 10 recovery is really different than previous version of Windows. In Windows 7/8/8.1 a "full-backup" on the Windows installation (including drivers, apps, updates, etc.) was created and copied on a secondary partition. When recovery, this image was used again to reinstall Windows. With Windows 10, it is different. During the installation process of my recovery Tools, a file (c:\Recovery\Customizations\Recovery.ppkg) is created. This file is a difference between a clean installation of Windows and the current state. All applications are copied in this file. During the recovery process, the Recovery environment use the currently installed Windows 10 version to "recreate" a new installation, copy actual drivers from the old Windows to the new Windows (and the same for major updates). Then, it reapply the capture files which bring back the applications. This mean that a computer captured when using 1703 and that has been upgraded to 1709 will be restored to 1709 and not 1703, which is nice. And this take less space on the computer. The only way to have the option to roll-back to a previous vesion of Windows 10 is to create the recovery media, but using it will format the computer.
OK. 4.0.8 is officially out. o Fixed: Windows 10 compatibility with build 16299 o Fixed: Windows 10 update script (unsupported option) o Fixed: Double execution of logon script under Windows 8/8.1 o Added: Spanish for Windows 7 o Added: Windows 10 tools update
I got a problem using generated recovery usb drive on windows 10 16299 to restore on my computer. Restoring via local partition is working. Tool used latest 4.0.8.
I use 16299.19 x64 (according to winver). I dont get what what you mean by install or official iso but i get this error after testing the recovery tools, first on local partition which work fine as always then create recovery drive which I use to reset. so it means that it will still break no matter what I do? . Files $PBR_DISKPART.TXT and $PBR_RESETCONFIG.TXT is different from inside OEM folder RECREATEPARTITIONS.TXT and RESETCONFIG.TXT. It give always use uefi recommended setting instead of uefi default with data partition that I put.
@Enthousiast and @The_Guardian thank you for your reply and information. @AnarethoS thank you for the tools. I give up on recovery drive.
My Tools automatically do "DISM.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase" before running Sysprep. This create problem ? On all build (1703, etc.) or only on 1709 ?
The $PBR files are "default" files that are used is ResetConfig and Recreatpartition are not set if I remember correctly. I must say that I didn't test the recovery media since I can't easilly boot VMware from USB drive and I don't have sparecomputer to test.