![]() ![]() ![]() ![]() Prevent Google Chrome from writing on your SSD (Solid-state drive). Let’s break down the fixes we have in store for you. This issue is most common on Windows 10 PCs that have an SSD (Solid-state drive) rather than an HDD (Hard disk drive). The waiting for cache error you see on your laptop or computer occurs when Chrome is unable to access this information. The cache is that place where your internet browser, in this case, Google Chrome, stores certain information about your browsing activity so it can access regularly used websites quicker. Let’s start by quickly going over what cache is. What does “Waiting for cache” actually mean? In this guide, therefore, you'll learn some quick fixes to help you fix this bug. This can even affect your computer performance overall as system resources will be used to try to connect. Whenever this happens the website freezes for a few seconds or a few minutes. When trying to load up a website they get the message “Waiting for cache” at the bottom left of the window. Disabling UDP (to force TCP) seems to be a decent enough work-around, though the protocol can feel a bit laggier.Many users, especially Windows 10 users, have reported issues with Chrome. Then Windwas meant to fix these, I think.Īpparently the new version of the RDP protocol has some issues, e.g. I'm fuzzy on the details, but in short, I think there was something about some bugs being discovered in the RDP protocol as implemented prior to Windows 10 1903:ĬVE-2019-1181 | Remote Desktop Services Remote Code Execution Vulnerability ĬVE-2019-1182 | Remote Desktop Services Remote Code Execution Vulnerability. I reverted this solution after trying it, preferring to rely on the Group Policy instead. On client: Registry Editor → Computer → HKEY_LOCAL_MACHINE → SOFTWARE → Policies → Microsoft → Windows NT → Terminal Services → Client → → New → DWORD (32-bit) Value → Name: fClientDisableUDP → Value data: 1 → Base: Decimal Note: This seems to have worked for me when I tried it, but can't verify much beyond that. Not recommended (tweaking Registry Editor) Source: answer. On server : Local Group Policy Editor → Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections → Select RDP transport protocols → Enabled → Use only TCP On client: Local Group Policy Editor → Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Connection Client → Turn Off UDP On Client → Enabled Three ways to implement (probably mutually compatible, but probably only need to do one): Switching to TCP-only does seem a bit more laggy, but the lag is more ordered (which is strangely nicer than the erratic lag) and I've yet to encounter an indefinite hang. RDP seems to behave a lot better with TCP than UDP. Reducing RDP session settings, avoiding audio, and avoiding video seem to help.įull-ish work-around: Disable UDP. ![]() Partial work-around: Reduce network strain. A direct local connection may be relatively reliable. Partial work-around: Improve network connectivity. However, TCP-only coupled with trying to improve network connectivity or/and reducing load (such as video and audio) seems to greatly reduce the incident rate. For example, I've had RDP completely freeze even in TCP-only mode. My guess is that the RDP protocol has lost some of its resilience to packets getting lost or out-of-order. Seems to occur primarily when using the UDP protocol under load. No error messages seen client window can be closed and restarted normally. Other times the RDP session seems to hang indefinitely. Sometimes the RDP session recovers, resuming normal function. Client window is responsive, but the content within it is essentially a static image. RDP session updates oddly, distorting audio and video. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |