When I disconnect HDMI, then Intel driver create virtual display. Is it on any purposed?

[idata]

I use portable computer, and there is intel graphic driver.

I check Device Manager then I got following Information.

* Intel(R) HD Graphics

* matching Hardware Ids is PCI\VEN_8086&DEV_22B0&SUBSYS_0E6A105B&REV_20

I installed few different version of drivers, Then

* `20.19.15.4331` version does not create virtual display when I pull off HDMI.

* `20.19.15.4380' and `20.19.15.4444` version does create virtual display when I pull off HDMI.

So, the question is simple.

Intel driver after 20.19.15.4380, create virtual display. Is it on any purposed? or bug?

Anyone know about this?

[KWong21]

I am getting the exact same results like you did...

But I didn't install any virtual display software.

[idata]

Hello kenofstephen,

Thanks for reporting back about this matter.Would you please provide me with the SSU report from your system? This is to get a clear overview of the scenrio you are facing.Please create the report while having the drivers with the issue installed.How to get this report?-Access: https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-Download the utility-Scan your system with the utility-Export the report (hit next and then save) and attach it to your answer with the advanced editor option (reply button and then check upper right corner)I will look into this to test it with a system that has a built-in display as well.Regards,Esteban C

[JHogg]

Same issue here using a WindowsBox portable PC. That is a screenless device with battery. I am using with Targus docks using displaylink, but Intel HD is often creating a ghost display meaning when docked there is a screen I cannot access.

Using Teamviewer to connect remotely I see two displays. One is the HD Graphics, which is serviced by micro HDMI port that is disconnected. The other is my docking station the Targus USB3 DVI1K-2K Compact Dock (using DisplayLink). I'm assuming that when PC boots it needs a monitor and so Intel HD creates the ghost display?

Unsure if this is the graphics driver or a bug in Windows 10 (1607 build 14393.953) automatic monitor detection feature, but as a work around in my case I have just manually connected system to each of the docks it may use and used teamviewer and set the display settings so that Intel HD display is disabled. Recently updated version of Windows as Teamviewer was struggling and flicking display adaptors once update of displaylink was installed. All stable now in my case.

[idata]

Hi James@IOH,

May I have your system information with the tool in the link?

https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility

Please attach the file to your answer.

Thanks,Esteban C

[KWong21]

I copied this problem on several devices:

1.) Intel Compute Stick (Cherrytrail Z8300)

2.) Asrock Beebox (Braswell N3150)

3.) MINIX NEO Z83-4 (Cherrytrail Z8300)

All running with the latest Windows 10 Anniversary edition and updated to the latest graphics driver.

[idata]

Hello,

Have you guys tried to pin Microsoft support about this issue?Regards,Esteban C

[idata]

Hello All,

seungrye

Where you guys able to check further troubleshooting with Microsoft support?

Please let me know.

Regards,

Esteban C

[idata]

Hello seungrye,

I am here to check if you were able to get this solved, please let me know.

Regards,

Esteban C

[idata]

I don't use the issued application recently.

So, you can mark this thread to solved as your wish.

Thanks your help : )

[idata]

Hello seungrye,

Thank you for letting me know about this, peer!

I will, but remember that any time you require support, you can certainly reach us here or any other service platform.

Regards,

Esteban C

[KWong21]

May I know how? Can't Intel (big guy) speaks to another big guy (Microsoft)?

[KWong21]

I found a patch on the Internet that disable the virtual display function of the Intel driver which temporarily fixed the problem,

but it shouldn't be fixed this way because the virtual display capability is lost after applying the patch.

Here is the patch:

; ForceVirtualDisplay

; 1-Enable Virtual Display 0-Disable Virtual Display

cmd /c reg ADD "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000" /v ForceVirtualDisplay /t REG_DWORD /d 0 /f

cmd /c reg ADD "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001" /v ForceVirtualDisplay /t REG_DWORD /d 0 /f

cmd /c reg ADD "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0002" /v ForceVirtualDisplay /t REG_DWORD /d 0 /f

[idata]

Hello kenofstephen,

Thank you for the feedback and workaround provided.

I will send this to be reviewed by the team in charge.

Regards,

Esteban C

[KWong21]

Hi Esteban C,

I read how you tested in the first page,

I got the same result as the thread starter.

You have to test with a device that doesn't have a built-in display.

And I think it's better for you to look at how many monitors in the device manager page,

it's the easiest way to visualize the problem.

I posted the method to create the generic non-pnp monitor every time.

The patch above simply disabled the virtual display feature so that it can't be created,

it's a prevention, not cure.

[idata]

Hello kenofstephen,

I was wondering if you were able to check my last answer.

seungrye, would you please let me know if you require any further support?

Regards,

Esteban C

[idata]

Hello seungrye,

Just wanted to check if you still need support for this matter.

Regards,

Esteban C