Upgraded to 15.2: problem with Finder (and win network shares)

[Schroinx]

I have upgraded my air 7,2 with the latest update. Since I did that, I have had problems with Finder stalling. I can kill the process but when I try to restart it by clicking on the icon in the bar, nothing happens and the process does not start. If I right click and chose relaunch nothing happens either. The dock works with other programs, so it is finder that is the issue. I need to reboot the machine to get it back.

Any advice?

 

[jpn]

I have upgraded my air 7,2 with the latest update. Since I did that, I have had problems with Finder stalling. I can kill the process but when I try to restart it by clicking on the icon in the bar, nothing happens and the process does not start. If I right click and chose relaunch nothing happens either. The dock works with other programs, so it is finder that is the issue. I need to reboot the machine to get it back.

Any advice?

if you make a new test file, in pages or numbers for example, can you open that file through Finder?
and, can you open that same file also through the Recent Items menu (apple/Recent Items)?
and is that test file saved in the same location as the other files you see in Finder but cant open?
lastly, do you have enabled iCloud Disk?

it sounds like Finder isn't being given the proper permission to open those files you are having trouble with.
when you updated to the new macOS update, were those files already on yr local disk? or did you move them there after you updated?
are the apps to open these files located in the (your disk)/Applications ? or are the apps in a different Applications location?

 

[Schroinx]

if you make a new test file, in pages or numbers for example, can you open that file through Finder?
and, can you open that same file also through the Recent Items menu (apple/Recent Items)?
and is that test file saved in the same location as the other files you see in Finder but cant open?
lastly, do you have enabled iCloud Disk?

it sounds like Finder isn't being given the proper permission to open those files you are having trouble with.
when you updated to the new macOS update, were those files already on yr local disk? or did you move them there after you updated?
are the apps to open these files located in the (your disk)/Applications ? or are the apps in a different Applications location?

When I restart, it works. Then after some hours Finder would stall. When that happens, I cannot get a Finder window and the process is red in process viewer and I cannot restart it. I can still access files throu recent menus. I don't use icloud but googles backup/file software.
When I restart the computer, I have to force it, as it stalls.

It all started after the last update, but that my just be coincidence. The files where already there before the update. I don't think it is related to access rights.

Can it be the HD card that is failing after some time? Is there a utility to check it?

 

[jpn]

When I restart, it works. Then after some hours Finder would stall. When that happens, I cannot get a Finder window and the process is red in process viewer and I cannot restart it. I can still access files throu recent menus. I don't use icloud but googles backup/file software.
When I restart the computer, I have to force it, as it stalls.

It all started after the last update, but that my just be coincidence. The files where already there before the update. I don't think it is related to access rights.

Can it be the HD card that is failing after some time? Is there a utility to check it?

understood.
so, you can open files using Finder after a reboot, but after some time when you try to open a file the file won't open at all.

sounds disk space is so low that it doesn't have room to make temporary copies (which it needs to do during opening a file).
or, RAM related (process or Finder not releasing RAM)
this sounds a little bit like what happened to me one time:
i accidentally deleted a folder that contained several GB of data.
but i stopped the delete about 2 or 3 seconds after i realized what i had done.
my Air became very slow. so i rebooted.
could open files but computer remained sluggish for about 3 or 4 hours even after a reboot.

i realize its not just a 3 or 4 hour problem for you, but the point is, the OS is trying to deal with an issue and during that time it isn't giving enough resources to other tasks even opening files.
you might want to do an SMC reset that might be able to reset yr starting state after a reboot.
and of course doing Force Quit on all open apps including Finder before you do that.

 

[Schroinx]

I have gotten a little further in pinning the issue down. I am using network shares on my windows server. Using this with a mac already sucks, but so far it has just been annoying that it would loose the mounted drives now and again and I would have to remount them. The network works just fine as I can access the server with MS remote desktop from the mac and the shares from another windows computer.

What appears to happen, is that if the server drives is in power down and hence take a few seconds to spin up, finder looses the network drives and stall, and then I have to reboot to restore finder to a working state. I have to force the last part of the reboot by pressing the power button, as the reboot stalls.

I'll try the SMC reset later, for good measure.

 

[jpn]

I have gotten a little further in pinning the issue down. I am using network shares on my windows server. Using this with a mac already sucks, but so far it has just been annoying that it would loose the mounted drives now and again and I would have to remount them. The network works just fine as I can access the server with MS remote desktop from the mac and the shares from another windows computer.

What appears to happen, is that if the server drives is in power down and hence take a few seconds to spin up, finder looses the network drives and stall, and then I have to reboot to restore finder to a working state. I have to force the last part of the reboot by pressing the power button, as the reboot stalls.

I'll try the SMC reset later, for good measure.

i think you have pinpointed the problem.
great.

 

[SuperSonic80]

Apple really messed up in Catalina. I have a problem with network shares too. Primarily, when I bring my laptop back home and try to connect to my NAS. Two possible scenarios usually happen:
1) I cannot connect to NAS even though it is visible in Networks (this is a rare case).
2) I cannot open the shared folder. I can see it in the Finder, and Finder actually shows it as "mounted", however, when I click I get an error, something like: "Cannot find the folder" (this happens almost every day).

However, if I restart the Finder, everything starts works as should be, but sometimes Finder "hangs" as you described (I cannot open it after restart). The only solution here is a complete restart.

I tried SMB and AFP separately, but the problem persists. So far I could not find a permanent solution to fix the problem.

Maybe one day I'll try to do a clean install of Catalina (currently I installed Catalina on top of Mojave).

I have gotten a little further in pinning the issue down. I am using network shares on my windows server. Using this with a mac already sucks, but so far it has just been annoying that it would loose the mounted drives now and again and I would have to remount them. The network works just fine as I can access the server with MS remote desktop from the mac and the shares from another windows computer.

What appears to happen, is that if the server drives is in power down and hence take a few seconds to spin up, finder looses the network drives and stall, and then I have to reboot to restore finder to a working state. I have to force the last part of the reboot by pressing the power button, as the reboot stalls.

I'll try the SMC reset later, for good measure.

 

[MBPmac]

Same problem here, even after a clean install of last 15.2 version. Did not happen with 15.1

 

[frimage]

I have the same problem. I have NAS (qnap TS-228A, SMB) connected to my network.
Every single time, since upgrade to 10.15.2, when I re-open (waking-up) my MBP, Finder can't open shared folder. Only complete restart (MBP) works.
Even when Finder hangs I can still access my NAS using web browser, Windows PC, iPad, iPhone...
Clean install of Catalina didn't help.

 

[xnsys]

Seems to be a known issue - have a read through this thread.

macOS Catalina 10.15.2 freezes/crashes MBA every single day – am I alone?

Hi everyone, I can't find any info on this so I'd like to check if I'm alone. I'm running Catalina on a MBA late 2013 and have been upgrading from Mojave to 10.15.1. Everything was working fine until 10.15.2 dropped. Since I installed 10.15.2 my MBA freezes every single day. Mostly when...

forums.macrumors.com

 

[AJMike]

Seems to be a known issue - have a read through this thread.

macOS Catalina 10.15.2 freezes/crashes MBA every single day – am I alone?

Hi everyone, I can't find any info on this so I'd like to check if I'm alone. I'm running Catalina on a MBA late 2013 and have been upgrading from Mojave to 10.15.1. Everything was working fine until 10.15.2 dropped. Since I installed 10.15.2 my MBA freezes every single day. Mostly when...

forums.macrumors.com

Same problem! I have decided to go back to Mojave. Catalina is as bad as old Windows Os!

 

[AJMike]

• #71

So I downloaded Onyx and ran the maintenance tab and “Eureka” my 2013 MBP is now functioning normally?. Next task is to make a donation to the Onyx developers

 

[MBPmac]

• #71

So I downloaded Onyx and ran the maintenance tab and “Eureka” my 2013 MBP is now functioning normally. Next task is to make a donation to the Onyx developers

Tried this too, alas to no avail... will not donate ;-)

 

[Schroinx]

Have anyone tried installing the .3 update and to see if this clears the problem?

 

[xnsys]

10.15.3 fixes the SMB issue it would appear...

 

[AJMike]

After a week or so (about mid-January) my MBP went back to its Catalina habits. I gave up trying to find a fix and reinstalled Mojave. I have had NO issues since reverting. Catalina must have been written by someone at Microsoft!

 

[MBPmac]

Have anyone tried installing the .3 update and to see if this clears the problem?

Much better now. Seems to be solved for me with .3