Checking public Office distribution channels for new updates *** ERROR checking: * Monthly_Channel * channel *** No response from Office content delivery server
You get no Internet access to Microsoft Office content delivery servers. Firewall restrictions or Antivirus programm active? Disable Firewall/Antivirus and create Exclusions for OfficeRTool in AV. What to exclude look here.
Really appreciate your help. However, after having changed the update channel from Monthly_Channel_Targeted to Insider_Channel, the installed mondo 2016 has been updated successfully to 16.0.10216. Obviously, C2R program can update without problem, while OfficeRTool.cmd failed to connect office server.
"Monthly (Retail)" channel is NOT working, but "Insider (FAST)" DOES work ? Really strange things happening here. Is new version list at startup only affected by testing "Monthly" channel ? Did the other channels work and show the build-number?
By changing channels with OfficeRTool.CMD, I suceeded to update twice, C2R UI (the MS-office program) automatically appreared upon the CMD running , then updated the Mondo 2016 from (latest_Monthly_Channel_Targeted) to Insider (FAST) or Business(latest_Semi_Annual) without connection problem
OK, now I see clearer where your problem is: 3rd-party modul wget.exe used by OfficeRTool is not working on your site, whereas internal Office update is working. But I'm not able to reproduce your error. Will need some time to think about how to deal with this.
It might be able to explain. I wonder why the web-browser cannot access the update file on the Microsoft server. Actually, the IDM cannot download the update file either, with the error "you don't have the permission to download the file on the server"
@luozhiqi: Webbrowser, IDM and OfficeRTool/wget: All have different User-Agent signatures compared to Office internal update which sends "User-Agent=OfficeClickToRun" on every request. I've send you a test modification for OfficeRTool by private post. Would like to hear if it helped...
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)?