Finder keep crashing on Mac Os High Sierra

@wefredi

Apple has told me they have a fix for it in 10.13.3. This is from a bug report filed:

>>This looks like a known bug that has been recently fixed, but currently has only shipped for iMac Pro.<<

>>You are encouraged to try the beta version of 10.13.3 (on a test system or separate partition, ideally) to see if the fix works for you.<<

>>macOS High Sierra 10.13.3 beta 4 build 17D34a https://developer.apple.com/download/<<

I've always had pretty good luck with the betas (sometimes better than the releases).

Maybe this can help you from the **** of reinstalling, possibly losing data, for it to just happen again.

Ugisv wrote:

- connected to server with cifs://192.xxx.x.xxx instead of smb://192.xxx.x.xxx

I am the only Mac in a Windows office - and I usually don't have any problems. I thought I waited long enough to upgrade to High Sierra, but almost immediately was getting the Finder crashes over the SMB connected servers.

Changing from SMB to CIFS has worked for me and it all seems to work fine - no more frustrating Finder crashes! It's not slowed down production either.

I'm happy to use this method until 10.13.3 comes out.

We have had this same issue with High Sierra.

I have just done another update to 10.13.3 and it seems to of fixed the problem!

Fingers firmly crossed.

Use Etrecheck https://etrecheck.com/

It's a nice software to find out problems in Mac , sometimes its wiser to take back up of all data , erase the data and reinstall the OS , it is time taking but your system will be free from all troubles .

Read this article macOS Sierra: Erase and reinstall macOS

So in my case (which I explained above) I am half-way with the solution

What I did

- cleared Finder preferences

- connected to server with cifs://192.xxx.x.xxx instead of smb://192.xxx.x.xxx

Connection worked, but got lost again

- switched off Windows Firewall off again

Everything works

- updated to last Public Beta

seemed to solve the Finder crashing issue (tried to put back smb connection, Firewall on, didn't connect, but didn't crash)

So now need to figure out what changes should be made in the windows firewall settings. Because at one point switching it on and off made it to refuse connection also for Win machines now. At the first glance everything looks ok.

Is there a Finder crash report for any of these ?. I recall some Adobe 'extension' shown in System Preferences - Extensions causing a similar problem for some, although the name escapes me at the moment.

Hey Guys,

Just coming back on to comment so after having to contact apple a COUPLE of times I finally came to a conclusion and hopefully the problem is officially fixed!! ::crossing fingers::

I have a backup of my iMac with an external hard drive... So I erased the iMac hard drive and reinstalled using the latest backup of my iMac from the external... YES I installed the latest backup with the same update again because I wanted to test it out.

So far So good... Also Apple stated they are working on it but have no current solution. I also mentioned this thread they stated its better to actually contact them then to just state on the apple threads. The threads are more for customers to discuss and conclude solutions together as we are doing. So even though we are complaining here it really doesn't help unless we actually tell them our selves.

Again I am working on my office iMac and two other iMacs got effected as well.

So far I just did my computer and most likely going to do the other two if the problem persists on those iMacs as well.

Hopefully this helps you guys out!

I had the same problem, one of a plethora of issues. It was one of the first ones which were resolved. I did a killall from the terminal among PRAM (3 cycles & SMC two times) a safe boot, and a power down/off & back up after about a minute being down. Not sure which one eliminated that issue because I was having more pressing problems but it did resolve itself one of the first things.

You might want to upgrade your system to 10.13.3 beta 5 (came out today) that seems to have solved quite a few of my issues. It's available to now to anyone if you sign up. Try it on a least concern computer.

I am suggesting turn the firewall off for the LAN. Microsoft put it in for those people who are out "in the wild" all the time as the default. Probably not a bad assumption, but when you are in a LAN there is no purpose and you just have to poke holes in it so you can get work done. If you have a good router with a firewall to the WAN, then you are good.

We have this problem on various MacBooks in our office – interesting is that the problem appeared for two more devices about 2 weeks after the upgrade to High Sierra.

In our case it could be something with the SMB shares we are using. We had Finder crashes both with Windows 2012 R2 server shares, and a Samba share running on an Ubuntu server.

In the Finder crash log I found something like SMB connection lost or similar, I have to look on Wednesday next week.

This only seems to happen to me when working with SMB shares at work so thanks for mentioning that where few others have. Interesting that I tried force-quitting/relaunching Finder and it won't fully relaunch. As you say, a hard reboot is required. Since I have 4 virtual machines running various test processes, this becomes nearly impossible! I guess I need to stick to using one Win10 VM for connecting to the SMB shares. Crazy! This wasn't happening until the last security upgrade.

>>Apple should listen more to the community to help solve all the bugs and issues. *JUST WISHING*<<

Have you filed a bug report? If you have not, they have no reason to listen. It's very easy to go to bugreport.apple.com

They have setup a means for you to communicate with them and this forum is not it. This is for user to user only.

File the bug report. It's simple and they usually respond to you. If they don't they will let you know that it's an issue they are working on and set it as a duplicate case.

I have solved the problem...... I downgraded back to El Capitan! Done. No finder issues. 😬😬😬