Regarding your Qs:
- I don't expect it would affect new installations as there's no existing driver catalog files at that point for the WDAG container to be locking.
- I'd definitely expect it to affect future updates, alongside the existing v15.5.6 update, unless there's some change in WDAG behaviour (via Microsoft) or the installer handling (via VMware).
- It could conceivably affect updates from older versions as well, but as the pre-v15.5.5 releases aren't compatible with Hyper-V (and thus WDAG), you'd be updating from a non-functional installation. So possible, but uncommon. Maybe if someone intentionally installed WDAG before updating to v15.5.5+ knowing the latter will fix the incompatibility (i.e. updated both, but in the "wrong" order).
In all cases the answers above assume the underlying system has the WDAG feature enabled. If not, the circumstances to encounter the issue won't be present.
