Description of problem
Virt-v2v can't remove vmware-tools 11.0.5 successfully from win2019 and win10 guest after conversion

Version-Release number of selected component (if applicable):
virt-v2v-1.45.2-1.el9.x86_64
libguestfs-1.45.6-10.el9.x86_64
guestfs-tools-1.46.1-3.el9.1.x86_64
libvirt-libs-7.5.0-1.el9.x86_64
qemu-kvm-6.0.0-10.el9.x86_64
nbdkit-1.26.2-1.el9.1.x86_64
virtio-win-1.9.15-3.el9.noarch

How reproducible:
100%

Steps to Reproduce:
1.Prepare a win2019 guest which has installed vmware-tools 11.0.5.15389592 on Vmware environment and convert it from VMware to rhv by v2v

1. virt-v2v -ic vpx://root@10.73.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.2 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win2019-x86_64 -o rhv-upload -of qcow2 -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -ip /home/passwd -op /home/rhvpasswd -os nfs_data -b ovirtmgmt -v -x |& tee > virt-v2v-win2019-vmware-tools-rhel9.log

2.Check the guest after v2v finishing conversion, found although vmware-tools service is stop, vmware-tools isn't removed from windows programs and exit code is 1603 of uninstalling vmware script in firstboot log, please refer to screenhost"win2019-vmware-tools-after-rhel9-v2v.png"

Test the other windows guests (except win2012r2 because can't install vmware-tools for win2012r2 guest on vSphere 7.0 client) which have installed vmware-tools 11.0.5.15389592 from ESXi7.0 to rhv by v2v

VMware-tools uninstall
win2016 Success
win10 x64 Fail
win2012 Success
win8.1 x64 Success

Actual results:
As above description

Expected results:
Virt-v2v can remove vmware-tools successfully from all windows guest after conversion

Additional info:
1.Can reproduce the bug on rhel8.5 AV:
virt-v2v-1.42.0-14.module+el8.5.0+11846+77888a74.x86_64
libguestfs-1.44.0-3.module+el8.5.0+10681+17a9b157.x86_64
libvirt-libs-7.5.0-1.module+el8.5.0+11664+59f87560.x86_64
qemu-kvm-6.0.0-25.module+el8.5.0+11890+8e7c3f51.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64
virtio-win-1.9.17-3.el8_4.noarch

2.Can reproduce the bug on rhel8.4 AV:
virt-v2v-1.42.0-9.module+el8.4.0+9561+069bb9c1.x86_64
libguestfs-1.44.0-2.module+el8.4.0+10146+75917d2f.x86_64
libvirt-libs-7.0.0-14.1.module+el8.4.0+11095+d46acebf.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+10806+b7d97207.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64