• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Why beta version instead of WHQL version

1

100PIER

New Member
Joined
Jan 24, 2020
Messages
7 (0.00/day)
Hello,
Can you explain why a Intel WHQL version is detected as a beta version ?
 

Attachments

  • GPUZ2290_bug_24janv20.PNG
    GPUZ2290_bug_24janv20.PNG
    154.2 KB · Views: 651
Interesting, that shouldn't happen. Let me try to reproduce tomorrow
 
Happens often.
 

Attachments

  • Capture.PNGbvw.PNG
    Capture.PNGbvw.PNG
    302.3 KB · Views: 530
  • wvb.PNG
    wvb.PNG
    372.8 KB · Views: 578
YES, I do replicate the problem using DXDIAG tool as well.
 

Attachments

  • GPUZ2290_bug_28janv20.PNG
    GPUZ2290_bug_28janv20.PNG
    84.7 KB · Views: 512
harm9963 said:
Happens often.
Click to expand...
442.01 was a hotfix driver and 450.12 a leaked driver. do you see the same issue on official nvidia whql release drivers?

bqtadyrwg5.jpg

hmmm works for me. any chance i could log onto your system with teamviewer to check a few things?
 
Problem does occur with Intel GPU 27. x branch drivers on i3-8300 CPU.
Is it possible for you to use a 27.x branch driver instead of 26.x ?
 
Where do I get that driver?
 
Insider driver , are beta to me , by nature , preview build are for testing and feedback, not everyday users, DXDIAG has alway shown WHQL .
 

Attachments

  • Capture.PNGnld.PNG
    Capture.PNGnld.PNG
    38.2 KB · Views: 445
Even with the native W10 (1903, Build 18363.592) Basic GPU driver GPUZ tool does report a "beta" signature which is obsiouly a wrong indication.
GPUZ should investigate this wrong signature detection and do fix the bug.
Here are a set of various Intel drivers version tested with DXDIAG and GPUZ tools.
Drivers version branch 26.xx are correctly detected WHQL, branch 27.xx are NOT correctly detected WHQL.
DXDIAG tools does provide correct signature status as well for 26.xx and 27.xx branch.
 

Attachments

  • GPUZ2290_bug_nativeW10_GPU_28janv20.PNG
    GPUZ2290_bug_nativeW10_GPU_28janv20.PNG
    107.3 KB · Views: 403
  • GPUZ2290_Intel_GPU_26201007156_28janv20.PNG
    GPUZ2290_Intel_GPU_26201007156_28janv20.PNG
    115.4 KB · Views: 407
  • GPUZ2290_Intel_GPU_26201007755DCH_28janv20.PNG
    GPUZ2290_Intel_GPU_26201007755DCH_28janv20.PNG
    82.2 KB · Views: 277
  • GPUZ2290_Intel_GPU_27201007738DCH_28janv20.PNG
    GPUZ2290_Intel_GPU_27201007738DCH_28janv20.PNG
    103.5 KB · Views: 246
100PIER said:
Basic GPU driver GPUZ tool does report a "beta" signature
Click to expand...
I fixed that this morning, while playing with the Intel WHQL testing

100PIER said:
Drivers version branch 26.xx are correctly detected WHQL, branch 27.xx are NOT correctly detected WHQL.
Click to expand...
I suspect the 27.xx drivers are not WHQL but "attestation signed". Will download and check tomorrow
 
Just tested this, the new driver is indeed attestation signed, aka beta

jgzsikzrgp.jpg
 
Suggestion -- add a 3rd kind of drivers status except current TWO - Beta and WQHL.
Name it however you wish/think is best. :)
 
Last edited:
Yes, I do agree with Naki suggestion to provide one exact status driver, so GPU should be the unique tool to display a correct Intel driver status and so will avoid any confusion with DXDIAG tool status driver which do provide one 'approximate' information..
 
gpuz displays the correct driver status already, are you saying you prefer to confuse 99% of users by showing "attestation" instead of "beta" ?
 
IF "Attestation" equals "Beta", then of course no use or need to do this.
Maybe in a tooltip then? Unless of course Attestation is exactly the same thing as Beta, in which case tooltip would be also useless.
 
Insider driver 450.12 , that comes from Preview Builds, fast ring,are for testing and feedback;) i do not make available for download, but others do, and post as WQHL ,from Guru3d ,for available download .
forums.guru3d.com

Nvidia 450.12 WHQL for Win10 x64

https://c-t.work/s/8316b48efff046 https://pan.baidu.com/s/1LdUmtyDRCyFkuv2Qiq651A 提取码: m58c
forums.guru3d.com forums.guru3d.com
 
harm9963 said:
Insider driver 450.12 , that comes from Preview Builds, fast ring,are for testing and feedback;) i do not make available for download, but others do, and post as WQHL ,from Guru3d ,for available download .
forums.guru3d.com

Nvidia 450.12 WHQL for Win10 x64

https://c-t.work/s/8316b48efff046 https://pan.baidu.com/s/1LdUmtyDRCyFkuv2Qiq651A 提取码: m58c
forums.guru3d.com forums.guru3d.com
Click to expand...

There was already a thread about it:
www.techpowerup.com

insider leaked nvidia drivers whql 450.12 branch, fresh of the press, for windows 20h2 but works with wddm 2.7 on 20h1 rtm. post your findings!

this is of course newer than the recent december 445.23 leaked driver which features wddm 2.7 and hardware accelerated gpu scheduling on 20h1. This driver is the next in line. I uploaded to dropbox for you to avoid chinese or russian limited bandwidth sites...
www.techpowerup.com www.techpowerup.com
 
Dxdiag doesn't know about attestation signing. It will show whql for everything with a ms counter signature

Per Definition by Microsoft, attestation signing does not run a single of the whql tests.
 
Thank you ,Insider driver for testing and feedback should not be posted as WHQL.
 
I have a question, and perhaps I missed something, why are drivers not being downloaded from the makers of the drivers? For example, why are the Intel drivers in question here not being downloaded from Intel.com?
 
@W1zzard - is there such a thing as Beta drivers without attestation? :confused:
 
You must log in or register to reply here.
Back
Top