AWS WorkDocs Drive Client Silently Fails Install

0

I tried installing using msiexec.exe so I could produce a log file. I see the following error in the install log: System.IO.FileNotFoundException: Could not load file or assembly 'System.Collections.Immutable, Version=1.2.1.0...'

I have tried uninstalling and re-installing MSMQ several times. No matter what I do however, workdocs just fails to install, and fails silently if not used with msiexec.exe.

asked 2 years ago671 views
1 Answer
0

Hi,

Thank you for your rePost question. My name is RJ - an AWS Support Engineer who will be addressing your inquiry today.

I understand you are looking to silently install the Amazon Workdocs Drive client, leveraging the msi file and respective flags.

To better help understand the requirements, I reproduced the same using Windows Server 2019 and Windows Server 2022. In my test environments, I was able to successfully install the Amazon Workdocs Drive client using the following command with PowerShell as Administrator.

PS > .\AWSWorkDocsDriveClient.msi /quiet /norestart

Also in my environment, I found that omitting /norestart left the installation paused in an incomplete state.

Lastly, Amazon WorkDocs Drive client requires Microsoft .NET Framework 4.6.2 or later, as well as the Microsoft Message Queuing service to be installed on the target client(s). Please validate that the prerequisites are installed and try the installation once more, using the example command provided above.

If the installation is still unable to complete successfully, please consider opening an AWS Premium Support case.

References

AWS
SUPPORT ENGINEER
RJ-D
answered 2 years ago
  • It's not that I'm trying to silently uninstall. I can't uninstall it at all. I only used msiexec.exe so I could produce a log file of the install process.

    Workdocs will not uninstall and it will not re-install either. It's just made a computer unusable as we require workdocs for our daily work. If I can't install it or uninstall it, and it isn't working, it just leaves you the option to reinstall windows. That is not optimal nor is it acceptable.

    We are having this issue on multiple machines.

    We have had issues with workdocs from the beginning. It needs some serious developer attention and needs to be made more robust.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions