13.01.2021

Windows Hello Something Went Wrong

38

Just upgraded to Windows 10 and chose to use a local account when I set up this computer. But now when I go to Start > Settings > Accounts and click on the 'Sign in with a Microsoft account instead' link, I keep getting the message 'Something went wrong'. Net result is that I am unable to sign into my Microsoft account through this method. Please tell me how to fix this.

  1. Windows Hello Something Went Wrong On Our End
  2. Windows Hello Something Went Wrong 1909
  3. Windows Hello Something Went Wrong And Your Pin Isn't Available
  4. Pin Unavailable Windows 10

Can't switch from local account to Microsoft account? Cannot sign into Microsoft account in Windows 10 to use Cortana, Microsoft Store, or any other features? Now this page will show some useful solutions to fix this issue.

Hi, You may try the following steps: 1.Try to create the PIN again. Some errors are transient and resolve themselves. 2.Sign out, sign in, and try to create the PIN again. Something Went Wrong, Please Try Again (Windows Hello at power on). Windows Hello provides an alternative way for users to log into their respective devices using iris scan, facial recognition, or fingerprint scan. It can also be used to sign into apps, online services, and networks. In some cases, Windows Hello simply stops working after an update, a Windows reset, or without an apparent reason at all.

Common issues:

Part 1: Cannot sign into Microsoft account - Something went wrong

Many Windows 10 users cannot sign into Microsoft account and are stuck in the message 'Something went wrong'. This usually happens when they click Sign in with a Microsoft account instead but find cannot switch from a local account to Microsoft account, or try to sign in Cortana/Windows Store with Microsoft account. The causes can be various. I sum up several available solutions you can try.

Solution 1: Network speed

If your internet is disconnected or the net speed is very slow at that moment when you are trying to sign in to Microsoft account, it is likely to become the reason why your Windows 10 cannot sign in Microsoft account. In this case, you have to diagnose your network connection and take a few more attempts until you can sign in successfully.

If that is not the network problem and still you cannot sign into Microsoft account in Windows 10 after many attempts, try the following solutions.

Solution 2: Create a new local account

Another reason why your Windows 10 cannot sign into Microsoft account is there may be an issue with your current user profile. In this case, you can create a new local admin account.

Step 1: Open Windows 10 Command Prompt as administrator.

Bad piggies crack. Bad Piggies v1.5.1 Crack.rar 226.71 KB It will only get better! Free ANSWERS and CHEATS to GAMES and APPS. Thank you for visiting Datafilehost.com, the leading provider of the latest downloads on the Internet! We appreciate your visit and hope that you enjoy the download! We appreciate your loyalty. TAGS: Bad Piggies V1.5.1,Piggies V1.5.1 Crack,V1.5.1 Crack Free,Crack Free No. Links to download this video: Download Bad Piggies V1.5.1 windows 10 64 bit 2020 Augu 06 Thu. Advertisement Related Downloads For Piggies V1.5.1 Crack windows rt 2020 Augu 06 Thu.

Step 2: Type net user <username> /add (for example: net user iSumsoft /add) and hit Enter key to add a new local user account. Then type net localgroup Administrators <username> /add and hit Enter key to make the user an administrator account.

Step 3: Sign out your current account. Then sign in Windows 10 with the newly added local admin account and then try to sign into (switch to) Microsoft account.

Tips: This way worked for many Windows 10 users including myself.

Solution 3: Check Microsoft account sign-in assistance service

One of the reasons why your Windows 10 cannot sign into Microsoft account is likely because Microsoft account sign-in assistance service is not turned on.

Step 1: Press Win + R keys to bring up the Run dialog box. Then type services.msc and click OK.

Step 2: The Services window opens. On the right pane scroll down to find Microsoft Account Sign-in Assistant Service, and then double-click on it.

Step 3: Make sure the Service status is Start. Click the drop-down behind the Startup type and select Automatic or Manual. Then click Apply and OK to save the changes.

Windows Hello Something Went Wrong

Step 4: Restart your computer and then try to sign in Windows 10 with Microsoft account.

If this still cannot work for you, try the following solutions.

Solution 4: Troubleshoot by program

Step 1: Download the program Microsoft Accounts troubleshooter.

Step 2: Run the program. It will automatically detect invalid settings on your system. Just need to click Next and wait till troubleshooting is completed.

Step 3: Once problems are fixed, reboot your Windows 10 and then try to sign in to Microsoft account.

If this still cannot work for you, what a pity! I’m afraid you have to reinstall system.

Part 2: Cannot sign into Microsoft account – Password is incorrect

If Windows 10 cannot sign into Microsoft account because of an incorrect password, things will be much easier. Just need to reset the password.

(1) If your Microsoft account is tied to your local account, reset your password from https://account.live.com/resetpassword.aspx.

(2) If your Microsoft account has existed independently on your Windows 10, you can reset Microsoft account password from Windows 10 login screen or by using our software product Windows Password Refixer.

Related Articles

  • How to Secure Your Microsoft Account
  • Locked Out of Microsoft Account on Windows 10
  • Why Do I Need a Microsoft Account for Windows 10
  • How to Create Administrator Account When Can't Sign in Windows 10
  • A New Way to Unlock Microsoft Account Using Your Phone instead of Password
  • Fixed: Windows 10 User Account Not Appearing on Login Screen
-->

Applies to

Windows Hello Something Went Wrong
  • Windows 10

When you set up Windows Hello in Windows 10, you may get an error during the Create a PIN step. This topic lists some of the error codes with recommendations for mitigating the problem. If you get an error code that is not listed here, contact Microsoft Support.

Windows Hello Something Went Wrong On Our End

Where is the error code?

Acid pro 7 serial number. The following image shows an example of an error during Create a PIN.

Error mitigations

When a user encounters an error when creating the work PIN, advise the user to try the following steps. Many errors can be mitigated by one of these steps.

  1. Try to create the PIN again. Some errors are transient and resolve themselves.
  2. Sign out, sign in, and try to create the PIN again.
  3. Reboot the device and then try to create the PIN again.
  4. Unjoin the device from Azure Active Directory (Azure AD), rejoin, and then try to create the PIN again. To unjoin a desktop PC, go to Settings > System > About and select Disconnect from organization. To unjoin a device running Windows 10 Mobile, you must reset the device.
  5. On mobile devices, if you are unable to setup a PIN after multiple attempts, reset your device and start over. For help on how to reset your phone go to Reset my phone.If the error occurs again, check the error code against the following table to see if there is another mitigation for that error. When no mitigation is listed in the table, contact Microsoft Support for assistance.
HexCauseMitigation
0x80090005NTE_BAD_DATAUnjoin the device from Azure AD and rejoin.
0x8009000FThe container or key already exists.Unjoin the device from Azure AD and rejoin.
0x80090011The container or key was not found.Unjoin the device from Azure AD and rejoin.
0x80090029TPM is not set up.Sign on with an administrator account. Click Start, type 'tpm.msc', and select tpm.msc Microsoft Common Console Document. In the Actions pane, select Prepare the TPM.
0x8009002ANTE_NO_MEMORYClose programs which are taking up memory and try again.
0x80090031NTE_AUTHENTICATION_IGNOREDReboot the device. If the error occurs again after rebooting, reset the TPM or run Clear-TPM.
0x80090035Policy requires TPM and the device does not have TPM.Change the Windows Hello for Business policy to not require a TPM.
0x80090036User canceled an interactive dialog.User will be asked to try again.
0x801C0003User is not authorized to enroll.Check if the user has permission to perform the operation​.
0x801C000ERegistration quota reached.Unjoin some other device that is currently joined using the same account or increase the maximum number of devices per user.
0x801C000FOperation successful, but the device requires a reboot.Reboot the device.
0x801C0010The AIK certificate is not valid or trusted.Sign out and then sign in again.
0x801C0011The attestation statement of the transport key is invalid.Sign out and then sign in again.
0x801C0012Discovery request is not in a valid format.Sign out and then sign in again.
0x801C0015The device is required to be joined to an Active Directory domain.​Join the device to an Active Directory domain.
0x801C0016The federation provider configuration is emptyGo to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the file is not empty.
0x801C0017​The federation provider domain is emptyGo to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the FPDOMAINNAME element is not empty.
0x801C0018The federation provider client configuration URL is emptyGo to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the CLIENTCONFIG element contains a valid URL.
0x801C03E9Server response message is invalidSign out and then sign in again.
0x801C03EAServer failed to authorize user or device.Check if the token is valid and user has permission to register Windows Hello for Business keys.
0x801C03EBServer response http status is not validSign out and then sign in again.
0x801C03ECUnhandled exception from server.sign out and then sign in again.
0x801C03EDMulti-factor authentication is required for a 'ProvisionKey' operation, but was not performed.
-or-
Token was not found in the Authorization header.
-or-
Failed to read one or more objects.
-or-
The request sent to the server was invalid.
Sign out and then sign in again. If that doesn't resolve the issue, unjoin the device from Azure Active Directory (Azure AD) and rejoin.
0x801C03EEAttestation failed.Sign out and then sign in again.
0x801C03EFThe AIK certificate is no longer valid.Sign out and then sign in again.
0x801C03F2Windows Hello key registration failed.ERROR_BAD_DIRECTORY_REQUEST. Another object with the same value for property proxyAddresses already exists. To resolve the issue, refer to Duplicate Attributes Prevent Dirsync. Also, if no sync conflict exists, please verify that the 'Mail/Email address' in AAD and the Primary SMTP address are the same in the proxy address.
0x801C044DAuthorization token does not contain device ID.Unjoin the device from Azure AD and rejoin.
Unable to obtain user token.Sign out and then sign in again. Check network and credentials.
0x801C044EFailed to receive user credentials input.Sign out and then sign in again.

Errors with unknown mitigation

Windows Hello Something Went Wrong 1909

For errors listed in this table, contact Microsoft Support for assistance.

Windows Hello Something Went Wrong And Your Pin Isn't Available

HexCause
0X80072F0CUnknown
0x80070057Invalid parameter or argument is passed.
0x80090020NTE_FAIL
0x80090027Caller provided a wrong parameter. If third-party code receives this error, they must change their code.
0x8009002DNTE_INTERNAL_ERROR
0x801C0001​ADRS server response is not in a valid format.
0x801C0002Server failed to authenticate the user.
0x801C0006Unhandled exception from server.
0x801C000BRedirection is needed and redirected location is not a well known server.
0x801C000CDiscovery failed.
0x801C0013Tenant ID is not found in the token.
0x801C0014User SID is not found in the token.
0x801C0019​The federation provider client configuration is empty
0x801C001AThe DRS endpoint in the federation provider client configuration is empty.
0x801C001B​The device certificate is not found.
0x801C03F0​There is no key registered for the user.
0x801C03F1​There is no UPN in the token.
​0x801C044CThere is no core window for the current thread.
0x801c004DDSREG_NO_DEFAULT_ACCOUNT: NGC provisioning is unable to find the default WAM account to use to request AAD token for provisioning. Unable to enroll a device to use a PIN for login.

Pin Unavailable Windows 10

Related topics