- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago (Last edited 3 weeks ago ) in
Monitors and MemorySo I need some help and Samsung support has not been helpful. My post pertains to KVM specifically when using flex move screen. When I have my USB input selection set to "Switch Automatically" It works as intended switching inputs and multimode. However, when I use flex move screen and resize my screen down, it fails to switch my input to the computer I am using. I have to go into the settings and change "Automatically switch" to the desired input I am using.
I tried calling Samsung support and the people had absolutely zero idea of the feature I was referring to. The person told me that she suggest I plug my keyboard and mouse directly into the computer and bypass the KVM. I tried their text option and I kept getting a new person every 5 min and repeating my problem. I tried filling out a support request online and I just get a "Something went wrong" error when I try to submit it. So hoping I can get an answer here.
If the auto switch KVM was never intended to work with the flex move screen I can live with it. But if it is supposed to and isn't working, with the amount of money I paid I want full functionality. I tried a factory reset, updated all drivers, installed easy setting box, used HDMI vs DisplayPort, USB-B vs USB-C for upstream and downstream connections and still nothing.
I'm hoping someone on here actually knows what the monitor is and isn't supposed to do and can give me some insight.
Solved! Go to Solution.
1 Solution
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago in
Monitors and MemoryAnybody interested, got a software update today which resolved the issue. It was indeed a software problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago in
Monitors and MemoryAnybody interested, got a software update today which resolved the issue. It was indeed a software problem.