Couldn't Uninstall Spyware Terminator 2012

I originally posted in the wrong forum (sorry) about my difficulties with Spyware Terminator 2012. It would not uninstall itself (saying the program no longer existed - if only that were true!) and when I used uninstallers they would render my laptop unusable and I would have to revert to a system restore and begin all over again. I was assured by Max
"It is hosted in MG which means it has been TESTED for malware.
I just downloaded it and scanned the set up file with: Malwarebytes, SuperAntispyware, Comodo AV = all results CLEAN
I installed it and scanned it with the above three programs - all results CLEAN
I then ran a standard uninstall and it was removed fully.
Please don't post inaccurate information."
So when I told him I still couldn't get rid of ST and AVG refused to install when it found ST was running. He then advised:
"My suggestion is to do the following:
1. DISABLE all the features of AVG
2. CREATE A SYSTEM RESTORE POINT
3. Reinstall ST from a NEW 2015 fresh download
4. Use something like Revo Uninstaller, and choose it's highest uninstall method from the three available, removing everything it finds.
5. RESTART your system and then run the Cleaner, and then the Registry Scan > Fix All Issues, with CCleaner Slim.
Your system should now be EMPTY of ST."

That got me part way there, but every time I then ran Zemana AntiMalware it would identify the stflt.sys file created by ST in the driver folder (and not removed by Revo) as a browser hijacker. Whether I quarantined it or deleted it, my computer would then not boot up properly. I would I end up with windows failing to load Win64ShellLink.exe on boot up and refusing to continue. The only way out of it was to do a system restore. Win64ShellLink.exe is a Glary utilities file I am told.
My solution was to use Revo to uninstall as directed above and then let Zemana quarantine the Stflt.sys file. Then immediately use Revo to uninstall Glary to get rid of the the infected Win64ShellLink.exe file then reinstall Glary utilities and that seems to have done it.
Hopefully no one else has this problem, but if so I hope the above might save them some grief. Thanks to MaxTurner for your patience and help.