i just recently installed the new BOC build 4.26… i don’t use “automatic updates”, but check for updates manually…
when i “check for updates”, about half of the time, if not more, the BOC update-window will pop up, but it just hangs there, “frozen”, not doing anything… i don’t get any message, like “downloading updates”, “no updates available”, “connection failed”… it just hangs there… i can’t close the window, either, but it will eventually close, after waiting about 4 minutes… usually, the update-process will run normally if i run the updater a second time after it has failed the first time…
i am not sure if something on my computer is causing the problem, or not…
i had “task manager” running during one of the hanging-updates and, so, i could see that no process was “hanging” while the BOC update-process was running ie no process was “hanging” and using 99% of “CPU”…
update: i just ran the updater again, and it hung, again… i then ran the updater again and, that time, the updater worked normally…
i have run the updater a few more times since making the original post… the first time, it worked normally, but, the second time, it hung, again…
like i said, sometimes it works, other times it hangs…
i use the new “antivir 8” with its new “webguard”, and the update-problem might be related to that, however webguard has not seemed to cause any problems with updating any of the other programs that i use…
i am not having any problems with the updates, now…
i think that the reason BOC’s updater was “hanging”, before, was because there was a problem with the update-server, where the updater was “hanging”, waiting for a response from the update-server, but it wasn’t getting one…
Great news that you aren’t having any problems now.
For me, when I had re-installed it, I had to temporarily turn on Windows Firewall, run the update and then turn it off again before mine worked properly. You can, set the automatic updates to whatever time period you desire. I’ve got mine set to every 6 hours but that’s just me and my paranoia LOL…
Let us know if we can help you with anything else…
They’ve been reworking the datacenter as demand for the new “http download” goes through the roof … I think the traffic management is improving by the hour, but it’s still a “learning curve” for the crew.
i logged some of the internet-connections that were made when updating BOC…
i saw that, when the updates are successful, there are two connections logged for each update…
successful updates use connections to ip addresses:
91.199.212.132
208.122.24.146
91.199.212.132
72.20.6.62
(two connections for each successful update)
when the updater (briefly) connects to ip address 85.91.228.132, the update-process fails… there is a problem when the updater connects to ip address 85.91.228.132…
Hi Eric, My setting for Auto-Update is 7 hours. Does it mean that I am one hour less paranoid? Yes it does! (:WIN) Cheers
Hi redwolfe_98,
I didn’t pay attention lately to the addresses since I never experienced BOC update problem, but in the past I was looking at that. Interestingly don’t remember 85… What I am getting now is mainly 91.199.212.132 and in rare occasions 72.20.6.62 but still cannot see 85.91.228.132 ???
The question for developers is: why BOC just fails as in your case if that address was not accessible but not trying to connect to other available addresses? or I’m missing something?
Below is some info about addresses
