I have tried unselecting the x64 and x86 updates, re-selecting them and re-publishing, and I get the same error.
I've also followed the steps at the URL provided in the error message, but there's not much I can change in the update. Since it's using an MSI, it appears to need the script runner to run pre-install scripts.
Any suggestions, as I keep getting the error every auto re-sync?
today our VMWare Players were updated to version 17.5.1, and immediately after the update we recieved calls about VMs no longer starting. When trying to start the VMs now they will get to the point of the Windows boot manager an then just freeze. The only way to get out of the freeze is to kill VMware through taskmanager.
We then tried to uninstall the newest update and downgrade to version 17.5.0. But when trying to uninstall version 17.5.1 the package always runs into an error and doesnt uninstall. When looking into the problem we discovered that the process "vmware-vmx" is running, and cannot be closed. Even with full admin access. After using a 3rd party tool to kill the process, we were finally able to uninstall the new version and install the old version manually. When we upgraded to the new version manually the problem doesnt appear anymore, but upgrading via intune using the package the problem appears again.
SH The easier thing may just be to have a machine group for your pilot(test) of 6.2.2, exclude it from the 5.2.9 assignment. Then have the 6.2.2 required to your test group, that way you are managing the devices by taking them in and out of the group instead of potentially breaking assignment by adding complexity.