D
Go in peace dear friend...No, we did everything correctly. We confirm that it was properly disabled with wireshark. This is a known problem with the CPU that Intel is well aware of and we called their tech department to confirm. We found the exact problem and the fix. I don't know why you're denying it. I'm pretty sure Intel is much more knowledgeable with their own equipment.