Where are all the Microsoft Networking MVPs?

There's a gnarly networking question on stack overflow that I've since reposted on various Microsoft forums and so far I've had absolutely no useful response. Not even an "I don't know, but I'll look into it".

I can understand that, perhaps, the issue may be a little bit technical for a support person who isn't steeped in networking API knowledge; but where are the MVPs? Why isn't there a Winsock MVP who can tell me that the bug has already been raised somewhere and might get fixed, or that it's a known and desirable breaking change??

This issue looks to be a bug, IMHO, quite a subtle and serious one and one that has made its way into Windows 8 RTM. At this rate it will also be part of Windows Server 2012 RTM and we'll all have to write convoluted code to spot the broken platform and work around it; then once it's fixed in some obscure hotfix we'll have to wait until a service pack comes out before we can spot that the platform we're running on DOESN'T have the bug and thus run without the convoluted work around code. Bleugh!

And don't get me started on how it's practically impossible to work out WHERE I should be asking this question....


Hey Len,

I notified Microsoft via mail (wskapi at microsoft.com) about the thread on stackoverflow.com.

Response was: Thanks for reporting this issue. We are investigating the report.


Was that an automated response?

How does one find out about that email address?

Is that really the ONLY way to report things like this?

I've reported it via MS Connect, but I'm not convinced the category that was available (Windows Server 2012 Essentials Pre-Release Feedback) was the best place...

It was a personal response, i got the reply after 2 days.

I found this email address in some PowerPoint presentation about winsock kernel api, i used this way because i didn't know any better way. ;)

Well, at least someone might look at it...

I just cant believe that the issue reporting system for a new OS is SO amazingly and utterly broken. :(

This is confirmed as a bug in Windows 8 and all Server 2012 variants - see the Microsoft Connect ticket here: https://connect.microsoft.com/WindowsServer/feedback/details/760161/breaking-change-to-acceptex-and-iocp-in-server-2012-and-windows-8

The official response is "We've passed this to the base OS team and they will consider this for a future update. I'm resolving this postponed."


Leave a comment

About this Entry

Half of the classic singleton is a useful concept; a class that has only one instance. The other half is bollocks; providing a global way to access that single instance. was the previous entry in this blog.

Building OpenSSL for x86 and x64 on Windows for side by side deployment is the next entry in this blog.

I usually write about C++ development on Windows platforms, but I often ramble on about other less technical stuff...

Find recent content on the main index or look in the archives to find all content.

I have other blogs...

Subscribe to feed The Server Framework - high performance server development
Subscribe to feed Lock Explorer - deadlock detection and multi-threaded performance tools
Subscribe to feed l'Hexapod - embedded electronics and robotics