Windows 10: Switch to Local Account in Windows 10

Are you able to remove the PIN if you didn't want it?

https://www.tenforums.com/tutorials/6...dows-10-a.html

 

The only option is to change to another pin.

 

The tutorial link I posted will show you how to remove it.

 

I have removed the pin but now have to sign in with the same M$ account password on both Release and Insider versions.
I think my original post asking your advice was not very clear, I have now amended it and hope you can come up with an answer.

Brink, please can you advise me on the following.

On the same computer I have W10 and W10 Preview on separate SSD.s , hot swapping to keep them separate. both on the same M$ Account.

W10 works perfectly with a password, but Preview is corrupt as source file cannot be found, will not open Metro tiles.

Have performed a refresh, and a clean install using the Media creation tool ISO, but the problem remains.
How can I repair the corrupt Preview version?

Is it perhaps using both versions on the same computer that M$ recognise that they both use the same motherboard?.

If I created a Preview Local Account would it solve the problem?

 

A local account wouldn't help since modern apps need a Microsoft account.

Please provide more details on when "Preview is corrupt as source file cannot be found" happens?

 

My first inkling that something was not right was Metro Tile apps would not open.

Did Admin Command prompts, Scannow and Dism checkhealth and restorehealth which indicated Corrupt source file could not be repaired.

Neither a Refresh or a clean install have rectified the problem.

My release to the public version works perfectly this being installed using the Windows Media tool, from which I also used the ISO to clean install the Preview.

 

Ah, ok. That would be best posted in a new thread to get support with since it's unrelated to this tutorial.

 

Appreciate your assistance and pointing me in the right direction, will post another thread, thank you.

 

I have an idea, about the anomalies I've described earlier. I just remembered that before the upgrade, in Win7 I was using the built-in admin account (SID: 500). So after the upgrade to Win10 the account was kept and probably that is causing some weird glitches here and there. I'm too lazy to test and confirm this guess, but maybe this can be a pointer to someone willing to check. *Smile

I remember having major headaches in Win8.1 (another PC) with the built-in admin, that made me switch to normal admin at the end. So maybe Win10 is improved in this regard too.

 

Hello niksus,

Thank you for posting back. Yes, that would be why you don't have an option to switch to a Microsoft account. The built-in elevated "Administrator" account can only be a local account.

 

If you check back, I was actually able to switch to MS account, but unable to go back to local.
That's the weird thing - it's the opposite of what should be happening *Smile

 

Yeah, I'm not sure how that happened. Is the account or it's user profile still named "Administrator"?

 

No, I've renamed it prior its activation.

 

I'm not sure what to suggest other than to reinstall Windows since this is the built-in Administrator account that has been messed up. *Sad

 

Yeah, I'm not looking for a solution anymore. I agree that reinstall is probably the only real fix.