Windows 10: interrupt affinity policy errror

When i try to set an affinity for a device on interrupt affinity policy tool, i get an error saying "registry value for affinity mask has an unexpected type". in this article it shows the fix Interrupt Affinity Policy Tool and unexpected affinity mask type microsoft.com but the owner of that article is quite vague in his explanation. I was able to to find affinity policy-temporal, but i dont know how to change "target set" value to "binary" like the op of that article claimed. Someone please help, looking forward to replies.

:)

 

How to bind network card to cpu0 using affinity mask tool

In order to bind a network card to CPU 0 using interrupt affinity policy configuration tool do you need to install Microsofts hardware pk if not is there any steps needed when using the interrupt affinity policy configuration tool?

 

interrupt affinity, system handles interrupts only on core0

I have everything in msi/msi-x mode, except usb. From measuring dpc in latencymon, i have still 400k dpc calls on core 0, while other 7 cores gets 500-7000 for each, which is disappointing.

And setting in regedit interrupt affinity doesn't help, because hardware/drivers can override that setting. It is really strange, that hardware/drivers/windows wouldn't allocate multicore for handling interrupts: my pc isn't that old i have i7 3700k chipset b75m, which isn't best but still... Interrupts should be spread on all cores, instead being handled only on core 0. It is really like something from 2005.

I am positive i have set it under right device in regedit and i entered under Affinity Policy: "DevicePolicy" and put value 3 in decimal. Or i tried put there IrqPolicyAllProcessorsInMachine instead devicepolicy. Because i am unsure if i have to put there either this or that. But again drivers/hardware can override this setting, so it hasn't necessarily have to work.
Interrupt Affinity - Windows drivers

Still i would expect hardware and drivers should handle this and use multicore for interrupts today times. I am getting new pc, so i will test it on that and hopefully it will be fine. But this doesn't make sense...

Edit: after setting device/driver to msi, interrupt affinity started to work, which shouldn't be needed for it to work.

 

Messed Up Cpu Interrupt Cycle Times

Im trying to setup up interrupt affinity policy. I have a i59400f proccessor which has 6 cores so i have been told to set my gpu and usb to 2 and 4 in interrupt affinity policy. My average interrupt to proccess latency is good but my Cpu interrupt cycle
times are all messed up.