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

@ratzlefatz

As promised yesterday, here is my report:

After having studied your batch command file JATDevice.cmd in detail (especially the function "DownloadO16Offline"), I know that for the x86-architecture c2rfireflydata.xml, v32.cab and v32_16.0.4229.1009.cab are the first 3 files that are downloaded - using the commandline-tool "wget.exe".

I restarted the JATD-download a few times and cancel it within the first minute and in fact these 3 files were downloaded each time successfully.
But nevertheless v32.cab and also c2rfireflydata.xml were NOT downloaded the very very first time yesterday. That's why error 30101-101 was raised.

So my question is:

Does wget.exe include some kind of exception handling if a file cannot be downloaded - whatever the reason may be ?
Or do you have to verify the existence of a ALL downloaded files yourself with a simple "if not exist"-batch command like this:

Code:

if not exist "%downpath%\%o16build%_%o16lang%_%o16arch%\Office\Data\v%o16arch%.cab" (
   echo *** ERROR downloading "%downpath%\%o16build%_%o16lang%_%o16arch%\Office\Data\v%o16arch%.cab" ***
   set /p errortrigger=Cancel download now? (1/0) ^>
   if "%errortrigger%"=="1" exit /b
)

This would be my suggestion for updating your really very impressive batch command script !

 

I am getting same error 30101-101 and unable to install x86 version.

 

Same here - Considering the fact that I had successfull downloads/installs yesterday, but Jayden had not
and now there is a new Office version released, Microsoft must have changed something.

I investigate now. Please be patient.

 

@Ratzlefatz: Thanks
@jayden: thanks due to your renaming v32.... file post i am able to install 1009 version

 

Microsoft already changed dependencies of files. The x86-line in script must load 2 extra x64 files to
get 32bit/x86 setup running.

Now MS did it again and I'm tired of fiddling which one they need now and may change this once more
in further releases.

Update after testing:
Combining x86 and x64 files in one setup-folder did the trick.

I will change the wget-line in JATD to fetch both achitectures in one run.
Download times will increase. But better that, than endless frustration because of error 30101.

 

We have to check the existance of 20 files (x86 and x64). If there is 1 file missing the whole setup will fail.

I suggest in case of install errors: Don't bother the users with "abort" questions. Simply redo download and
try the setup again. You must download missing files anyway if you want a clean install package. And wget
checks existance of already downloaded files and skips the matching ones, so reloading time is not that much.

And with the next JATD version both architectures (x86 and x64) are included in 1 package. This will avoid
most setup errors.

 

HowTo instructions (posts #2 - #6) are updated, too

 

Can you share and compare mine, your Routine on how you update your Office 2016 installation to your PC/Laptop every Updated Release/Build.

My Routine:

1. Uninstall Office 2016 using OffScrubC2R.vbs
2. Run CCleaner for Registry Issues
3. Reboot
4. Install Office 2016 (x86/x64) using JAT-D nstall VNEXT Office

Spoiler

Downloaded vnext Setup Package found in:
C:\O16-32_64BiT\16.0.4229.1011_en-US_x86_x64

Set Office Install (1/0) >1
Set Project Install (1/0) >0
Set Visio Install (1/0) >0

Set Architecture to install (x86 or x64) >x64

Language is preselected: en-US
(matches vnext download)


▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Pending Setup - SUMMARY -

Install Office ? : 1 = YES
Install Project ? : 0 = NO
Install Visio ? : 0 = NO


Install Architecture ?: x64
Install Language ? : en-US

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Start local install now (1/0) or Create Install Package (C) ? >
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

or is there any Shortcut method you can suggest?

Thank You very much again to both of you @ratzlefatz @s1ave77

P.S. excuse my English Grammar

 

If you always want to do a clean FULL setup, your routine is pretty good. But that is not
really necessary. Use this on fresh installs.

Yes. Rather than doing a time consuming cleaning and full install on every new Office version,
you can use the internal Office Update Routine in Word or any other Office 2016 product:

Menu -> File -> Account -- on the right, click -> "Update Options" -> "Update Now"

"Update" in this case means = If there is a newer version available, it will be downloaded and
installed by Office itself. It is almost the same as a new full setup.

 

No. But will do immediatedly - HowTo in post #2 updated - New entry 6.)

 

which is the latest 64bit MS office plus build out there right now?

 

16.0.4229.1011

always read the O.P

Post #6

 

You need to login to view this posts content.

 

You need to login to view this posts content.