What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When Chrome causes trouble on AWS, first identify which service you are using: Amazon WorkSpaces Applications (formerly AppStream 2.0) streams individual applications, while Amazon WorkSpaces provides a virtual desktop. For the common WorkSpaces Applications problem of Chrome’s cache filling persistent profile storage, launch Chrome with a cache directory outside the location meant to persist. Access and connection fixes depend on the service and, for WorkSpaces, the streaming protocol.
Identify the AWS service before changing Chrome
“Chrome on AWS” can mean two different setups. In Amazon WorkSpaces Applications, users stream applications through a browser or client. In Amazon WorkSpaces, users access a virtual desktop, potentially through browser-based Web Access.
As an Amazon Associate I earn from qualifying purchases.
Determine which service and access path are involved before applying a fix. Chrome profile and cache behavior in a WorkSpaces Applications session is not the same issue as a WorkSpaces Web Access protocol or browser-compatibility problem.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Stop Chrome’s cache from filling persistent WorkSpaces Applications storage
On a WorkSpaces Applications Windows fleet instance, Chrome stores both user data and its local disk cache in the Windows user profile by default. If the cache is consuming the VHD used for persistent application settings, AWS documents starting Chrome with a cache directory outside the location intended to persist:
chrome.exe --disk-cache-dir C:path-to-unsaved-locationRun this from an administrator command line on the fleet instance, adapting the path to a suitable location that is not meant to persist between sessions. AWS states that using this option prevents the disk cache from persisting between WorkSpaces Applications sessions. It changes the cache location and persistence; it does not move all Chrome user data or prevent user data from persisting. Check the image’s launch configuration and target path before rolling it out. See AWS’s General Troubleshooting guidance.
Set the persistence trade-off deliberately
- Use a non-persistent destination when the goal is to stop accumulated cache from consuming persistent settings storage.
- Do not treat this switch as a complete Chrome profile relocation; the command specifies the disk cache directory, not the full user-data directory.
- Confirm the chosen path exists or can be used by Chrome in the fleet image and matches the intended session lifecycle.
Check browser access and feature compatibility
WorkSpaces Applications browser streaming
AWS lists Chrome, Firefox, Safari, and Edge as supported browsers for WorkSpaces Applications browser access. The web client supports the three latest major versions of supported browsers; users on older versions are notified. AWS says browser access requires no extension or plugin.
Feature requirements can narrow the choice: drawing tablets are supported only with Chrome or Firefox, while webcam redirection for conferencing is supported on Chromium-based browsers, including Chrome and Edge. Confirm the specific feature and browser version against AWS’s browser requirements.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWorkSpaces Web Access
For a WorkSpace accessed in a browser, confirm that an administrator enabled Web Access and identify whether it uses DCV or PCoIP. DCV web access is available for Windows- and Linux-based WorkSpaces through a supported browser. PCoIP browser access is limited to Windows WorkSpaces, is unavailable in some AWS Regions, and supports Chrome or Firefox on desktop systems. PCoIP Web Access does not support multiple monitors or GPU-enabled WorkSpaces. AWS also warns that YUV444 encoding can cause login or rendering issues. Check the current WorkSpaces Web Access requirements rather than assuming WorkSpaces Applications browser support applies.
Rank #3
Find the WorkSpaces Applications session ID
When an administrator needs to investigate a WorkSpaces Applications streaming session, AWS documents retrieving its session ID from browser session storage:
- Open the browser developer tools during the affected session.
- Locate session storage for
https://appstream2.<aws-region>.aws.amazon.com, substituting the AWS Region used for the session. - Expand
sessionStorage.as2SessionDataand read thesessionIdkey. - Share that identifier with the administrator investigating the session.
Follow AWS’s browser troubleshooting guidance. The session ID identifies the streaming session; it is not a substitute for client connection logs.
Collect the right diagnostics for connection problems
Browser session storage and WorkSpaces client logs answer different questions. Use the session ID for a WorkSpaces Applications streaming investigation. For a WorkSpaces client connection issue, AWS documents advanced logging and platform-specific log locations in its WorkSpaces troubleshooting guide.
Before escalating, record the exact error and time, affected service and AWS Region, protocol, client and browser versions, and whether the problem also occurs in another supported browser. This helps separate a Chrome-specific symptom from a streaming or client connection failure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Understand what client deployment settings control
The WorkSpaces Applications client deployment tutorial describes an Enterprise Deployment Tool, client installation files, and a Group Policy administrative template. It also covers StartURL and TrustedDomains registry settings and a DNS TXT record option for trusted domains. These settings customize the streaming client experience; they are not Chrome browser policies. See AWS’s client installation and customization tutorial.
Troubleshoot by symptom
| Symptom | Likely area to check | Next action |
|---|---|---|
| Persistent application settings storage fills during WorkSpaces Applications use | Chrome’s local disk cache is stored in the Windows user profile by default. | Use --disk-cache-dir to place the cache outside the location intended to persist, then confirm the fleet launch configuration and path. |
| Browser access to a streamed application fails or a feature is unavailable | Browser major version or feature-specific support. | Check the WorkSpaces Applications browser requirements; verify the three-latest-major-version support boundary and the requirements for webcam or drawing tablet use. |
| WorkSpace browser login or rendering fails | Web Access protocol, administrator enablement, Region, or PCoIP limitation; YUV444 encoding may also cause login or rendering problems. | Identify DCV versus PCoIP and check the applicable WorkSpaces Web Access requirements, including OS, Region, monitor, and GPU restrictions. |
| An administrator needs to trace a WorkSpaces Applications stream | Streaming session identity. | Retrieve the sessionId from the specified regional appstream2 session storage. |
| The WorkSpaces client itself cannot connect | Client-side connection diagnostics rather than browser session storage. | Enable or collect the relevant advanced client logs and use the platform-specific locations in AWS’s troubleshooting guide. |
Or skip the browser setup
If your goal is to capture a webpage rather than troubleshoot Chrome inside an AWS streaming session, ScreenshotNeo can return a screenshot or PDF with one request. For example, using cURL:
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. It accepts cookie or consent banners and removes known consent platforms, newsletter popups, and chat widgets before capture; these steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides screenshot tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
