1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans