I had a bit of a bug which was demanding money for a problem on the computer that did not exist. I have since deleted it and since the virus was nasty I had to do a system restore. Before I did that I could tell that Boinc was having problems and literally downloading and uploading corrupted files at an incredible rate. I suspended its' operation and did a reset of the project since all the files were now reading as corrupted. I had to uninstall Boinc and re-install it. I am now getting a message saying it is communicating with the client. It has been doing that for hours now. I cannot do anything with the manager without that message coming up. I have re-installed Boinc again with the same result.

Any advice?

---

Make sure BOINC is allowed to pass through your firewall again.
Copying an old post of mine:

Normally this happens automatically, but sometimes you have to help by hand.
boinc.exe and boincmgr.exe need to be able to talk to each other on TCP port 31416
boinc.exe needs to be able to talk to the internet on TCP ports 80 and 443.

Also make sure, in Windows Task Manager, that boinc.exe is actually running. Also check the processes of all users.

And from another post of mine:

Please check in Windows Firewall, Exceptions, if boinc.exe and boincmgr.exe are showing there. If they aren't, add them

Start->Control Panel->System and Security->Windows Firewall->Allow a program through Windows firewall;

Boinc.exe may be showing as just that, or as BOINC Client.
Boinmgr.exe may be showing as just that, or as BOINC Manager.

Click Change settings, then when boinc.exe and boincmgr.exe are in the list, add a check mark in front of them and one for Home/Work (Private).
If they aren't in the list, click "Allow another program", browse to C:\Program Files\BOINC\ and one by one add boinc.exe and boincmgr.exe then add the check mark in front and at Home/Work (Private). When done, click OK at the bottom. No need to reboot or anything.

---

Unfortunately, uninstalling BOINC does NOT delete all of the executables and data files that have been downloaded, but the reset should have taken care of that.

The BOINC Manager (BOINCMgr.exe) not being able to communicate with the BOINC daemon (BOINC.exe) is caused by an inability to use http port 31416 on the local host. This can be caused either by a firewall setting being incorrect, or by more malware that is using port 31416 for something.

Check to make certain that BOINC.exe is allowed to act as a server on port 31416 and that BOINCMgr.exe (and BOINCcmd.exe) are allowed out on port 31416. This is done for the local host only for local control or the LAN for remote control from other computers on the LAN.

If BOINC looks like it should be allowed through, you may have more viruses on your computer (possibly a root kit that needs to be removed by MalwareBytes).

---

BOINC WIKI

Thank you for the help! Ran some more scans on the system and while I did not anymore virus I did find what was blocking the communication. I am (rather the computer is) happily crunching away again.

Part of the problem is there are so many programs that seem to be all to willing to assist a user (for our own protection ...lol) that it all gets out of hand at times. I am once again in charge of the machine ...or am I?

---