Windows Updates Fail to Install on a System Booted from a VHD

Syaheko Firman 20 Reputation points
2026-11-19T05:24:07.0166667+00:00

A Windows system configured to boot directly from a virtual hard disk (VHD) is unable to install certain updates successfully. What steps can I take to determine whether these failures are caused by native VHD boot restrictions, compatibility issues with the Windows servicing process, or limitations in supported update scenarios?

Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

2 answers

Sort by: Most helpful
  1. Jason Nguyen Tran 30,745 Reputation points Independent Advisor
    2026-11-19T06:05:48.9933333+00:00

    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

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-19T05:24:29.5733333+00:00

    Use a narrow triage path to separate native VHD boot limits from general Windows Update servicing problems:

    1. Confirm whether the system is using native VHD/VHDX boot.
      • Native boot has specific requirements: the local disk must contain the boot environment and a separate partition that stores the VHDX file.
      • The partition that stores the VHDX must also have enough free space for the VHDX to expand to its maximum size and for the page file to be created outside the VHDX during boot.
      • If free space is low on the host partition, update installation can fail for capacity-related reasons rather than because of Windows Update itself.
    2. Check for known native VHDX boot restrictions.
      • If Windows updates from November 2022 or later are installed, native boot from a VHDX is blocked when the VHDX has the Zone.Identifier alternate data stream (Mark of the Web).
      • That condition is a native-boot restriction and can cause boot or application issues, so it should be ruled out first when the VHDX originated from the internet or was copied from a downloaded source.
    3. Determine whether the failure is actually a servicing-capacity issue.
      • On Azure Windows VMs, error C01A001D indicates the OS cannot complete update installation because a core file cannot be created on the file system and the OS cannot write files to disk.
      • Even outside Azure, this is a useful indicator that storage/write capacity should be checked before assuming an unsupported VHD update scenario.
    4. Reset Windows Update components before deeper servicing analysis.
      • Use the Azure VM Windows Update Reset Tool where applicable.
      • The reset process stops wuauserv, cryptsvc, and BITS, renames SoftwareDistribution and catroot2, re-registers Windows Update DLLs, and restarts the services.
      • If updates succeed after the reset, the issue was with Windows Update servicing state rather than native VHD boot support.
    5. Validate system file integrity.
      • Run an elevated PowerShell session and execute:
             sfc.exe /scannow
        
      • If SFC reports no integrity violations, that helps rule out corrupted Windows system files as the cause.
    6. Check whether the issue matches a known VHD-specific corruption scenario.
      • There is a documented issue where a differencing VHD created by expanding from a parent VHD can become corrupted if ParentPath is non-null and MaximumSize is larger than the parent disk size.
      • This affects Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012, and the resolution is to install the December 2014 update rollup for the affected OS.
      • If the booted system uses an older differencing VHD design, verify whether this exact condition applies.
    7. If the system fails during VHD boot itself, distinguish boot initialization failure from update failure.
      • Bug check 0x12F VHD_BOOT_INITIALIZATION_FAILED means initialization failed while attempting to boot from a VHD.
      • Parameter 1 identifies the failed action, such as inability to extract VHD information, timeout waiting for the parent device, or VHD mount failure.
      • If this bug check appears, the problem is in VHD boot initialization, not Windows Update servicing.
    8. For Azure VMs, use the built-in Windows Update diagnostics first.
      • Run the Azure VM Windows Update Error Detection Tool.
      • Run the Azure VM Windows Update Reset Tool.
      • Run the Azure VM Windows OS Upgrade Assessment Tool.
      • These are the recommended first steps before deeper troubleshooting or support escalation.

    A practical decision point:

    • If the host partition lacks free space, treat it as a native VHD boot storage requirement issue.
    • If the VHDX has Zone.Identifier, treat it as a native boot restriction.
    • If reset/SFC resolves the problem, treat it as Windows servicing corruption or state.
    • If bug check 0x12F appears, treat it as VHD boot initialization failure.
    • If the system matches the documented differencing-VHD expansion bug, treat it as a known VHD compatibility issue for the affected older Windows versions.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.