You must choose the X64 folder on 64 bits installation and the X86 folder for 32bits instalation. So you are right. Sory for my lack of response. I was on vacation and probably took too much Cuba Libre (rhum and coke).
ok but to avoid to choose which architecture to put in the boot folder, you can put both architecture (x86 and x64) at the same time in the boot folder by creating 2 subfolders (x86 and amd64) into boot folder and this way you will be able to put 4 files of x86 archtirecture into x86 boot subfolder and put 4 files of x64 architrcture into amd64 boot subfolder as you did for windows 10. It's easier and more practical to do it this way, don't you agree ?
I am having some trouble with the software. I am getting an pop up error message "this app can't run on your PC " when scanstate is trying to capture the installed software. There are no logs generate in C:\Recovery\OEM\Logs. I am using a custom window 10 CU image using msmg toolkit. I am testing the software in vmware fusion pro(workstation).
which win10 version did you install ? if i'm correct, you need the scanstate file that correspond to your windows 10 version, otherwise you will get errors. if i'm correct, the scanstate file on first page correspond to win10 15063 (1703, creators update) version so if you use it on another win10 version it won't work and it seems that this is what happens in your case.
Are you in Audit mode when you start the process? That cmd prompt doesn't look like it's running as Administrator. @mehdibleu , the scanstate version doesn't matter...
are you sure about that ? because i saw @AnarethoS asking in one of the previous posts if the scanstate files are from 15063 version or from older win10 version as you can see here => https://forums.mydigitallife.net/th...eator-for-windows.21978/page-147#post-1350947
Yes he got the updated ver but the old ver still worked. With the old ver you had to set "Windows-Defender-AM-Sigs", "Windows-Defender-AM-Engine" and "Security-Malware-Windows-Defender" to "No" for Migration. With the new you don't.
@sciblue : make sure to be in audit mode while starting the process as @Flipp3r mentionned, otherwise it won't work. Also make sure to follow carefully the instructions in the documentation that is available on first page (copy both scanstate files (x86 and x64) to the right folders and at the end don't forget to copy both files ("ResetConfig.xml” and “ReCreatePartitions.txt”) to “C:\Recovery\OEM” There are members who managed to make this work for win10 so there is no reason that this wouldn't work for you, again you just have to follow the instructions in the documentation and it should work. I personnally managed to make it work for windows 7 , i haven't tested yet for win10 but the procedure is the same. Please let us know if you have managed to make it work.
I finally was able to get the software tools to work with a clean and custom windows 10 1703. I re-download the tools, extracted them using 7zip. Everything is working like it should. Thanks everyone for your the help.
Glad to hear that you finally managed to make it work. Could you please specify what you did to make it work and what you missed to do last time to make it work so that everyone can take advantage of it if someone has the same problem later ? did it have something to do with the iso that you used ? or maybe did you forget the firs time to add needed files to the right place ?
Sorry for the late reply. When I first download the recoverytools it was in exe file. I ran the installer, the files were extract in there own folder, i.e. windows 7, 8, 10, etc. and extracted the windows ISO to a flash drive. Somewhere down the line some file got corrupted either the windows ISO or the tools. Using 7zip I extracted the windows ISO to a flash drive and recoverytools exe, which put the files in one folder called RecoveryTools4.0.7. From there correctly forward the instructions. So far everything is working like it should.
I am having an issue after install & completion of OEM Recovery Partition Creator when running recovery tools with either computer backup for media creation or computer repair full recovery i get the following error when it starts to mount recovery partition An Error occured Process aborted has anyone seen the error or can help?? Using on Hp laptop with Windows 7 Professional 64 Bit (Amd athlon dual core processor)
ScanState return code: 29 ***************************** Running Sysprep ***************************** ERROR: The process "SYSPREP.EXE" not found. ERROR: The process "WMPNETWK.EXE" not found. Any one knows how to fix this. Windows 10 Pro x64
I wait your update ! Because I want test my new project for detect if EFI or MBR, my script can copy the recovery folder and attribut in OOBE mode
Does anyone have a solution or come across the problem it works ok on windows 7 pro 32bit Thanks in advance Bigo229