As if relevant to the members, a new BOINC public release is out, 7.6.6. for Windows/Linux, 7.6.7 for Mac. The 'official announcement at http://boinc.berkeley.edu/dev/forum_thread.php?id=10459

No word on W10 in the release notes, but from some reports previous versions would report this OS as W8 or earlier. Not that it's important for the results, except it potentially warps the error analysis and 3rd party statistics. On those, the show is at this time

# 12 Microsoft Windows 10 5740 1,676,898,640.59 3,143,714.57 292,142.62 547.69

5740 devices in a short period already blasted past Android's 62506 devices

#16 Android 62506 304,682,602.20 523,951.51 4,874.45 8.38

Anyway, been running 7.6 for longer in test, upgraded from W8 to W10 and except for a little efficiency loss [started big but with driver and fixes being updated after release now on 98.7% for OET1 from before 99+]. [Did not look if it said W10 in the event log]. Hardly run W10, just a test/support set up, mainly the multiboot is in Ubuntu when on... That's not to say W10 can't reach that efficiency efficiency of 99.7% but Linux eats the OET+FAHV projects twice as fast, and it comes for free too, always.

BTW, do think twice before going for the Virtualbox version offered as download. It's big and the VM is only used by very few projects. Another layer of software eating cycles.

hmmm
hmmmm
and more hmmmmm

So you tick the options not to sent [supposedly anonymous] data to MS on usage, failings etc. Seems W10 will ignore that and still does, http://www.independent.co.uk/life-style/gadge...l-it-not-to-10453549.html

They'll claim an oops-bug of course [but the Smuckenburgs are everywhere]

Meanwhile there's reports of W10 sending weekly reports to parents... most very amazing... someone must have set those parental controls, or?

One of the updates I saw on W7 was "To improve the migration from W7/8 to W10"... LMHO.

Actually I've hidden the W10 ''upgrades'' on W7/8, so now I don't get pestered every sign-in, just every few days, postponing indefinitely. These 'cumulative' packages makes is even less transparent then it was before... no easy clicking to find out which KBs were added/changed.

And now we have "Crucial error: Start Menu and Cortana aren not working... Sign Out Now, and we'll try to fix it the next time you sign in." Aint working.

http://techdows.com/2015/06/fix-start-menu-co...ndows-10-build-10122.html

They suggest to start Powershell, but as there is no functional start menu/bar, nothing useful when right-clicking on the desktop, how to get to powershell? And this one is known since February, has a August 26 Update: MS is working on resolving the problem.

To get to Safe mode to fix, read bottom of this article: http://techdows.com/2015/08/microsoft-yet-to-...rking-critical-error.html

So signed out, held shift key while hitting the power button right bottom... amazing, the Troubleshoot screen appeared, hit Advanced > Startup Settings > Restart and......... 30 minutes later finally the Safe Screen came up, and low and behold, safe mode is much much faster. hmmm, now to boot again to see if 'Normal' will run... another chapter later no doubt... the test account has disappeared, but the start bar is back, and cortana was never there anyway... there's no sound on this system ;P

What a bunch of cobblers this 'Pretends to be an OS' is. (This is official build 10240 I saw while in safe mode)

Something swapped my function keys... now have to push FN+F1 to F12 to get them to work. argh

Whilst, there's yet another major roll-up of fixes for W10: https://support.microsoft.com/en-us/kb/3081455 , nothing on 'Start' newer than August 11, so guess there's no fix for the critical error. Will know next week when maybe booting in Win to apply.