Windows 10: microsoft family saftey SUCKS

I can describe Microsoft family safety in 1 word: hell

:)

 

family saftey

My parent is no longer in charge of my laptop she moved out , but she installed family saftey on my laptop and i wanna remove it . But i cant because i dont know her passwrod for her account on my laptop . How can i take it off?

 

Can I set up an account protected by family saftey without it being a Microsoft Account?

In Windows 8, we had an account on the family computer called 'Kids'. It was a local account without a password, that was protected by family saftey. It was to be used by any kids in the family who came to visit.

When we upgraded to Windows 10, the family safety was gone. The new system says it needs a new Microsoft Account to use family saftey, but we want an account for ALL kids to use, JUST on this PC.

A local account made perfect sense, but doesn't seem to be an option any more.

What should we do to make a universal account for all kids to use, that has family saftey?

Has anyone else had to work around this problem?

 

Family Saftey is broken & can be totally bypassed. Will it be fixed?

Please re-read my post. All your questions are answered there.

Here are some quotes:

1. Are you signing in with the Administrator Account?

"Any Standard User, even when using a Microsoft Account in a family and designated as a Child, can remove all Family Safety coverage." So, not an Admin Account but a Standard User Account.

2. What do you mean by the statement Family Safety is now broken?

"Family Saftey ... can be totally bypassed". That is "broken" by any measure if your security can be bypassed.

Here are the steps to reproduce: "In 'Change Account Settings', in 'Your Account', select 'Sign in with a local account instead'. This makes the user a local user and outside of Family Safety." Thus "Users can now add and remove themselves at
will" from Family Safety. Time restrictions and usage tracking are unenforceable.

3. Since when are you facing the issue?

This is a Windows 10 problem as indicated by tagging this post as Windows 10. Since Windows 10 has been released for about 30 days, it is new.

I'd highly recommend trying the steps I included, then escalating this before you have a fiasco on your hands. I'm already looking at other solutions due to your response.