Things didn’t work until the F: partition hit 44 GB in size. For each try, I had to use MiniTool Partition Wizard to reduce the size of the C: partition. Then I used that space to expand the F: partition. I got increasingly vexed as I kept upping the size of the F: partition that OneKey Recovery used for the AOMEI partitions shown. I started small (at around 2 GB), and went through too many muffed attempts last night. These are labeled AOMEI and AOMEI Recovery Partition in the preceding screen capture from the Disk Management utility. To begin with, the program provides no guidance on how to size the partition from which it will create its partitions. Lack of Sizing Data Means AOMEI OneKey Recovery Gets Interesting Indeed! Here’s what the nominal 256 GB SSD drive on my Dell Venue looked like when the program finished its work:Īlas, considerable trial and error was required to properly size the F: partition I had to give AOMEI OneKey Recovery to work with. It’s particularly so when it comes to sizing the disk space that the program needs for its partitions.

But in practice, AOMEI OneKey Recovery gets interesting. As a bonus, its recovery partition incorporates a backup of your Windows OS partition. Then, AOMEI OneKey Recovery adds partitions to that disk for boot-up and repair. You must make space on your system/boot drive. In theory, installing this program is easy. It’s called AOMEI OneKey Recovery, and it’s available in both free and commercial versions. My explorations led me to a decent but flawed tool that does some nice things for Windows OS recovery. I’ve been working with and learning about recovery partitions on Windows boot/system disks lately.

Use onekey recovery