If you think D0p2000 is not being co-operative, take a step back and look. D0p2000 is more than co-operating. He created a thread and asked reasonable questions. He has offered up his time and provided you with lots of options and details. As a response, you closed the bug. That is not helping anyone.
Instead of being so hostile and jumping on any chance of closing these threads everytime, how about creating a safe environment people can openly discuss the issue and come up with solutions? You know, be proactive instead of discouraging any type of talk about the issue.
There are a ton of stuff still to try and a ton of workarounds that help mitigate the issue. I can't post any of them without thinking you are going to ban me or just close the thread for doing so. As a result, I have numerous people msg'ing me for these suggestions, more and more each day. It is a tad crazy when you think about that...people have to PM me for help, because they don't want to be called a troll or get banned by you for questioning this bug.
It is clear you are not going to give the time required to assist people in figuring it out (yes, you have given time, but not enough time to properly help your users and that is OK given how busy you are...). The least you could do is create a safe and open environment people can try and figure it out. Considering we are all trying to solve an issue that includes running your software, that sounds completely resonable to me. Open up a thread, acknowledging people are getting this issue. Set some ground rules and let people gather solutions together. Let people feel safe in your forums, and who knows, maybe C2 will run on W10 like it does on W7 one day. Perhaps a thread similar to the NW.js roundup thread would be helpful.