New user logged off at log-on

I have upgraded my Vaio laptop to Win 10 Home, and with my single admin user have created a new non-admin local user (not with a Microsoft account). When logging in with this local user the log-on screen immediately says "Signing out" and that's it. Nothing.


I've been Googling and have found no cure, so here goes - full detail:


- The Vaio SVP, originally Win 8 was put through a full factory reset, then upgraded with Win 8 updates, then upgraded to 8.1, updated, then upgraded to Win 10. There's very little software installed apart from AV.


- New non-admin user created (non-Microsoft), then logged on with that user. Was immediately logged off. When I logged on with my admin account and looked at the Event viewer there were the following errors:


- The winlogon notification subscriber <SessionEnv> was unavailable to handle a critical notification event.
- Windows Search Service has created default configuration for new user 'VAIO\NewUser' .
- The description for Event ID 0 from source igfxCUIService2.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
- The description for Event ID 0 from source SynTPEnhService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
- Profile notification of event Create for component {2c86c843-77ae-4284-9722-27d65366543c} failed, error code is Not implemented
- User Profile Service - Windows cannot load classes registry file. DETAIL - The system cannot find the file specified.
- Winlogon - The Windows logon process has failed to spawn a user application. Application name: . Command line parameters: C:\Windows\system32\userinit.exe.
- User Profile Service - Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required.

So, I deleted the user, then tried creating the user as an admin. At first logon, which took 15-20 mins of setup, i finally arrived at the desktop. Great! But then trouble. Start button doesn't work, right-click desktop and choose personalize and getting an error message: ms-settings:display This file does not have a program associated with it.....

Based on advice elsewhere I can include:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit = C:\Windows\system32\userinit.exe,
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell = explorer.exe
- I've also tried creating the new user with the "net user /add" command, but same outcome


Any thoughts, advice, help?

Thanks
Mark

Just noticed that this has gone unanswered for 6 days. Are you still looking for a solution?

philc43 said:

Just noticed that this has gone unanswered for 6 days. Are you still looking for a solution?

Hi, I still have no solution. The only option open to me is to completely restore the laptop back to factory default (Win 8), then add the 2nd user, then follow the long and laborious upgrade route again.

If you have any means of fixing my Win 10 installation it would be greatly appreciated.

Hi Mark,

I think a W10 clean installation is best and login with your MS account before adding a new user.

You do not need to go through the long process of W8 to 8.1 but download the W10 from MS Tech Bench to a DVD or USB and select the correct home version to match what you had before. You skip any activation steps during the install and wait for W10 to activate itself once it is installed.

You will lose any software that came with your laptop but that may not be a bad thing!

Do first make a system image backup in case you do want to ever go back.

I've just done a repair install to fix a user account problem and I'm now getting the problem you describe immediately after a repair install - this is very disappointing.

Is there a known fix for this problem? If not, I fear a clean installation may be required.