I hope someone can help me with this. I installed a copy of Office 2016 from about a year ago from this forum using the OfficeRTool from here. I had trouble then uninstalling the previous copy of Office and putting in a new copy. I finally ended up formatting my hard drive and installing Windows all over again just get Office to install. Now a year later I had not tried to upgrade to any recent builds which might have something to do with what went wrong. My copy of Office was crashing and not responding and I could no longer get updates for the software I suspect due to the fact that I was using a year old version of the software. I tried to uninstall the older version and reinstall a new one using the latest OfficeRTool and no matter how hard I tried and even when I used the Microsoft uninstall tool from the Microsoft support website to uninstall my old copy of Office, I made sure there was nothing left of the old copy anywhere yet when the installation was almost complete, I would get an error message that the computer needed to be restarted and I had the error code: 30175-11 (5). I have just got done reformatting my hard drive and reinstalling Windows but before I try to put Office 2016 on here again, I was wondering if anyone can tell me why I got this error even though I'm 100% sure there was nothing left of my previous copy of Office before I tried installing the latest version and how can I maybe avoid this from happening again in the future? Anyone have any advice before I try to install Office again or can offer any help here? Thank you for any help in advance!
I have tested with latest (Jan 22nd) as you describe and not found a problem. What OS are you running?
Not exactly, they are simply obsolete and not relevant. I did not become a special person to comb the script, because I wanted to sleep, and the idea with the date check failed. If there is a desire, you can try again to parse the file with info, or try to time the files in the archive to assign the date of the version. --- In the final file there is no superfluous data?
I'm on 365 ProPlus-Insider Channel and also had some problems. First it wouldn't update to latest version, Error 30088-28. Decided to do a clean install (uninstalled via o15-ctrremove first). Everything seemed to be going well, but activation failed (without an error message in OfficeRTool!), status was "unlicensed". Uninstalled again via tool and on second try "Activation failed" came up in KMS. Doing more clean installs with WinDefender disabled and using older Office-versions didn't help. Activation status was always "unlicensed", never "grace period". What finally solved the problem was rebuilding tokens.dat & cache.dat, see here: [HOW-TO/SUPPORT/CHAT] OFFICE C2R Download/Install/Activation Before above troubles with Office started, system was updated to latest build on Win10 Insider Fast-Ring (17093), which I think could be another potential source. Something seems to have changed / got messed up in tokens at some point, that's for sure. Edit: All with OfficeRTool 22nd Jan.
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