Can confirm that. Oh boy... so much about forced updates. Hope they're going to test them a little more intensive once it is in the wild... EDIT: Quick workaround if you need to access adapter properties: you can go to network and sharing center (old control panel), click on your connection to view the old fashioned status window, and click properties there.
I have right clicked on each of the installed updates multiple times under control panel>Programs>Programs and Features> installed updates.....It does not crash....Neither does clicking uninstall and then canceling. I am not saying it doesn't happen to you. But it does not happen on my machine and that update along with all others are currently installed. Neither does the other issue of the closing of network properties effect this machine. So it may be the update that causes the issue but there is also some other issue involved.
I have AMD graphic card , which graphic card do you have? Maybe this windows update double time click bug is only on AMD graphic card!
Well, the fact that many people seem to encounter this issue after they installed the update (it wasn't there before) it's a strong indicator that it must be somehow related to it. Maybe you're lucky to have a configuration that is not affected by this bug. Probably not. Got Intel graphics here, same bug.
i updated the KB3074681 and went through successfully. But i noticed boot startup is bit slower which might be related to one of updating some driver files as my screen scaling went oversize for a few seconds during startup then went back to normal. Lastly, my regional settings from Simplified Chinese back to my original regional settings. UBR is now 16399 after update.
I have another machine with Windows 7 installed and Windows 10 installed in VMware. I just ran that and installed the update on it. When installing the update the graphics screen flashed. I rebooted and tried the it on that machine. Explorer crashed in the VM Windows 10. So it probably does have something to do with the graphic card.
I don't see why it should be graphics-related as everything else concerning Explorer seems to work fine. According to event viewer, the module in question is shell32.dll (just for info).
