With a proper backup scheme, the negative consequences of buggy Microsoft updates are usually reversible and fixable. Or to the *many* victims of the Petya ransomware attack not long after, which exploited the *same* vulnerability and would have been prevented by the *same* Microsoft update. Tell that to the UK’s National Health Service, many of whose trusts’ Windows 7 computers got locked up by a WannaCry ransomware attack *two months* after Microsoft released the update that patched the vulnerability it exploited. Now You: Did you check? (via updates are worse than the viruses.”
It is unclear but it is probably a good idea to check the tasks and folders on Windows 7 or Windows 8.1 devices to make sure that these tasks and files don't exist. Is Microsoft preparing for another Get Windows 10 campaign? Is it a bug? Leftover files on a system that were never removed completely?
Microsoft ended the Get Windows 10 campaign in 2016 and there is no reason to keep scheduled tasks or files associated with it on the system. What is puzzling about all this is that GWX should not be running anymore on the system. Renaming GWX.exe did not work either what worked was renaming the GWX folder but it is too early to tell whether the renaming is enough to block GWX tasks from running on the system. The folder C:\Windows\system32\GWX displayed that most files were from 2015 including GWX.exe. Two tassk, refreshgwxconfig and launchtrayprocess under Microsoft > Windows > Setup > gwx, had been disabled by Horowotz in the past. The task were MachineUnlock-5d, OutOfIdle-5d, and OutOfSleep-5d.
These tasks were never execute, however, unlike the three tasks mentioned above. Horowitz discovered three additional tasks in the same folder.
0 kommentar(er)
