This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 1%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
It's been almost a year... can MS please fix the silly default install behaviour of Windows Server 2022 where it places the recovery partition AFTER the primary partition? Because of this it's impossible to extend the primary partition (something very common when working with virtual machines) without either removing the recovery partition or 3rd party paid tools.
Updated Windows Server 2022 ISOs are being rolled out, but the latest one still has this behaviour...
Afrraid the product engineers will not see this forum post. Better to provide this via the feedback hub from any 10/11 desktop.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
I've added feedback. Honestly? It feels like spitting in the ocean. I'll be extremely surprised if I ever get a response of any kind over there.
Reason: that feedback entry doesn't get indexed by search engines AFAIK. People aren't going to find it. Additionally it's related to servers, not Windows 10/11 (which is needed to run the Feedback app) so I sincerely doubt IT admins working with Windows Servers would look in there to vote on any server-related issues...
I expect any IT admin needing to extend a Windows Server 2022 disk to either remove the recovery partition and call it a day or use a 3rd party tool if they have one lying around - since at the end of the day you do what you need to do to get the work done. I.e. MS engineers will likely remain happily oblivious to the problem or, if it ever does reach them, they'll think it's not a big deal.
Just a reminder, please don't forget to close up the thread by 
I'm extremely reluctant to accept this as an answer.
The feedback hub has something like 10 feedback items for Windows Server + Storage (of which at least one is spam / namecalling). Seeing this doesn't fill me with confidence that anyone's actually looking over there.
Unless I get explicit confirmation or a response indicating that "yes, the feedback hub works and MS reads it" this answer cannot possibly be accepted.
While I agree, unfortunately the other feedback channels (uservoice) have been closed. This is all there is. The only other option is starting a case with product support.
--please don't forget to upvote and Accept as answer if the reply is helpful--
We have a number of cases we can open from our partnership with MS. If an issue is clearly due to a bug / issue with MS tech does MS refund such cases? I wouldn't mind "temporarily" burning one to get the point across...
Yes, as far as I know confirmed bugs always result in no charge.
--please don't forget to upvote and Accept as answer if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 20%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERB%3C/text%3E%3C/svg%3E)
This won't help with existing systems, but for a new VM Template, you can build VM with only a 10GB drive and install Windows Server 2022 on it. The lack of disk space prevents the recovery partition from being created as an additional partition on the disk. (The disk was 9.88/10 GB) Then just expanded the disk size and extended the volume as needed. I am replacing my templates and just making sure I have good backups set so the recovery drive partition is never needed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 12%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAI%3C/text%3E%3C/svg%3E)
Same problem also for me.
Not that I think this is a bad idea, but at this point one might as well just remove the recovery partition after a normal install, and then expand as needed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 30%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
I just discovered this after moving to 2022 as well, simply unreal that this is the case. I submitted feedback and definitely didnt see Mateusz so his point is correct, it will never be noticed.