DirectX 12 shown as available version on first page "System" of DXDIAG is not sufficient. Please switch to second page "Display". Here you must look in "Driver" info window on the right. The important part is shown at "Feature Levels". I just tested 3D Maps in a VMware Image. VMware graphics hardware / VMware-Tools driver info shows as "Feature Levels": 10_0, 9_3, 9_2, 9_1 ( = DirectX versions supported) Even as DirectX version 10_0 is listed as supported, Excel 2016 Insider 3D Maps complains: So your graphics hardware AND the driver must be supporting DirectX 10_1 and up to get 3D Maps running. I assume your's won't.
Thanks for the question, musical123. I have literally been spending hours trying to get this to work. It wasn't until I read ratzlefatz's reply with his path example, that I realized the path I had it extracted to was what was causing the problem (i had it saved to c:\downloads\MS Office 2016 VL KMSTool\O2016RTool\O2016RTool.cmd). Once I moved the extracted folder to the C: drive - current path C:\O2016RTool\O2016RTool.cmd). Now all appear to be working correctly.
ratzlefatz, thanks for the path designation of: If you run it from folder (ex. drive:\O2016RTool\O2016RTool.cmd) then O2016RTool-Menu is shown. I too was having issues with the windows almost immediately closing. I would get the ouput: O2016RTool Checking all Office 2016 distribution channels for new updates. Please wait.... The system cannot find the file D. then window closes. I did my best to read the script, as well as the instructions, but the part about saving to (ex. drive:\O2016RTool\O2016RTool.cmd) completely escaped me. I least I have been learning today Thanks for the tool, I will post again once I complete the install/patch.
Thanks for the tool. After quite a few hours, I was able to get MS Office ACTIVATED!!! (Issues with a aprtial install, old MS Offices files not completely removed, etc.). Much thanks to the developers and testers who posted issues and bugs. I did find that when designating the install path, the O2016RTool had issues (or at least it did for me) if there were spaces in the directory name. (I had issues when install directory was named "C:\MS Office 2016 VL" ,but everything ran fine once I removed the spaces naming it "C:\MS_Office_2016VL" Thanks again
Another thanks.... The O2016RTool seems to work great....Tried it out on my desktop, and was able to complete the install with only a few minor glitches.
Thanks for reporting. "Check for new Office versions" routine: Confirmed. "Spaces" in O2016RTool-path is a problem here. I will look into this and come back with a solution.
hello. is there a link for previous version of O2016RTool? I just downloaded and used the current O2016RTool and nothing's happening when i'm choosing the convert to volume, KMS activation, and change office update path. seems like something's wrong somewhere in :CheckOfficeApplications. it is also not installing project and visio. so yeah if there's a link to previous version of the tool i'll be glad to test whether it's my machine or the tool that's having problem :/ edit: turns out the original installation doesn't installs the retail licenses.. tried O16-C2R-Retail2Volume and it can't find Office 2016 License Files
the reason I asked without converting, it's hard to download another VLSC copy, almost all monthly quota is gone anyhow I'll download VLSC next month thanks
Just reporting in with another success ... went with defaults mostly ... OS ... latest Win 10 Insider ... 15007 x64 .... Office local set-up .... Insider Fast .... Architecture x64 no problems downloading ... luckily I've got a quick connection so it didn't take long! .... Installed full Office suite + Project + Visio .... Converted to Volume .... Activated !! All went smoothly with no errors! I must admit I'm not an Office user normally so I've not checked everything out yet, but so far so good!! Big thanks to ratzlefatz and all the team involved in putting this together!
This whole concept of VL for C2R is pretty cool coming from the old VL MSI world. MSI is really getting left behind except for fixes. Question: Is it normal that the Convert option (Menu item C) will always try to convert even when there should be nothing to convert? That is, once a C2R has been converted from retail to VL, I noticed that going back into C appears to convert it (Office 365 ProfessionalPlus = "FOUND") again, though it really can't be, right? Also, is the string in the "About" box of the programs (EULAID:O16_RTM_VL.1_RTM_EN) a reliable indicator of Retail or Volume status? I forgot to look at it before conversion, but I assume that it would have been something like RTM_RETAIL.
Yes, that's not quite perfect. Let me see if I can improve the check. Most parts of the Enduser License Agreement (EULA) text change according to which license (Volume or Trial, Evaluation, Retail) is activated.
I just downloaded 'O2016RTool' but while unzipping it, i am being prompted for password. Can you help with the password? Thanks.
Password for zip downloaded! Above download of 'O2016RTool' prompts for a password? can you help? Thanks.