"Freezing" Win10 updates does not really freeze them. It only delays them, and for I think it's one week tops, else they boot you off-line and Win10 quits working... The updates from MS, while seeming to be the direct culprit, might actually sabotage the video drivers, which is why rolling them back works in some instances. The roll-back overwrites some of the Windows update. Similarly if it's a DirectX issue, putting the old one with the required files in it will overwrite and / or replace the new stuff. Windows comes out with an "update" that trashes the other guy's stuff, and then expects them to get into the new API kit and rewrite and update their drivers. Sort of like you write a procedure in C, calling certain compiler functions, and someone decides that the #standardio.h# no longer needs printing functionality, and they pass that off to a different header file, without telling you ahead of time. "Oh, btw, you're going to have to re-write over half of your entry point coding, since we dumped several of the functions you call in it."
