I Didn't Know How to Expand C: Past a Recovery Partition. So I Asked ChatGPT.

Expanding a Windows C: drive seems simple until a recovery partition blocks the unallocated space. Managing real computers requires more than a basic script. It requires a system that connects intelligence to context, permissions, and approved action.

One of our Windows Runner machines had a 120 GB disk, but the C: drive was only using 78.94 GB. There was roughly 40 GB of free space sitting at the end of the disk.

Normally, that sounds easy. Extend C: and move on.

Except there was an 870 MB Windows recovery partition sitting directly between C: and the free space.

The disk looked roughly like this:

• EFI
• C: 78.94 GB
• Recovery 870 MB
• Approximately 40 GB unallocated

Windows cannot extend C: through another partition. I knew what the problem was. I did not know the exact sequence I wanted to trust on a live machine.

So I opened ChatGPT and asked FlowRMM to use the space at the end of the disk to expand C:.

I never had to manually click through Disk Management or remote into the machine to start experimenting.

Why The Command Alone Is Not Enough

Most AI examples stop at advice.

Run this PowerShell command.

Open Disk Management.

Delete the recovery partition.

That is not enough when the computer is real and the change can break recovery or the boot path.

FlowRMM gave the conversation a control plane around the machine. ChatGPT could inspect the live endpoint, understand the disk layout, propose an action, request human approval for the destructive step, execute it, and then verify what actually happened.

The first read showed the important facts:

• Disk 0 was a 120 GB GPT disk.
• C: was 78.94 GB.
• An 870 MB recovery partition was directly after C:.
• About 40 GB of unallocated space was sitting after recovery.

That explained exactly why C: could not simply be extended.

How A Managed Failure Protects The System

This is the part I actually liked.

The first change attempt failed because of a PowerShell parser issue. Nothing on the disk changed.

The next attempt disabled Windows Recovery so the recovery partition could be moved safely. The workflow expected Winre.wim to still be on the recovery partition, but Windows had moved it back onto C: when recovery was disabled.

The guardrail noticed the file was not where we expected it to be and stopped before deleting the recovery partition.

That is a good failure.

Instead of guessing, ChatGPT checked the machine again. We found Winre.wim safely staged under Windows on C:, confirmed the original recovery partition was still intact, and adjusted the plan.

The Final Approved Action

After another human approval, FlowRMM performed the actual disk work:

1. Remove the recovery partition that was blocking C:.
2. Expand C: into the newly contiguous free space.
3. Create a new recovery partition at the end of the disk.
4. Format it for Windows Recovery.
5. Copy Winre.wim into the new recovery partition.
6. Register the new recovery path.
7. Re-enable Windows Recovery.
8. Remove the temporary recovery drive letter.

The action still showed as failed at the very end because Windows rejected one extra partition flag operation with a message stating the operation is only supported on data partitions.

So we did not trust the status alone. We verified the machine.

C: had grown from 78.94 GB to 118.71 GB.

The temporary R: drive letter was gone. Windows Recovery had been registered and enabled against the recreated recovery partition.

The goal was complete. We reclaimed about 39.77 GB for C: without me manually performing the disk surgery.

Building A Real Control Plane For AI

The interesting part is not that ChatGPT knows PowerShell.

The useful system is everything around the model:

• Context: It could inspect the real machine instead of guessing from a screenshot.
• Scope: The work was limited to the exact endpoint we selected.
• Approval: Destructive partition changes required a human decision.
• Execution: The approved action ran on the endpoint.
• Verification: We checked the live state after each important step.
• Auditability: The successful steps and the failures were visible in the action history.

The failures actually made the example better. They showed why an AI agent operating a computer needs more than shell access.

It needs boundaries.

Frequently Asked Questions

Can Windows natively extend a partition over a recovery partition?

No. Windows Disk Management cannot extend a volume into unallocated space if another partition sits between them.

Does FlowRMM execute destructive actions automatically?

No. FlowRMM requires human approval before executing destructive actions like deleting a partition.

Why is Winre.wim important?

Winre.wim contains the Windows Recovery Environment. Moving or deleting its partition requires proper staging to avoid breaking the boot path.

Setting The Goal And Staying In Control

I still needed to understand the goal and approve the risky step. I still owned the decision.

But I did not have to memorize the exact Windows recovery workflow, search through a pile of forum posts, or manually drive the machine while translating those instructions into commands.

I could describe the outcome in normal language: Use the space at the end of this disk to expand C:. There is a recovery partition in the way.

Then the system could inspect, reason, act with approval, learn from the result, and verify the final state.

That is the direction I think computer management is heading.

Not humans clicking every screen forever. Not AI with unlimited access either.

Humans set the goal and stay in control. Software provides the context, permissions, approvals, execution, and evidence needed to safely get the work done.

That is what we are building with FlowRMM.

If you manage real computers and want to see what this kind of workflow looks like, visit FlowRMM.com. To discuss how we can build the applications your business runs on, schedule a call on our bookings page.