[HOW-TO/SUPPORT/CHAT] OFFICE C2R Download/Install/Activation

You need to login to view this posts content.

 

what is the difference? why is this click2run is crap? it installs way faster than msi setup files. i want to use it for deployment.

 

You need to login to view this posts content.

 

Is there a way to be able to set the installation path during the installation?

 

No, sorry. Setup-Path "C:\Program Files\Microsoft Office" // "C:\Program Files (x86)\Microsoft Office"
seems to be fixed by MS in Click2Run-versions.

I didn't find a way or config-variable to change this, so we have to live with it.

 

Hello There,

Can not open archives O2016RTool, KMS_VL_ALL_6.6

password: s1ave77 is not match



Thanks

 

The password is 2015.

 

Can't figure out what's wrong. i did download of the O2016RTool twice



I've tryed change the string to the new one (final 23) too

 

It's the last ending backslash -- in D:\Downloads\Office 2016 TP\ <-- this one!

Just tested here. Downloading .1021 and newest .1023 using language pt-BR and
setting path to

Code:

D:\Downloads\Office 2016 TP\

gives the error.

Omit the last backslash like shown

Code:

D:\Downloads\Office 2016 TP

and it will work.

 

O2016RTool only gives me a black screen with a flashing cursor. I even ran it as admin. I disabled my anti-virus too.

 

Does the foldername you saved it in, contain special characters like brackets () or "umlauts" ?
If yes, please change foldername to have only characters or numbers (spaces are ok, too).

It's a restriction of the used powershell routine. It will be changed back to VB.script.

If that's not the case then edit O2016RTool.cmd and comment out / add REM to lines 5 and 6:

Code:

REM set "o2016rtoolpath=%~dp0"
REM (NET FILE||(powershell start-process -WorkingDirectory '%o2016rtoolpath%' -FilePath '%0' -verb runas)&&(exit /B)) >NUL 2>&1

and start script with admin-rights / rightclick run as administrator.

 

The same happens on my test machines (7 Ult. & 10 Ent.) both with UAC disabled via Group Policy, no Defender, no 3rd-party AV. Removing this line from script gets everything back to work:

Code:

(NET FILE||(powershell start-process -WorkingDirectory ‘%o2016rtoolpath%’ -FilePath ‘%0’ -verb runas)&&(exit /B)) >NUL 2>&1

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

New Office 2016 Version: 16.0.4229.1024

Release date: September, 11

To get, either start Update from within Office or use VNEXT download from O2016RTool
by manually entering version string in setup dialogue.

All languages are available.

 

Nope, still nothing but a black screen. But with the following editing it works at my side:

Code:

:: GET ADMIN RIGHTS@echo off
set o2016rtoolpath=%~dp0
set o2016rtoolpath=%o2016rtoolpath:~0,-1%
set o2016rtoolname=%~n0.cmd
setLocal EnableExtensions EnableDelayedExpansion
pushd "%o2016rtoolpath%"
cls
mode con cols=80 lines=45
color 1F

Assigning admin rights to an account that already has highest privileges seems the culprit here.

 

ok, thank you for reporting back.

you removed the code lines where "run as administrator" priviledges are requested.

Note: There is a difference between a user who is member of administrators
group and the "run as administrator" priviledge.

Removing the code requires the script always to be run with right-click
-> "run as administrator" to work properly. Starting it as user being member
of administrators group is not sufficient enough. Hence the Powershell-/VB-code.

The problem is related to hiding/disabling UAC with group policy and using
Powershell-/VB-script to request the higher "run as admin" priviledges.

 

You need to login to view this posts content.

 

This worked

 

You need to login to view this posts content.