Currently, there is no resolution.
Workaround:
To workaround this issue:
- Ensure that the user account being used is not identical to the computer name/host name of either the Converter server machine or the machine being converted.
- In case of a domain account being used, use a local windows account to authenticate.