This is where you put on your scrum-master hat, go into "protect the team" and "guide the process"-mode and have a talk with your colleague.
Ask him for a short meeting and talk to him. Your two questions are two different topics, so maybe even just do two meetings.
For the daily standup, ask him whether he understands the purpose of it. Is he the only person who gives you trouble over it? Do the other developers like hearing what's going on? Does he appreciate the update on the progress towards the sprint-goal?
Also, make sure you got the basics of a standup down:
It's always at the same time. So if he says "but I'm busy", you can say "we have the standup at this time every day. You know you're supposed to make sure you have a few minutes to do it".
And make sure it's valuable. If the standup is just "doing the motions", I can't blame your colleague for not caring about it. If it's actually worth attending, he'll probably stop complaining. If he doesn't, the rest of the team will start complaining because this guy is also taking up their time since they'll be waiting for him to attend.
Figure out why he isn't interested in gathering with the team to have a very short update on the most important thing of his job: making sure the sprint-goal can be met.
For the status updates explain him that the stakeholders want to be informed about his progress from time to time. Then ask what the best way to get these status updates is. Can he track task progress on a board somewhere? Does he prefer an email? IM somewhere? Whatever gives you the needed information without disturbing his progress.
Alternatively, also talk to the stakeholders. Is it really important to know right now? Is a daily update enough? Perhaps you can give them an update every day. Perhaps you can show them how to get the info they want directly from the sprint-backlog. Maybe they can join the standup (as long as they remember the rules: stakeholders stfu during standup) to get their update. Maybe they are just curious and they don't realize that their requests for updates are hurting productivity.
As a scrummaster, it's your job to talk to your team and find out what is bothering them and then deal with it. Sounds like step one is to find out what's bothering him. In this case, it's apparently something you do. Or maybe that's just a symptom and he's unhappy about something else. Find out what it is.