EOF won't open at all.

[noel]

Hi guys, I downloaded eof1.8RC10(r1337) and applied the 1-2--2016 hotfix, double clicked eof.exe, got some Windows SmartScreen popup that I ignored and chose to run anyway, then nothing. Running on Win 10, tried running in compatibility mode for Win 7 but still nothing. Any help?

[raynebc]

Did you extract the RC10 zip file to a folder and then overwrite its eof.exe and eof.dat files with the ones in the hotfix? When you open it, do you continue to get any error messages or prompts? If you open the log file in EOF's program folder, does it display anything? Is EOF located in a protected location in the filesystem (ie. anywhere within the "Program Files" or "Program Files (x86)" folders or at the root of the C drive? SmartScreen is one of Microsoft's security features, it's possible that it incorrectly labeled EOF as unwanted/malicious software.

[noel]

Yes I extracted the files and overwrote them with the files in the hotfix.

I no longer get error messages or prompts.

There doesn't appear to be a log file in the directory (I assume it's created the first time the program is run?)

It is not in a protected location.


After I execute the program the computer acts as if it's booting the program but nothing appears. Task Manager doesn't list EOF but Process Hacker does.

[raynebc]

I'm not sure how the compatibility mode would affect it showing up in process manager, but honestly I don't have access to a Windows 10 computer to test with. The log file should be called "eof_log.txt" and be in the same folder as the eof.exe program. If it's not there, you could try right clicking EOF and selecting the option to run EOF as administrator. This will tell us if it's a permissions issue preventing EOF from running. I'd also suggest manually having your antivirus scan EOF, and then if it has no complaints, temporarily turning off your antivirus to run EOF just to rule out interference from it.

[noel]

"eof_log.txt" doesn't exist.

Running as admin causes explorer.exe to freeze.

Disabling the antivirus fixes the problem, so that's definitely what was going wrong. Thanks! I'll see if I can add an exception to allow EOF.