#E2016hv shows up as generic pnp monitor install

So the monitor disables overscan only when getting an RGB signal. Why? Because even though Windows could discover that the monitors supported both RGB and YPbPr, the monitor sees a YPbPr signal as a TV signal and the RGB signal as a computer signal. When I connected them to my Windows machine, they did funny things, however: the monitor would kick in to overscan mode, as if it was a TV. For example, I had a pair of HP monitors with HDMI ports on them. inf file, but there are times that the DCC information doesn't give Windows enough information to properly handle the monitor. Most of the time, Windows and monitors can talk to each other without the need of an.

And even then, color profiles are next-to-useless most of the time. But only if you are doing color-corrected graphics work.

#E2016hv shows up as generic pnp monitor install

Now, if you want to install the manufacturer's *color profile*, that actually does stuff. You don't need to install monitor 'drivers', is what I'm saying. All of which Windows is perfectly capable of discovering for itself.

They're just '.inf' files with a list of available resolutions and refresh rates. Monitor 'drivers' don't actually do anything. I had a misadventure this weekend which borked my new OS install (you can read about it here if interested) and I'm loath to chance plugging the USB 3 cable into the motherboard's USB 3.1 port again (it's the only one left open) if there'd be no point in trying due to the lack of a manufacturer's driver. I've had the monitor for years, but I just upgraded to Windows 10 and was rather disgusted to find that there was no manufacturer's Windows 10 driver for it (unless that's generally not a thing in Win 10 anymore-for all I know that may be the case).