check for updates ... endless

[FetzBox22]

check for updates in the about tab results in:

for an endless time... (i waited a few minutes)

Update: the same occurs when "check for updates" is used in the General section - application updates.

when closing Malwarebytes with the "X" and reopen it, doing a scan, "checking for updates" is immediately done

(I did already quit Malwarebytes and restart ...)

"checking for updates" before a Threat Scan works the way it should work, if there is no update available.

 

 

 

 

Edited September 16, 2022 by FetzBox22
update

[FetzBox22]

Update: 09.16.2022 10:12

the last update from Malwarebytes was yesterday, there might be something wrong with the update process?

[FetzBox22]

I did reboot my PC and now Malwarebytes got a new update.

And now, I got the same problem, mentioned in my first post, again.

Edited September 16, 2022 by FetzBox22
update

[brad03]

I will give my feedback on this as well. I have been currently testing malwarebytes 5 since invited. Although I don’t have the endless cycle as described by fretz. One day in particular I didn’t get updates for the entire day but this has since been resolved and appeared to be just a “FLUKE”.

[FetzBox22]

Right now, everything works fine with the update process.

 

15 hours ago, brad03 said:

I will give my feedback on this as well. I have been currently testing malwarebytes 5 since invited. Although I don’t have the endless cycle as described by fretz. One day in particular I didn’t get updates for the entire day but this has since been resolved and appeared to be just a “FLUKE”.

Every now and then I noticed that Malwarebytes didn´t get any updates for a half day.

 

 

 

 

 

 

 

Edited September 17, 2022 by FetzBox22
update text

[FetzBox22]

On 9/17/2022 at 11:11 AM, FetzBox22 said:

Right now, everything works fine with the update process.

 

Every now and then I noticed that Malwarebytes didn´t get any updates for a half day.

 

 

 

 

 

 

 

last update was yesterday ...

(since this is a beta test, i look a little bit closer what Malwarebytes is doing - maybe this is/or has been the same for Malwarebytes 4.x and i never cared about it)

[brad03]

I guess this is also being reported in the 4.0 version as well i believe this is a wide spread issue as of now.