This is related to How does one Blacklist a patch based on Knowledge Based/KB number? and How to add a Deny ACE for TrustedInstaller?.
The Get Windows X malware has returned (again) on two Windows 7 machines and Windows 8 machine. I have previously removed it 5 times or so (per machine). After the last removal and I pre-created the folder it installs itself into and then placed a DENY ACE for both SYSTEM and TrustedInstaller. According to Microsof's documentation, this should have stopped it from installing and executing.
How did the malware install itself given it was denied access?
This is absolutely amazing... The machine was off for about 6 weeks, so I had to perform two update/reboot cycles. The malware installed itself twice in one day even though it is denied access to the folder!
The second update/reboot cycle was for KB3102429. Notice it claims to resolve issues in Windows - it does not state its marketing nagware or malware.