> On this end this is a W10 Hyper-V guest.
Do you have a Windows 11 "host", with Hyper-V having a Windows 10 "guest" operating system?
> I also have two recovery partitions one is 450mb and the other is 789mb which is the active one and is at the end of the disk after my C:
The early releases (in 2015) located the "Recovery" partition at the start of the disk-drive. That explains the 450 MB partition.
When I use the "reagentc /info" command, I see:
**Recovery Environment:**
*\?\GLOBALROOT\device\harddisk0\partition2\Recovery*
Harddisk "zero" is my computer's first disk-drive,
while "partition2" is the 3rd partition on my disk-drive.
Do you see "partition1" in the output on your computer, or "partition5 ? If the former, then that partition is too small for the update to be applied. If the latter, then the 789 MB might be too small.
Do not believe that "0% used" tag for your "partition 5".
Unfortunately, the "hidden" files/folders are not counted, when giving that "0%" result. Sigh.
You must have installed Windows 11 a LONG time ago, to have that partition at the start of your disk-drive.
There do exist free utilities that will "shrink" your "C:" partition by some amount, e.g., 1000 MB, and then to "expand" your 5th partition by that amount, namely 1000 MB plus the 790 MB.
Then, retry the Microsoft update.
I also have the dreaded C: 100% disk utilization on this guest.
Since you seem to be using Hyper-V, are you measuring the utilization on the "host" operating system, or are you measuring the (virtual) disk utilization on the "guest" ?
Note that restarting Windows (10 or 11) after a Windows Update may trigger:
- a virus-scan
- disk-drive optimization ("defragmenting")
- updating the Windows Search "cache" after noticing new/changed files
Any of these will result in a short-term "100%" condition.