My new baby
I posted this "problem" to the internal PCS tech support web page last Thu (25/6), it's been read but no reply after a week. Thought I'd try for a faster response from this board
I upgraded to Windows 10 Ver. 2004 a couple of days after getting the new PC, I found my Wireless Xbox 360 controller wasn't recognised. I had the same problem In my previous PC, running Ver. 1909, previously I was able to force Windows to check it's stored drivers to use a suitable driver for the controller.
This method did not work on Ver. 2004. But I did find a method which altered the MS driver for the controller, but as the driver was no longer digitally signed I had to turn on/off the test signing mode e.g.
bcdedit /set testsigning on
But I had to turn off secure boot to do this.
I did this and the controller now works, but when I turned secure boot back on I noticed the values had changed for DBX e.g.
From:
PK Management | 886 | 1 | Default
KEK Management | 3573 | 3| Default
DB Management | 6322 | 10 | Default
DBX Management | 4040 | 83| Mixed
To:
PK Management | 886 | 1 | Default
KEK Management | 3573 | 3| Default
DB Management | 6322 | 10 | Default
DBX Management | 3724 | 77| Default
The PC boots normally and has no issues.
Found this for the Keys meaning:
The Platform Key (PK) establishes a trust relationship between the platform owner and the firmware (UEFI BIOS) by controlling access to the KEK database. ... The KEK consists of a list of public keys that can be checked against for authorization to modify the whitelist database (DB) or blacklist database (DBX)
Not sure why DBX changed, I have added to the system-> 2x 2TB HDD disks + 500GB 850 EVO M.2 SSD
Do I need to change the values in secure boot back to the original values, if so how?
Can't add my spec in the same email, must be too large
Thanks
Jim
I posted this "problem" to the internal PCS tech support web page last Thu (25/6), it's been read but no reply after a week. Thought I'd try for a faster response from this board
I upgraded to Windows 10 Ver. 2004 a couple of days after getting the new PC, I found my Wireless Xbox 360 controller wasn't recognised. I had the same problem In my previous PC, running Ver. 1909, previously I was able to force Windows to check it's stored drivers to use a suitable driver for the controller.
This method did not work on Ver. 2004. But I did find a method which altered the MS driver for the controller, but as the driver was no longer digitally signed I had to turn on/off the test signing mode e.g.
bcdedit /set testsigning on
But I had to turn off secure boot to do this.
I did this and the controller now works, but when I turned secure boot back on I noticed the values had changed for DBX e.g.
From:
PK Management | 886 | 1 | Default
KEK Management | 3573 | 3| Default
DB Management | 6322 | 10 | Default
DBX Management | 4040 | 83| Mixed
To:
PK Management | 886 | 1 | Default
KEK Management | 3573 | 3| Default
DB Management | 6322 | 10 | Default
DBX Management | 3724 | 77| Default
The PC boots normally and has no issues.
Found this for the Keys meaning:
The Platform Key (PK) establishes a trust relationship between the platform owner and the firmware (UEFI BIOS) by controlling access to the KEK database. ... The KEK consists of a list of public keys that can be checked against for authorization to modify the whitelist database (DB) or blacklist database (DBX)
Not sure why DBX changed, I have added to the system-> 2x 2TB HDD disks + 500GB 850 EVO M.2 SSD
Do I need to change the values in secure boot back to the original values, if so how?
Can't add my spec in the same email, must be too large
Thanks
Jim
