My Rig2 in signature got hit in the wee hours this morning and it is set Not to update the drivers.  That makes MS two for two - pushed lousy Nvidia  373.53 driver on my dedicated folding machines that use Win10 Pro.
 
This "new and improved" 373.53 driver Kills Folding PPD by 66% and does not even try to apply itself as the old one was setup.  So it goes and installs the full Nvidia junkware package of Experience, Sound and 3-D that were not previously loaded on the system - 
 
Most annoying these PCs were Actively Folding WU, when the driver was pushed on the systems; not like they were idle or asleep
 
As I had just changed this Rig back to 372.90 and it was good yesterday PPD at 1.6+ Million, surprised to find it "infected" this AM with SLI enabled and PPD in the gutter

bcavnaugh

Tiger770
Just for clarification, are you running Windows 10 Home or Pro?  I've seen a lot of runners of Home have this issue, but not many with Pro.
 
Also - I've always used the GeForce Experience to control driver installations and defer updates.  So far I've not had any issues *knock on wood.*

I am not spreading or starting a rumor, how would this help our Folding Team.
I spent over 3 hours last night fixing all 3 of my Windows 10 Pro x64 The Anniversary Update + 1 Windows Home x64 Anniversary Update.
Both, they are the same OS only the Enterprise Version is different when it comes to Windows Update.
I Never Use GeForce Experience, Ever. Most Folders know not to use this Tool. Gamers are another story.

Whoa, killer - ease up on the reins.  No one accused you of starting a rumor, I was merely asking you for a bit more clarification of the issue.  I'm sure I wasn't the only one wondering if this was limited to one flavor or another.  It's good to know now that you have 3 rigs, and a mix and match of versions.  Thank you for the clarification.
 
I'm not sure why you're resistant to the GeForce Experience.  Also I'm not sure why most folders know to not use it.  A quick google search returned no obvious issues with it and [link=mailto:Folding@home]Folding@home[/link].  Perhaps you can elaborate (or just direct me somewhere) as to why?  
 
I only mention it as a way to help you and possibly others in the future from trying to circumvent the OS from patching your drivers.  It's definitely worth a look.  I've never had my machines running it update without my express say so.  Screen grab below.
 

 

Tiger770

bcavnaugh

Tiger770
Just for clarification, are you running Windows 10 Home or Pro?  I've seen a lot of runners of Home have this issue, but not many with Pro.
 
Also - I've always used the GeForce Experience to control driver installations and defer updates.  So far I've not had any issues *knock on wood.*

I am not spreading or starting a rumor, how would this help our Folding Team.
I spent over 3 hours last night fixing all 3 of my Windows 10 Pro x64 The Anniversary Update + 1 Windows Home x64 Anniversary Update.
Both, they are the same OS only the Enterprise Version is different when it comes to Windows Update.
I Never Use GeForce Experience, Ever. Most Folders know not to use this Tool. Gamers are another story.

Whoa, killer - ease up on the reigns.  No one accused you of starting a rumor, I was merely asking you for a bit more clarification of the issue.  I'm sure I wasn't the only one wondering if this was limited to one flavor or another.  It's good to know now that you have 3 rigs, and a mix and match of versions.  Thank you for the clarification.
 
I'm not sure why you're resistant to the GeForce Experience.  Also I'm not sure why most folders know to not use it.  A quick google search returned no obvious issues with it and [link=mailto:Folding@home]Folding@home[/link].  I only mention it as a way to help you in the future from trying to circumvent the OS from patching your drivers.  It's definitely worth a look.  I've never had my machines running it update without my express say so.  Screen grab below.
 
Image Removed to save space
 

You will see this on Windows 7 as well but at lest it is Optional.
 Priority here is Folding and Crunching so to speak and yes we all stay away from GFE.
"Gamers are another story" The first thing you will see on this Forum From a Gamer to a Gamer is to remove it.

Chris21010
376.53 is the driver version that windows updates to. so unless you were already running that version for some reason you too have been updated.

Ah!  You're right.  I didn't look closely enough.  I had manually updated to 376.48 on 12/21/16 when it came out. So Nevermind, scratch that.  Windows update did screw with my drivers.
 
What's interesting is that I'm not having any issues with this particular set.  Have been running them all month... but then again I'm used an older generation card (970).  I'd imagine you two are on the bleeding edge or at least in the 10series, right?
 

bcavnaugh, What GPUs are you running on those 3 systems?
 
It's been pretty quiet over here since that forced update.  I apparently have had 1 Bad WU.
 
*********************** Log Started 2017-02-02T23:30:24Z ***********************
******************************* Date: 2017-02-03 *******************************
******************************* Date: 2017-02-03 *******************************
******************************* Date: 2017-02-03 *******************************
******************************* Date: 2017-02-03 *******************************
******************************* Date: 2017-02-04 *******************************
******************************* Date: 2017-02-04 *******************************
12:32:57:ERROR:WU00:FS01:Exception: Server did not assign work unit
******************************* Date: 2017-02-04 *******************************
******************************* Date: 2017-02-04 *******************************
******************************* Date: 2017-02-05 *******************************
******************************* Date: 2017-02-05 *******************************
******************************* Date: 2017-02-05 *******************************
******************************* Date: 2017-02-05 *******************************
******************************* Date: 2017-02-06 *******************************
******************************* Date: 2017-02-06 *******************************
******************************* Date: 2017-02-06 *******************************
******************************* Date: 2017-02-06 *******************************
******************************* Date: 2017-02-07 *******************************
******************************* Date: 2017-02-07 *******************************
******************************* Date: 2017-02-07 *******************************
******************************* Date: 2017-02-07 *******************************
******************************* Date: 2017-02-08 *******************************
******************************* Date: 2017-02-08 *******************************
******************************* Date: 2017-02-08 *******************************
******************************* Date: 2017-02-09 *******************************
******************************* Date: 2017-02-09 *******************************
******************************* Date: 2017-02-09 *******************************
14:52:16:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
******************************* Date: 2017-02-09 *******************************

I just updated to the latest official Nvidia driver after getting that stupid update. Personally I don't mind gfe. I only object to their ridiculous inclusion of 3d Vision support all the time. I can't imagine there are that many 3d displays out there to justify such nonsense. My Fah install finally got the new core 21 version right before that stupid update caused a black screen with no way out besides a hard reset. The latest driver install did the same thing, so as far as I'm concerned Nvidia QA/QC stinks. Luckily my folding stats still look good. Anybody hitting this debug mode bug? I haven't had a change to check yet.

This is an Off Domain Computer Running Windows 10 x64 Pro Current Build.
Running Driver 373.06 on the GTX 980 HC Graphics Cards.
Seems that setting the Policy may no longer work, ATM.
 
 




 
 
And Yes a Reboot was done between each of the changes and even ran GPUpdate /Force /Sync between each change.
I also use the Metered Ethernet Registry Settings *Hacks
 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]
"Ethernet"=dword:00000002

 
( I am Using AllowCortana registry key set to 0 )
 

Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"AllowCortana"=dword:00000000

Windows Registry Editor Version 5.00
 
[HKEY_USERS\S-1-5-21-4003516287-2183146536-844082379-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E83018A1-0452-4C89-B3FB-1CEB8C0F2E2A}Machine\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"AllowCortana"=dword:00000000

bcavnaugh 
If you guys can would you please post your PPD over the next day or two while on Driver 376.53?

 
Sure thing.  The numbers from Thursday and Friday won't be accurate, as it sees light use while I'm working from home.  Headed out of town this weekend though, so I'll leave it on to get some good numbers.
 

SM-71

bcavnaugh
This is an Off Domain Computer Running Windows 10 x64 Pro Current Build.
Running Driver 373.06 on the GTX 980 HC Graphics Cards.
Seems that setting the Policy may no longer work, ATM.

Is that with the AllowCortana registry key set to 0 or a different registry key???

As Posted Above in Post #44
Also using the Cortana Reg Hacks. This Means YES.

SM-71
Is that with the AllowCortana registry key set to 0 or a different registry key???

 
YES
 
Their is most likely more than one way to stop Windows Update from Installing Device Drivers.
Sorry SM-71 I am having such a hard time with you, not sure where this is going anymore.
I am trying very hard to work with, I am not sure why what I am doing is wrong for other to do as well.
What does Cortana even have to do with this Thread?

I will remove all of my settings and only use "AllowCortana registry key set to 0" and report back.
I Deleted this Key "ExcludeWUDriversInQualityUpdate"

 
 
Do you want me to Delete this "Enabling the "Do not include Drivers" policy" and retest?  (Same as Above) Not setting it back to Enabled
 
Adding this back but set to 0 ExcludeWUDriversInQualityUpdate and retesting now. (Same as Above) Setting it back 1 
 
Set to 1 Now and did have an update to do.

@ipkha when and if this happens I will move back to Windows 7 solely to Fold and Crunch that is.

I hear you on that one. I'd prefer to keep the driver updates out of the core WU system, buts that a list cause since they added them. I think even Windows 7 will show them. But in the end, I see the writing on the wall. They don't even note non Security updates anymore, an even more egregious move in my mind. They just combined them into 1 massive update going forward. Honestly, anyone who still cares should drop back to Windows 7 or even move to Linux. At least Linux can update now without rebooting these days.

bcavnaugh
I will remove all of my settings and only use "AllowCortana registry key set to 0" and report back.

The AllowCortana key will not stop manual updates but it has prevented me from getting ANY automatic updates so far.  I only disabled it because I don't like Cortana's new intrusiveness, the automatic update prevention was just a bonus side effect.  It can be removed if you only wish to prevent driver updates.
 

bcavnaugh
Do you want me to Delete this "Enabling the "Do not include Drivers" policy" and retest?  (Same as Above) Not setting it back to Enabled

 
The "ExcludeWUDriversInQualityUpdate" registry key, and the "Do Not Include Drivers" group policy both perform the same task.  The one you change last (key or policy) will be the one that is in effect.  

In group policy, you can both stop driver updates and with two other options block auto restarts.
Configure Automatic Updates can revert to download and prompt or just notify.
No auto-restart with logged on users should fix the restarts.