Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

45 points

MacOS High Sierra 10.13.2 causing Finder crash

Since updating to MacOS High Sierra 10.13.2 (from 10.13.1), I cannot connect to my NAS unit or other computers on the network, and in attempting to do so, Finder crashes and will not relaunch. I cannot find a fix to this problem, and as a consequence, my MacBook Pro (with TouchPad 2016) has become an island. I share files between computers on the network as part of my work process so this is a pretty big issue.

MacBook Pro (15-inch, Late 2016), iOS 10.3.2

Posted on Dec 7, 2017 9:05 PM

Best reply

xmetienne

Level 2

192 points

Posted on Dec 15, 2017 2:12 AM

Had the same issue after installing the 10.13.2 update... I should have listen to my intuition not to install it after failing twice! It has been real headache to install the said update which has messed up big time and apparently many users...

Now I've seen some of the answers here below and you could also install macOS High Sierra 10.13.3 beta update, it worked out for me and stabilized the entire OS High Sierra system, but you need to subscribe to the Apple Beta program first! here is how:

Subscribe to Apple Beta:

Apple Beta Software Program

AppleConnect Sign In

enroll your Mac

Download Feedback Assistant:

Feedback Assistant

Do another backup with Time Machine:

How to use Time Machine to back up or restore your Mac - Apple Support

Once done then go to App Store and update the above mentioned update!

Let me know if it was helpful and more importantly, in a later stage if you have resolved this issue, as it seems that there are a high volume of issue with the 10.13.2 update, and it would be important to inform other users of a way to resolve it!

Good luck!

View in context

157 replies

Dec 19, 2017 4:03 AM in response to lfuller105

My Fix:

Delete all shortcuts, aliases etc to any shares.

Don't mount shares at startup (login items)

Delete any keychains to server to store passwords

Turn off bonjour browsing in finder sidebar

Reconnect to shares as cifs:// instead of smb://

Everything happier. Not perfect but does bring a degree of stability. Apple Engineering calling me this afternoon (UK) to discuss.

Cheers

Dec 19, 2017 5:44 AM in response to Vmax28

Delete shortcuts to shares (inc login items)

Turn off bonjour browsing in finder.

Delete any saved keychains for your server.

Reconnect to server as cifs://server instead of smb://server

This helped for us. Not perfect but reduces the amount of finder freezes.

Dec 19, 2017 9:19 AM in response to Image Line

This change has actually sped up my connections and allows me to eject the volumes quickly. Before when I would eject with smb, the servers would get hung up and wouldn't eject until I logged off or did a hard quit with power button.

Dec 19, 2017 3:39 PM in response to lfuller105

I have the same issue. I am the lead IT Admin at my organization. I have followed the previous suggestions in this thread to switch to the CIFS protocol temporarily (very thankful for that suggestion), but as a much slower protocol, it has ground my entire marketing department, and any other media dependent users, to a halt.

This cannot go un-addressed. As a company we decided years ago to use Macs because of their bug-free nature, but lately our decision has really been challenged.

andy72

Level 1

14 points

Dec 19, 2017 4:53 PM in response to BKMacAdmin

if the issue is somewhat related to the SMB version and if it is related to smb v3 than you could try to add :

protocol_vers_map=2

to your nsmb.conf.

This would force smb version 2.1 instead of cifs which is smb version 1.

you can verify the connection protocol using "smbutil statshares -a" in a terminal.

I tested it now with my mac and it is seems to work as cifs with no crash, maybe the protocol is faster.

Vmax28

Level 1

23 points

Dec 19, 2017 6:33 PM in response to Vmax28

Just verified exactly the same problem with another machine (Macbook Pro), which usually is not used in office to connect to the shared directory on the Windows 2016 Server.

Apple if he hear us and care about using the Mac in a corporate environment, please urgently give us a patch to fix this problem.

P_Boyer

Level 1

4 points

Dec 20, 2017 6:57 AM in response to lfuller105

Same problem! MacPro (Late 2013) Version 10.13.2... I should just get a computer running Windows, I went away from Windows because of all the bugs and now I'm dealing with this on my Mac. I can't get any work done, all of my data is on an SMB share.

Steve Jobs wouldn't have let this happen.

Rayk217

Level 1

13 points

Dec 20, 2017 9:17 AM in response to P_Boyer

Thanks for all this feedback..We too are seeing the same issues both with Windows Server 2016, and 2012 R2. The problem does not exist when connecting to Windows Server 2003 R2, or on my NAS for that matter. A short term bandaid for us is using the cifs protocol as suggested. 10.13.1 is fine as well. I Actually rolled a few Macs back to Sierra in the interim as well.

lfuller105 Author

Level 1

45 points

Dec 24, 2017 3:42 PM in response to Sefari

After several finder crashes and lockups, my system became unstable, coupled with a new issue - my Mac would no longer charge (the inability to charge has since been resolved). After several attempts at getting the OS back on my Mac with a clean build (it would hang with a critical error message, preventing installation) and loading my data back (no restore from Time Machine, simply copying of data), I am once again having the same Finder crashes when trying to connect via SMB to my NAS unit and/or other servers. This has been going on since December 8th after the update to 10.13.2. It is disappointing that I still see no viable solution on this thread or from Apple. I can transfer data using a Windows machine, but this option is hardly convenient.

lfuller105 Author

Level 1

45 points

Dec 27, 2017 2:27 PM in response to Rusic Ivan

I have seen no definitive answer from Apple on this and there have been no OS updates to remedy the Finder crash experienced when connecting to a NAS unit and/or Windows server using MacOS version 10.13.2.

What I have done to circumvent this issue is to set up my NAS (Samba via Linux) unit to use SMB2 and Windows to use SMB1 (since Windows seems to view SMB2 protocol the same as SMB3). I have used these settings for 3 days and have not had a Finder crash to date. For detailed listing of samba connections including the protocol in use, type this into your terminal on the Mac: smbutil statshares -a (make sure you are connected to your server before typing in this command).

In order to make changes to Windows, you will need to use Regedit to go to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and add 3 DWORD entries: SMB1 (value data “1”), SMB2 (value data “0”) and SMB3 (value data “0”). I had to make these three entries in order for Windows to acknowledge SMB1 protocol. Reboot. Once you are back into Windows, go the your Mac terminal after connecting to your Windows server to verify the SM1 connection.

After changing the SMB protocol on your Windows and/or NAS units, be sure to remove the old server connections in Finder and enter them again. Yes, I know, you are still using SMB, but for some reason, I had to reenter them as new server connections to see results.

Dec 29, 2017 7:34 AM in response to lfuller105

I have the exact same issue on my Mac Pro towards SMB shares on my Windows Server 2012 R2.

Sometimes it works when doing a manual mount (browsing not working anymore) & when it does it always hangs when I connect to another share

Rayk217

Level 1

13 points

Jan 3, 2018 6:54 AM in response to verolux

Just FYI..This problem, at least for me, does not happen when connecting to Windows Server 2008 R2..Just 2012 and 2016. Works fine with my Synology NAS too.

Ray Kelejian

Indigo Operator / Prepress Specialist

ray@colorgraphicprint.com

Jan 3, 2018 7:09 AM in response to lfuller105

Do you connect to your NAS via a smb:// file share? Try to change it to cifs://

German computer magazine ct has reported problems with smb on 10.13.2 macOS 10.13.2 hat erhebliche Probleme mit Netzwerkfreigaben | Mac & i so changing your share to cifs should solve the problem.

Greetings from germany

Chris

Jan 3, 2018 7:19 AM in response to lfuller105

For reference to everyone using Windows:

SMB 1.0 – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2

SMB 2.0 – The version used in Windows Vista (SP1 or later) and Windows Server 2008

SMB 2.1 – The version used in Windows 7 and Windows Server 2008 R2

SMB 3.0 – The version used in Windows 8 and Windows Server 2012

SMB 3.02 – The version used in Windows 8.1 and Windows Server 2012 R2

SMB 3.1.1 – The version used in Windows 10 and Windows Server 2016

nsg_dev

Level 1

4 points

Jan 3, 2018 2:43 PM in response to Rayk217

How do you connect via cifs:// from the Finder? Shares that come up via smb:// produce the error "There was a problem connecting to the server 'Server'. Check the server name or IP address, and then try again."

smb:// mounts the share but replacing the prefix with cifs:// produces the error. Does cifs require mounting from the command line or can it be done from the Finder?

MacOS High Sierra 10.13.2 causing Finder crash