If you have a VM, which was deployed a few months ago or even earlier, there is a high chance that installation of a next D365FO update will fail. This error is caused by planned switch from Visual Studio 2015 to 2017 and specifically by adding a dependency on .NET Framework 4.7.2, which is missing on "old" VMs. Details could be found here.
This is how the error might look like in LCS:
The solution is to install .NET Framework 4.7.2 and retry the update.
Alternatively, delete an existing VM and deploy a new one. It will have all required libraries installed.
