Thank you for that clarification—it's a helpful detail!
I also want to clear up one important point from your update:
"We did not realize the company email address was setup as a child account..."
Just to be perfectly clear, your company email was never a child account. It was automatically assigned the role of the "Organizer" or "Parent" in the Family Safety group.
You are experiencing the child filter because your company account is operating inside the Windows profile that was built by the child account.
Thus, one approach you can try, is to create a new, untainted local administrator account on the machine, migrate the user's data, and then delete the problematic profile. Please follow these steps in order to perform the action.
1.Boot into Advanced Startup / Command Prompt:
- On the Windows login screen, hold down the Shift key + click the Power icon in the bottom-right corner, and then click Restart.
- The computer will reboot into a blue screen with options. Navigate to Troubleshoot -> Advanced options -> Command Prompt.
2.Create a New Local Administrator Account:
- In the Command Prompt, we will create a new local user. Type the 2 following commands, pressing Enter after each one. Replace
NewAdmin with a temporary username and StrongP@ssw0rd! with a secure password.
net user NewAdmin StrongP@ssw0rd! /add
net localgroup administrators NewAdmin /add
- This creates a new user named
NewAdmin and adds it to the local administrators group, giving it full permissions.
- Close the Command Prompt: click the X in the top-right corner of the black window.
- Continue to Windows: After closing the command prompt, you will be returned to the blue recovery screen. Look for and click the option that says "Continue" or "Exit and continue to Windows".
- Restart: Your PC will restart automatically. This is a normal boot-up.
- Log In: When the login screen appears, you should now see the new account you created,
NewAdmin, in the list of users (usually in the bottom-left corner). Click on it and log in with the password you set.
- Log into this account. You will go through a brief "Hi, we're getting things ready for you" process as Windows builds the new profile.
3. Set Up the New Hire's Account Correctly:
- Once logged in as
NewAdmin, go to Settings > Accounts > Family & other users.
- Add the new hire's company email (
Work or school account). Crucially, make this account an Administrator.
- Sign out of
NewAdmin.
4.Log In as the New Hire & Migrate Data:
- Log in using the new hire's company email account. A fresh, unrestricted profile will be created.
- Open File Explorer. Navigate to
C:\Users\.
- You will see the folder for the old, problematic profile (e.g.,
C:\Users\T.M.) and the new one.
- Open the old user's folder. You may be prompted for admin permission; grant it.
- Copy the necessary files (from Desktop, Documents, Pictures, etc.) from the old profile folder to the new profile folder. Do not copy entire folders from the root of the old profile (like AppData), as this can bring over the corrupt settings. Be selective. Cleanup:
- Once you are certain all necessary data has been migrated, you can log back into the
NewAdmin account and remove the original, problematic user account via Settings > Accounts > Family & other users. This will also delete its associated user folder and free up space.
- You can then also remove the temporary
NewAdmin account itself, leaving only the new hire's clean administrator account.
I recognize these steps involve re-configuring the user's profile, but this is the most direct and effective path to bypass the locked-down state caused by the deleted MSA. This procedure isolates and removes the problematic component (the local profile) without needing to recover an account that is, for all practical purposes, unrecoverable.
Please proceed with this action plan and let me know the results.
Best regards,