We made the change over to EXE a couple months go to be more in-line with our Protect product. Normally, we have product filtering in place to prevent patches being offered to non-applicable OS/Product combinations. This was missed in the latest definition files which is causing what you are seeing. This will be fixed in tomorrow's release.
Let me know if you have any questions.
I just received word from our Content Team that this issue will actually be resolved within Friday's Shavlik Patch data release. I apologize for the inconvenience.