I know . And that's the test-modification I sent @luozhiqi. Because I didn't get that error, I am waiting for his/her test and confirmation of success. It's useless to implement this if it doesn't work. But if successful, then a new OfficeRTool version is released. btw: Of course you have to add --user-agent=OfficeClickToRun in all wget-download commands then.
Latest builds of all standard distribution channels are maintained and listed in post #6 on page 1 of this thread. OfficeRTool's function "(A) SHOW CURRENT ACTIVATION STATUS" will show this (and more) info from a already installed C2R Office.
I just checked Virustotal and SppExtComObjPatcher.exe comes up positive on several engines: AegisLab: Application.Patcher.mB9H AhnLab-V3: HackTool/Win32.AutoKMS.C956504 Antiy-AVL: RiskWare[RiskTool]/Win64.ProcPatcher.a CAT-QuickHeal: Risktool.Procpatcher ClamAV: Win.Malware.Agent-6359146-0 Cylance: Unsafe Cyren: W64/Trojan.BMWQ-4018 DrWeb: Tool.KMS.7 ESET-NOD32: a variant of Win64/HackKMS.C potentially unsafe GData: Win64.Application.Agent.9FOPMP Ikarus: not-a-virus:RiskTool.ProcPatcher K7AntiVirus: Unwanted-Program ( 004bf5511 ) K7GW: Unwanted-Program ( 004bf5511 ) Kaspersky: not-a-virus:RiskTool.Win64.ProcPatcher.a McAfee: RDN/Generic PUP.z McAfee-GW-Edition: BehavesLike.Win64.Hacktool.xt Microsoft: HackTool:Win32/AutoKMS!rfn NANO-Antivirus: Trojan.Win64.HackKMS.deintz Panda: PUP/Patcher SentinelOne: static engine - malicious Symantec: Trojan.Gen.2 TrendMicro: TROJ_GEN.R002C0OAO18 TrendMicro-HouseCall: TROJ_GEN.R002C0OAO18 VIPRE: RiskTool.Win32.ProcessPatcher.Sml!cobra (v) (not malicious) ViRobot: HackTool.KMSpico.4608 Webroot: W32.Hacktool.Gen Yandex: Riskware.ProcPatcher! ZoneAlarm: not-a-virus:RiskTool.Win64.ProcPatcher.a Nothing to get too worried about but worth noting.
Antivirus programs are acting very aggressive against such "little helpers". Nothing to worry and only worth noting: These are completely false positives.
Hi, I'm new here... I have new laptop with pre-installed Office 365 included. When I used OfficeRTool2018May23, I skipped the process directly to Step 3 (Convert Retail to VL). But it says that "Supported Office 2016/2019 not found". Should I download Office Package from the start (Step 1)?
I am sure, this is Office 365 Personal Trial version and not Office 365 ProfessionalPlus. Preinstalled Office Trials can not be converted and activated. YES! All steps (Download, Install, Conversion, Activation) are needed. But before, you must uninstall preinstalled Office by using Microsoft FixIt-Tool from post#4 on page 1 of this thread. Follow recommended steps in usage instructions. This ensures, no trash from preinstall interferes with new install.
Thanks @ratzlefatz for the explanation... Yeah, just like you said that the preinstalled version is Office 365 Home. I already follow all the instructions from page 1, without uninstalling preinstalled ver. But it works. no error detected so far.
I'm a fan of a clean ground basement. In case of trouble, I never tried to repair Office installations. I always used MS FixItTool and it was a good decision. So I always suggest to use FixItTool to remove all existing Office remnants (Preview/Beta <-> Trial) before installing a new full version or up-/downgrading from one main version to an other (2010 <-> 2013 -> 2016 <-> 2019). Next case for FixItTool: One of the "Microsoft Internal Use Only" Beta-/Dev- channels was used and you want to go back to standard distribution channel.
Access got 2019 SKU Code: Access2019Retail Access2019Volume also noticed new VL licenses for 2019 SKUs didn't download or install recent C2R version to check yet
I justed installed the Office 2016 (downloaded with OfficeRTool and convert it to VL license) and everything works fine. However, whenever I use the (K) START KMS ACTIVATION try to activate, it always reply "Activation Fail" without further elaboration and my Office is still left at grace period (which is ... 2 days left...) During activation, there is another console opened (then close automatically) with following information: 2018-06-01 1256: Listening on [::]:16880 2018-06-01 1256: Listening on 0.0.0.0:16880 2018-06-01 1256: vlmcsd 1111, built 2017-06-17 01:00:56 UTC started successfully I had used MS fixit tool to completely removed my previous Office several times, (including reboot, re-run fixit to make sure it doesn't find any Office) also deleted tokens.dat/cache.dat (always follows reboot). I even tried to install from VL ISO but activation still fail. I have no AntiVirus installed other than built in windows defender. Firewall is not activated. (Yea, I know it's a dangerous setup...) Any suggestion? I am on Windows 10 Pro. Please let me know if any log is needed. Thanks!
For a quick test, please disable Windows Defender completely! Extract again all OfficeRTool files from 7z-archive and try to redo KMS activation. Create exclusions in Windows Defender for OfficeRTool directories and files. I assume during extraction, KMS-activation helper module "SppExtComObjPatcher.exe" was caught by active Defender, hence KMS activation fails. But if this didn't work and you still fail to activate, then something is seriously wrong with your system. On non tampered systems, OfficeRTool is working fine. In this case, I suggest to wipe the system and install a fresh new Windows 10.
New 2019 SKUs: They all need new GVLKs . Code: Product: ProPlus2019Volume SKU-ID: {85DD8B5F-EAA4-4AF3-A628-CCE9E77C9A03} License-Family: Office19_RTM19_ProPlus2019VL_KMS_Client_AE Volume: GVLK Group-ID: 4145
two updates within 1 week ... Hey Why C2R Office Ver. Doesn't support 'Sets Tab' of Windows 10 like the O365 one's
Thank you. The important ones are those, having ...VL_KMS_Client_.... in their name. These are needed for Retail2VL-conversion. The main license file for product-keys is "pkeyconfig-office.xrm-ms". This one checks and allows keys to be entered for the active VL_KMS_Client license files. If you want to inspect "pkeyconfig-office.xrm-ms", you can use 'PKeyConfigReader'. You will find this software here on MDL.
Thanks for the help! It works now! As you indicated, I need to 1) Disable WD, 2) Extract again from 7z-archive, 3) Run OfficeRTool. Previous I did in wrong sequence 2-->1-->3 thus cannot work. ------------ Also, On an separate issue with ORTool Beta: I can use OfficeRTool version 2017/Sep/18 to Install the Office no problem. However, with Beta version (2018/May/23), when I try to install, the Office setup program will fail with a dialog saying: We found a problem! This installation requires a compatible Microsoft Office program installed on your computer. Similar to situation at below page... (but the solution is not effective...) www[dot]techyv[dot]com/questions/resolve-this-installation-requires-a-compatible-microsoft-office-program-failure/ (Sorry I have yet no permission to post web link here...) Any idea? Thanks for your great work!
I suggest to use MS FixIt-Tool to remove all remaining Office traces from the system. See post #4 (section 5) on page 1 of this thread where to get this Tool from Microsoft. Be sure to follow all recommended steps (don't forget the reboots!). Use always latest OfficeRTool to download a new setup package. Then install, convert and activate. I'm sure it will work.