After you install BOINC on a new Windows 10 computer and go to tools -> add project

it produces the following error message: "The password you have provided is incorrect, please try again"

We have un-installed BOINC, deleted the BOINC directory under the ProgramData folder and installed again. We have downloaded a copy of the program from the website several times.

The file name looks a little screwy. After all the standard file name verbiage it says "boinc_7.14.2_windows_x86_64__18_18_190117_7d6da0a7.exe"

I have another older copy of this file and it is named "boinc_7.14.2_windows_x86_64.exe"

Anyone got a clue?

Tom

---

A proud member of the OFA (Old Farts Association).

Exit BOINC completely.
Go to the BOINC Data directory and delete the gui_rpc_auth.cfg file.
Restart BOINC Manager.

If this doesn't work, add a password of choice into this file. Don't add an Enter after the password.

---

The filename suggests that you downloaded BOINC from a project supporting the new auto-attach feature, rather than from the BOINC website itself.

"The password you have provided is incorrect, please try again" is the default fall-through error message, shown when something has gone wrong but the developer didn't anticipate and program for the specific failure mode.

The filename suggests that you downloaded BOINC from a project supporting the new auto-attach feature, rather than from the BOINC website itself.

"The password you have provided is incorrect, please try again" is the default fall-through error message, shown when something has gone wrong but the developer didn't anticipate and program for the specific failure mode.

What bothers me is I downloaded that file from the main Seti website.

Tom

---

A proud member of the OFA (Old Farts Association).

What bothers me is I downloaded that file from the main Seti website.

Like I said, a project. SETI != BOINC

Get it from https://boinc.berkeley.edu/download.php if you want the unvarnished version.

I got my friend to copy a "standard" named copy of the install from one of his other windows machines.

We un-installed Boinc Manager. Deleted the ProgramData/BOINC folder so we are "clean" right?

Then we installed the boinc setup copied from another apparently working windows.

And got the same password error.

Shut down boinc manager, deleted the

Exit BOINC completely.
Go to the BOINC Data directory and delete the gui_rpc_auth.cfg file.
Restart BOINC Manager.

If this doesn't work, add a password of choice into this file. Don't add an Enter after the password.

As recommended.
Re-started the Boinc Manager.
Got same password error.
Shut down Boinc Manager
Examined the ProgramData/BOINC folder.

There is now no "gui_rpc_auth.cfg" file there.

Assuming we can locate that file again, what password should be put in there? There is no evidence that the program knows what the Seti email address of my friend is (that I have found, yet).

Thank you for your attention and ongoing advice.
Tom

I have successfully remoted into his system and except for not being able to do anything after I run the Boinc Manager, I have been able to examine the files in the ProgramData/BOINC directory. Should I be looking elsewhere?

BINGO. The password in the file is the "Weak Account Key" on the Seti website. And it appears to have directions for how to "attach" to the project without using the Boinc Manager Gui.

Will try that trick next.

Tom

---

A proud member of the OFA (Old Farts Association).

Why try the hard things when the simple work
Get a copy of BOINC from the URL Richard provided https://boinc.berkeley.edu/download.php
Delete the BOINC data folder
Install BOINC using the copy you downloaded.
Run BOINC, select "add a project", and add as a returning user.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Why try the hard things when the simple work
Get a copy of BOINC from the URL Richard provided https://boinc.berkeley.edu/download.php
Delete the BOINC data folder
Install BOINC using the copy you downloaded.
Run BOINC, select "add a project", and add as a returning user.

We did, multiple times. Multiple times. And got the same error as previously reported.

I have since had PM where it turns out he wasn't running as an Administrator when we were installing it, and the problem went away once he was.

Tom

---

A proud member of the OFA (Old Farts Association).