Thanks. I had the same thought, though experienced no difficulties doing it in this order (after requisite reboot afterwards, not mentioned)

From what I can tell, this is coming down to a matter of the community at large throwing stuff in the air to see what sticks. At present, it's looking to me like this has been an ongoing project at M$ for longer than Win10 prerelease, so finding all the gotchas could be a challenge.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Looks like they're (M$) are out to make Win7 experience as much of a hell as possible. Will be working through things as best I can, but let's alert the Linux Community they may need to take some refugees from this Putinesque calamity.

+1, With Me SCREAMING HELP! ;o)

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Looks like they're (M$) are out to make Win7 experience as much of a hell as possible. Will be working through things as best I can, but let's alert the Linux Community they may need to take some refugees from this Putinesque calamity.

+1, With Me SCREAMING HELP! ;o)

Had a feeling this might be impacting others when my friend asked for help. Will consult with him when he's available, see what his experiences are, and maybe make up a page describing events and workarounds. Really seems the current regime wants to get rid of us. Seems like a really crap endgame, if they are thinking that far.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

For the record, they (m$) broke my trust the moment they tried to install updates as I clicked on Windows Update (but before selecting any)

[..And I think in any legal system worth its salt, you'll find trust sacrosanct...]

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Since the release from version 8 for NVIDIA GPU every download from GPU tasks ended as failed.
With version 7 there was no problem.
Reset the project and update the videodriver from 359.06 to the lates driver 361.75 has no result.
All the V8 Cuda tasks still shows the error: download failed.
On my other computers Cuda tasks have no problems

My computer ID is: 6349991

What can I do to resolve this problem?
Downgrade the driver and if so to which version number?
Exclude Cuda tasks for this computer?
But that will not resolve this problem.

The log in BOINC Manager gives the following messages:

26-1-2016 11:50:05 | SETI@home | Requesting new tasks for NVIDIA GPU
26-1-2016 11:50:07 | SETI@home | Scheduler request completed: got 37 new tasks
26-1-2016 11:50:09 | SETI@home | Started download of setiathome_8.00_windows_intelx86__cuda50.exe
26-1-2016 11:50:09 | SETI@home | Started download of 15se15aa.12997.15208.12.39.107
26-1-2016 11:50:10 | SETI@home | Finished download of setiathome_8.00_windows_intelx86__cuda50.exe
26-1-2016 11:50:10 | SETI@home | Started download of 15se15aa.19588.9482.13.40.135
26-1-2016 11:50:10 | SETI@home | [error] File setiathome_8.00_windows_intelx86__cuda50.exe has wrong size: expected 6854656, got 5031
26-1-2016 11:50:10 | SETI@home | [error] Checksum or signature error for setiathome_8.00_windows_intelx86__cuda50.exe
26-1-2016 11:50:13 | SETI@home | Finished download of 15se15aa.12997.15208.12.39.107
26-1-2016 11:50:13 | SETI@home | Started download of 15se15aa.23818.5392.14.41.39
26-1-2016 11:50:14 | SETI@home | Finished download of 15se15aa.19588.9482.13.40.135

31-1-2016 1:57:08 | SETI@home | Requesting new tasks for NVIDIA GPU
31-1-2016 1:57:11 | SETI@home | Scheduler request completed: got 20 new tasks
31-1-2016 1:57:13 | SETI@home | Started download of setiathome_8.00_windows_intelx86__cuda42.exe
31-1-2016 1:57:13 | SETI@home | Started download of 03jl11ad.32074.14795.12.39.229
31-1-2016 1:57:15 | SETI@home | Incomplete read of 4879.000000 < 5KB for setiathome_8.00_windows_intelx86__cuda42.exe - truncating
31-1-2016 1:57:15 | SETI@home | Finished download of setiathome_8.00_windows_intelx86__cuda42.exe
31-1-2016 1:57:15 | SETI@home | Started download of 12oc11ad.4534.8652.6.33.222
31-1-2016 1:57:15 | SETI@home | [error] File setiathome_8.00_windows_intelx86__cuda42.exe has wrong size: expected 10925056, got 0
31-1-2016 1:57:15 | SETI@home | [error] Checksum or signature error for setiathome_8.00_windows_intelx86__cuda42.exe
31-1-2016 1:57:17 | SETI@home | Finished download of 03jl11ad.32074.14795.12.39.229
31-1-2016 1:57:17 | SETI@home | Started download of 12oc11ad.4534.8652.6.33.237
31-1-2016 1:57:18 | SETI@home | Finished download of 12oc11ad.4534.8652.6.33.222

31-1-2016 8:28:51 | SETI@home | Requesting new tasks for NVIDIA GPU
31-1-2016 8:28:53 | SETI@home | Scheduler request completed: got 38 new tasks
31-1-2016 8:28:55 | SETI@home | Started download of setiathome_8.00_windows_intelx86__cuda32.exe
31-1-2016 8:28:55 | SETI@home | Started download of 12oc11ad.5728.21538.13.40.166
31-1-2016 8:28:56 | SETI@home | Incomplete read of 4921.000000 < 5KB for setiathome_8.00_windows_intelx86__cuda32.exe - truncating
31-1-2016 8:28:56 | SETI@home | Finished download of setiathome_8.00_windows_intelx86__cuda32.exe
31-1-2016 8:28:56 | SETI@home | Started download of 12oc11ad.5728.21538.13.40.81
31-1-2016 8:28:56 | SETI@home | [error] File setiathome_8.00_windows_intelx86__cuda32.exe has wrong size: expected 15462912, got 0
31-1-2016 8:28:56 | SETI@home | [error] Checksum or signature error for setiathome_8.00_windows_intelx86__cuda32.exe
31-1-2016 8:28:58 | SETI@home | Finished download of 12oc11ad.5728.21538.13.40.166
31-1-2016 8:28:58 | SETI@home | Started download of 12oc11ad.5728.21538.13.40.168

---

What can I do to resolve this problem?
Downgrade the driver and if so to which version number?

The video driver won't be having any effect on file downloads.
Are all the computers using the same modem? I'd suggest rebooting the computer & modem. Are you running the same AV on each system? Check that the problem computer hasn't received a recent update that's changed it's settings or made it consider the CUDA executables viruses.

If you're still having issues I'd suggest starting a new thread.

---

Grant
Darwin NT

That's not a driver problem.
Either your internet connection is broken or - much more probably - an AV scanner intercepts the downloads and prohibits installation of the executables.

[edit] Too late to the show... ;)

---

Aloha, Uli

Finally got round to this. The Win 10 thread has some additional Win7 patches to avoid:

Previously listed:
KB 3081954 - This update ensures users can continue using Work Folders when upgrading from Windows 7 to 10. Also adds telemetry points to Work Folders for Asimov telemetry pipeline.
KB 3102810 - Improvements to the New Update Client provided by KB3083710
KB 3112343 - Improves the Update Client when upgrading from 7 to 10 and provides MS with feedback on how smooth the process was.

Added today:
KB 3123862 - This update adds capabilities to some computers that lets users easily learn about Windows 10 or start an upgrade to Windows 10. (read: "nags you with propaganda until you give-in")
KB 3135445 - New Update Client for Windows 7 - February 2016.

You also have these patches which don't appear on Cosmic Ocean's Win 7 list:

2505438
2670838
2922324 **
2976978 *
3014460 **
3015249 **
3044374 *
3050267 *
3065988 *
3068707
3075853 *
3083225 **
3083325 *
3083711 *

( * these are on CO's list, but marked as Windows 8.1 only)
( ** these aren't on the DSL reports list either)

hmmm, good to know, and will watch out for further anomales. While still exploring, here is the batch, I named removeupdates.cmd and ran, which was based on information from http://www.dslreports.com/forum/r30348398-WIN7-Win-7-updates-to-avoid-or-be-careful-with. More precisely the initial list there later adding more from further in that thread. There could be more lurkers, though seems OK for now. Some entries I know only apply to Win8/8.1 and 10. It'd be interesting to me if someone so inclined wanted to compare to information in the Win10 thread.

@echo off 
wusa /uninstall /kb:2505438 /quiet /norestart 
wusa /uninstall /kb:2670838 /quiet /norestart 
wusa /uninstall /kb:2922324 /quiet /norestart
wusa /uninstall /kb:2952664 /quiet /norestart
wusa /uninstall /kb:2976978 /quiet /norestart 
wusa /uninstall /kb:2977759 /quiet /norestart 
wusa /uninstall /kb:2990214 /quiet /norestart
wusa /uninstall /kb:3014460 /quiet /norestart
wusa /uninstall /kb:3015249 /quiet /norestart 
wusa /uninstall /kb:3021917 /quiet /norestart 
wusa /uninstall /kb:3022345 /quiet /norestart 
wusa /uninstall /kb:3035583 /quiet /norestart
wusa /uninstall /kb:3044374 /quiet /norestart 
wusa /uninstall /kb:3050265 /quiet /norestart
wusa /uninstall /kb:3050267 /quiet /norestart 
wusa /uninstall /kb:3065987 /quiet /norestart
wusa /uninstall /kb:3065988 /quiet /norestart
wusa /uninstall /kb:3068707 /quiet /norestart 
wusa /uninstall /kb:3068708 /quiet /norestart 
wusa /uninstall /kb:3075249 /quiet /norestart
wusa /uninstall /kb:3075851 /quiet /norestart
wusa /uninstall /kb:3075853 /quiet /norestart 
wusa /uninstall /kb:3080149 /quiet /norestart
wusa /uninstall /kb:3083225 /quiet /norestart
wusa /uninstall /kb:3083324 /quiet /norestart
wusa /uninstall /kb:3083325 /quiet /norestart 
wusa /uninstall /kb:3083710 /quiet /norestart
wusa /uninstall /kb:3083711 /quiet /norestart

OK, Thanks. Will add the missing ones later, and see if I have any of them. Worth me crossreferencing once I can spend more time at the machine. Some I had came from a subsequent updated post, and indeed are expected on 8/8.1 or 10 itself only. Probably will attempt to 'unbreak' Win update for the exercise at some point, though for now happy with 361.75 clean install, broken Windows update, and the handy combined lists of updates to watch/flag. Some part, or the combined total seems to have made a big difference on what is a quite dated core2Duo.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.