Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Reindeer_Games

macrumors 6502
Nov 29, 2018
286
228
Pueblo, CO
New Web Driver out for Security Update 2019-002:

(17G6029) (CUDA 10.1/418.105): https://www.nvidia.com/Download/driverResults.aspx/145775/en-us

I'm staying with 387.10.10.15.15.108.

Lou

Screenshot 2019-03-28 02.09.07.png

I "updated" just to take a look and see.
 
Last edited:

Mac_User 0101

macrumors regular
Oct 8, 2017
133
43
[B said:
NVIDIA Web Drivers[/B]

NOTE: NVIDIA is officially stating to uninstall the 387.10.10.15.15.108 driver and move to 387.10.10.10.40.122. Leaving this information and links for those who choose to use anyway. See post #17 below for release notes.

NVIDIA Web Driver version 387.10.10.15.15.108 does not break with each macOS update (through High Sierra), but was pulled by NVIDIA and is no longer publicly available directly from NVIDIA's servers. The 387.10.10.15.15.108 driver included VOLTA support.

387.10.10.15.15.108 has been posted below (See post #8):
http://scriptsandbits.billybobbongo.com/nvidia/WebDriver-387.10.10.15.15.108.zip

It is not 100% confirmed that 387.10.10.15.15.108 is functionally compatible with all features of CUDA 10.1/418.105. Driver appears to work with most basic CUDA acceleration applications. If your workflow depends on latest versions of CUDA, might be best to stick with the publicly released driver versions and would be first place to troubleshoot potential issues.
This was an extremely useful driver you pointed me to. I went ahead and installed 387.10.10.15.15.108 and it totally works. I don't use CUDA so I can't confirm that there are no issues there but I can confirm that it survives security updates. Thank you so much.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
I was checking the SU catalog and noticed that Apple reissued the High Sierra SecurityUpdate 2009-002 and now the build is 17G6030.

So, NVIDIA will need to release a new version of the web driver.
 

flowrider

macrumors 604
Original poster
Nov 23, 2012
7,323
3,003
I was checking the SU catalog and noticed that Apple reissued the High Sierra SecurityUpdate 2009-002 and now the build is 17G6030.

So, NVIDIA will need to release a new version of the web driver.

And again, the pulled Web Driver 108 is still working fine along with Cuda. I will keep my eyes open for the new driver. Why Apple used the same Security Update identification is a mystery to me 1387914497.gif

Lou
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
And again, the pulled Web Driver 108 is still working fine along with Cuda. I will keep my eyes open for the new driver. Why Apple used the same Security Update identification is a mystery to me View attachment 829457

Lou
Some years ago, one security update had 4 reissues, all with the exactly same name with just different builds - no surprise this happening again.
 
  • Like
Reactions: Eschers

flowrider

macrumors 604
Original poster
Nov 23, 2012
7,323
3,003
^^^^And it also appears the the public Beta for Security Update 2019-003 was pulled.

Lou
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Someone spotted this funny fact. Both Mac Pro 4,1 and Mac Pro 3,1 are NOT supported for High Sierra. There is no way to install 10.13.6 on these Mac natively and run this version's web driver.
Screenshot 2019-03-31 at 2.18.27 PM.png

TBH, I believe that they are just too lazy to check and update the info. I don't think they intentionally support those Mac that run patched macOS.
 
  • Like
Reactions: Reindeer_Games

worldburger

macrumors member
Jan 27, 2008
44
5
Some years ago, one security update had 4 reissues, all with the exactly same name with just different builds - no surprise this happening again.

@tsialex (or anyone else) What would you do if you were on 10.13.6 (17G6028)? I can't find a driver for my release anywhere (or any documentation for 17G6028).

Is there anything wrong with updating to the new Nvidia web driver 387.10.10.10.40.123?

EDIT: I'm currently on Nvidia Driver version 387.10.10.10.40.118
 
Last edited:

flehman

macrumors 6502
Feb 21, 2015
352
194
You could try downloading the 10.13.6 Combo Update and run it. I think the combo updates periodically get the security updates rolled into them. That might update your build number.
 

09872738

Cancelled
Feb 12, 2005
1,270
2,125
@tsialex (or anyone else) What would you do if you were on 10.13.6 (17G6028)? I can't find a driver for my release anywhere (or any documentation for 17G6028).

Is there anything wrong with updating to the new Nvidia web driver 387.10.10.10.40.123?

I believe the *.123 only works for the pulled Apple update.

This driver (pulled by Nvidia presumably on Apples request some time months ago) should work though: http://scriptsandbits.billybobbongo.com/nvidia/WebDriver-387.10.10.15.15.108.zip
 
  • Like
Reactions: bsbeamer

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
What would you do if you were on 10.13.6 (17G6028)?

This is your easiest option RIGHT NOW if you need a driver:

I believe the *.123 only works for the pulled Apple update.

This driver (pulled by Nvidia presumably on Apples request some time months ago) should work though: http://scriptsandbits.billybobbongo.com/nvidia/WebDriver-387.10.10.15.15.108.zip

If you do not NEED a driver for your GPU to work, suggest you wait 1-2 days. There likely will be an updated NVIDIA driver released by then. Other options are to downgrade macOS to a compatible version or attempt to run the driver script.

The 387.10.10.15.15.108 driver does not "break" with each macOS release, however there are some issues when used in combination with CUDA 10.1. Best to stick with CUDA 10.0 if you utilize CUDA with this driver.
 

northernmunky

macrumors 6502a
Jan 19, 2007
846
323
London, Taipei
This seems like a good thread to drop this off, I had an issue today at work where I ran a security update on a Sierra machine to discover suddenly that there was no webdriver for the build. After a bit of research I managed to work out a solution:

SOLUTION if youre stuck GPUless on Sierra / High Sierra.

As all NVIDIA users may know... NVIDIA's drivers are locked to build numbers of the OS.

If you install an OS update or even so much as a security update, the build number of your machine will change which will force the NVIDIA GPU drivers to revert to OSX default until you update to a compatible driver from NVIDIA.

Unfortunately I just made the mistake up running a security update and NVIDIA has not yet released drivers for my Sierra machine. The result is BLANK SCREEN!

But heres the solution (briefly):

This worked on Sierra, but in High Sierra you must disable SIP before proceeding.

Basically you have to manually change the macOS build number to fool the installer.
  • Depending on your situation, remote desktop to your machine or ssh in through Terminal
  • You need to know the WebDriver version you currently have and change your macOS build number to match.
So in my case for example, I have Webdrivers for (16G1818) 378.05.05.25f11 installed.
But my OS build is 16G1918. And no NVIDIA drivers exist for this version yet (If they ever do).

Easy way to find driver versions and buildnumber is here: http://www.macvidcards.com/drivers.html
Now the fun part:

I noticed the build numbers listed dont always seem to exactly match (I havent bothered to research why but...), download the driver you have installed.

Type: cd ~/Downloads/
pkgutil --expand WebDriver-378.05.05.25f11.pkg Webdriver/


This will create a folder called Webdriver and place the contents of the package inside it.

cd Webdriver/
cat Distribution | grep supportedOSBuildVer

Look for the line which reads:
var supportedOSBuildVer = "16G1618"; < this is the number you want.

Type:
sudo nano -w /System/Library/CoreServices/SystemVersion.plist

Type in your admin password.

Look for the lines:
<key>ProductBuildVersion</key>
<string>16G1918</string>


This is the line you need to change to match the OS version from the Webdriver package distribution file:
Change to:
<key>ProductBuildVersion</key>
<string>16G1618</string>



Type: control+x
and Y to save.

If you get a warning about not being able to save the file, then your SIP is enabled and you need to disable it.

This again depends on your situation, if drivers are already installed and your rolling back the build number, a simple restart will probably do.

Or if remoted in, double click the installer and the package will then run and successfully install.

If you dont have access to your GUI anymore, you can also run something like:

installer -pkg WebDriver-378.05.05.25f11.pkg -target /
Which will install the driver to your machine.
 

Mac_User 0101

macrumors regular
Oct 8, 2017
133
43
This seems like a good thread to drop this off, I had an issue today at work where I ran a security update on a Sierra machine to discover suddenly that there was no webdriver for the build. After a bit of research I managed to work out a solution:

SOLUTION if youre stuck GPUless on Sierra / High Sierra.

As all NVIDIA users may know... NVIDIA's drivers are locked to build numbers of the OS.

If you install an OS update or even so much as a security update, the build number of your machine will change which will force the NVIDIA GPU drivers to revert to OSX default until you update to a compatible driver from NVIDIA.

Unfortunately I just made the mistake up running a security update and NVIDIA has not yet released drivers for my Sierra machine. The result is BLANK SCREEN!

But heres the solution (briefly):

This worked on Sierra, but in High Sierra you must disable SIP before proceeding.

Basically you have to manually change the macOS build number to fool the installer.
  • Depending on your situation, remote desktop to your machine or ssh in through Terminal
  • You need to know the WebDriver version you currently have and change your macOS build number to match.
So in my case for example, I have Webdrivers for (16G1818) 378.05.05.25f11 installed.
But my OS build is 16G1918. And no NVIDIA drivers exist for this version yet (If they ever do).

Easy way to find driver versions and buildnumber is here: http://www.macvidcards.com/drivers.html
Now the fun part:

I noticed the build numbers listed dont always seem to exactly match (I havent bothered to research why but...), download the driver you have installed.

Type: cd ~/Downloads/
pkgutil --expand WebDriver-378.05.05.25f11.pkg Webdriver/


This will create a folder called Webdriver and place the contents of the package inside it.

cd Webdriver/
cat Distribution | grep supportedOSBuildVer

Look for the line which reads:
var supportedOSBuildVer = "16G1618"; < this is the number you want.

Type:
sudo nano -w /System/Library/CoreServices/SystemVersion.plist

Type in your admin password.

Look for the lines:
<key>ProductBuildVersion</key>
<string>16G1918</string>


This is the line you need to change to match the OS version from the Webdriver package distribution file:
Change to:
<key>ProductBuildVersion</key>
<string>16G1618</string>



Type: control+x
and Y to save.

If you get a warning about not being able to save the file, then your SIP is enabled and you need to disable it.

This again depends on your situation, if drivers are already installed and your rolling back the build number, a simple restart will probably do.

Or if remoted in, double click the installer and the package will then run and successfully install.

If you dont have access to your GUI anymore, you can also run something like:

installer -pkg WebDriver-378.05.05.25f11.pkg -target /


I wonder if you could force the web driver to install with Pacifist. I haven't tried it and don't recommend buying it just for that. If you already own it, it's worth a shot. It has helped me many times with outdated hardware drivers.
 

worldburger

macrumors member
Jan 27, 2008
44
5
The vast majority of people would have better luck using the "nvidia-update.sh" script method. Search this forum, it's been posted numerous times.

Was looking at the other solutions, but ended up doing this. Thanks! Simple and elegant!
 

northernmunky

macrumors 6502a
Jan 19, 2007
846
323
London, Taipei
The vast majority of people would have better luck using the "nvidia-update.sh" script method. Search this forum, it's been posted numerous times.

I do use this script, but didnt work in my case, it actually incorrectly installed the very latest version for 10.13 High Sierra, as opposed to the latest version for 10.12 Sierra.
 

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
I do use this script, but didnt work in my case, it actually incorrectly installed the very latest version for 10.13 High Sierra, as opposed to the latest version for 10.12 Sierra.

You can install a specific version:
https://github.com/Benjamin-Dobell/nvidia-update#install-a-specific-driver-version

Install a specific driver version
Code:
bash <(curl -s https://raw.githubusercontent.com/Benjamin-Dobell/nvidia-update/master/nvidia-update.sh) <revision>
Where <revision> is a driver version e.g. 378.10.10.10.25.106
 

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
Is this accessible over FTP? Or is there a site that lists every driver version in their repository?

At the moment I'm using this site as a reference, and the problem is, the version I wanted isn't on the list.

You'll have better luck with this list:
https://gfe.nvidia.com/mac-update

That is the "official" currently from NVIDIA.

There are some exceptions, 387.10.10.10.40.118 is not on this list but is still hosted/distributed by NVIDIA.
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Is this accessible over FTP? Or is there a site that lists every driver version in their repository?

At the moment I'm using this site as a reference, and the problem is, the version I wanted isn't on the list.

That link is directly connected to the Nvidia server, you prefer some 3rd part host more than Nvidia?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.