Hi everyone. Sorry for the delay for the next version. Lots of stuff at my job, vacations, etc. For now, it seems that .PPKG file cannot be splited into smaller file and SWM file cannot rally "split" a file. Which mean that a 5gb PPGK file will always result to at least one 5gb SWM file. Curriouslt, the "built-in" recovery generator for Windows 10 seems to be able to split the PPKG file so I still have to figure out how this is done. For now, if you PPGK file to bigger thant 4gb, I will recommend you to use the "built-in" recovery image of Windows 10. Under 1803 it seems to be working again. If I don't find a way to split PPKG file into smaller piece I will use a turn around. Windows 10 now support multiple partition on USB key, so I will probably create 2 partition on the recovery media, The boot one in FAT32 for UEFI support and one in NTFS format holding all the SWM file.
I am working on the new recovery option. I am trying to integrate WMI information into AutoIT to get the drive informations.
hello thank you for your work it is the best backup for backup system your script is awesome we look forward to your new update is not to put it in beta to reassemble the test on a PC maximium to have less of bug again thanks anarethos
Hello guys. Hope you can help me and sorry for my poor English. I'm trying to use this wonderfull utility but I'm facing a little problem. I'm using Windows 10 LTSB 2016 x64 with BIOS MBR default settings. I think I did everything right. I can create and use an USB recovery drive but, when I want to reset computer using recovery environment, it starts reseting the machine but finishes to display "undoing changes" and says "There was a problem reseting…" I tried with the two recovery modes and result is the same. Is it a known issue? Is there something I did wrong? Thank you for your help.
Thank you for your answer. No I didn't change anything. I have the 3 partitions (WinRE, system reserved, all) made with diskpart and recreatepartition.txt. I thought it could be because of missing Ei.cfg and PID.txt and I created them. But no joy, always same trouble. Then, I thought it could be because of an update and I tried without no updates and same result.
@PJ-DCM Questions: 1. What version of the scanstate files? Your DISM shows 14393. 2. The fourth and fifth screenshots show an error. Would you mind translating? 3. Logs are: C:\Recovery\OEM\ScanState\amd64\scanstate.log & C:\Windows\System32\Sysprep\Panther . Look those over. If you can't figure it out, 7-zip them and attach them or filedropper_com . 4. Why did you change your shirt during the installation?
Please send a message to AnatheroS for a old version, if you use a build 14393. He didn't work with the last version of this Recovery, many change is Added.
Just for info perhaps it is out of topic but yesterday I tried to reset the en_windows10 enterprise ltsc2019 and faced the exactly same issue. Please notice I don't use Anatheros tool. So perhaps it is coming from this edtion of Windows. If someone else tried to reset this version it could be helpful to share that experience.
Hi Silekonn, thank for your answer. About hwcompat.dll, I do have this file in sources folder. And about Scanstate files I used the ones in Windows 10 ADK, like it was indicated in Anaretos manual. But I downloaded the last one. I wasn't aware that Windows 10 ADK was related with the different build. I will perform more tests after download the Windows 10 ADK 1607. Thank you.
@AnarethoS I don't expect you need a copy of the 1809 RTM ISO. If you do, I can point you to one with checksums. I have no requests and am just offering a bit of assistance if needed. Thank you for your great project.