As the subject states, about every 24-48 hours I find that I have to enter my password to access the KVM. No issues doing so but not only is this annoying but I find the screens in Windows are slightly corrupted afterwards. I have to reboot the KVM then all works well again and the Windows screens are sharp once more…until I’m logged off…then the cycle repeats.
provide debug log to us
How to send debug logs? Email? Private Attachment?
You can PM @minmie
Done. Thanks for looking into this issue.
It seems screens slightly corrupted every time when you logged off ？Have you ever change ”video Mode“ to normal to see
Yes…I only use normal video mode
corrupted video here aswell, on comet pro firmware 1.8.0 beta 2, although the screen corruption happened before this firmware aswell but less frequently.
It seems to happen more for me when the login screen from windows has been altered by wallpaper engine from steam, this is a option which replaces the background, in the boot process this issue is not present.
Yesterday I had it too, and decided to just wait and see after i logged on, it restores over some time to me, if I directly refresh the browser it is fixed, the artifacting is a moving discolorisation maybe because of the animated wallpaper.
I guess that windows loads the driver for gpu/monitor or some filter software (HDR is disabled though) which does a fast disable/enable toggle fast enough to cause this issue.
Maybe it is worth noting that I use a nvidia card (5080) on the connected device, I know that nvidia and windows can sometimes do very strange things or even sent a reset driver command if it takes too long to respond, theres often a timer associated, I'm aware their software but also windows sometimes do these strange work arounds 
I’m seeing the corrupted video with the native video drivers on the Intel chip of my NUC 8. The KVM window is running on Firefox on a Mac Studio. The HDMI detection is much better with 1.72…my understanding is 1.8 might be released this week. I’ll be sure to update when it is released.
This is what I see:
Gonna sent logs to @minmie
This issue is quite common in rv1126bp chip(all product except rm1 base on this chip), especially on non-Chromium-based browsers like Firefox. I haven't tested it on mobile devices. Essentially, it's caused by the decoder's inability to handle certain errors. Generally, refreshing the page will resolve it. We will contact with Rockchip to see if they can solve this problem.