I have been experiencing this issue since Nov 8th, right after I did the 1709 update on Nov 4th. I talked to three different Microsoft tier 1 technicians. None of them solved my problem.
The 1st guy told me it was the latest driver of Nvidia (GTX 1070) not compatible to Windows 10. So he degraded my Graphic card driver. The problem occurred again later after that.
The 2nd guy showed me some “advance techniques” to tune my Windows 10 for a “higher performance.” He said it must have “solved the problem 101%”, quote. I could not recall what exactly he did, but it did not solve it at all.
The 3rd guy told me to “repair installation” of Windows 10 and guaranteed me once again it would “definitely solved” the problem. I did not buy it, because my friend @Boya_Wang had already tried to completely reinstall Windows 10 and Rhino 5 twice, which did not even solve the problem.
After my tiring insists, I was guided to a “supervisor” of Windows support, who told me directly that I should talk to McNeel instead. He was passing the buck to Rhino 5 “not compatible with our 1709 update”. Seriously? This is not a freeze up of only Rhino 5 port, but the entire system (CAP key not functioning) without a blue screen or any error codes. How dare they say it has nothing to do with Windows? It is pretty obvious that the answer lies somewhere within the 1709 update.
I wonder if the Rhino 6 Beta will encounter this same issue. I will be working in Rhino 6 Beta from now on. I will keep you posted.