Restoring MIcrosoft Basic Display Adapter

[Mr. Man-wai Chang]

I deleted the Microsoft Basic Display Adapter and its drivers by mistake
while doing a hardware upgrade.

Is there an easy way to restore them?

Reinstalling the OS would surely fix the problem... but would like to do
that later when all else fail.

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA):
http://www.swd.gov.hk/tc/index/site_pubsvc/page_socsecu/sub_addressesa

[Paul]

Mr. Man-wai Chang wrote:
>
> I deleted the Microsoft Basic Display Adapter and its drivers by mistake
> while doing a hardware upgrade.
>
> Is there an easy way to restore them?
>
> Reinstalling the OS would surely fix the problem... but would like to do
> that later when all else fail.
>

Do you have System Protection enabled on C: ?
Is there a System Restore point from before the mistake happened ?

A second possibility, is open Device Manager and see if there
is an option to "roll back" the driver. Driver roll back is
one level deep. You can put back the previous driver, before
you made a change.

That's all that comes to mind, short of using a backup
you made of the OS C: partition at some point. For example,
I made one backup of C: already, before doing some experiments,
so I occasionally have something sitting there which can be used.

*******

When you delete files in System32, they also exist in WinSXS. The
OS hard-links files from WinSXS into System32. When you delete
a file from System32, it isn't really gone. All you've done is
erase the 1KB $MFT entry, not the actual clusters.

The OS has two levels of repair. This one should repair
System32, using resources from the driver cache or from WinSXS.
This puts info into a .log file as well, as to what was repaired.
You can run this from an Administrator Command Prompt (available in
the right-click of Start Menu, unless you're using the Insider Edition).

sfc /scannow

The other kind of repair, is to WinSXS. It's done using
DISM and a network connection to the Microsoft server.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
corruption marker is already present in the registry.
It is just a quick way to see if corruption currently
exists, and to inform you if there is corruption. It
does not fix anything or create a log.
This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
It only checks for component store corruption and records
that corruption to the log file.

This is useful for only logging what, if any, corruption
exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
records the corruption to the log file, and FIXES the
image corruption using Windows Update. This should take
around 10-15 minutes up to a few hours to finish depending
on the level of corruption.

Paul

[Mr. Man-wai Chang]

On 22/02/2017 4:47 PM, Paul wrote:
> Do you have System Protection enabled on C: ?
> Is there a System Restore point from before the mistake happened ?

I turned them all off. :)

> A second possibility, is open Device Manager and see if there
> is an option to "roll back" the driver. Driver roll back is
> one level deep. You can put back the previous driver, before
> you made a change.

Problem is the Display section has gone.

> That's all that comes to mind, short of using a backup
> you made of the OS C: partition at some point. For example,
> I made one backup of C: already, before doing some experiments,
> so I occasionally have something sitting there which can be used.

Guess I should just reinstall the whole OS.

[Paul]

Mr. Man-wai Chang wrote:
> On 22/02/2017 4:47 PM, Paul wrote:
>> Do you have System Protection enabled on C: ?
>> Is there a System Restore point from before the mistake happened ?
>
> I turned them all off. :)
>> A second possibility, is open Device Manager and see if there
>> is an option to "roll back" the driver. Driver roll back is
>> one level deep. You can put back the previous driver, before
>> you made a change.
>
> Problem is the Display section has gone.
>
>> That's all that comes to mind, short of using a backup
>> you made of the OS C: partition at some point. For example,
>> I made one backup of C: already, before doing some experiments,
>> so I occasionally have something sitting there which can be used.
>
> Guess I should just reinstall the whole OS.
>

In Device Manager, did you try Action : Scan for hardware changes ?

You really shouldn't be able to lose the display.

*******

Have you done a reboot yet ?

The hardware should be rediscovered on a reboot,
in the same way as the "scan for hardware changes" works.

Please try to provide details about how you got
to the current situation. Did you select "uninstall"
while the Display adapter was open in Device Manager ?
If so, the hardware will be rediscovered on the next
scan for changes.

Paul

[Mr. Man-wai Chang]

On 22/02/2017 5:51 PM, Paul wrote:
> In Device Manager, did you try Action : Scan for hardware changes ?
> You really shouldn't be able to lose the display.

> ...

> Have you done a reboot yet ?

Did re-scan and reboot multiple times. Display -> Basic Adapter still
didn't show up again in Device Manager. However, the display is still
working.

Motherboard is J3455M. OS is Win Server 2012 R2.

[Mr. Man-wai Chang]

I went ahead and reinstalled the OS. The Display section was again gone
after a few reboots. NO display adapter in the end. ;)

The Asrock J3455M got Intel HD 500 as display.

[Paul]

Mr. Man-wai Chang wrote:
>
> I went ahead and reinstalled the OS. The Display section was again gone
> after a few reboots. NO display adapter in the end. ;)
>
> The Asrock J3455M got Intel HD 500 as display.
>

I can find examples of other Win10 users with the same problem.
It seems the Microsoft Basic Display Adapter is present by behavior
(resolution stuck), but there is no entry in Device Manager.

A trip to Windows Update is supposed to fix it. Unless you've
already disabled Windows Update hardware driver updates.

I've done installs before (in a VM), where a notification box
appears saying the OS is "searching for a graphics driver",
or words to that effect. Maybe your install is in the same
state, and is looking for the real driver.

*******

Downloadcenter has a driver for your graphics.
The Asrock download page has a driver file too, from the same series.

2/3/2017 ~240MB Win7/8.1/10

https://downloadcenter.intel.com/download/26563/Graphics-Intel-Graphics-Driver-for-Windows-15-45-

The graphics\igdlh64.inf file has some labels:

iSKLULTGT1 = "Intel(R) HD Graphics 510"

However, your processor is Goldmont, and I don't see a
specific entry for that. It really shouldn't matter
about the core, if the GPU block is just copied from
another chip. Your graphics are supposed to be GT1
with 12 execution units.

*******

A command like this is supposed to display the details (in an
Administrator command prompt). I don't have any Intel graphics
here to test with, to see what it would show.

wmic PATH Win32_VideoController GET Description,PNPDeviceID /Format:List

Paul

[Mr. Man-wai Chang]

Thank you first!

[Mr. Man-wai Chang]

For curiosity, I tried installed Windows 10 to this Asrock J3455M
without a product key. The Basic Display Adapter didn't disappear.

So it seemed the problem was limited to Win Server 2012 R2.

[Mr. Man-wai Chang]

Because the Micro$oft Basic Display Adapter disappeared during Win
Server 2012 R2 installation, I could NOT install Intel's HD 500 driver.

[Mr. Man-wai Chang]

On 24/02/2017 8:40 PM, Mr. Man-wai Chang wrote:
>
> Because the Micro$oft Basic Display Adapter disappeared during Win
> Server 2012 R2 installation, I could NOT install Intel's HD 500 driver.
>

The error message was: ... does not meet minimum requirement....

[Paul]

Mr. Man-wai Chang wrote:
> On 24/02/2017 8:40 PM, Mr. Man-wai Chang wrote:
>>
>> Because the Micro$oft Basic Display Adapter disappeared during Win
>> Server 2012 R2 installation, I could NOT install Intel's HD 500 driver.
>>
>
> The error message was: ... does not meet minimum requirement....
>

It should be the same driver as Windows 8.1.

For example, Dell has a driver here, which they list for WS2012R2,
and yet it has desktop Windows sections. "6.3" means Windows 8.1

http://www.dell.com/support/home/ca/en/cabsdt1/Drivers/DriversDetails?driverid=7NM88

Intel HD Graphics Driver For Windows Server 2012 R2, A00

A look in the INF file on that one shows what looks like older hardware:

;=====================================================================
; Windows 8.1 Install
;=====================================================================
[IntelGfx.NTamd64.6.3]
; IVB Server
%iIVBGD0SRV% = iIVBD_w81, PCI\VEN_8086&DEV_016A
%iIVBGD0SRVGT1% = iIVBD_w81, PCI\VEN_8086&DEV_015A
; HSW Classic
%iHSWGT1D% = iHSWD_w81, PCI\VEN_8086&DEV_0402
%iHSWGT2D% = iHSWD_w81, PCI\VEN_8086&DEV_0412
%iHSWGT15D% = iHSWD_w81, PCI\VEN_8086&DEV_041E
; HSW Server
%iHSWSVGT2% = iHSWD_w81, PCI\VEN_8086&DEV_041A
%iHSWSVGT1% = iHSWD_w81, PCI\VEN_8086&DEV_040A

The INF file in the Intel DownloadCenter looked like this.

;=====================================================================
; Windows 8.1 Install - DT Only
;=====================================================================
[IntelGfx.NTamd64.6.3]
; SKL HW
%iSKLULTGT1% = iSKLD_w81, PCI\VEN_8086&DEV_1906
%iSKLULTGT2% = iSKLD_w81, PCI\VEN_8086&DEV_1916
%iSKLULXGT2% = iSKLD_w81, PCI\VEN_8086&DEV_191E
%iSKLDTGT2% = iSKLD_w81, PCI\VEN_8086&DEV_1912
%iSKLULTGT2f% = iSKLD_w81, PCI\VEN_8086&DEV_1921
%iSKLULTGT3e% = iSKLD_w81, PCI\VEN_8086&DEV_1926
%iSKLULTGT3% = iSKLD_w81, PCI\VEN_8086&DEV_1923
%iSKLULTGT328W% = iSKLD_w81, PCI\VEN_8086&DEV_1927
%iSKLDTGT1% = iSKLD_w81, PCI\VEN_8086&DEV_1902
%iSKLHaloGT1% = iSKLD_w81, PCI\VEN_8086&DEV_190B
%iSKLHaloGT4% = iSKLD_w81, PCI\VEN_8086&DEV_193B
%iSKLHaloGT3fe% = iSKLD_w81, PCI\VEN_8086&DEV_192B
%iSKLHaloGT2% = iSKLD_w81, PCI\VEN_8086&DEV_191B
%iSKLSRVGT3e% = iSKLD_w81, PCI\VEN_8086&DEV_192D
%iSKLSRVGT4% = iSKLD_w81, PCI\VEN_8086&DEV_193A
%iSKLWSGT2% = iSKLD_w81, PCI\VEN_8086&DEV_191D
%iSKLWSGT4% = iSKLD_w81, PCI\VEN_8086&DEV_193D

Maybe the GoldMont part of the equation really matters ?
What is the VEN and DEV of the graphics ? (If the Basic Display
Adapter will not show up, you could try Everest or you
could boot up a Linux DVD and lspci/lshw/inxi from there.)

You may need to start Googling the VEN and DEV when
searching for a driver, to narrow it down.

*******

There are other possibilities. For a Basic Display Adapter,
normally the BIOS would have a VESA declaration for the
built-in processor graphics. But on a UEFI BIOS, it's also
possible for the maker to include a GOP declaration.

From a Linux thread

"Ahh, yes, this is because gop doesn't set a vesa mode and let you play
with the flat frame buffer. You actually make gop calls to perform
the IO for you. Grub can leave the display in that state when passing
off to the kernel, but the kernel has to have its own KMS video driver
to take over; it can't just start poking at a frame buffer like it can
with VESA."

Now, I don't know if that's your issue or not, or at what point
GOP became available. A while back, you could flash a video card
from a VESA config ROM, to a GOP config ROM, but it wasn't clear
at the time, what purpose this served.

https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#GOP

"In addition, the Graphics Output Protocol (GOP) provides limited
runtime services support.

The operating system is permitted to directly write to the framebuffer
provided by GOP during runtime mode. However, the ability to change
video modes is lost after transitioning to runtime services mode until
the OS graphics driver is loaded."

Paul

[Mr. Man-wai Chang]

On 25/02/2017 12:35 AM, Paul wrote:
> Mr. Man-wai Chang wrote:
>> On 24/02/2017 8:40 PM, Mr. Man-wai Chang wrote:
>>
>> The error message was: ... does not meet minimum requirement....
>>
>
> It should be the same driver as Windows 8.1.
>
> For example, Dell has a driver here, which they list for WS2012R2,
> and yet it has desktop Windows sections. "6.3" means Windows 8.1

>....

> The operating system is permitted to directly write to the framebuffer
> provided by GOP during runtime mode. However, the ability to change
> video modes is lost after transitioning to runtime services mode until
> the OS graphics driver is loaded."

I will archive your replies and try again later. Maybe by then Intel HD
500 would have proper if not official drivers for Win Server 2012 R2.

I tried the .INF hack, didn't work. I really suspected the disappearance
of the "Microsoft Basic Display Adapter" in Device Manager affected the
installation process.

I had another idea:

1. Insert a PCIe display card to Asrock J3345
2. Install the driver of the PCIe display card
3. Install the driver of Intel HD 500 driver
4. Remove the PCIe display card
5. Reboot and see whether Intel HD 500 would show up in Device Manager

Not in the mood to attempt this procedure now that I had Win 10
installed and working ... :)

[Mr. Man-wai Chang]

On 25/02/2017 12:35 AM, Paul wrote:
>

> There are other possibilities. For a Basic Display Adapter,
> normally the BIOS would have a VESA declaration for the
> built-in processor graphics. But on a UEFI BIOS, it's also
> possible for the maker to include a GOP declaration.

I have enabled Compatibility Support Module in BIOS and booted using MBR
partitions. SO it should be irrelevant!

BUT... maybe there is a bug in this process. VESA should be supported at
all costs, using lower resolutions, I supposed. :)