UE4 vs Other Engines (read before deleting, please)

anonymous_user_2abc45731 · May 20, 2015, 6:21pm

franktech;295920:

I chuckled when I read this as it sounded like some of the late-nite PC voodoo call-outs I’ve had from family and friends… In those cases Symantec & McAfee etc botched their updates and / or fried the uninstaller. Last year both companies admitted that the retail end of the products only work some of the time too, comforting, eh? Anyway if you can’t find a official course of action on the AV forums, here’s a few approaches to try for dealing with rogue AV’s…

If you don’t have an original boot CD (its OEM only), but you can get an old copy of Win2000, it can boot into a repair console whereby you can rename / delete the AV files that are causing the problem. Occasionally you can do this too by booting directly into the command prompt with networking disabled (F8 at start-up ). The other approach is to download a boot CD or Bootable USB image with DOS4NTFS which will also let you directly into the file system… If all that fails, take out the drive and buy a kit from a Radio Shack (RIP) / Maplins type outfit that will connect the drive via USB to a separate PC.

You need to know which files to edit, but that’s a separate project. Sysinternals Process Explorer can help here as can the insightful diagnostic tool: Depends.exe… As I read back this stuff is all a bit under the hood… But try out the simpler stuff first. Good luck!

I read that wrong… I thought he said that the whole computer was locked! Looks like I was wrong…