10 and 7 virtual machines. Activation with KMS VL all 7.0 beta or latest OfficeRTool activator shows an error message that no valid key is found, but it works using Abbodi's convert Office to VL script (but in this case you loose black theme). But if you install Office and convert it with january 6 Offce20016RTool, all is OK. So I wonder if when using new setup installer from latest OfficeRTool, older licences are no more valid. Here is a screenshot for report of activation status pressing A after conversion and KMS activation try (conversion to VL status is checked OK). I'll try with latest Office version that was published yesterday.
Very odd.I uninstalled everything and cleaned up, Then installed full 365 (Project and Visio inc.) 16.0.9001.2144_en-US_x86_Monthly_Channel, then converted to VL and activated sucessfully using 22nd Jan tool for everyhting.(Win 7 Pro OS -non virtual) Black theme available. Maybe @ratzlefatz or some of the other experts will have a theory?
I don't know. I retried with previous OfficeRTool and effectively it didn't activate too, but all was OK with KMS vl all 6.9 (but not with 7.0 beta). I regularly check updates and do tests keeping previous working versions in case of bugs. A friend's Windows 10 computer had a problem with Office (he disconected during Office update and loosed everything) so I tried a reinstall and tool didn't work. In my real computer I have an official licence for Office so I can't reproduce the test. Concerning my virtual machines I made a lot of tests in them uninstalling and reinstalling Office but I assume that when you uninstall Office all licences are deleted ? I'll redo a clean Windows installation at next Patch tuesday and report. So in my case the working solution is to install and convert Office via latest OfficeRTool, and then activate it with KMS VL 6.9.
I tried to reproduce the bug. An other solution is to rebuild tokens.dat and cache.dat and all is working again. So problem definititely solved in my case.
For me not once. At first no error during the whole process, later on activation produced an error. But conversion always ran through without any issues. Tried cleanospp as well, but again conversion went through fine. Came down to tokens and cache. And just to clarify: It all started with normal update failing (error 30088-28), that never happened before. License was fine and had 160+ days left, just wouldn't update. Clean install and it always stayed on "unlicensed", even directly after install and conversion.
Hello everybody I have installed office pro plus and made it volume via oc2r tool. I have a simple question. I have my work saved in one drive, so when I need to make changes in one file, excel tells me to log in my microsoft account. I know that my office is “illegal” but my one drive is not as I use only the free space of 5gb. Is there any danger of being caught if I am logged in with my Microsoft account in the hacked office? Should I do this? Thanks a lot
Hey, sorry if asked before, but I searched the thread and there is no clear answer. Can I change installation path from C to D?
A new OfficeRTool version (2018/February/12) was released today Error corrections: - Detection of Insider FAST distribution channel corrected (needed for Office 2019 download/install) Enhancement: - Added KMS Retail2Volume conversion, insertion of default KMS-Volume-Keys and 180days KMS activation for Office 2019 Pro, Visio 2019 Pro and Project 2019 Pro. No other changes were made. Download-links and checksums in OP were updated.