Security Update 2017-001 BREAKS File Sharing

[chrfr]

Was wondering why the 2017-001 update message showed up again in the App store. I installed the original 2017-001 update and it was successful. In fact, my build number is 17B1002.

From another forum I read that since the build number changes as chrfr pointed out, the Nvidia driver (Macs that use this driver) gets disabled. Correct if I am wrong.

That is correct. You'll be ok as long as you don't reboot the computer, until Nvidia updates the driver again.

 

[joedec]

Was wondering why the 2017-001 update message showed up again in the App store. I installed the original 2017-001 update and it was successful. In fact, my build number is 17B1002.

From another forum I read that since the build number changes as chrfr pointed out, the Nvidia driver (Macs that use this driver) gets disabled. Correct if I am wrong.

I have two updates installed, both named the same "Security Update 2017-001". The macOS build version changes from 17B1002 to 17B1003 when the second is installed.

 

[Sciuriware]

Was wondering why the 2017-001 update message showed up again in the App store. I installed the original 2017-001 update and it was successful. In fact, my build number is 17B1002.

From another forum I read that since the build number changes as chrfr pointed out, the Nvidia driver (Macs that use this driver) gets disabled. Correct if I am wrong.

Moreover, APPLE is out of sequence numbers: the security update by Nov 5th had also that same number.
;JOOP!

 

[gages]

Trying to figure out why is't the fix to enable a password for the root user?

 

[chrfr]

Moreover, APPLE is out of sequence numbers: the security update by Nov 5th had also that same number.
;JOOP!

No. The version number is specific to this update. 17B1003 is unique to the 10.13.1 update. Digits aren’t considered separate from the 17B part of the build number.
[doublepost=1512065888][/doublepost]

Trying to figure out why is't the fix to enable a password for the root user?

There’s no need to have root enabled for the vast majority of users. Having it enabled with a password increases the security risk for those people.

 

[Aguaman]

I just installed the security update, and suddenly AirDrop isn't working. Anyone else having this problem?

After the update, I rebooted and applied Apple's fix for File Sharing. Still no AirDrop.

 

[solidstate94]

That is correct. You'll be ok as long as you don't reboot the computer, until Nvidia updates the driver again.

Thanks for clarifying chrfr! I do not want to jump to conclusions but I remember reading either on the Support Page or directly in the App Store that no reboot is required. Could the Nvidia driver issue be the reason?

For those that use the Nvidia driver, Nvidia has released an updated driver.

 

[chrfr]

Thanks for clarifying chrfr! I do not want to jump to conclusions but I remember reading either on the Support Page or directly in the App Store that no reboot is required. Could the Nvidia driver issue be the reason?

For those that use the Nvidia driver, Nvidia has released an updated driver.

The reason for what? The fact that the update doesn't require a reboot has nothing to do with graphics drivers, if that's what you're asking.

 

[joedec]

I just installed the security update, and suddenly AirDrop isn't working. Anyone else having this problem?

After the update, I rebooted and applied Apple's fix for File Sharing. Still no AirDrop.

Interesting, I tried Airdrop iPhone to Mac and Mac to iPhone, worked great.

Mac to Mac fails miserably. The authentication request doesn't show up on the reciever and the sender is waiting, then finally I get a message file was rejected. Sometimes it actually starts the copy, with no authentication, takes forever and times out.

Of course I don't know if it worked before the patch, since I rarely, almost never, use Airdrop.

 

[Sciuriware]

That is correct. You'll be ok as long as you don't reboot the computer, until Nvidia updates the driver again.

I noticed that the 'famous' update 2017-001 also pops up on Nov 5, then for 10.12.6
My theory: the root bug was already known during Sierra and mended as above.
Then High Sierra was released and, like it always seems to go, they forgot about that bug.
Notice that many products get almost the same updates in past, present and early-bird releases,
and all programmers know how confusing that can be, because those updates must differ in detail.
;JOOP!

 

[chrfr]

I noticed that the 'famous' update 2017-001 also pops up on Nov 5, then for 10.12.6
My theory: the root bug was already known during Sierra and mended as above.
Then High Sierra was released and, like it always seems to go, they forgot about that bug.
Notice that many products get almost the same updates in past, present and early-bird releases,
and all programmers know how confusing that can be, because those updates must differ in detail.
;JOOP!

No, the problem has never affected Sierra. That security update fixes all the stuff that was fixed in 10.13.1.
You’re looking for a conspiracy that doesn’t exist.

 

[solidstate94]

The reason for what? The fact that the update doesn't require a reboot has nothing to do with graphics drivers, if that's what you're asking.

I was referring to the fact that no reboot was mandatory with the update since the Nvidia driver issue was already known.

As a side question, what kind of updates require reboots please?

Thanks!