Unable to set disk quota for Windows2025 containers

[winkingturtle-vmw]

Describe the bug
We are in the process of upgrading to Windows Server 2025 and our initial testing is showing a regression from Windows Server 2019 by way of failing to set disk quota for containers. Previously, we have been able to enforce disk limit for each container.

To Reproduce

• docker run -it mcr.microsoft.com/windows/servercore:ltsc2025 powershell in one powershell
• mountvol.exe /L to get the the Volume GUID for the new container
• New-FSRMQuota -Path "\\?\Volume{GUID-FROM-ABOVE}\" -Size 10GB

New-FSRMQuota : 0x80045313, A required filter driver is not installed, loaded or ready
for service.
At line:1 char:1
+ New-FSRMQuota -Path "\\?\Volume{d7d5def4-b68d-43dd-b571-9eece130a16c} ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MSFT_FSRMQuota:Root/Microsoft/.../MSFT_FSR
   MQuota) [New-FsrmQuota], CimException
    + FullyQualifiedErrorId : HRESULT 0x80045313,New-FsrmQuota

Expected behavior
We expect to be able to set the disk limit for the volume the same way as Windows Server 2019. The same set of commands works for WindowsServer2019. If we need to install additional packages, it's unclear what else needs to be installed.

Configuration:

• Edition: Windows Server 2025 (Core or GUI)
• Base Image being used: Windows Server Core
• Container engine: docker
• Container Engine version [e.g. 22]

Additional context
Add any other context about the problem here.

[github-actions]

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

[winkingturtle-vmw]

@ntrappe-msft We are blocked on making progress until we can apply disk quota for every container. Can you please provide some guidance on best path forward ?

[ntrappe-msft]

Are you also on a Server 2025 host?

[winkingturtle-vmw]

Yes, the host was the same version of the container version.

[winkingturtle-vmw]

@ntrappe-msft Can you let us know if this is being tracked on your side? We are blocked on moving forward.

[ntrappe-msft]

@winkingturtle-vmw Yes, it's being tracked. It may take a while for me to share meaningful updates as my backlog is full but I'm in the process of investigating it now.

[winkingturtle-vmw]

Hi @ntrappe-msft wanted to check back in on this issue and see if we can find a resolution for it so that we can continue our Windows2025 Server work. Do you have any updates for us ?

[ntrappe-msft]

Thanks for the ping. My backlog has been very full for the last few weeks so I haven't been able to dive in deep. I'll try to take a look by the end of the week and let you know if I have any recommendations by next week.

[cphi-vmw]

@ntrappe-msft - Any update on this? It's risking our ability to support Windows 2025 within Tanzu/Cloudfoundry.

[ntrappe-msft]

Could you confirm if the image you're using perfectly matches the host OS version? You can specify an exact match with the image by doing: mcr.microsoft.com/windows/servercore:-<version>.