Forced restart within 10 minutee??

[mike41Old]

Today was the first time I've encountered a forced restart within 10 minutes.

I lost work, open windows, etc.

I was so shocked.  Never seen this before, and WHAT SOFTWARE DOES DOES THIS TYPE OF TIMED FORCED RESTART?     "Malware":  thats who.   I spent about 45 minuted researching this, I was sure my Malwarebytes had been corrupted/replaced with Malware itself, and now i was going to get a rootkit installed.

I am equally shocked to find out that this is your programmed behavior.  I've been recommending Malwarebytes to countless users for years and years and years.

10 minute forced restart leaves such a bad taste in my mouth.

Can't help but feel that the malwarebytes i have known and loved for forever is something different now.

And, who is so stupid  to require a 10 MINUTES forced restart without any prior warning BEFORE INSTALLING.

That's like going up to a car driving down the highway at 120 KM per hour and saying, In 1 second I am going to pull  all your wheels off (Sorry if you don't have enough time to stop first)

Thank God i did not do the install during the day when i was working, trading stocks, Video conferencing, etc.

 

 

 

 

[exile360]

Greetings,

Thank you for your feedback, it will be submitted to the Product team for consideration.  I am sorry for any inconvenience the forced restart might have caused; that said, there should have been a warning prior to the installer starting indicating that a system restart may be required and to save any work before proceeding, at least that's what I noticed when prompted to install the most recent upgrade a few days ago when it was released (I don't personally know if the pop-up is shown to all users/under all conditions, so it may be that you did not receive this pop-up/notification).

I am personally not a fan of forced reboots either as they can be disruptive, however I believe the logic in doing so is to keep the system protected since, when components are awaiting replacement due to being active in memory, the system is left unprotected until the system is restarted, though that is simply speculation on my part.

If you have any further feedback, suggestions or issues please let us know.

Thanks

[mike41Old]

I have seen the message before such as you  "MAY" have to restart from many, many, many programs over years an years.  No other program that I can recall (ever) finished installing and forced a restart, let alone in ten minutes.  TELL US BEFOREHAND THAT IT IS A "IMMEDIATE FORCED RESTART"

[exile360]

I've actually experienced similar behavior multiple times with multiple apps (and I wasn't happy about then either).  I guess the reason for the ambiguous wording in the initial dialog is due to the fact that a reboot is not always required; it depends on whether or not it is needed for the purpose of replacing components that are locked/in-memory, which doesn't always occur.  Again, that's just my own speculation; I have no control over the installer's behavior, I just help out here on the forums.

Either way, your comments/feedback will be provided to the Product team so that they may consider it and factor it into their decisions for the product.

[davefox]

I'm with Mike on this one.  A forced reboot is completely unacceptable, and I'm at a loss to understand how Malwarebytes could have thought otherwise.

I'd also like more guidance on whether a reboot will be required.  I've just upgraded my 5 systems.  Four did not require a reboot.  The fifth one did, and I have no idea why that one was different.

I like your software, but the upgrade process leaves a very sour taste.

 

[Porthos]

1 hour ago, davefox said:

I'd also like more guidance on whether a reboot will be required.  I've just upgraded my 5 systems.  Four did not require a reboot.  The fifth one did, and I have no idea why that one was different.

The are many variables. Most likely an open browser or program. But that is why the following is shown during the upgrade install.

 

[davefox]

Thanks for the reply.  But if I had saved my work and closed all my applications before starting, I would have wasted my time in 4 of the 5 cases.  And the one system that did need the reboot had fewer applications running than the other four, and was not running any unique application.  I had figured it was the least likely to need a reboot, in fact.

In the past, I've also been notified of a new version on one or two systems but not the others, even though they were all running the same version.  It's just unpredictable.

So I've just turned off "Notify me when a new version becomes available" and will check for updates manually when I do my monthly Windows updates.

They still need to get rid of that forced reboot.

 

 

[Porthos]

32 minutes ago, davefox said:

I've also been notified of a new version on one or two systems but not the others, even though they were all running the same version. 

The company has program updates pushed through the normal updater (the one that checks for database updates) metered in such a way that it is throttled so not every user is offered the new build once it has been released, so it becomes a matter of probability and is somewhat random.  This means that you might be offered it early, or it might take a really long time before it is offered to you, it just all depends.  Basically a luck of the draw kind of deal.

[creamycheese]

This really makes me regret buying another year.

I was in a long transfer 3 hours in and I decided to install malwarbytes update due to a pop up. No problem BUT wait there is a 10 minute forced reboot. Now guaranteed one of my files is corrupted.

Forced reboots are and always have been a bad idea. Windows does it and everyone flips out. You should know better.

Stupid, Stupid idea.

[creamycheese]

As per the notification it states might and usually that is when it is chosen to be done by the end user. 

 

It does not state it will force a reboot.