Windows 7: WES7, Intel 945GSE, Ghost Monitor / LVDS issue

Hi, I am a developer for Windows Embedded Standard 7 and I have been tasked with developing a software fix for a somewhat unique issue. My company's thin clients have been assembled with a Mobile Intel(R) 945GSE chipset, which, as I understand, is a graphics chipset for laptops.
The problem is that the LVDS signal for driving laptop monitors is being detected by Windows. Windows, in turn, assumes that this is a valid display port, which is causing issues with our customers. When the screen resolution dialog comes up, it shows that there are 2 monitors attached to the device: (1) Mobile PC Display, and (2) the actual monitor that is attached.
It is my understanding that this is really a BIOS issue, but for one very complicated reason or another, we cannot modify/update the BIOS. Does anyone know how to hide/disable/remove this "ghost monitor" with a software fix? I have already tried the following:

1. From the Screen Resolution dialog, selecting the option to "Show only on desktop 2." Unfortunately, this has been deemed an unacceptable solution for my company, as the ghost monitor is still present.

2. Adding the Mobility Center package with DISM to turn off the internal display. Unfortunately, whereas the package can be added, the mobility center will not load.



3. Creating a group policy to prevent the installation of any device with the GUID corresponding to the "Default Monitor" that is "detected" and then uninstalling it. This will prevent the monitor from being automatically reinstalled, but Windows still thinks that something is, or should be, there. The same results are achieved by simply disabling this "monitor."

4. Installing an IEGD v10.4 driver that I configured for WES2009, which implicitly disables LVDS detection by not adding it to the port order list. I found a post somewhere that said that it should successfully install when run as an administrator and in compatibility mode for XP-SP3, but it does not (in compatibility mode for ANY version of Windows).

5. Frantically deleting every possible registry key/value that MIGHT fix our issue in desperate hopes to achieve something. No such luck.

Does anyone have any ideas?? I'm kind of desperate here. Thanks so much, in advance, to anyone who can help me out with this.