Even using the Office Click-to-Run configuration tool, this always installs the wrong version of Visio. I can't activate it. It's pathetic that Microsoft can't resolve this issue.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@mguyett -- What version of Visio does it install?
Same here, using the VisioProXVolume product ID and when I go to activate using a VL key, it tells me the key is for volume licensed edition which is not installed.
I had similar issue for office proplus. i restarted my computer and tried to activate using ospp.vbs command switch
Code has changed, there is no configuration.xml file any more

@kylethompsonpt The code hasn't changed, the "configuration.xml" is the generic name for the XML file you need to create. You can use one of the included XML files (that you listed above), as a starting point, or create your own, using additional instructions found in the "Overview of the Office Deployment Tool".
@timmmay Same here, using the VisioProXVolume product ID and when I go to activate using a VL key, it tells me the key is for volume licensed edition which is not installed.
Did you use the C2R-P key from the licensing site? If so, were you ever able to resolve the issue?
Is there an answer to above? I just had the same situation with Visio. The keys worked fine a month ago and now I get activation failed.
@rconlee1 The keys they provide in the article are generic keys, that would probably only give you the equivalent of a Trial Period. Those keys would not be for permanent use. If you’ve purchased Visio, you should be using your C2R-P keys which would be on the Microsoft Volume Licensing site.
Just for the record, the procedure worked just fine for me, and the correct version of Visio Pro 2016 installed, as expected. I am using my purchased keys (labeled C2R-P in the licensing site), and they activated just fine, after install. So I don’t anticipate any activation issues in the future. But I’ll definitely keep you all posted, if I have any issue.
I noticed after a restart it worked fine. If you are activating using kms then be sure kms is diwcoverable or host cache enabled . Do a restart and check .
null
Thank you williestylez! I hadn't even noticed the C2R-P keys. I've been looking for this answer for awhile. I don't know why Microsoft has not made it clear in their documents! I'm up and running because of you!
I had a lot of problems with installing Project 2016 with these instructions. Finally, I got it working on Windows 10 1903 64 bit running FROM ADMINISTRATIVE COMMAND PROMPT
... the following command where setup.exe latest version ODT and configuration file were: .setup.exe /configure .configurationPr2016.xml
The configurationPr2016.xml is the following:
The license code for the volume license does not work. I have Office 365 license from my university, and Project volume license from national academy of science, who is not interested in getting the keys. I got Project working this way for more than a year now.
XML does not pass, so figure out substituting _ for triangular brackets
_Configuration_
_Add OfficeClientEdition="64" Channel="Monthly"_
_Product ID="ProjectProXVolume" PIDKEY="WGT24-HCNMF-FQ7XH-6M8K7-DRTW9"_
_Language ID="en-us" /_
_/Product_
_/Add_
_/Configuration_
Hi, I got similar issue. When I tried that way, I am stucked at "setup.exe/ download visio.xml". The dialogue box said error, CODE 30029-1007 (0). I do have plenty of storage and working internet access. Please share the Office folder file downloaded from the "setup.exe/ download visio.xml" step or kindly help me to explain. Thank you. :)
...When I tried that way, I am stucked at "setup.exe/ download visio.xml". The dialogue box said error, CODE 30029-1007 (0). I do have plenty of storage and working internet access.
@avwplace the issue you're facing is that you're either:
setup.exe /download visio.xmlThe last theory is more of a long shot because I think one of the other three issues is what's really plaguing you.
For issue #4, you can use the Office Customization Tool at config.office.com. This allows you to point+click a configuration file and you can be 100% certain that the syntax is correct.
Closing due to the age of the initial issue report and it seems to have been resolved. Feel free to open new issue if problem persists.
Most helpful comment
Just for the record, the procedure worked just fine for me, and the correct version of Visio Pro 2016 installed, as expected. I am using my purchased keys (labeled C2R-P in the licensing site), and they activated just fine, after install. So I don’t anticipate any activation issues in the future. But I’ll definitely keep you all posted, if I have any issue.