Yes, it's been awhile since my last post. While I've been busy on lots of interesting work, nothing blog-worthy. 

A friend just reported this minor issue to me, and it was confirmed by some folks in Windows.

In the latest SDK headers, you'll find the following:


It should instead be:


Note: I'm just the messenger here. I myself haven't yet played with InitializeCriticalSectionEx myself. I just wanted to get this info out there to prevent others from the pain of discovering this.