skyman52 Posted January 31, 2019 Report Share Posted January 31, 2019 Hi Emsisoft, I noticed in my logs after the most recent auto update to stable version 2019.1.0.9204 that the Emsisoft "CORE" disabled the "Start on windows start-up" setting as part of the update process. This appears odd to me, is this a bug or is these any reason that this setting would have been turned "OFF" when it was previously set to "ON" I assume if left unchanged this would mean that Emsisoft protection would not start automatically after a reboot or power on PC Cheers Link to comment Share on other sites More sharing options...
Cister Posted February 1, 2019 Report Share Posted February 1, 2019 Same for my EAM. Link to comment Share on other sites More sharing options...
Frank H Posted February 1, 2019 Report Share Posted February 1, 2019 Thanks for you feedback. Could you please check the status if the setting in Settings/advanced: Start on Windows startup Thanks Link to comment Share on other sites More sharing options...
Cister Posted February 1, 2019 Report Share Posted February 1, 2019 Start on Windows startup was disabled Link to comment Share on other sites More sharing options...
Frank H Posted February 1, 2019 Report Share Posted February 1, 2019 Thanks. You probably enabled it again. Could you enable debug logging in Settings/advanced, reboot the pc and if the checkbox gets unticked again, pls send me the logs. If the issue shows-up again, I will provide you details per pm. Thanks Link to comment Share on other sites More sharing options...
slopes Posted February 1, 2019 Report Share Posted February 1, 2019 My windows 7 machine, start on windows startup was disabled. My windows 10 machine was shut off for a few days. Powered it up and checked settings before the update and this feature was enabled. Box was unchecked immediately after update/restart application Link to comment Share on other sites More sharing options...
Cister Posted February 1, 2019 Report Share Posted February 1, 2019 Frank, I made a reboot and the checkbox was still ticked. All is OK now. Thanks. Link to comment Share on other sites More sharing options...
stapp Posted February 1, 2019 Report Share Posted February 1, 2019 Even with ''start with Windows'' unticked EAM still starts at next boot. I've reported this in beta forum. Perhaps its a cosmetic issue? Link to comment Share on other sites More sharing options...
Frank H Posted February 1, 2019 Report Share Posted February 1, 2019 37 minutes ago, Cister said: Frank, I made a reboot and the checkbox was still ticked. All is OK now. Thanks. Thanks. Link to comment Share on other sites More sharing options...
skyman52 Posted February 1, 2019 Author Report Share Posted February 1, 2019 9 hours ago, Frank H said: Thanks for you feedback. Could you please check the status if the setting in Settings/advanced: Start on Windows startup Frank, In my case once i saw the log entry that EAM had turned OFF "Start on windows startup" I did then check the feature under settings/advanced as you suggest above and the feature toggle button was also set to OFF (grey) I turned the toggle button back to "ON" and you can see this in the log entry in my original post. I then rebooted my PC to confirm that EAM would auto-start and it did just fine. The windows startup feature also remained checked as "ON" in Settings/advanced. This will be an issue if it is happening to everyone that gets this 2019.1 auto update as they will not realise that the "Start on Windows Startup" feature has been turned OFF ( unless they check logs ). The users will be unaware that anything has changed possibly for weeks until next PC reboot and then wonder why EAM is not running FYI my system is Windows 10 current build 1809. Thanks. Link to comment Share on other sites More sharing options...
skyman52 Posted February 1, 2019 Author Report Share Posted February 1, 2019 As an update, I just noticed that my EAM did another Auto-Update this morning from build 2019.1.0.9204 to 2019.1.1.9207. The update went fine and there were no log entries for features being turned off as with the previous build, so i guess this update may have been released to address the issue Thanks Link to comment Share on other sites More sharing options...
Recommended Posts