arturpanteleev
I have just started working on my comparison analysis, but it looks like the issue MIGHT be a .NET Security Update. Which could be across Windows editions
I have restored my PC to an image from 2 weeks ago and the problem vanished. I had not updated my PC before this since May, so I am building a new Win 7 Virtual Machine and am going to get it to update parity with my physical machine. I am then going to apply each months Updates (June, July, etc all the way to Nov) and see where the issue pops up.
I will keep this thread updated on my findings