new local account wont sign in W10 (with correct password)

thenewoc · 2 May 2016 at 19:56

Have a laptop to send back to lenovo and they have asked us for our user password to be placed in with the item.

Not being keen on including a ms account password I thought I'd set up another user as a local account. However, each time signing in is attempted as the new local account it just says signing out straight away.

I think this is W10 Home 64bit, it has the option to create family and other users in 'Settings > Accounts > Family and other users' so rather baffling...

Any ideas please?

BigBoy · 3 May 2016 at 00:03

sign out of the system with the MS account and re create a local account.

thenewoc · 3 May 2016 at 09:07

Hi, the ms account was the admin account though. When I created a new admin local account, that didn't form properly either as it only had a desktop and no start menu.

Is all packed up ready for courier now so i'll probably receive a factory restored image when it comes back. Am guessing it's either a bug with W10 or somehow broken from in place upgrades from W8 to current W10.

It also had a 'users/default.migrated' folder which I understand is meant to be the basis of a new users profile albeit it's usually 'users/default' on a non updated system.

Bantu · 3 May 2016 at 11:00

I've had this with windows 10 before, where the profile becomes corrupted and signs me out every time. If memory serves it was something to do with the tiles in the start menu. There is a circuitous workaround somewhere on the internet. I can find this (on BT forums of all places), but don't think it's the one i followed:
http://home.bt.com/tech-gadgets/com...g-here-are-four-ways-to-fix-it-11364000314532

Best bet is to re-format though.

thenewoc · 3 May 2016 at 11:46

Thanks Bantu, when it comes back from Lenovo I'll most likely do a fresh install since it was full of bloat ware before anyway. Hard to say whether it was the Lenovo image that was somehow corrupt from their meddling or a side effect of the home edition being gimped in some ways, resulting in this bug.

Having said that I did find feedback yesterday from those with the Pro version having the same difficulties.

leigh_boy · 4 May 2016 at 08:22

iv had it where the logon language is different to the profile languages e.g US at logon and Uk when in.