1 Answer
- Newest
- Most votes
- Most comments
0
I have experienced this issue with a number of Windows devices, and found that removing the cache folder under %LOCALAPPDATA%\Amazon Web Services\Amazon WorkSpaces\ then re-launching the WorkSpaces client will resolve the issue. In this scenario, the cache folder is recreated on launch. Hopefully this is helpful for anyone supporting Windows devices that have the same issue.
answered 2 years ago
Relevant content
- asked 10 months ago
- asked 19 hours ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago