All of a sudden the computer loses the correct files for the monitor and it falls back on the Generic non Plug and Play monitor driver that only maxes out at 1024 x 768 resolution. I proceeded to uninstalled this driver and attempted for a restart to see whether if this was just a hiccup; I believed Windows should be able to identify the correct driver for the monitor after the cycle. The method fails miserably and it looks as though there is something wrong with the monitor.
Or if this cannot help, you can try to right-click the generic non-pnp monitor > uninstall device to uninstall it at first, and then go to the monitor official site to download its driver and install it manually.
If this cannot solve your problem, try to install within a compatible way. Right-click the generic non-pnp monitor > update driver > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > check show compatible hardware and install it. Here is the detail: -generic-pnp-monitor-issue-on-windows-10/
Most of the credit for this answer goes to the user Facebook, who rightly guessed that it was a driver issue. In short, this issue is solved by replacing the generic driver for the monitor with the right driver for your monitor.
You may have trouble with this, as monitor drivers can be incredibly obscure, and the manufacturer may not have provided any at all. For my AOC 2795E, the driver was found on the no-frills page here. If you do manage to find a driver, download it and remember where you downloaded it to.
The colour profile is what tells your monitor how it should render colour. If the colour profile that was included with the driver you just installed wasn't written as it should have been, it will behave defectively, causing Windows Photo Viewer to render colours incorrectly. This is easily solved by making use of one of the colour profiles that Windows ships with.
My, HP 250 G7 Notebook PC, device manager lists Display as: Generic Non-PnP monitor. How to install correct Monitor driver? In the compatible driver window shows only Generic Non-PnP monitor & Generic PnP monitor NO HP monitor is listed, How to find compatible HP monitor?
In Windows, PnP stands for Plug and Play. When you plug a PnP monitor in Windows, it starts working without having to install a specific driver. And, when the device manager shows Generic PnP Monitor, that means: Windows has installed a basic monitor driver, in the absence of the required monitor driver. A generic monitor driver provides basic functionality to the monitor.
But, with the generic monitor driver, you cannot customize display settings. You cannot set the best resolution and highest possible refresh rate. For that, you have to install the required monitor driver.
Note: If you have already tried to install a monitor driver using the device manager. Then, check solution 4. I have mentioned in it how you can generate a monitor driver file and install it.
You must be thinking if I uninstall the generic driver, will I lose the monitor display? The answer is no, your monitor display will not stop working. Windows will revert to either a standard driver or the same default driver that was used during the original installation of the OS. In other words, Windows will recognize it as new connected hardware and it will install the drivers automatically. Do follow the following steps:
Step 2. If the monitor driver file is in .exe format. Then, you can directly run it and install it on your PC or laptop. But, if it is an INF file, then you can use the device manager to update it.
INF File or as known as setup information file is a plain-text file used by Microsoft Windows. It is most commonly used for installing device drivers for hardware components. So, we are going to create a monitor INF file. And, after that, we will install it from the device manager. And, that will fix the Generic PnP monitor problem.
Hi ! Method 4 worked for me, thanks a lot ! I was looking for a solutions for many weeks. Just a question : is it possible to make driver signatures checked after we installed the self-made monitor driver ? I get back to the advanced settings but it only gave me the possibity to accept unckecked signature (as it did previously). Thanks again !
Also, do check optional Windows updates, you might find your monitor driver. If you find it, then uninstall Monitor Driver and enable driver signature enforcement. After that, install it from Windows Optional Updates.
The generic PnP monitoring is usually pre-installed on the computer that is first used. Sometimes, however, the monitor might stop working after an upgrade or after installing Windows updates.
Press F5 Click the right button to activate your Non-PnP generic monitor Choose your driver Update Driver Software >> Browse my computer for driver software >> Let me choose from a list of device drivers for my computer.
While some people might think there is only one generic PnP Monitor with no exclamation (someone reported seeing a PnP Monitor with a yellow triangle, or a generic Non-PnP Monitor with a yellow exclamation), others may not be aware that the monitor has a yellow exclamation. You can uninstall Generic Monitor if it is a driver error.
System file checker allows users to scan and restore corrupted files from the system files and conflict driver files. This tool can be used to detect corrupt files that may have been created by the monitor driver files.
As with most pieces of hardware, monitors (especially newer-generation versions) come with drivers. These enable you to make use of various specific functions. In simple terms, monitors perform better, or at least as intended, when your OS uses the appropriate drivers.
Hit:1 eoan InReleaseHit:2 -os.org/proprietary eoan InReleaseHit:3 eoan-updates InReleaseHit:4 eoan-security InReleaseHit:5 eoan InReleaseHit:6 eoan-backports InReleaseReading package lists... DoneReading package lists... DoneBuilding dependency treeReading state information... Donegrep is already the newest version (3.3-1build1).pciutils is already the newest version (1:3.6.2-2).pciutils set to manually installed.usbutils is already the newest version (1:012-1).usbutils set to manually installed.The following additional packages will be installed: libhd21 libx86emu2The following NEW packages will be installed: hwinfo libhd21 libx86emu2The following packages will be upgraded: rfkill1 upgraded, 3 newly installed, 0 to remove and 451 not upgraded.Need to get 815 kB of archives.After this operation, 3,498 kB of additional disk space will be used.Do you want to continue? [Y/n] yGet:1 eoan/universe amd64 libx86emu2 amd64 2.4-1 [45.5 kB]Get:2 eoan/universe amd64 libhd21 amd64 21.67-1 [728 kB]Get:3 eoan/universe amd64 hwinfo amd64 21.67-1 [18.1 kB]Get:4 eoan-updates/main amd64 rfkill amd64 2.34-0.1ubuntu2.4 [22.9 kB]Fetched 815 kB in 1s (1,501 kB/s)debconf: unable to initialize frontend: Dialogdebconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.)debconf: falling back to frontend: ReadlineSelecting previously unselected package libx86emu2:amd64.(Reading database ... 300987 files and directories currently installed.)Preparing to unpack .../libx86emu2_2.4-1_amd64.deb ...Unpacking libx86emu2:amd64 (2.4-1) ...Selecting previously unselected package libhd21:amd64.Preparing to unpack .../libhd21_21.67-1_amd64.deb ...Unpacking libhd21:amd64 (21.67-1) ...Selecting previously unselected package hwinfo.Preparing to unpack .../hwinfo_21.67-1_amd64.deb ...Unpacking hwinfo (21.67-1) ...Preparing to unpack .../rfkill_2.34-0.1ubuntu2.4_amd64.deb ...Unpacking rfkill (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2) ...Setting up libx86emu2:amd64 (2.4-1) ...Setting up libhd21:amd64 (21.67-1) ...Setting up rfkill (2.34-0.1ubuntu2.4) ...Setting up hwinfo (21.67-1) ...Processing triggers for man-db (2.8.7-3) ...Processing triggers for libc-bin (2.30-0ubuntu2) ... *-network description: Wireless interface product: Wireless 8265 / 8275 vendor: Intel Corporation physical id: 0 bus info: pci@0000:03:00.0 logical name: wlp3s0 version: 78 serial: 38:de:ad:64:28:a0 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-18-generic firmware=36.77d01142.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:131 memory:a5400000-a5401fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:04:00.0 logical name: enp4s0 version: 0c serial: 80:fa:5b:5b:38:ee size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.2.3 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:18 ioport:3000(size=256) memory:a5300000-a5300fff memory:a2100000-a2103fff *-network:0 description: Ethernet interface physical id: 1 logical name: virbr0 serial: 52:54:00:71:53:3a capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.122.1 link=no multicast=yes *-network:1 DISABLED description: Ethernet interface physical id: 2 logical name: virbr0-nic serial: 52:54:00:71:53:3a size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=no multicast=yes port=twisted pair speed=10Mbit/s *-network:2 description: Ethernet interface physical id: 3 logical name: br-bfd1ce625514 serial: 02:42:68:75:46:5d capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.18.0.1 link=no multicast=yes *-network:3 description: Ethernet interface physical id: 4 logical name: br0 serial: 4e:5c:28:53:3c:e9 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=no multicast=yes *-network:4 description: Ethernet interface physical id: 5 logical name: docker0 serial: 02:42:ec:17:4f:aa capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes *-network:5 description: Ethernet interface physical id: 6 logical name: br-b589ec8cb755 serial: 02:42:b3:12:bd:12 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.20.0.1 link=no multicast=yes *-network:6 description: Ethernet interface physical id: 7 logical name: br-8bd7e9edeb9c serial: 02:42:75:e7:ed:82 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.19.0.1 link=no multicast=yes *-network:7 description: Ethernet interface physical id: 8 logical name: br-5837b70510a4 serial: 02:42:15:1b:20:46 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.21.0.1 link=no multicast=yes0: hci0: Bluetooth Soft blocked: no Hard blocked: no1: phy0: Wireless LAN Soft blocked: no Hard blocked: novirbr0 Interface doesn't support scanning. 2b1af7f3a8