- Joined
- Oct 8, 2017
- Messages
- 24
- Reaction score
- 2
I have a client who has Windows 10 running in a VM. He set the virtual boot drive size too conservatively, and now the update package for 1903 won't fit on the available space.
I successfully added more space to his virtual drive, but when I went to grow the C partition to encompass the new space, I discovered that there was a recovery partition inbetween them preventing it. I tried some tools to move the recovery partition to the head end of the drive to get it out of the way, but none of them would even offer to do it. I gather that partition and/or the C partition has some kind of property that says it's unable to be moved.
I found many places on the web offering the advice to just blow the recovery partition away to accomplish this task. I would be willing to do that if there were a way to recreate a recovery partition at the end of the new drive. It's there for a reason, after all.
Can this be done?
I successfully added more space to his virtual drive, but when I went to grow the C partition to encompass the new space, I discovered that there was a recovery partition inbetween them preventing it. I tried some tools to move the recovery partition to the head end of the drive to get it out of the way, but none of them would even offer to do it. I gather that partition and/or the C partition has some kind of property that says it's unable to be moved.
I found many places on the web offering the advice to just blow the recovery partition away to accomplish this task. I would be willing to do that if there were a way to recreate a recovery partition at the end of the new drive. It's there for a reason, after all.
Can this be done?