I'm not familiar with the bug reporting practices, so I have not personally done any additional measures to inform this problem. Maby the development team doesn't even know that we finns are suffering...

They know and problem has been fixed. Boinc version 7.0.30 and later will work.

I'm not familiar with the bug reporting practices, so I have not personally done any additional measures to inform this problem. Maby the development team doesn't even know that we finns are suffering...

The project team are aware of the problem, and have made a correction - too late for version 7.0.28, unfortunately, but included in version 7.0.31, currently being tested.

What I haven't seen is any attempt to "harden" the translation handling system, so that typos like this don't result in the complete launch failures described in this thread. It would be far better if a badly-formed translation was handled by:

* warn (error message in log)
* ignore (use untranslated form)
* proceed

I had this same problem...

And solve is...

Run regedit -> HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager

Check language value, if it is 0 change it to 1.

Same problem every time for first install in version 7.0.28.

Has this been reported to BOINC bug reports?

Yes, it was reported and fixed in 7.0.30, so why not go and get 7.0.38 instead? I am pointing you to the Change Log thread, where I put in links to specific releases. My post will point to the log for 7.0.38 for Windows test release.

---