Manjusri108

after update computer won't boot

Recommended Posts

Pinned posts

Hello Libor, thank you for your feedback.

As I'd mentioned, "We're still unable to replicate the issue". Up until just a few minutes ago, we have not been able to replicate this issue at all, whatever we tried, and nobody had been able to provide usable debugging information. Those who were willing to try ended up having the problem go away prior to any information being gathered, so we were left with a problem we could not see to diagnose. Impossible as you might imagine. So no, we're far from asleep, we have just not been able to get any usable data other than "it happens", and that it's with current Emsisoft Anti-Malware, Comodo Firewall, and Windows 7 x64.

By "up until this evening", I mean that I just had a virtual machine with Windows 7 x64, Emsisoft Anti-Malware, and Comodo Firewall (free) lock up well after the desktop was loaded. I'm going to try gathering information if I can, if the problem repeats itself. So, some progress possibly.

I'll post back here with workaround instructions should I find any, and update with fix status as well once that comes.

Share this post


Link to post
Share on other sites
UnPinned posts

> Frank is actively working with you, correct?

I'd hope so, but I haven't heard from him for a while.  I didn't post in this thread to try to get that other problem fixed sooner (because it's not a show-stopper), but because I thought there might be a connection to the hangs you were looking into, if your hangs were to do with file explorer's initialisation of its context menu handler code.

Share this post


Link to post
Share on other sites

Hi havredave,

I have a client with this problem as well, yes Windows 7 and Emsisoft (no Commodo FW).

They are keen to have someone from Emsisoft to look at the issue, from what I can see you have not have the chance to gather more information apart from "it happens" etc.

We have three computers down, they are more than happy for Emsisoft staff to look at them, gather more information and come up with a solution.

We're in Sydney UTC +10

Thank you.

Bernardo

Share this post


Link to post
Share on other sites

Adding to my original post:

To: [email protected]

Hi there,

We have been hit with the dreaded 2018.3 update on three computers (75 in total).

I've posted on the support thread "after update computer won't boot" by Manjusri108, havredave is the Emsisoft person looking at this matter.

Three computers affected, here is the explanation from the client:

Bernardo,
I am at my wits end with this.  I am so fed up with Emsisoft – you should be able to sue them for damages.

We are at the point where some machines must be shut down as they have ground to a standstill.  About 50% of them don’t come back up.  Of those about 50% can be repaired on startup or using the USB boot memory stick.

Two of these had issues on reboot during emsisoft removal that required about an hour each to run through the repair options.

We now have two machines that we can’t get running, even using startup repair and the USB drive.  One of them says ‘can’t repair this computer’, and the other goes through the windows introductory boot screen, goes to a blue screen and then drops out again.

For these two computers can you either:

1.       Lead me through something else I can try; or

2.       Get someone to come out and fix.

Make that three now!  Another one went while preparing this email.

Share this post


Link to post
Share on other sites

Well my theory that is completely lacking of any debugging attempts, was based on the idea of service startups and if comodo loaded and hooked something eam wanted to hook before eam could or not. Say if it did hook fast enough, eam could hang, and if comodo took too long, it would be ok, or vice versa, could be eam hooking and comodo throwing a fit. The best thing to compare at a code level is what exactly was changed between versions, and I assume they have a version repository so that could be reviewed. Could easily be both trying to hook the same thing or something one or the other are both trying to protect.

Share this post


Link to post
Share on other sites

@endevite: yes, this I meant by saying Emsisoft programmers should know what they did in the last major EAM update - they should be able to compare code before and after this update to find out. Because on my comps Comodo and EAM coexist more than four or five years no problem. I could ask Comodo too but it's fair to say Comodo is free (I use their free firewall) and EAM is paid - for me it's slightly different. First I ask for help where I paid money (and cannot use that product for two weeks just now), on second place I could beg on the helpdesk of the free product...

And, well, I can see this last update works strangely not only on comps with Comodo installed so maybe the problem is bigger.

Share this post


Link to post
Share on other sites

bmunoz: Please email [email protected] That issue is not related to this thread at all, which is specific to a Comodo Firewall conflict. The issue you're having might be a known one that is not related in function or symptoms to this particular one. When you email, please let me know the brand of the machines they're using. If this is what I think it is, it's actually pretty easy to fix for an experienced tech, not so much for others.

endevite/Libor: I wish it was as simple as reviewing changes. That's a great idea in theory, but given how complex the systems are, and I'm not just talking about our program here, but our program and all of the things it could possibly interact with, it's not quite that easy. We do know roughly where to start of course, but that doesn't mean that's where the issue will be found. I'm not giving up on testing/trying.

Share this post


Link to post
Share on other sites

Well, either way, whatever is the cause, hoping I don't need to try to help and debug to spot the faulting point (especially since I am having fun problems with a middle ear infection and my right tonsil where I should be sleeping it off for a few weeks, it was bad and had brown foul sludge draining, so lots of antibiotics).

I do hope the delayed channel stays at the build it is until this is resolved because I cannot afford to run only eam on the networks I manage and firewall/hips control is the more important feature at the moment from comodo. I really do hope this gets worked out as windows firewall is insufficient and I went with eam due to it having passed a battery of detection testing when I did my yearly evaluations and how it worked with comodo firewall. (I do wish eam had a real firewall management system both with traditional ip/port rules and application rules, then I wouldn't have to fuss with comodo anymore nor would many users who want both firewall control and a good anti malware suite.)

Share this post


Link to post
Share on other sites

'Delayed' is not an automatic promotion of older versions. We only pick those that have exhibited better stability.

For a real firewall management system, you might think about evaluating one of the Windows Firewall front-ends. Windows Firewall is actually pretty good, albeit 'interesting' to manage. A lot more products use it as their back-end than I ever thought, until I looked into it.

And yes, I hope this gets worked out soon too. Now that we've figured out and dealt with the issue specific to HP accelerometer (hard drive freefall protection) software, there might be more resources available.

Share this post


Link to post
Share on other sites

> Where do we find details of the specified "HP accelerometer (hard drive freefall protection) software"?

Presumably it's part of the firmware in some HP laptops?

Share this post


Link to post
Share on other sites

Leks: If you have a Windows 7 or Windows Server 2008 R2 machine (which uses Windows 7 codebase), and it's an HP, and it's running or has installed HP's drive protection (accelerometer, free fall protection) software, please email [email protected] and let us know. If that particular HP software does not exist on your machine, or it isn't an HP, or it isn't Windows 7 codebase, the problem should not exist. There have so far been no reports of any version of Windows, other than those, having the issue. Two of the affecting HP programs are named "HP 3D Drive Guard" and "HP ProtectSmart Hard Drive Protection". That is not to say that with those installed on a Windows 7 codebase machine the issue WILL happen.

I will not give further details or help about that in this forum topic since it will derail the original topic (that I'm still working on), plus we need to handle these individually in some cases. Depending on how the machine was treated after affected, IF affected, what we need to do for that particular machine might change a bit.

To keep this topic on-task for those having trouble with Emsisoft Anti-Malware and Comodo Firewall, please understand that I'll clean up further posts not related to that issue. I'm still very willing to communicate and have more details - just send in an email.

This is only for housekeeping and staying on-task for this forum topic.

Share this post


Link to post
Share on other sites

Only quick question: is anything new with EAM and Comodo Firewall problem? After three weeks of nonfunctional EAM (on W7 with Comodo Firewall) it seems nothing is happening. Is Emsisoft still interested in this or is it necessary to look for a new antivirus program?

Share this post


Link to post
Share on other sites

 

5 hours ago, Libor said:

Only quick question: is anything new with EAM and Comodo Firewall problem? After three weeks of nonfunctional EAM (on W7 with Comodo Firewall) it seems nothing is happening. Is Emsisoft still interested in this or is it necessary to look for a new antivirus program?

 I hope it's still being looked into, I am getting grumpy complaints from clients who are still stuck in delayed release.

Share this post


Link to post
Share on other sites

I have the same problem too, and similar backgroud: Windows 7 Home Premium 64bit + EAM (licensed) + Comodo FW 10.2 (licensed, only firewall no internet suite) + Avira (licensed, only antivirus no internet suite and firewall management disabled).

From last update of EAM, my computer boots but Windows remains into infinite waiting after login, sometimes screen goes black with mouse cursor active and nothing on it, sometimes black screen plus prompt window with cmd.exe waiting and blinking curson inside.

Only reboot into safe mode and restore previous configuration or remove EAM works, and let  me use PC again.

After reading last suggestions, I tried this: installed (again) EAM, opened Comodo control panel, disabled Emsisoft program folder control into "Auto-Containment" and "Viruscope" sections (adding rules with + button) and ONLY NOW reboot the machine.

Results: boot...login  screen...wainting...black screen with mouse cursor.............after waiting 1 or 2 minutes without results, an hard reset (ctrl+ald+del not working), boot, login, ALL WORKS!!!!


I hope this is useful for everyone else

Share this post


Link to post
Share on other sites

Yes, I switched over from what I typed earlier, and have been using EAM with delayed release with updates enabled. It is working that way. I still have not tested to see if the software works correctly in normal mode. I am waiting for word that it is fixed.

Could you please explain delayed release a bit better? Is it current signatures, but the older program version? Or are the signatures delayed, too?

The tech security world is going crazy this year. New vulnerabilities, good updates, bad updates, including with MS updates. Good luck, all!

Share this post


Link to post
Share on other sites

Door Knob,

This is a simplification, but delayed is the most stable of the last month's releases. While 2018.3.x is current, 2018.2.x's most stable version will be delayed. Again, this is a simplification and it's not guaranteed to follow that scheme at all. Yes, delayed uses current signatures, but may be missing features, even those that protect the computer better in some cases. Yes, it is current signatures in a slightly older program version.

Back to the Comodo Firewall issue: On my test computer, I'm using stable, currently 2018.3.1.8572 on Windows 7 x64. I just put in a few Windows updates. I also updated Comodo Firewall. As of this moment, the problem isn't happening to me with no exclusions set up anywhere, and both programs running with everything enabled that would be by default with the Comodo installation options I chose, mentioned earlier. I have full logging enabled though, even beyond just turning on debug logging in-program. Hopefully I'll catch something. Note though that several changes were made in the latest stable, and one of those may have had an affect.

Share this post


Link to post
Share on other sites

It didn't work! At first reboot, after a first black screen, it seemed to work fine. All worked for hours until switch off.
Yesterday, the sequence:
-at first boot, login and after a black screen with mouse pointer on. Again.
-Hard reset, login, black screen+mouse pointer.
-Hard reset, login, windows desktop but mouse pointer locked in waiting circle and click inactive.
-HArd reset, login, black screen.
-Hard reset, login, windows desktop, mouse active, one click on browser icon, infinite waiting circle mouse pointer.
-Hard reset, safe mode, removed EAM. All works fine until now, with two or three reboot.

And now? There was a signature update during machine working; a new bug?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.