Intel Arc and integrated graphics drivers on Windows

Verified 2026-10-293 min read

DCH packaging, Arc Control versus the legacy control panel, hybrid graphics with a discrete GPU, and the update paths that actually work.

Tested onPro (26H2) · Build 26300.9457 · x64

Build: 26300.9457
Edition: Pro (26H2)
Architecture: x64
Support: Documentation (E1)
Evidence: E1Official documentation
Verified: 2026-10-29
Page type: Vendor

The short answer

Intel graphics on modern Windows means DCH driver packages: the driver is split into a base driver plus optional components (control panel, audio, display colour), delivered through Windows Update or Intel’s installer.

Two practical consequences:

The control panel is a separate Store-style app on newer packages — installing only the base driver leaves you without it.
Integrated and discrete GPUs coexist: the iGPU drives the desktop and video decode, the dGPU renders games. Both need working drivers, and the wrong one can cause stutter or a black screen.

Which package

Device	Package
Recent Core iGPU (UHD/Iris Xe/Arc integrated)	Intel’s current graphics driver
Arc discrete	Same installer family, different device IDs
Older iGPU (pre-DCH era)	The last legacy package Intel lists for that product
Laptop with OEM support	OEM build first

Intel’s download pages are organised by product; use the exact device ID if you are unsure:

Get-PnpDevice -Class Display | Select-Object FriendlyName,Status,InstanceId
Get-CimInstance Win32_VideoController | Select-Object Name,DriverVersion,DriverDate,VideoProcessor

InstanceId starts with PCI\VEN_8086 for Intel display devices. Matching by name alone is unreliable across generations.

Hybrid graphics: what actually happens

On a laptop with Intel iGPU + NVIDIA/AMD dGPU:

the iGPU usually owns the panel (or the MUX decides at boot);
the dGPU renders on request and copies frames over;
the display driver stack is therefore two drivers plus a switching mechanism.

Failure modes follow from that:

Symptom	Likely cause
Game runs on the iGPU	wrong GPU preference, or the app is not recognised
Stutter every few seconds	frame copy path / MUX state, or MPO interaction
External monitor works, internal does not	panel is wired to the other GPU
Black screen after driver update	one of the two drivers updated, the other did not

Set the preference per app in Settings → System → Display → Graphics, and check whether the laptop has a MUX switch — with the MUX in discrete mode, the iGPU no longer owns the panel and behaviour changes completely.

Updating without breaking things

Note the current version (Get-CimInstance Win32_VideoController).
Disconnect the network so Windows Update cannot interleave.
Install the new package; reboot.
Confirm the version changed and the control panel opens.
Reconnect, then re-check after the next Windows Update — if the version reverts, Windows Update is overriding you.

# installed display driver packages
pnputil /enum-drivers | Select-String -Context 0,6 'Display'
# rollback target, if any
Get-PnpDevice -Class Display | Get-PnpDeviceProperty -KeyName 'DEVPKEY_Device_DriverVersion'

Rollback

Device Manager → Display adapters → Properties → Driver → Roll Back Driver. Greyed out means Windows has no previous package; then reinstall the older installer you kept.

For a black screen after install: boot into safe mode (Shift + Restart), roll back there, reboot normally.

Integrated graphics are not “just for display”

The iGPU also handles:

video decode (battery life on laptops),
some browser GPU work,
display output for every monitor wired to the board.

Disabling it in Device Manager to “force” the dGPU is a common tip that breaks video decode and can black-screen laptops whose panel is wired to the iGPU.

Lab boundary

E1. Packaging and hybrid-graphics behaviour are documented by Intel and Microsoft. Intel’s download pages block automated requests, so this page cites Microsoft documentation and describes the vendor page rather than quoting version numbers. No Intel GPU was tested here.