Windows 10: Can someone help me with... "Something went wrong. We're unable to send your request. Are...

My sons laptop gives us this message when he starts it and after it says he has to ask for more permission. I've gone into my account and removed the restrictions. Internet is connected. I've restarted both computers. I've hard-started his. I've turned the internet on and off and restarted both computers. My laptop and phone show the updated screen time. Anyone have any other ideas?

:)

 

Send A Request

This used to work. It would enable them to send an email and I could remotely give more time. Now child using computer runs out of time so wants more of course, clicks on send request but gets "something went wrong we were unable to send your request.
are you connected to the internet?" No other prompt.

 

Help Me Understand What I'm Doing Wrong

I may be missing something, but I think what's being suggested is you use the arrow to choose another different method other then 'phone number' such as email or an authentication app, whatever's on the drop down list that's not a phone number.

 

Child unable to submit request for additional time

I have two child accounts setup under my family. Both were working fine until recently. I have both accounts setup so that they must send a request to me for time before they are allowed to log in. This way I know their homework and chores are completed.

One child account is able to submit the request for time. The 2nd child account gets an error every time stating "Something went wrong. We were unable to send your request. Are you connected to the Internet?" He is connected to the internet.

We have tried the following:

• Rebooting several times
• Logging into his Microsoft account to ensure its verified and that he is assigned to the correct device
• Opening up the time limits so that he can log in for an hour daily

He still gets the message when he attempts to send a request. I don't understand why his account is getting this, but the other child account is working perfectly fine.

Please advise how I can correct this issue.