On a Master Image that has the VDA software installed, any changes made to the Master Image are not persisted across reboots.
The issue starts happening after the VDA software 7.9 or later has been installed.

This issue has been observed when the ESET Anti-Virus is installed on the Image.
When the ESET Anti-Virus is installed on the Image, it will detect the changes to the Registry Value and will rollback the changes, effectively removing the PvsVmBoot entry from the Registry.
ESET Anti-Virus is aware of the issue and has released an update to their software to prevent the issue. Please contact ESET for the update.

If any additional Anti-Virus or Security software removes the entry from the Registry Value, uninstall that third party software or contact the vendor for support configuring an exception rule or an update to that software.

If there is no other software installed that might have removed the entry from the Registry value, then re-install the VDA Software to make sure the value is added correctly.

Warning: Do not attempt to add the value directly to the Registry. Doing so could render the Image unusable. To properly add the value to the Registry, re-install the VDA software.

---

Problem Cause

This issue can be caused by Third Party security software, such as Anti-Virus, that removes changes to the following registry key:
    Key Path:   HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager
    Value Name: BootExecute

Per Microsoft documentation the BootExecute value "specifies the applications, services, and commands executed during startup".

When the VDA Software is installed, the following entry is added to the list of values in BootExecute:
    PvsVmBoot
This value is added to correctly initialize the MCS I/O Optimization driver inside the VDA.

If this value is removed from the Registry, the MCS I/O Optimization driver is not initialized correctly and the behavior explained above will be observed.