Error when installing VMWare Standalone Converter to Windows 10

[macspace]

Having an odd problem, I have use the converter software before with no issues until now. Recently purchased a new PC with Windows 10 Home edition, ( Version 1703, Build 15063.540). Installed VMware-converter-en-6.1.1-3533064 with no issues, however when I try to launch it, I get the following error:

Config File Error:  Not Well-Formed (invalid token) (line 4)

I've tried installing and launching the software as well in Compatibility Mode for Windows 8, also same issue.

Does anyone have an insight on this?

[parmarr]

Hello,

Please see the KB below for assistance

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10087...

[mrosik]

Hi,

I need make p2v image but i get error message during run "config file error not well formed invalid token line 4"

PC DELL Optiplex 9020 with latest BIOS.

Can I have help about above issue

Best Regards

Marcin

[mbraymon]

I also get config file error not well-formed (invalid token) (line 4) on a Lenovo Yoga 900 Laptop.  The KB article doesn't help,  Anyone have any insights?

[continuum]

Lets sum it up:

- you install an unknown version of VMware converter using an unknown host operating system
- you read an unknown KB-entry
- maybe you tried some unknown tricks following that unknown KB-entry but the results are unknown
- something is wrong with line 4 in an unknown file

Suggestion: lets start with looking into line 4

Ulli

[EzioM]

Resolved:

In my case the line 4 of the configuration file: converter-client.xml contained the <defaultDataPath> parameter specified by a path that included a special character in the computer user name. I commented out the line which is not needed and the program starts fine. Alternatively I suppose it is enough to change the user to a name without special characters (the problematic user was "B & B"), or quote the path in some way to consider completely the string and do not manage the special & character.