Hi Syaheko Firman,
When Windows is configured to boot natively from a VHD, certain updates may fail because the servicing process, recovery environment, boot configuration, or update mechanism encounters scenarios that differ from a standard physical installation. My first recommendation is to identify whether the failure affects all updates or only specific categories, such as feature updates, cumulative updates, or updates that modify boot-related components.
I would start by reviewing WindowsUpdate.log, CBS.log, and DISM.log to determine the exact stage at which the installation fails. These logs often reveal whether the issue is related to package applicability, servicing limitations, storage access, or boot configuration processing. It is also important to verify the current VHD configuration, including how the VHD is attached and whether the system meets the supported requirements for the type of update being installed.
Another useful step is to compare the behavior against a similar system booting from a physical disk or a known-working VHD deployment. If the failures began after a specific update or configuration change, reviewing the update history and any recent modifications to the boot environment may help narrow the investigation. I would also check whether the Windows Recovery Environment and boot entries are healthy, as some updates require successful servicing of those components.
In my experience, the key is to determine whether the failure is caused by a supported VHD boot limitation, a servicing issue within the Windows image, or a specific update package. A careful review of the servicing logs usually provides the clearest indication of which category the problem falls into.
I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.
Jason