cpohts
Comments
-
Solved. I didn't inject drivers into the onekey_pe.iso WIM file. I renamed the ampe.iso that I already updated and copied it into the recovery partition. Booted perfectly and sees the hard drive, able to backup and recover! Until Aomei updates…
-
Update, this fix allows OKR to reboot during the first backup and create the recovery partitoin with subsequent onekey_pe.iso but the embedded WIM inside also lacks the drivers for NVMe. I'm going to try to follow the same steps to inject driver…
-
I found the fix. I had to inject drivers into the boot.wim in the ampe.iso file in the OneKey Recovery install folder. This allowed OKR to see the NVMe drive and load one creating the first backup file and recovery partition.
-
My first exposure to Aomei was OneKey Recovery. I was looking for a system recovery tool to replace the tools integrated with Windows and different tools provided by different OEMs - to standardize computer builds with one recovery system regard…
-
The laptop I'm working with is a ThinkPad T470s, Win7x64 on NVMe drive. The OEM ships GPT. I converted it MBR, fixed the boot, so it does load into Windows successfully. I used the native T470s W7x64 GPT to create a bootable image from Backupp…
-
I uploaded 2 ISOs to dropbox and emailed the links. One has the injected NVMe drivers
-
I tried these commands, did not work. I have converted the drive to MBR, but OKR would not create the PE stating WAIK was required. I've NEVER needed this before.
-
The Windows install is fine. It's the PE that Onekey creates that fails. I don't know where OneKey pulls drivers from to build the PE or if it is pre-bundled, but the PE doesn't see the NVMe drive.
-
No it does not. The drive is also GPT, the first time I've worked with one.