Finder Weirdness in 10.13.4

[bayswater]

Since the most recent update on my MBP, I've been seeing a lot of strange things in the Finder. Holding off on updating the iMac until I can figure this out.

- Finder tells me a folder or server cannot be found because the original cannot be found, at the same time it is showing me the folder it cannot find and allowing access to the files.

- Finder freezes when simple moves or copies from one folder to another are attempted.

- Finder will not relaunch, or will not quit and after relaunch there will be two instance of the Finder running

- File management on servers or disks on other Macs gives frequent errors, "files not found" (which are shown in the Finder window), etc.

Restarting fixes these things, but even restarting is messy because the Finder interrupts the shutdown process.

Buggy apps are one thing, but a buggy Finder make a Mac a waste of space.

[mikehalloran]

Have you tried a Safe Boot?

[MIDI Life Crisis]

Same here on my wife's machine. Yes, tried Safe Boot and it seemed to fix things for a while, but after bout a week or so, it's getting wonky on the MBP. Trash Can unaffected AFAIK.

[bayswater]

Have you tried a Safe Boot?

Thanks. Will give it a go.

[bayswater]

That seemed to clear up some of the issues at least temporarily, but not all of them.

I notice that connections to drives on other Macs are done via my Apple ID even though I've logged onto these previously as an authorized user and stored the ID/PW in the Keychain. Maybe HS wants connections made via the Apple ID, but this makes a connection where drive contents cannot always be displayed, and file transfers don't always complete.

I also noticed that a Mini with 10.13.4 that has no mouse or keyboard (that I control with an Apple remote) does not recognize the remote about 1 in 3 times. Restarting fixes this, as it does most of these issues, but this is not good.

Another odd thing: while TM backups are working consistently, making a connection in the Finder to the TM device prompt for a password every time, as though it is being accessed for the first time, even though the ID/PW are saved in the Keychain.

I had a Windows XT PC from an employer a long time ago, and these sort of things happened a lot. I was told it was "security". Not being able to use your computer presumably solves some security problems, just like having your printer feed directly into a shredder, but it sure makes mess of the user experience.

[mikehalloran]

That seemed to clear up some of the issues at least temporarily, but not all of them.

I notice that connections to drives on other Macs are done via my Apple ID even though I've logged onto these previously as an authorized user and stored the ID/PW in the Keychain. Maybe HS wants connections made via the Apple ID, but this makes a connection where drive contents cannot always be displayed, and file transfers don't always complete.

I also noticed that a Mini with 10.13.4 that has no mouse or keyboard (that I control with an Apple remote) does not recognize the remote about 1 in 3 times. Restarting fixes this, as it does most of these issues, but this is not good.

Another odd thing: while TM backups are working consistently, making a connection in the Finder to the TM device prompt for a password every time, as though it is being accessed for the first time, even though the ID/PW are saved in the Keychain.

I had a Windows XT PC from an employer a long time ago, and these sort of things happened a lot. I was told it was "security". Not being able to use your computer presumably solves some security problems, just like having your printer feed directly into a shredder, but it sure makes mess of the user experience.

I’d elevate this to Apple support. You can get phone support for just about any reason but an OS upgrade definitely qualifies. Go through the support links at apple.com and schedule a window for a call back.

I suspect that, when the Time Machine issue is resolved, the rest should be good. I have 4 Macs running 10.13.4 around here and mine running 10.13.3. None are having these issues—you know I’d be hearing about it if they were.