I recently updated to Windows 10 21354.1 and now BOINC no longer does any work and just says "Reconnecting to the Client". When I go to File -> Select Computer and then type 127.0.0.1, I see my *'ed out password show up, but upon pressing OK it still says "reconnecting to client". I'm currently running BOINC Manager 7.16.11 (x64), and I'm not sure if I've installed BOINC as a service or not. I attempted to review my logs but pressing CTRL+Shift+E doesn't seem to do anything when I have my BOINC Manager open.

When you have the Manager open, can't you pull up the Event Log from the Tools menu dialog? Shouldn't have to use the key command for the Event Log.

Sounds like the Windows update messed up BOINC file permissions or directory accesses where the gui_rpc_auth.cfg file resides.

Unfortunately I went ahead and rolled back the Windows Update and now things are working as intended. I'm planning on updating again this weekend so if an issue arises, I'll post my logs.

I upgraded to Windows 10 21359 and it looks like it's still broken. Unfortunately I cannot get the logs in the tools menu either, it appears greyed out for some reason. Looks like BOINC is completely busted in this new version of Windows 10...


image hosting

The first thing to troubleshoot is "does the Client even start" before addressing the Manager problem. If the client doesn't run, then the Manager has nothing to connect to.

I would try running the client standalone in the Windows Terminal so you can see the client messages.

cd to C:\Program Files\BOINC and then run the client with boinc.exe. All the messages that would normally go to the Manager Event Log will be displayed in the Terminal.

You are looking to see if the Client even starts and also if it continues running and processing tasks or does it abnormally exit.

Known performance regression with the latest update.
https://www.extremetech.com/gaming/322040-a-new-windows-10-update-is-wrecking-game-performance

It does appear that the BOINC client itself is opening but then closing repeatedly. This is persisting on the most recent Dev build, 21364

My issues were occurring a few weeks before this particular KB hit, so I don't think that's the issue...

It does appear that the BOINC client itself is opening but then closing repeatedly. This is persisting on the most recent Dev build, 21364

What is the reason for the client quitting? What are the error messages from the Terminal?

Hey Keith,

I had reported this issue to Microsoft also as part of the Windows Insiders feedback, I'm not sure what the issue was but this appears resolved as of the 21370 Dev update that just got pushed. I'm waiting to hear back to see what the issue was, but it sounds like it was something from the Windows side of things.

Thanks for your help!