Malwarebytes Update - Not happening

[#1]

Has anyone else found they are unable to obtain a connection for updates. This started a few days ago. The update window is there but nothing happening.
All other internet activity is fine including accessing their website directly.

[#2]

Mine updated yesterday, database version 1718

[#3]

I'm still on 1710.
Is that the free version you are using.
I also see that, with the last update - I think, I now do not have any choice of servers to update from whereas, before, there was a choice of two.

[#4]

Mine is the full version 1.33
I manually updated this morning to 1725.
I don't see an option to select update servers.
Maybe you could try reinstalling it to kick off the updates again.

[#5]

I was on 1.30 and have just updated to 1.33 no problem

[#6]

I've just had to do a system reboot and all is now fine.
I am wondering whether the previous update had required a reboot which I had forgotten to do or just a simple glitch which a reboot resolved.
Edited header to reflect problem now resolved

[#7]

Problem has re-appeared. No other internet issues but MWB does not update again. I have database version 1724. I get the update window but nothing happens
I will add that MWB responds and works in all other areas. It is happily running a scan now.
Edit: Changed header again 

[#8]

I saw this in the "help" run this from the commandline
mbam.exe /parameter
(where parameter is one of the following)
/runupdate: allows you to update the program without displaying result dialogs.

[#9]

Thanks Santiago
After reading the above I decided to try the /updateshowdialog parameter after closing down MWB.
Would you believe it - it updated fine while showing the update window. I now have database 1727.
Subsequent attempts using the usual interface gives me the expected 'You have the latest database version'.
Coincidence after using the /updateshowdialog parameter or did it fix something?
I'll try another update later and report what happens.

[#10]

Might have fixed itself

[#11]

Hope so.
Just did another update attempt and now have database 1728.
I'll not mark this as resolved again just yet, though

[#12]

OK so now you are ahead of me on updates!

[#13]

It seems to take a little while to get going but does get there.
Just updated to 1728.
If you are having trouble resolving the domain might be worth flushing your DNS resolver cache (I turn the darn DNS client service off anyway)

[#14]

erm, techguy, I thought you were supposed to be studying now

[#15]

No good studying the theory without seeing how it works in the real world 
Truth is cant keep away when I'm finished for the day
Think I spend longer on here than any other forum I'm a member of.