Ya know, it's possible that it will never be reported because Win 7 didn't natively support secure boot. As the article you linked called it, a "half-azzed secure boot." I think you need to test it the way I did: before you download the secure-boot ESU, try to activate secure boot in your firmware, so you'll see how your firmware reports an inability to secure-boot. Then download the secure-boot ESU and try again. That's how I know secure-boot is working even though the Win 7 utilities were not designed to report something that's not natively supported.