I did open a ticket with both MS and NVidia on this. Fat lot of good it will probably do ...

Text of the update I sent NVidia today regarding this issue. I think it's pretty self-explanatory. Watch the Your Computers tab at SETI, if you're on Win 10. If you also experience this issue, as I have on 4 PCs now, I would like to hear from you. I know there are some folks here who have "ins" at NVidia. Perhaps you can help escalate this?
Jim ...
=== Update to Ticket 160924-000022 ===
I had an additional machine which had not yet received the Anniversary Update. So I placed this machine, named HP-Z600, on 372.90, verified proper installation of OpenCL and allowed the machine to continue. Overnight, the Anniversary updated was pushed. When it installed, it _downgraded_ the machine from 372.90 to 369.09, which again loaded without OpenCL support.
So, even if one is proactive in keeping the machine updated, the MS push will mess this up. Attached are 3 added files: 1) HPZ600_msinfo.txt, an msinfo export before the Anniversary Update, 2) HPZ600b_msinfo.txt, an msinfo export from after the update, and 3) HPZ600_BOINC_info.txt, a listing from the BOINC servers of status as detected by the BOINC Client when reporting to the servers located at UC Berkeley.
I sincerely hope this issue will receive the attention it deserves.
====

---

I was proactive on the anniversary update. I downloaded the update to a thumb drive and updated a total of 9 computers. Before letting BOINC to start, I did clean install of my nvidia drivers first.

---

If MS Update is _downgrading_ drivers, there's a definitely a problem that needs to be addressed. Especially if there actually is no way to prevent them for doing so.

---

MS have been using their "update" path to distribute crippled (downgraded) drivers for a good many years. This mainly affects graphics drivers, where MS are only interested in having functionality available that they need for their bloated Office offerings, for example they have not distributed CUDA with their builds of the Nvidia drivers.

---

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

I have a Windows 10 Home edition updated from 8 and 8.1 on a HP PC. When I installed on it a Geforce GTX 750 OC to run both SETI@home and Einstein@home GPU tasks, I installed a nVidia driver using Geforce Experience and I regularly update it. MS never overwrote my driver in its updates.
Tullio

---

MS have been using their "update" path to distribute crippled (downgraded) drivers for a good many years. This mainly affects graphics drivers, where MS are only interested in having functionality available that they need for their bloated Office offerings, for example they have not distributed CUDA with their builds of the Nvidia drivers.

Gotta love it. Too tired to rant about it...

---

Yesterday I had a major Windows 10 update, which changed my Windows from 1511 to 1607. I had to reinstall VirtualBox on it, so I updated it to the latest release but my nVidia driver for the Geforce GTX 750 OC remained unchanged. I had updated it using Geforce Experience to 372.90 and it remained unchanged.
Tullio

---

Just got diverted to the new Outlook Mail to send an email...... what a P.O.S! More great thinking from the idiots in Redmond.

---

"Sour Grapes make a bitter Whine." <(0)>

Just got diverted to the new Outlook Mail to send an email...... what a P.O.S! More great thinking from the idiots in Redmond.

Really gotta wonder what's in the air up there right now ...

---

Just another heads-up about a potential issue. Back in July, I tried and failed on a Win10 free upgrade on one of my Win7 boxes. Failure was due to BIOS not supporting a required function even though the CPU did. No matter, Win7 is fine.

Have started having a lot of trouble with that machine recently, which I finally ran down to running out of disk space, for no good reason. After doing the normal things, like cleaning, checkdsk and the like, with no help, what I came to discover was that my C:\windows directory was greater than 90gb. Yep, 90+gb! Not good on a 120gb SSD, for sure, and pretty bloated even by M$ standards!.

A little more checking revealed that of that 90+gb, over 47gb of it was in C:\Windows\Temp. Since it should normally not be an issue, I deleted all contents of C:\Windows\Temp and got my 47gb back. This is not 100% safe, but it's very unlikely that anything essential will live there.

Only reason I mention this here is my suspicion that this happened due to a failure of GWX to clean things up properly when it aborted the Win 10 upgrade install. So if you tried and then failed or aborted a Win 10 upgrade, might check your disk space, especially the above folder.

Jim ...

---

Only reason I mention this here is my suspicion that this happened due to a failure of GWX to clean things up properly when it aborted the Win 10 upgrade install. So if you tried and then failed or aborted a Win 10 upgrade, might check your disk space, especially the above folder.

Same scenario occurred on a laptop I had given a friend. Older HP with 4Gb of ram and no way to expand. The 'automatic' upgrade to 10 from 7 failed and left less than 5Gb on the Hard drive. No room to uninstall so I had to wipe and reinstall the OS.

It's only used as an internet access portal so no important data was lost. I locked down the update function after running the June 'mass update'. So far in two months no more problems.

---

"Sour Grapes make a bitter Whine." <(0)>

For those slugging away try to keep some control of their own Windows machines...

Is all the continued effort now rendered futile by the latest Microsoft development?


Like it or not, here are ALL your October Microsoft patches

Redmond kicks off the era of the force-fed security update

Microsoft is kicking off a controversial new security program this month by packaging all of its security updates into a single payload.

The October security release introduces Redmond's new policy of bundling all security bulletins as one download. While more convenient for end users, who now get just one bundle, the move will irk many administrators, who had preferred to individually test and apply each patch to avoid compatibility problems...


For anyone 'frustrated', please reply to the more 'political' Politics thread!

It is what we allow all this to be...
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

From my understanding, WSUS still gets the individual updates, as well as the rolled-up one. But truth be told... I turned Updates off on both of my machines.

I don't really see a point in continuing to get these updates, unless you still use IE and go to sketchy websites frequently. For those of us who excise a bit of caution and sense, we can basically run without updates or even A/V without issues--I know I did just that for a number of years back in the XP days, even with IE6. Someone called BS on the fact that I was using IE6 and had no A/V and claimed I had no infections, so I downloaded the A/V scanner they considered the best and ran a full system scan... it came up clean.

A little bit of caution goes a long way.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

"Microsoft Update Catalog works with any browser now"

From my understanding, WSUS still gets the individual updates, as well as the rolled-up one. But truth be told... I turned Updates off on both of my machines.

I don't really see a point in continuing to get these updates, unless you still use IE and go to sketchy websites frequently. For those of us who excise a bit of caution and sense, we can basically run without updates or even A/V without issues--I know I did just that for a number of years back in the XP days, even with IE6. Someone called BS on the fact that I was using IE6 and had no A/V and claimed I had no infections, so I downloaded the A/V scanner they considered the best and ran a full system scan... it came up clean.

A little bit of caution goes a long way.

I haven't used AV software on my main home rig since the 90's. All I ever found AV good for is slowing down a perfectly good system and quarantining needed files from false positives.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Don’t install Nvidia driver 375.57 on Windows 10

"Some symptoms observed by Windows 10 users was that Windows Store apps started to crash, that drag and drop operations in the Start Menu did not work as intended and were causing issues, and that videos and animated GIFs were showing artifacts."

Don’t install Nvidia driver 375.57 on Windows 10

"Some symptoms observed by Windows 10 users was that Windows Store apps started to crash, that drag and drop operations in the Start Menu did not work as intended and were causing issues, and that videos and animated GIFs were showing artifacts."

I dropped this on 20 Oct, you might want to take a look at it http://-http://setiathome.berkeley.edu/forum_thread.php?id=80411#1825587

---

I don't buy computers, I build them!!

I don't really see a point in continuing to get these updates, unless you still use IE and go to sketchy websites frequently. For those of us who excise a bit of caution and sense, we can basically run without update

+1

---

For some humor on the subject:

http://www.vgcats.com/comics/?strip_id=377

---

I have installed Geforce driver 375.63 on my Windows 10 PC with GTX 750 OC and everything seems to work. I have processed a huge number of SETI@home GPU tasks of very short duration and they are all waiting for validation.
Tullio

---