[ms office - 2019] Install Error

[Gongalong]

Hi Folks,

 

I’m unable to get Office 2019 to install.

 

I’ve installed it many times before without issue, and I know I need to use the Office deployment tool which I’ve tried to use in conjunction with an existing XML that’s worked fine before. In this particular case I’m trying to install it on stand-alone laptops that we use for exams (hence why we’re installing 2019). The install fails early on with the error below.

 

In terms of what I’ve tried to do to resolve it: I’ve downloaded the latest SETUP.EXE deployment tool, created a new XML, ensured that both the EXE and XML are in a local path that the user had rights to (I’m using the local admin). I’ve ensured that the machine’s Internet connection isn’t filtered, I’ve also put it on an alternate “normal” unfiltered Internet connection. I always get some error of the type below. Microsoft’s suggestions are an anti-virus or filtering issue, so I’ve also tested by removing the anti-virus (and as above I’ve tested with no filtering). I’ve also used their Office uninstaller to no avail.

 

We’re sorry, we can’t continue because we weren’t able to download a required file. Please make sure you’re connected to the internet or connect to a different network, then try again. Error Code: 30182-2030 (2).

 

Any ideas?

 

Thanks

[Oaktech]

What happens if you just do it like a consumer and just run the exe file and set the options in the gui?

[Gongalong]

Running the SETUP.EXE from the deployment tool?

[Steve21]

Whats in your XML file? It could be something silly like if you have it pointing to a local path and it's a standalone laptop that it can't access it

 

If it's fully standalone, why not download the installers and transfer them across rather than trying to download it direct on the laptop?

 

Steve

[Oaktech]

Running the SETUP.EXE from the deployment tool?

 

Mount the iso like a DVD, double click the setup.exe, do the next,next,next thing...

[Steve21]

Mount the iso like a DVD, double click the setup.exe, do the next,next,next thing...

 

It's 2019, there is no ISO etc (unless I've missed something very obvious). It's the silly C2R items

 

Steve

[Oaktech]

It's 2019, there is no ISO etc (unless I've missed something very obvious). It's the silly C2R items

 

Steve

 

Interesting... I've got a bog standard ISO of 2019 with setup.exe for individual no domain devices, just came from VLSC

 

My bulk deployment is as you say...

[Steve21]

Interesting... I've got a bog standard ISO of 2019 with setup.exe for individual no domain devices, just came from VLSC

 

My bulk deployment is as you say...

 

Interesting indeed... Do you still have access to download it?

 

The only versions I've ever seen on VLSC are Office online servers, or the setup.exe standalone download. Never had access to a 2019 ISO on mine:

 

 

Steve

[Gongalong]

Whats in your XML file? It could be something silly like if you have it pointing to a local path and it's a standalone laptop that it can't access it

To-date I've always managed to use setup with the /configure option and download it on the fly, but I'm wary that often the installer gives an error suggesting a download issue and there's nothing wrong with downloading at all. For example, we had an issue where the installer would fall over if the Remove MSI line was in there.

 

XML as follows, about as simple as it can be, at least from what I can see. PID obviously obscured!

 

[Gongalong]

Do you still have access to download it?

Ironically we're in the middle of renewing our licenses, and our reseller are late (as per usual) so the VLSC is currently in limbo while the renewal is processed. Although I was sure the 2019 installer wasn't there, and you had to use the ODT.

[Oaktech]

I downloaded about 6 weeks after 2019 was released and I've never needed to do it since... I wonder if I sneaked in under the radar for something.

[Gongalong]

It must be some change in the SETUP.EXE from the latest ODT. I remembered that I had installed it successfully on some other standalone laptops which uses a SETUP.EXE dated 10th Jan 2021. I tested again, and that still works. The newest SETUP.EXE dated 30th May 2021 throws up this error, so the quick fix for the moment is to use this old SETUP.EXE.

[Oaktech]

It must be some change in the SETUP.EXE from the latest ODT. I remembered that I had installed it successfully on some other standalone laptops which uses a SETUP.EXE dated 10th Jan 2021. I tested again, and that still works. The newest SETUP.EXE dated 30th May 2021 throws up this error, so the quick fix for the moment is to use this old SETUP.EXE.

 

I think you're right. After the last couple of messages I tried a bog standard deployment to a single machine using the latest ODT rather than the historic ODT I usually use and while mine succeeded it took aaaagggggeeeesssss... My normal deployment takes about 15 minutes start to finish on a moderately specc'd machine. The one I tried yesterday took over an hour and a half and the webfiltering showed that it crawled at very-small-numbers-of B\s for 10+ minutes on some files.

[Gongalong]

So much for progress!