If you want create a PS-only version, no problem. Just do it. Would be nice if you mark this fork as your's. What Powershell-Version will you require on client's site? Windows 7 uses V.2.0 out of the box. If your converted PS-script needs a higher version, then the Win7-users have to install PS 3.x/4.x and the corresponding dot.net-framework. The announcement of such a new PS-version in thread's first post can only be done by s1ave77 because he's owning it. But at the present moment it seems, he is very busy with his Non-Digital-Life
Please try downloading and installing the current/newest version 16.0.6228.1010 (Insider) or 16.0.6001.1038 (Retail). Just enter Office Build/Version-string in O2916RTool download dialogue: Set VNEXT Download Path >c:\test Set Office Build >16.0.6228.1010 -- (or 16.0.6001.1038) In the meantime I will do some research/investigation... TEST-UPDATE: There is something wrong with the older version 16.0.6228.1004. I got the same error after download and install. But I also knew this version worked before. Maybe MS changed something in the files on the content delivery server regarding this version. I will try if I can find out what's the reason, but you shouldn't bet on a successful investigation. RESULT: Newest version 16.0.6228.1010 will install without problems (just tested). SOLUTION: Download and use the latest version 16.0.6228.1010 for install.
I want to ask to be sure... I have legal win10. If I want to install office 2016, crack it and keep win10 legal, I have to download from "beta emote" in ratzlefatz's signature and just follow what is written in readme. Am I correct?
Hi ratzlefatz, Currently trying to install Office 2016 using the O2016RTool. I've downloaded the Office 2016 VNEXT / Insider C2R (16.0.6228.1010). - The VNEXT download completed successfully - Office 2016 installs successfully - Conversion to Volume completes successfully but... The KMS activation does not work. When selecting option (1) to proceed with the internal O2016RTool KMS server, I am greeted with the following problem: Code: -------------------------------------------------------- No Instance(s) Available. No Instance(s) Available. Activation Failed -------------------------------------------------------- I have removed the Office 2016 install using the Microsoft 2013/2016/365 removal tool (O15CTRRemove), and I am willing to troubleshoot. Some details: - XPS 15 9550 - Windows 10 Home version 1511, OS Build 10586.11 (x64) - Windows Defender is disabled (real-time OFF, cloud-based protection OFF, sample submission OFF) before installing with the 02016RTool.
Hi ratzlefatz, No rush on the request. I like the O2016RTool more, as it has worked on other computers. Would you like me to install using KMS VL ALL and report back with results? EDIT: Fresh install from 16.0.4266.1003_en-US_x86_x64, then running KMS_VL_ALL returns this result: Any thoughts on what would cause this error? I am willing to troubleshoot if required.
Uninstall complete, currently working on install from Retail-ISO (16.0.4266.1003_en-US_x86_x64) Conversion to Volume successful. KMS server not working. Still showing the "No Instance(s) Available" with "Activation failed". I have disabled Windows Defender Real Time and Cloud-Based scanning. At this point, I'm more than happy if you remote access my machine. This is somewhat frustrating, as I have used the suggested tools from Microsoft and this forum, but nothing seems to work.
I used your tool to download Office MSDN Retail v16.0.6001.1038 to my surface pro (win 10 pro). Then I converted it and activated (with internal activator) successfully. I check for update and no updates found so it's still v16.0.6001.1038. Then I copied downloaded folder to my desktop PC with win 10 pro too. So I installed with your tool again, converted and activated, exactly like before. Then checked for update and it updated to v16.0.6228.1010 which is supposed to be MS-VNEXT Insider version... Why?
Did you "set" Office-Version to "16.0.6001.1038" the second time? If you just pressed <return> without entering something at this step, then O2016RTool selects Insider-Branch. Update - I just forgot to mention: When you copy the complete download-package (including "setup.exe", "configureXX.xml" and "start_setup.cmd") then it is sufficient just to use "start_setup.cmd". So you don't need O2016RTool for download and setup again.