Currently there is no solution for this issue. Please subscribe to this article for future updates.
Workaround:
To work around this issue, you can use a custom baseline instead of the predefined one, where you exclude the intel-nvme-vmd and possibly the 7.0u3b VIBs:
In vSphere Client, go in Menu > Lifecycle Manager
- Select "Baselines"
- Select "Critical Host Patches (Predefined)" and click on DUPLICATE
- Enter a name for the baseline and confirm with DUPLICATE
- Select the new baseline and click on EDIT
- Under "Matched" un-selects the following Patches:
- Update Name: Intel NVME Driver with VMD Technology
- Update ID: intel-Volume-Mgmt-Device_2.7.0.1157-2vmw.703.0.10.18905247
-
- Update Name: VMware ESXi 7.0.3 Patch Release
- Update ID: ESXi70U3b-18905247
-
- Update Name: ESXi Component - core ESXi VIBs
- Update ID: ESXi_7.0.3-0.10.18905247
-
- Update Name: ESXi install/Upgrade Component
- Update ID: esx-update_7.0.3-0.10.18905247
- Detach the Critical Host Patch (Predefined) from the host or cluster
- Detach Baselines and Baseline Groups from Objects
- https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.update_manager.doc/GUID-70636F44-9DF2-4FCB-B4C6-71B899B32482.html
- Attach the new duplicated baseline
- remediate the host and check for compliance.