Just an FYI --- the result of this error in my case was an AccessViolationException from ADO. The related KB has been updated, listing .net 4.5.2 as...

Scratch that optimism. The 4.5.2 known issues article links to the .net 4.5.1 known issues article -- so it looks like it's not fixed :-/

Well, this post morphed to something totally different than I expected to say ....

Funny enough,.net 4.5.2 was posted today (link). The known issues article (link) doesn't list this...

I never heard back from PhilipC, so I don't know what happened on his end. On my end, a few things...

1) This is the relevant KB article

Have you gotten anywhere on this?

We've found the winsock reset will keep it running for 2-4 hours before tipping over and dying. Some other thoughts...

I stumbled upon this error too. We upgrade some servers to .NET Framework 4.5.1 and ran into precisely the same situation ( Win 2008 R2 x64).

From a command line run...