- Newest
- Most votes
- Most comments
Hello,
This is indeed very strange. It seems like there is some OS configuration limitation which not allowing WorkDocs to complete its initialization. As mentioned by you, only this machine is not installing WorkDocs correctly.
There could be several reasons as to why is this happening. We need to gather logs from your end to further investigate, But before that can you please perform the below action plan:
- Uninstall the Workdocs installer completely and then try to run the Workdocs installer. [1]
- Can you please restart the Message Queuing service to clean up message files. [2]
- Please refer to these articles which discusses the same issue and helped in fixing it.
[+] https://repost.aws/knowledge-center/workdocs-authenticating-user [+] https://repost.aws/questions/QUWcL6MOYFRzqXkd1oGhAnew/amazon-workdocs-drive-authenticating-user-stuck-on-windows-10-and-11
Additionally, If this doesn't help we would require WorkDocs drive client logs in order to further investigate and also deep dive into the issue to know the root cause. We would request you to Please reach out to us.
Get the logs from the PC: -> Open File Explorer -> Browse to the following location "%appdata%\Amazon\AWSWorkDocsDriveClient" -> Right click on the "logs" folder and click "Send to" and choose "Compressed(zipped) Folder"
References:
[1] https://docs.aws.amazon.com/workdocs/latest/userguide/uninstall.html [2] https://support.microsoft.com/en-us/topic/you-must-restart-the-message-queuing-service-to-clean-up-message-files-4d6a1e97-4428-6756-7584-81a1d1213ec1
Relevant content
- asked 2 years ago
- asked 5 years ago
- asked a month ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago