This is a known issue affecting vCenter Server 6.5.
Currently, there is no resolution.
Workaround:
To work around this issue, continue the upgrade/installation with the user name under the Specify a User Service Account option in the vCenter Server Service Account.
For example, enter only User Name instead of ComputerName\User Name.