nsurlsessiond taking 60% of CPU

Hi, thanks for your reply. I will try that. Just to follow up on i_rina's post. The 2 runaway processes started almost immediately after I turned on my iMac this morning for some reason so I tried to stop the nsurlsessiond process from Activity Monitor but it returned straight away. However, I selected both the nsurlsessiond AND the trustd processes and 'Quit' them from their respective windows together as fast as I could and they have not returned as yet (only 2 hours but promising)! Also it does not appear to have caused other problems. So if they stay 'dead' for some time at least that gives me a better option than a restart. On another note, can I change my sign in name? It was done in haste as I tried several before I found one that was not already used and I don't like it.

Hi, thank you for your reply. Let me give you a few more details. I looked at the System Preferences as you suggest and it shows that lots of applications are enabled to use the iCloud including Photos. However, the runaway processes do not start immediately. If I restart my Mac I can use it for a long (but variable) time before they start and it seems they are not triggered by anything I do. After which, in order to continue working, I do a restart. Your reference to the iCloud is interesting as there are 2 MacBooks in the household using the iCloud and the user (Apple ID) of one is the 'owner' of the increased capacity iCloud if that makes sense (sorry the iCloud is a bit of a mystery to me). I am wondering whether the sharing options have changed in Catalina from my 'old' El Capitan OS.

Hi and thank you for your reply.

Yes your method does stop the problem temporarily but as you say, the trustd process does reappear (with nsurlsessiond) with the same consequences. Although I have not used 'terminal' before, I did use your method but I think I can get the same result by simply double clicking on trustd in Activity Monitor and selecting 'quit' in the first window displayed and then 'Force Quit' in the next. Is that correct as it seems much simpler?

I guess the real problem now is how to stop the runaway trustd and nsurlsessiond processes restarting.

Thanks once again and stay safe!

Hi again and thank you for your prompt reply and your patience.

My second attempt using the method you suggested appears to have been successful. I realised after reading the more detailed posts in the thread you provided the link to in your last post, that I had used the incorrect [randomised name] when removing the nsurlsessiond folder. So now having used the correct one everything seems fine.

Thanks once again.