Finder doesn't work since High Sierra

hudinho wrote:

I have issues with finder since I upgrade my Imac and MacBook pro 2017 to High Sierra. Any suggestions or reasons for that?

Thanks!

Your post contains zero details about your problems...please be more specific.

Thx CT for the tips:

- In the Guest modus here is only the option to use Safari.

- Same problem in the Safe mode

- I used the check of Entrecheck. No problem discovered.

But i got a workaround for the finder problem. Finder doesn't start(and disappeared in a sec) when i click the icon. But i can used finder with the shortcut keys. For now this workaround works for me.

Hi

I got this same problem!

Yesterday i reinstalled my MacBook Pro (Retina, 13-inch, Late 2013) with

macOS 10.13.3 (17D47) High Sierra. Now i got this problem that the Finder doesn't work anymore. I clicked the icon you see in a short moment the finder interface and than it disappeared. After a couple of times i got a problem repport.

some details of the report:

Application Specific Information:

Process: Finder [404]

Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

Identifier: Finder

Version: 10.13.2 (10.13.2)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Finder [404]

User ID: 501

Date/Time: 2018-02-04 19:56:17.506 +0100

OS Version: Mac OS X 10.13.3 (17D47)

Report Version: 12

Anonymous UUID: F934464F-BA79-7B10-DBD2-40042951077B

Time Awake Since Boot: 520 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[TIconCollectionViewFreeFormLayout sectionAtIndexIsCollapsed:]: unrecognized selector sent to instance 0x7f7fa8467390'

terminating with uncaught exception of type NSException

abort() called

can someone give some advice/help to solved this problem?

Thx!

Yuri

It could be something in the folder you tried to open, it could be something wrong with your OS installation, it could be third party software. In order to narrow down the possibilities, some standard things to try include:

Does this occur for a different user, e.g., Guest?

Does this occur after starting up in Safe Mode?

Consider the possibility of a third party software conflict. EtreCheck can be used to investigate what is installed.