FOG Resize Fails on Windows 11 Build 28000.2269
-
Working in a VM (QEMU/KVM/Libvert) I found that attempting to capture (single disk resizable) a fresh ISO (June 2026 Windows 11 Enterprise) install where I enter audit Mode and then sysprep, the capture fails to resize during the FOG capture process:
“An error has been detected! … Resize test failed! … Device name: /dev/sda3 … Space in use: 10535MB (16.6%) … Needed relocations: 1610313 (6596MB) … ERROR(28): Could not update runlist for attribute 0x80 in node 156294: No space left on device (shrink partition) Args Passed: /dev/sda /images…”
Previously I had no issue capturing an install using Windows 11 Build 28000.1836 via FOG. The older build allowed for smaller VM disk size such as 40GB if I recall. The newer June 2026 ISO Build requires around 50GB for Windows 11Enterprise to install (else there is an error) so I allocated 60GB to the current VM (where I am getting the capture error).
I found that on the June 2026 Build (28000.2269) if I set the EFI partition size to 2GB (still using 60GB VM disk size) during the installation using diskpart, complete the install, enter audit mode, sysprep, and then attempt the capture I am successful and there is no resize failure. Why does setting the EFI partition to a larger size allow the capture process to succeed? (I found this by accident as I was increasing the EFI partition for another reason discussed in the side note here.
-
@vanfifty1 I feel like this was something you produced on GIthub as well, is this correct?
I’m just wanting to link things. As it’s usually usually me doing all the development now-a-days again, (but thank you AI) I can try to have Claude take a look.
I’m currently working on 26H1 update download at least thru a vm, but just wanted to give a heads up.
