Hello again @Manuel Flores-Bonilla
I assume that you have already updated the Integration Services to latest versions. You can check with the cmdlet: Get-VMIntegrationService –VMName <VM names in comma separated list> | Where-Object {$_.SecondaryOperationalStatus –eq 'ProtocolMismatch'}
To update them:
https://support.microsoft.com/en-us/topic/hyper-v-integration-components-update-for-windows-virtual-machines-8a74ffad-576e-d5a0-5a2f-d6fb2594f990
or
Copy vmguest.iso from a patched host (\Windows\System32\vmguest.iso) and mount it
I would also suggest, that in case that this machine has been migrated from Physical to Virtual, this s a non-recommended scenario, as has been proven many times to have different points of failure like you are experiencing. If that is the case, best to create a new VM from scratch.
Last but not least, you can try to troubleshoot the services with the next cmdlets from an elevated PS console:
- Check the status of services: Invoke-Command –ComputerName <Hostname> -Credential <Domain><Username> -Scriptblock {Get-Service -Name vmi*}
- Invoke-Command –ComputerName <Hostname> -Credential <Domain><Username> -Scriptblock {Start-Service -Name <comma separated service names>}
3.Repeat step 1
You can also try the file transfers with the next cmdlet:
Copy-VMFile “<Name of target Guest VM>” –SourcePath “<Path to file on host system>” –DestinationPath “<Path to new location on guest system>” –CreateFullPath –FileSource Host
Hope this helps in your case,
Best regards,