I've just setup a PC with a Pentium G4560. However, neither the latest driver (15.45.10.4542) or the newer beta (15.45.10.4552) work. Both say my PC does not meet the minimum requirements. The only drivers that do work are an older version that is downloaded by Windows. The problem with that driver, is that it doesn't seem to support any of the new features for 4k video playback. On that driver, YouTube's 4k VP9 hits 100% cpu usage and drops most frames and HVEC, h.265 videos just show grey and green blocks.

I spoke with Intel support and after trying everything they asked, all he could do was say that he would pass this info onto the driver team for them to address in the next driver. I asked about why the G4560 and its iGPU HD610 is not listed as supported in any of the driver or support documents and he said was it was probably an error.

Is this just an issue with my PC or are there more of you out there that are having the same issue?

These are the CPUs, which OCUK sell, that have HD610:

Celeron G3930
Celeron G3950
Pentium G4560

Many thanks.

Did you try forcing gpu acceleration in chrome.?

Hmmm I downloaded both drivers from Intel site and extracted it to have a look at infs.

Latest driver 15.45.10.4542:

; KBL
iKBLULTGT2 = "Intel(R) HD Graphics 620"
iKBLULXGT2 = "Intel(R) HD Graphics 615"

Beta driver 15.45.10.4552:

; KBL
iKBLULTGT2 = "Intel(R) HD Graphics 620"
iKBLULXGT2 = "Intel(R) HD Graphics 615"

Both drivers from Intel site did not have HD Graphics 610 listed so it is not supported by both drivers.

However I found HD Graphics 610 driver on Windows Update catalog, latest version are 21.20.16.4542 all drivers listed had higher version started with 21.

https://www.catalog.update.microsoft.com/Search.aspx?q=Intel+HD+Graphics+610

It seemed Intel had uploaded wrong drivers version 15 to their site so version 15 probably did not supported Windows 10. It strange that HD Graphics 610 page did not have any drivers.

So I googled further and found there are newer driver 21.20.16.4574 for HD Graphics 620 on Softpedia released days ago on 18 Jan 2017.

http://drivers.softpedia.com/get/GR...74-Windows-10-Anniversary-Update-64-bit.shtml

Newer driver 21.20.16.4574:

; KBL
iKBLULTGT1 = "Intel(R) HD Graphics 610"
iKBLULTGT2 = "Intel(R) HD Graphics 620"
iKBLULTGT2F = "Intel(R) HD Graphics 620"
iKBLULTGT3E15 = "Intel(R) Iris(TM) Plus Graphics 640"
iKBLULTGT3E28 = "Intel(R) Iris(TM) Plus Graphics 650"
iKBLULXGT2 = "Intel(R) HD Graphics 615"
iKBLDTGT1 = "Intel(R) HD Graphics 610"
iKBLDTGT2 = "Intel(R) HD Graphics 630"
iKBLHALOGT1 = "Intel(R) HD Graphics 610"
iKBLHALOGT2 = "Intel(R) HD Graphics 630"
iKBLWGT2 = "Intel(R) HD Graphics P630"

So newer driver has HD Graphics 610 support listed. Give it a try and it probably finally will have 4K playback enabled.

Nice detective work! I'd come to the same conclusion after browsing the Intel community forums. It seems a bit of a joke to not fully support your products on release.

I'll give that driver a crack, thanks.

Could it have been an oversight? The driver team maybe thought they all used the HD630? Glad it has been raised as I have this CPU on order.

That driver you listed doesn't work, unfortunately. When installing it only lists HD 520 and then, obviously, fails to install. It seems people/companies have been modifying existing drivers so they actually install, but without Intel releasing the base, we're not going to have 4k support.

Pretty sad considering it's one of the bigger changes on Kaby lake.

nashathedog said:

Pretty sad considering it's one of the bigger changes on Kaby lake.

Click to expand...

It's not acceptable to be honest. They've released a product, advertised its features but conveniently forgotten to mention that those features don't work yet.

Looks to be another Intel driver lockout then.
Intel did this too with dts hd master audio windows support on Braswells.

Official stance?

http://www.intel.com/content/www/us/en/support/graphics-drivers/000005526.html

That's interesting. Notice how the problem ones don't have pages? It seems they're only supported on paper.

benjii said:

That driver you listed doesn't work, unfortunately. When installing it only lists HD 520 and then, obviously, fails to install. It seems people/companies have been modifying existing drivers so they actually install, but without Intel releasing the base, we're not going to have 4k support.

Click to expand...

HD 520??? It seemed Softpedia uploaded driver from Intel labelled as HD 620 so Intel messed all it up badly, it not Kaby Lake driver but it is Sky Lake driver.

I opened ki120214.inf to looked for PCI\VEN and found two:

;=====================================================================
; Windows Threshold Install - DT + Mobile
;=====================================================================
[IntelGfx.NTamd64.10.0]
; SKL U UMA
%iSKLULTGT2% = iSKLD_w10, PCI\VEN_8086&DEV_1916&SUBSYS_81A0103C

;=====================================================================
; Windows Redstone Install - DT Only Using Driver Store
;=====================================================================
[IntelGfx.NTamd64.10.0...14393]
; SKL HW
%iSKLULTGT2% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1916&SUBSYS_81A0103C

Matched iSKLULTGT2 to the list below found at bottom of inf:

; SKL HW
iSKLULTGT1 = "Intel(R) HD Graphics 510"
iSKLULTGT2 = "Intel(R) HD Graphics 520"
iSKLULXGT2 = "Intel(R) HD Graphics 515"
iSKLDTGT2 = "Intel(R) HD Graphics 530"
iSKLULTGT2f = "Intel(R) HD Graphics 520"
iSKLULTGT3e = "Intel(R) Iris(TM) Graphics 540"
iSKLULTGT3 = "Intel(R) HD Graphics 535"
iSKLULTGT328W = "Intel(R) Iris(TM) Graphics 550"
iSKLDTGT1 = "Intel(R) HD Graphics 510"
iSKLHaloGT1 = "Intel(R) HD Graphics 510"
iSKLHaloGT4 = "Intel(R) Iris(TM) Pro Graphics 580"
iSKLHaloGT3fe = "Intel(R) Iris(TM) Graphics 555"
iSKLHaloGT2 = "Intel(R) HD Graphics 530"
iSKLSRVGT3e = "Intel(R) Iris(TM) Graphics P555"
iSKLSRVGT4 = "Intel(R) Iris(TM) Pro Graphics P580"
iSKLWSGT2 = "Intel(R) HD Graphics P530"
iSKLWSGT4 = "Intel(R) Iris(TM) Pro Graphics P580"
; BXT HW
iBXTGTP = "Intel(R) HD Graphics"
iBXTGTP12 = "Intel(R) HD Graphics"
; KBL
iKBLULTGT1 = "Intel(R) HD Graphics 610"
iKBLULTGT2 = "Intel(R) HD Graphics 620"
iKBLULTGT2F = "Intel(R) HD Graphics 620"
iKBLULTGT3E15 = "Intel(R) Iris(TM) Plus Graphics 640"
iKBLULTGT3E28 = "Intel(R) Iris(TM) Plus Graphics 650"
iKBLULXGT2 = "Intel(R) HD Graphics 615"
iKBLDTGT1 = "Intel(R) HD Graphics 610"
iKBLDTGT2 = "Intel(R) HD Graphics 630"
iKBLHALOGT1 = "Intel(R) HD Graphics 610"
iKBLHALOGT2 = "Intel(R) HD Graphics 630"
iKBLWGT2 = "Intel(R) HD Graphics P630"

The driver is only for laptop Sky Lake HD Graphics 520 but there are 3 versions of HD Graphics 520! Guess ULT is for laptop, DT is for desktop but I am not sure what HALO is for, maybe it could be for business or server. So I went to Microsoft catalog to searched for HD Graphics 610 drivers and looked at package details for hardware IDs. Found one driver with 3 hardware IDs:

pci\ven_8086&dev_5902
pci\ven_8086&dev_5906
pci\ven_8086&dev_590b

I downloaded these driver cab and extracted it but only found 1 device ID matched:

;=====================================================================
; Windows Threshold Install - DT + Mobile
;=====================================================================
[IntelGfx.NTamd64.10.0]
; SKL HW
%iSKLULTGT1% = iSKLD_w10, PCI\VEN_8086&DEV_1906&SUBSYS_39FD17AA
%iSKLULTGT2% = iSKLD_w10, PCI\VEN_8086&DEV_1916&SUBSYS_39FD17AA
%iSKLULTGT2f% = iSKLD_w10, PCI\VEN_8086&DEV_1921&SUBSYS_39FD17AA
%iSKLULTGT3e% = iSKLD_w10, PCI\VEN_8086&DEV_1926&SUBSYS_39FD17AA
%iSKLULTGT3% = iSKLD_w10, PCI\VEN_8086&DEV_1923&SUBSYS_39FD17AA
%iSKLULTGT328W% = iSKLD_w10, PCI\VEN_8086&DEV_1927&SUBSYS_39FD17AA

;KBL HW
%iKBLULTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5906&SUBSYS_211217AA
%iKBLULTGT2% = iKBLD_w10, PCI\VEN_8086&DEV_5916&SUBSYS_211217AA
%iKBLULTGT2F% = iKBLD_w10, PCI\VEN_8086&DEV_5921&SUBSYS_211217AA
%iKBLULXGT2% = iKBLD_w10, PCI\VEN_8086&DEV_591E&SUBSYS_211217AA

;=====================================================================
; Windows Redstone Install - DT Only Using Driver Store
;=====================================================================
[IntelGfx.NTamd64.10.0...14310]
; SKL HW
%iSKLULTGT1% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1906&SUBSYS_39FD17AA
%iSKLULTGT2% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1916&SUBSYS_39FD17AA
%iSKLULTGT2f% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1921&SUBSYS_39FD17AA
%iSKLULTGT3e% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1926&SUBSYS_39FD17AA
%iSKLULTGT3% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1923&SUBSYS_39FD17AA
%iSKLULTGT328W% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1927&SUBSYS_39FD17AA

;KBL HW
%iKBLULTGT1% = iKBLD_w10_DS, PCI\VEN_8086&DEV_5906&SUBSYS_211217AA
%iKBLULTGT2% = iKBLD_w10_DS, PCI\VEN_8086&DEV_5916&SUBSYS_211217AA
%iKBLULTGT2F% = iKBLD_w10_DS, PCI\VEN_8086&DEV_5921&SUBSYS_211217AA
%iKBLULXGT2% = iKBLD_w10_DS, PCI\VEN_8086&DEV_591E&SUBSYS_211217AA

iKBLULTGT1 used hardware ID PCI\VEN_8086&DEV_5906 but I don't know which 2 of hardware IDs used for iKBLDTGT1 and iKBLHALOGT1.

1 hour later searched further and hit jackpot!!!

http://www.geeks3d.com/forums/index.php?topic=4619.0

Looked down to the last post found all 3 hardware IDs for HD Graphics 610:

;KBL HW
%iKBLULTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5906
%iKBLULTGT2% = iKBLD_w10, PCI\VEN_8086&DEV_5916
%iKBLULTGT2F% = iKBLD_w10, PCI\VEN_8086&DEV_5921
%iKBLULTGT3% = iKBLD_w10, PCI\VEN_8086&DEV_5923
%iKBLULTGT3E15% = iKBLD_w10, PCI\VEN_8086&DEV_5926
%iKBLULTGT3E28% = iKBLD_w10, PCI\VEN_8086&DEV_5927
%iKBLULXGT2% = iKBLD_w10, PCI\VEN_8086&DEV_591E
%iKBLDTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5902
%iKBLDTGT2% = iKBLD_w10, PCI\VEN_8086&DEV_5912
%iKBLHALOGT1% = iKBLD_w10, PCI\VEN_8086&DEV_590B
%iKBLHALOGT2% = iKBLD_w10, PCI\VEN_8086&DEV_591B
%iKBLSRVGT2% = iKBLD_w10, PCI\VEN_8086&DEV_591A
%iKBLWGT2% = iKBLD_w10, PCI\VEN_8086&DEV_591D

So what you need to do to install the driver for HD 610 is to modded the inf.

You will need to open ki120214.inf on notepad and copy below:

;=====================================================================
; Windows Threshold Install - DT + Mobile
;=====================================================================
[IntelGfx.NTamd64.10.0]
;KBL HW
%iKBLULTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5906
%iKBLDTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5902
%iKBLHALOGT1% = iKBLD_w10, PCI\VEN_8086&DEV_590B

;=====================================================================
; Windows Redstone Install - DT Only Using Driver Store
;=====================================================================
[IntelGfx.NTamd64.10.0...14393]
;KBL HW
%iKBLULTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5906
%iKBLDTGT1% = iKBLD_w10, PCI\VEN_8086&DEV_5902
%iKBLHALOGT1% = iKBLD_w10, PCI\VEN_8086&DEV_590B

Go to Edit on notepad menu and click Find to search for PCI\VEN then paste it on bold parts in ki120214.inf:

;=====================================================================
; Windows Threshold Install - DT + Mobile
;=====================================================================
[IntelGfx.NTamd64.10.0]
; SKL U UMA
%iSKLULTGT2% = iSKLD_w10, PCI\VEN_8086&DEV_1916&SUBSYS_81A0103C

;=====================================================================
; Windows Redstone Install - DT Only Using Driver Store
;=====================================================================
[IntelGfx.NTamd64.10.0...14393]
; SKL HW
%iSKLULTGT2% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1916&SUBSYS_81A0103C


Then save the inf and Device Manager should detect correct hardware ID and install correct driver for HD Graphics 610.

Thanks for your help investigating this, I appreciate it.

Do you think that would work on Intel's newest driver? As that supports HD620, so most likely has some sort of 4k support. The newest driver available currently, is this one. FYI, the last 4 numbers indicate the driver version.

benjii said:

Thanks for your help investigating this, I appreciate it.

Do you think that would work on Intel's newest driver? As that supports HD620, so most likely has some sort of 4k support. The newest driver available currently, is this one. FYI, the last 4 numbers indicate the driver version.

Click to expand...

That Beta 15.45.12.4552 driver from Intel site is not the newest driver. If HD 610 is not listed at bottom of inf then the driver would not supported all HD 610 features like 4K support. I think I found out why the driver is version 15.

http://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=select&id=108&lang=en

Accorded to station drivers, version 15 drivers is only worked for Sky Lake, Broadwell and Haswell while version 21 is only worked for Kaby Lake, Sky Lake and Apollo Lake.

Actually the HD 620 version 21.20.16.4574 driver from Softpedia site is the latest and newest driver, it had HD 610 listed at bottom of inf so it more likely supported all new Kaby Lake features like 4K support.

So you could download driver from Softpedia site and modded the inf.

Or you could download same latest 21.20.16.4574 driver from station drivers as it passed WHQL and had included all hardware IDs accorded to description below so you don't need to modded inf.

Description:
Date & Version du drivers:*12/23/2016,21.20.16.4574
Date & Version du package: December 29, 2016 & 21.20.16.4574
WHQL: oui
Officiel: non
Sous: Windows 7/8/8.1/10/Server2016
Systemes:*64bits (X64)
Plateformes:
7th Gen Intel(R) Core(TM) processor family (Codename Kaby Lake)
6th Gen Intel(R) Core(TM) processor family (codename Skylake)
Apollo Lake
Intel® Xeon® Processor E3-1200 v5 Product Family
Intel® Xeon® Processor E3-1500 v5 Product Family
Intel® Xeon® Processor E3-1200 v6 Product Family
Chipsets: (Intel(R) HD Graphics 510, Intel(R) HD Graphics, Intel(R) HD Graphics 515, Intel(R) HD Graphics 530, Intel(R) HD Graphics 520, Intel(R) Iris(TM) Graphics 540, Intel(R) HD Graphics 535, Intel(R) Iris(TM) Graphics 550, Intel(R) Iris(TM) Pro Graphics 580, Intel(R) Iris(TM) Graphics 555, Intel(R) Iris(TM) Graphics P555, Intel(R) Iris(TM) Pro Graphics P580, Intel(R) HD Graphics P530, Intel(R) HD Graphics 610, Intel(R) HD Graphics 620, Intel(R) Iris(TM) Plus Graphics 640, Intel(R) Iris(TM) Plus Graphics 650, Intel(R) HD Graphics 615, Intel(R) HD Graphics 610, Intel(R) HD Graphics 630*
Code IDs:
%iSKLULTGT1% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1906
%iSKLULTGT2% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1916
%iSKLULXGT2% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_191E
%iSKLDTGT2% *** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1912
%iSKLULTGT2f% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1921
%iSKLULTGT3e% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1926
%iSKLULTGT3% ** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1923
%iSKLULTGT328W% = iSKLD_w10_DS, PCI\VEN_8086&DEV_1927
%iSKLDTGT1% *** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_1902
%iSKLHaloGT1%** = iSKLD_w10_DS, PCI\VEN_8086&DEV_190B
%iSKLHaloGT4%** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_193B
%iSKLHaloGT3fe% = iSKLD_w10_DS, PCI\VEN_8086&DEV_192B
%iSKLHaloGT2%** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_191B
%iSKLSRVGT3e%** = iSKLD_w10_DS, PCI\VEN_8086&DEV_192D
%iSKLSRVGT4%** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_193A
%iSKLWSGT2%** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_191D
%iSKLWSGT4%** *= iSKLD_w10_DS, PCI\VEN_8086&DEV_193D
%iBXTGTP%**** = iBXTD_w10_DS, PCI\VEN_8086&DEV_5A84
%iBXTGTP12%** = iBXTD_w10_DS, PCI\VEN_8086&DEV_5A85
%iKBLULTGT1%******* = iKBLD_w10_DS, PCI\VEN_8086&DEV_5906
%iKBLULTGT2%******* = iKBLD_w10_DS, PCI\VEN_8086&DEV_5916
%iKBLULTGT2F%****** = iKBLD_w10_DS, PCI\VEN_8086&DEV_5921
%iKBLULTGT3E15%**** = iKBLD_w10_DS, PCI\VEN_8086&DEV_5926
%iKBLULTGT3E28%** **** = iKBLD_w10_DS, PCI\VEN_8086&DEV_5927
%iKBLULXGT2%******* = iKBLD_w10_DS, PCI\VEN_8086&DEV_591E
%iKBLDTGT1%******** = iKBLD_w10_DS, PCI\VEN_8086&DEV_5902
%iKBLDTGT2%******** = iKBLD_w10_DS, PCI\VEN_8086&DEV_5912
%iKBLHALOGT1%****** = iKBLD_w10_DS, PCI\VEN_8086&DEV_590B
%iKBLHALOGT2%****** = iKBLD_w10_DS, PCI\VEN_8086&DEV_591B
%iKBLWGT2%********* = iKBLD_w10_DS, PCI\VEN_8086&DEV_591D
Release note : non
Langues: ara – Arabic (Saudi Arabia) cht – Chinese (Simplified) hrv - Croatian cys - Czech dan - Danish nld - Dutchenu - English (US) fin - Finnish fra-* French deu - German ell - Greek heb - Hebrew hun - Hungarian ita - Italian jpn - Japanese kor - Korean* nor – Norwegian (Bokmal) plk - Polish ptg - Portuguese (Brazilian) ptb - Portuguese rom - Romanian
rus-* Russian SKY - Slovak SLV - Slovenian Esp - Spanish Sve - Swedish* Tha - Thai Trk - Turkish
Inclus:
Lien Officiel: http://www.intel.com/

http://www.station-drivers.com/inde...tory&Itemid=352&func=fileinfo&id=2666&lang=en

I see, thank you. I'll give that a try and report back!

The station drivers one install just great. However, CPU usage is still maxing out on 4k and it's dropping lots of frames. I guess the wait continues! Thanks for your help though.

benjii said:

I see, thank you. I'll give that a try and report back!

The station drivers one install just great. However, CPU usage is still maxing out on 4k and it's dropping lots of frames. I guess the wait continues! Thanks for your help though.

Click to expand...

Good to hear the driver installed great.

I decided to read the whole inf to find decoders and finally figured out why your CPU still maxed out on 4K:

;=====================================================================
[MSDK_Win7_MFT_Enable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableVideoProcessors, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableVideoProcessors, %REG_DWORD%, 0x0001

[MSDK_Win7_MFT_Disable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableVideoProcessors, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableVideoProcessors, %REG_DWORD%, 0x0000

;===============================================
[MSDK_w7.copy]
; 32 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw32.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin32_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264vd_w7_32.dll,,,0x00004000 ; H.264 Decoder MFT
mfx_mft_h264ve_w7_32.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mp2vd_w7_32.dll,,,0x00004000 ; MPEG-2 Decoder MFT
mfx_mft_vc1vd_w7_32.dll,,,0x00004000 ; VC-1 Decoder MFT
mfx_mft_vpp_w7_32.dll,,,0x00004000 ; Video Pre-Processing MFT
m_w7_32.vp
v1_w7_32.vp
vp_w7_32.vp
c_w7_32.cpa
cpa_w7_32.vp
dev_w7_32.vp
h_w7_32.vp
he_w7_32.vp
mj_w7_32.vp

; 64 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw64.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin64_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264vd_w7_64.dll,,,0x00004000 ; H.264 Decoder MFT
mfx_mft_h264ve_w7_64.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mp2vd_w7_64.dll,,,0x00004000 ; MPEG-2 Decoder MFT
mfx_mft_vc1vd_w7_64.dll,,,0x00004000 ; VC-1 Decoder MFT
mfx_mft_vpp_w7_64.dll,,,0x00004000 ; Video Pre-Processing MFT
m_w7_64.vp
v1_w7_64.vp
vp_w7_64.vp
c_w7_64.cpa
cpa_w7_64.vp
dev_w7_64.vp
h_w7_64.vp
he_w7_64.vp
mj_w7_64.vp

[MSDK_w7_RegisterDLLs]
16422,Intel\Media SDK,mfx_mft_h264ve_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_h264vd_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_mp2vd_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_vc1vd_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_vpp_w7_32.dll,1
16422,Intel\Media SDK,mfx_mft_h264ve_w7_64.dll,1
16422,Intel\Media SDK,mfx_mft_h264vd_w7_64.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_w7_64.dll,1
16422,Intel\Media SDK,mfx_mft_mp2vd_w7_64.dll,1
16422,Intel\Media SDK,mfx_mft_vc1vd_w7_64.dll,1
16422,Intel\Media SDK,mfx_mft_vpp_w7_64.dll,1

;===============================================

Windows 7 did not have hardware VP9 decoder!

;===============================================
[MSDK_Win8_MFT_Enable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001

[MSDK_Win8_MFT_Disable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
;===============================================
[MSDK_w8.copy]
; 32 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw32.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin32_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_32.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_32.dll,,,0x00004000
mfx_mft_vp8vd_32.dll,,,0x00004000 ; VP8 MFT

mfx_mft_vp9vd_32.dll,,,0x00004000 ; VP9 MFT
mfx_mft_h265ve_32.dll,,,0x00004000 ; H.265 Encoder MFT
h265e_32.vp,,,0x00004000

he_32.vp,,,0x00004000
c_32.cpa,,,0x00004000
cpa_32.vp,,,0x00004000
dev_32.vp,,,0x00004000
mj_32.vp,,,0x00004000

; 64 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw64.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin64_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_64.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_64.dll,,,0x00004000 ; H.264 Decoder MFT
mfx_mft_vp8vd_64.dll,,,0x00004000 ; VP8 MFT

mfx_mft_vp9vd_64.dll,,,0x00004000 ; VP9 MFT
mfx_mft_h265ve_64.dll,,,0x00004000 ; H.265 Encoder MFT
h265e_64.vp,,,0x00004000

he_64.vp,,,0x00004000
c_64.cpa,,,0x00004000
cpa_64.vp,,,0x00004000
dev_64.vp,,,0x00004000
mj_64.vp,,,0x00004000

[MSDK_w8_RegisterDLLs]
16422,Intel\Media SDK,mfx_mft_h264ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_32.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_32.dll,1
16422,Intel\Media SDK,mfx_mft_h264ve_64.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_64.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_64.dll,1

16422,Intel\Media SDK,mfx_mft_vp9vd_32.dll,1
16422,Intel\Media SDK,mfx_mft_vp9vd_64.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_64.dll,1

;======================================================

Windows 8 has hardware VP9 decoder!

;======================================================
[MSDK_Win10rs1_MFT_Enable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001

[MSDK_Win10rs1_MFT_Disable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000

[MSDK_w10rs1.copy]
; 32 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw32.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin32_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_32.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_32.dll,,,0x00004000 ; MJPEG Decoder MFT
mfx_mft_vp8vd_32.dll,,,0x00004000 ; VP8 Decoder MFT
mfx_mft_h265ve_32.dll,,,0x00004000 ; H.265 Encoder MFT
mfx_mft_encrypt_32.dll,,,0x00004000 ; Encryptor MFT

c_32.cpa,,,0x00004000
cpa_32.vp,,,0x00004000
dev_32.vp,,,0x00004000
he_32.vp,,,0x00004000
mj_32.vp,,,0x00004000
h265e_32.vp,,,0x00004000

; 64 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw64.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin64_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_64.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_64.dll,,,0x00004000 ; MJPEG Decoder MFT
mfx_mft_vp8vd_64.dll,,,0x00004000 ; VP8 Decoder MFT
mfx_mft_h265ve_64.dll,,,0x00004000 ; H.265 Encoder MFT
mfx_mft_encrypt_64.dll,,,0x00004000 ; Encryptor MFT

c_64.cpa,,,0x00004000
cpa_64.vp,,,0x00004000
dev_64.vp,,,0x00004000
he_64.vp,,,0x00004000
mj_64.vp,,,0x00004000
h265e_64.vp,,,0x00004000

[MSDK_w10rs1_RegisterDLLs]
16422,Intel\Media SDK,mfx_mft_h264ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_h264ve_64.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_32.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_64.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_32.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_64.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_64.dll,1
16422,Intel\Media SDK,mfx_mft_encrypt_32.dll,1
16422,Intel\Media SDK,mfx_mft_encrypt_64.dll,1
;======================================================
; End - Media SDK Support
;======================================================

Windows 10 did not have hardware VP9 decoder!

I find it interesting Windows 10 used same encoders and decoders dlls which Windows 8 used so I wondered why Intel allowed people to use Kaby Lake hardware VP9 decoder on Windows 8 but not on Windows 10? Could be bugs or it not ready for Windows 10 yet?

Maybe it is worth a try to modded inf and reinstall driver with modded inf that will let you to use hardware VP9 decoder on Windows 10!

You will need to copy below:

;======================================================
[MSDK_Win10rs1_MFT_Enable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0001
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0001

[MSDK_Win10rs1_MFT_Disable]
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders, %REG_DWORD%, 0x0000
HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders, %REG_DWORD%, 0x0000

[MSDK_w10rs1.copy]
; 32 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw32.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin32_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_32.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_32.dll,,,0x00004000 ; MJPEG Decoder MFT
mfx_mft_vp8vd_32.dll,,,0x00004000 ; VP8 Decoder MFT
mfx_mft_vp9vd_32.dll,,,0x00004000 ; VP9 Decoder MFT
mfx_mft_h265ve_32.dll,,,0x00004000 ; H.265 Encoder MFT
mfx_mft_encrypt_32.dll,,,0x00004000 ; Encryptor MFT

c_32.cpa,,,0x00004000
cpa_32.vp,,,0x00004000
dev_32.vp,,,0x00004000
he_32.vp,,,0x00004000
mj_32.vp,,,0x00004000
h265e_32.vp,,,0x00004000

; 64 bit - Using COPYFLG_IN_USE_TRY_RENAME
libmfxhw64.dll,,,0x00004000 ; Intel MediaSDK library
mfxplugin64_hw.dll,,,0x00004000 ; Media SDK Plugin
mfx_mft_h264ve_64.dll,,,0x00004000 ; H.264 Encoder MFT
mfx_mft_mjpgvd_64.dll,,,0x00004000 ; MJPEG Decoder MFT
mfx_mft_vp8vd_64.dll,,,0x00004000 ; VP8 Decoder MFT
mfx_mft_vp9vd_64.dll,,,0x00004000 ; VP9 Decoder MFT
mfx_mft_h265ve_64.dll,,,0x00004000 ; H.265 Encoder MFT
mfx_mft_encrypt_64.dll,,,0x00004000 ; Encryptor MFT

c_64.cpa,,,0x00004000
cpa_64.vp,,,0x00004000
dev_64.vp,,,0x00004000
he_64.vp,,,0x00004000
mj_64.vp,,,0x00004000
h265e_64.vp,,,0x00004000

[MSDK_w10rs1_RegisterDLLs]
16422,Intel\Media SDK,mfx_mft_h264ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_h264ve_64.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_32.dll,1
16422,Intel\Media SDK,mfx_mft_mjpgvd_64.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_32.dll,1
16422,Intel\Media SDK,mfx_mft_vp8vd_64.dll,1
16422,Intel\Media SDK,mfx_mft_vp9vd_32.dll,1
16422,Intel\Media SDK,mfx_mft_vp9vd_64.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_32.dll,1
16422,Intel\Media SDK,mfx_mft_h265ve_64.dll,1
16422,Intel\Media SDK,mfx_mft_encrypt_32.dll,1
16422,Intel\Media SDK,mfx_mft_encrypt_64.dll,1
;======================================================
; End - Media SDK Support
;======================================================

So you will need to find Media SDK Support using notepad to find the line and paste it on inf then save it and then after reinstall driver, make sure you have hardware VP9 decoder enabled. If you cant find option to enabled hardware VP9 decoder then open regedit and navigate to HKLM,Software\Microsoft\Windows Media Foundation\HardwareMFT, EnableDecoders and HKLM, Software\Wow6432Node\Microsoft\Windows Media Foundation\HardwareMFT, EnableEncoders to see if value 0x0001 set to enabled.

Good luck.

seems like a lot of hassle and potential for bricking your system

I'd rather wait for intel to solve the issue. OP can you send this on to whoever you spoke to within Intel?

Did you sort it mate? If not try the driver linked below it has 610 support.

https://www.asus.com/Motherboards/ROG-MAXIMUS-IX-APEX/HelpDesk_Download/

Nah, there's no solution. I've tried that driver any many more, still no luck. Looks like I just have to wait for Intel to release a proper driver.

I'm completely out of my depth here, apologies if I'm being redundant: Had the same problem. Found a driver from MS catalog that works on my system, Win 8.1 x64, Intel g4560, ASRock H110M-DGS. Here are the catalog links:
https://www.catalog.update.microsof...updateid=25a3b44c-127d-41ef-8576-53d980359bbc
http://download.windowsupdate.com/c..._f2a89da00c263376b9a6aeab074e14147c9cb08c.cab

Other catalog drivers would not work.

Had to disable driver signing check and then installed it by right-clicking and running the .inf file, which installed the entire setup with the Intel control panel. If this solves your problem or helps in some way, please let me know and disseminate.