Hello Derek M,
The error code 0x800f0905 during installation of KB5077181 indicates a servicing stack or component store corruption inside the VM, even though the host installed the update successfully.
The first thing to confirm is that the VM has access to Windows Update services and is not restricted by WSUS or group policy. If the host is patched but the VM fails, it usually points to a mismatch in the servicing stack or a corrupted WinSxS store inside the VM. Run the following commands inside the VM:
Code
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
If DISM reports source corruption, mount the latest Windows 11 Enterprise 24H2 ISO and point DISM to the sources\install.wim file using:
Code
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess
Replace D: with the mounted ISO drive letter. This ensures the VM repairs its component store against a clean image.
If the repair succeeds, retry installing KB5077181. If it still fails, the next step is to manually download the update package from the Microsoft Update Catalog and apply it using wusa.exe or DISM /Add-Package. This bypasses Windows Update and forces the patch installation.
At present, there are no official Microsoft advisories stating KB5077181 is blocked on Hyper‑V guests, so the failure is most likely due to corruption or servicing stack mismatch inside the VM. If DISM and manual installation both fail, the only supported remediation is to rebuild the VM from the latest 24H2 media, which already includes the servicing stack updates required for KB5077181.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.