I, as usual, downloaded and installed the update to 8.2.9 when it appeared. It did not restart BOINC. Rebooting also did not start BOINC.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

In reply to adrianxw's message of 4 Apr 2026:

I, as usual, downloaded and installed the update to 8.2.9 when it appeared. It did not restart BOINC. Rebooting also did not start BOINC.

Are you Windows or Linux?

It is possible that the lock file was not correctly deleted, in Linux it is in the Home folder and is called Boinc-xxxxx where xxxxx is, I think, $User.

Curious. Before the update, I'd start BOINC Manager and just leave it open top left of my screen to just see what was happening, it rarely needed any action. Now, after the last update, I start it, and it sits there. blank, BUT, leave it for a couple of minutes, and it returns to its normal display of jobs running and waiting. So it is running, but that delay is new and repeatable. <edit>Sorry, it is a Windows 10 system.</edit>

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Check the log. You will clearly see a delay between timestamps. That might explain what exactly was BOINC client doing in that moment.

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

Where is the log file? I just did a search, but nothing in the BOINC directory looks like a log file.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Check journalctl.

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

Windows 10 system.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Ah, sorry. Then in your BOINC Manager check Tools -> Event log

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

Whatever was causing this issue seems to have "gone". I've just rebooted this system, BOINC started by itself as usual, and projects have downloaded work. All is back to normal.... perhaps. Something else I did was close my VPN before the reboot, and have not restarted it yet as I only rarely actually need it, it just sat there routing my connection to somewhere else, (sorry, I can't remember where it was set to earlier).

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.