Share via


Windows 10 with KVM switch locks up after Sleep Mode

Question

Saturday, July 16, 2016 2:35 PM | 1 vote

I recently upgraded my Windows 7 Pro system to Windows 10 and now experience a problem.  The system has a KVM switch that showed no problems with Windows 7.  Windows 10 saw my monitor, keyboard and mouse on installation and everything works fine. However, frequently when I wake up the computer after it is in sleep mode, the monitor does not come on and the keyboard is locked.  This seems to happen if I accidentally double click the keyboard or move the mouse.  The only solution is to turn of computer off and then back on.  Windows starts where I left off before entering sleep mode.

All replies (3)

Tuesday, July 19, 2016 6:07 AM âś…Answered

Hi Mimas123,

What is the exact machine model?

Since the issue occurred after we upgraded to Windows 10, I suspect there may be a compatibility issue. Please ensure the device manufacturer website has released Windows 10 compatible drivers for your machine model and KVM switch has windows 10 compatible drivers, too.

If you have got Windows 10 drivers, we could try to run "powercfg -devicequery wake_armed" to lists devices that are currently configured to wake the computer from any sleep state.
Use "powercfg -deviceenablewake "device name"" to configure the device to wake up the machine.

Of course, we could try to run the built-in "Power" troubleshoot to have a diagnostic.

Control Panel\All Control Panel Items\Troubleshooting\All Categories\Power

Best regards

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected]


Saturday, July 16, 2016 3:02 PM

Is it a self powered or unpowered switch?

Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)


Saturday, February 15, 2020 9:10 PM

I am having the same problem. When my desktop goes to sleep, tapping the power button returns from sleep however the monitor does not get a signal from the desktop.

  • My KVM is unpowered
  • Desktop is connected as device 1 (Ctrl+Alt+1)
  • My laptop has a dock that is always connected to the KVM as device 2 (Ctrl+Alt+2). Toggling back and forth between desktop (black screen with no signal) and laptop works just fine.
  • Machine model is Gateway SX2800

Here's the powercfg listing:

Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\Paul>powercfg -devicequery wake_armed
HID-compliant mouse
HID Keyboard Device
LSI PCI-SV92EX Soft Modem
Intel(R) 82567V-2 Gigabit Network Connection
HID-compliant mouse (003)

Here's the System Information:

OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name KERNGATEWAYDESK
System Manufacturer Gateway
System Model SX2800
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz, 2336 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date AMI P01-A3, 5/26/2009
SMBIOS Version 2.6
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gateway
BaseBoard Product WG43M
BaseBoard Version
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.628"
User Name KernGatewayDesk\Paul
Time Zone Central Standard Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.97 GB
Available Physical Memory 463 MB
Total Virtual Memory 9.02 GB
Available Virtual Memory 2.26 GB
Page File Space 5.05 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions No
Hyper-V - Second Level Address Translation Extensions No
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes