Chrome Freeze ups on RDS server
-
That Windows Explorer keeps freezing as well points to Chrome being a symptom and not the source. It's probably just a heavily used process that is most likely to have the issue or the place where the issue is most visible.
-
Is the system fully up to date? Any non-standard AV running on there?
-
Last scheduled reboot was on the 15th where I patched as much as it let me. Since they are a 24/7 shop they hadn't patched or rebooted in a while. Currently, there is another reboot for patches pending.
Regarding the antivirus, webroot is installed.
-
@Romo said in Chrome Freeze ups on RDS server:
Since they are a 24/7 shop they hadn't patched or rebooted in a while.
The more 24/7 they are, the more important that they update and reboot regularly to ensure uptime. Otherwise even simple patches might create extended downtimes when least desired.
-
Sfc results
PS C:\Users\administrator.LVCC1> sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.DISM results
PS C:\Windows\system32> DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.14393.3085 Image Version: 10.0.14393.3085 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log -
@scottalanmiller said in Chrome Freeze ups on RDS server:
@Romo said in Chrome Freeze ups on RDS server:
Since they are a 24/7 shop they hadn't patched or rebooted in a while.
The more 24/7 they are, the more important that they update and reboot regularly to ensure uptime. Otherwise even simple patches might create extended downtimes when least desired.
@scottalanmiller I totally know, but they still don't like to reboot.
-
@Romo said in Chrome Freeze ups on RDS server:
@scottalanmiller I totally know, but they still don't like to reboot.
Then they don't really think that they are 24/7 or that uptime matters. It's one or the other.
-
Chrome is known to do this on workstations so I am taking into consideration as Chrome freezes everything on a Windows PC, let's say leave it open for more than 3 days and more than 45 Tabs. Chrome usage of RAM is over the top.
-
@Romo said in Chrome Freeze ups on RDS server:
Last scheduled reboot was on the 15th where I patched as much as it let me. Since they are a 24/7 shop they hadn't patched or rebooted in a while. Currently, there is another reboot for patches pending.
Regarding the antivirus, webroot is installed.
We should be able to schedule a weekly reboot early Sunday morning. If we reboot weekly the amount of time they will be down will be minimal considering there won't be a ton of updates each time.
Still doesn't fix the Windows corruption. Doesn't DISM allow you to point to an ISO or Windows DVD?
-
If the RDS server is a VM, have you disabled Hardware Acceleration in Chrome?
-
Best way to run Chrome on 2016 RDS.
Use this as a reference.
https://support.google.com/chrome/a/answer/187202?hl=en
Use enterprise edition and configure admx with GPO
Set
Disk Cache Directory
Roaming Profiles Directory
User Data Directory
Setting up Legacy Browsers and Plugin
Turning off Hardware accel and other settings for performance.Just read that
and configure what policies you need. Took me a day to set up but works smooth.
