You are not logged in.
No idea why the Epic processes aren't getting killed on close. That's odd as is this setting issue. We'll test it.
The default Windows Chromium behavior is that one process does run checking for updates even on close -- so that should be the case for Epic for Windows. But yes, all the other processes should get killed on close. It could be antivirus software interfering with Epic or something?! Odd!
Offline