XIII

Installed EAM 2018.11.0.9073 and booted. For the first time in a rather long time the PC did complete booting with EAM installed. Will keep it installed for a while and see whether EAM works again like it used to in the past. (Note that I won't be using my PC much during the holidays)

No, unfortunately not. Due to this issue I could not use EAM at all (have been using just Windows Defender instead). I'm happy to test it again somewhere next week (too busy this weekend).

Oops: Despite clicking all the boxes EmsiClean did leave most EAM files on my PC, except the uninstaller...

Can't even finish install. Completely locks up my PC again. Uninstall is not working either. EmsiClean to the rescue... Event ID is 1000, application is a2service.exe, and module is KERNELBASE.DLL (10.0.1.17763.1).

I haven't been running EAM (and visiting this forum) because of this issue for quite a while (couldn't work on my PC with EAM installed). I'll put it on my to-do list to check this week.

Any update on this?

As I already posted I had more than 10 GB free. Will check my event log later.

Thank you for that link. That would mean the 10 GB should have been enough... Would there be additional requirements? For example the size of the Windows partition? (I use a small SSD, but it does have more than 10 GB free space available)

8 GB of RAM. I did not see the 1.5 requirement before, so thought a 10 GB page file would be fine.

Even after selecting "Complete memory dump" (to %SystemRoot%\MEMORY.DMP) and setting the page file to 10 GB (and rebooting) the dump file is not created. Instead a 512 KB minidump is written to C:\Windows\Minidump. I did wait several minutes when the counter reached 100% on the manually initiated BSOD (which already took several minutes) before rebooting. I'm afraid I have to give up for now...

The pagefile is currently managed by Windows itself which allocated only 512 MB, but I can temporarily set it to 10 GB manually. I also noticed that "Write debugging information" was set to "Small memory dump (256 KB)"... Which option should I choose instead? Kernel memory dump Complete memory dump Automatic memory dump Active memory dump

Not that I'm aware of (and this PC used to have only 4 GB of memory; 8 now).

Reproduced immediately. Waited for Windows to report 100%, after which it rebooted itself. No DMP created. Worse: EAM is installed, but there's no uninstall option. And the link to emsiclean.exe on the website is broken... I'm stuck!

Ouch: after installing EAM and entering my license code EAM started updating; at 1% it locked up! Unfortunately 1Password was running unlocked, so I cannot share a dump of this state. Going to try again with no App open...

Ran the enable script and will install EAM again. Let's see how long it takes until I have another lockup.

No.

Since you told Alan you did not need a second one I never tried that… I'll put it on my todo list. Anything in particular I should (not) do?

Two more lock ups within 5 minutes. I have to uninstall EAM to use my PC now... 😢 Will follow this topic to see when I can install (beta of) EAM again.

Could be, but then it would be a new issue, which I hope is not the case. I think it's more likely the issue already reported here: EAM locking the PC when it starts.

Huh, why would the old version restart after an update?

This newest beta was the second update this week that locked my PC twice... 😢 The problem in this topic seems more related to not properly starting?

Any update on this? This week the behavior got way worse. Two EAM updates that required a program restart. Both locked up my PC and I had to force a reboot. That boot locked up the PC again and I had to foce another boot. Only then I could start working again (actually in one instance Windows complained that it could no longer boot, but another restart fixed this). I'm close to (temporarily) uninstalling EAM since EAM is currently a bigger risk to losing work than malware is... 😢

I'm already on then beta channel and I do subscribe to the updates feed. I was not aware of the beta feed though. Subscribed. Thanks!

Me too! Had another lockup this morning...

BTW, my computer is a no name PC with a Core 2 Duo (E8400), so it’s not HP specific. My BIOS is even older, but MSI (motherboard manufacturer) does not offer anything more recent.