Windows 10: Win10 experience depends entirely on the device.

I have a Surface Pro 1, i.e. a Signiature PC. Just pure windows etc.

Just got ''done'' setting up a friend's new laptop. 4GB, came with Win10, typical HP machine up to the ears in bloatware out of the box etc. Made it use a Microsoft Account for log-in, no problems, outside of it being extra slow to boot to the log-in screen (extra long black screen after HP logo, followed by a Windows Update swirling dots screen, and finally the log-in screen).

Got it back into Windows, and ran netplwiz to turn-off having to input the MS Account password every time the laptop is booted. Restarted, and it has malfunctioned it's log-in details, showing both the normal account and the MS account, with the MS Account saying I'm using the wrong password to log in etc.

Got back into Windows again, and just decided to change back to a normal account, meaning the friend is losing out on all the benefits of syncing with the MS Account etc.

But honestly I can't be bothered with all the behavioural inconsistencies that these slapass cheap laptops provide, in relation to my signiature spec SPro1, which "just works", no matter what tweaks or changes I make to the default settings.

:)

 

The vmcompute service depends on the following service: wcifs. This service might not be installed.

Wow, ok. Windows 10, Performance & system failures, PC sure sounded like the right place...

I'll go post my question over on TechNet.

Thanks for the reply.

 

Installation of Windows 10 - Pause restart for new PC Owner

I would like to keep the "first Install" "final boot" startup so that a recipient of the PC can experience the entire setup / startup. Is there a proper way to create a fresh install of Win10 and have it not perform the final boot? I have tried the PC
Reset options but they do not provide a fresh install startup experience.

Any thoughts / guidance?

enjoy.

/cp

 

switch back to the Microsoft ID and when you run netplwiz, enter the full e-mail address for the user name instead of just the username. I had a very similar thing happen to me a while back and that fixed it for me.