Windows 10: Credentials cannot be verified-trouble logging in

imf818imf818 · Nov 30, 2020

I have an HP Envy x360 and it is THE WORST purchase of my entire life. This computer SUCKS. It is only three years old and I have had so many problems with it it's truly ridiculous. Now, Microsoft has eliminated their customer support over the phone. WOOPEE. I hope some sees this message soon enough because the end of the school semester is here and my computer is impeding my ability to complete my homework.

I had this issue a while ago and it ended up being resolved but I don't know how. Once again, every single time I open my computer to log it in, I can log in once, ONCE before I have to completely shut my computer down so I can log back in. I can't let it go to sleep! AND it takes FOREVER to turn back on. My three year old computer is acting like a freaking dinosaur. I got a fake update several months ago and that put my computer out of the game for MONTHS because I don't have time to deal with this ****. I can't help but wonder if I am still dealing with the aftermath of that fake update. Anyways, once I log into my computer once and accidentally let it fall asleep because oh no I needed to switch the laundry out, I receive a message after I type in my pin and it has spent four minutes trying to log me in saying "the credentials could not be verified." Then if I type my pin in again, it tells me to set up a new pin. My facial recognition does the same thing. The only way I can solve the problem immediately is to turn my computer all of the way off and start it back up. If it catches my face when it finally does turn back on, I'm waiting another five minutes before it either logs me in or in 8 out 10 cases tells me it could not sign me in. I saw one other person with the same computer who had this problem in the support forum but none of the answers given to them were helpful to me. I am on my broken computer right now and I am not actively having trouble logging in. However, in about an hour when I leave for dinner, I will have this problem all over again. I am SO tired of this computer. I cannot believe I spent hundreds of dollars on it. Totally not worth it. Please help.

:)

Brink · Nov 30, 2020

Credential Guard lab companion

If you have heard about Credential Guard in Windows Server 2016 (and in Windows 10), but do not have an environment to try it out, here is a lab environment we built for you to play.

Lab access

The link will lead you to a sign up page, after that, you will see the following labs listed for Windows Server 2016:

Windows Server 2016 labs

There are 3 exercises in the “Implementing Breach Resistance Security in Windows Server 2016”:

Credential Guard

Remote Credential Guard

Device Guard

This blogpost will walk you through the Credential Guard lab details.

After click on the link of Breach Resistance lab, you be required to sign in and then you can launch the lab:

Sign-in

Launch page

It takes a few minutes to create the VMs, and once it has done, you will see the following machines prepared:

Initialize

DC: domain controller, which is not used for this exercise.

SRV01 and SRV02: both are Windows Server 2016, and used for the lab exercise.

Lab exercise – Explained

The steps are listed in the Content section:

Content

This lab is structured to cover the following in sequence:

Understand how attackers can use the hash in memory to gain access to domain controllers

Configure Credential Guard

Verify the hash in memory is protected using Credential Guard

You can follow the steps listed under the content section to complete the lab, the intent of the blog, is to break the procedures into groups, to help you understand the exercise better.

Prep the hash

Lsass.exe is the process which handles user logon, it stores the user credential information in its memory. The memory is cleared when the machine starts up. In this lab environment, all the virtual machines start at the time lab launches, when you logon to the machine, you will only have the logon user credential information in memory. In order to demonstrate an attacker gaining user access using other account’s hash, the first part of the lab is to simulate a server which has been running for a while, different users had remotely or locally connected to it, therefore, lsass memory stored many different user credential information.
This is accomplished by step 1-8.

Retrieving credential hash

Mimikatz is a popular tool for retrieving lsass memory information. The tool has been copied to the lab machines, step 9-13 walk you through the process of dumping lsass memory using Mimikatz.

Pass the Hash

Pass the hash is a hacking technique that allows an attacker to authenticate by using the underlying NTLM, instead of specifying the user password. In step 14 to 24, you will extract LabAdmin hash from lsass using Mimikatz, and use the hash to open a PowerShell console, and perform a couple of operations using the LabAdmin privilege:

Add a user to the domain admin group

Open remote PowerShell connection to a domain controller

Both operations could not be performed by the logon user. But using the hash of the LabAdmin, an attacker will be able to do it using the information retrieve from Lsass memory.

Configure and verify Credential Guard

Step 25 to 36 illustrate the steps to configure credential guard, then verify its status using msinfo32.exe and PowerShell.

Step 37 to 43 goes further to use Mimikatz to show the hash in Lsass is now encrypted using Credential Guard.

More info

The exercise illustrated the benefit of Credential Guard in Windows Server 2016 as well as Windows 10. For more information, you can find here.
Click to expand...

Source: Credential Guard lab companion Datacenter and Private Cloud Security Blog

See also:

Enable or Disable Credential Guard in Windows 10 Windows 10 Security System Tutorials

Verify if Credential Guard is Enabled or Disabled in Windows 10 Windows 10 Security System Tutorials

MaxBrand99 · Nov 30, 2020

Your credentials could not be verified

i am having the same problem that is listed here:

Your Credentials Couldn't be Verified

but none of those solutions are working for me

Ryan Fra · Nov 30, 2020

Windows Network Credentials

Hi Keith,

We suggest that you disable Credential Manager before mapping your Drives. Please follow these steps to disable Credential Manager:

In the search box type “Services”

Right click on “Services” and select “Run as Administrator”

In the Services Window, look for Credential Manager Service and click “Stop”.

Restart the computer and go back the Credential Manager Service and set it to “Automatic”.

Restart the computer again.

Please keep us updated if you were able to map your drives.

Windows 10: Credentials cannot be verified-trouble logging in

Credentials cannot be verified-trouble logging in

Credentials cannot be verified-trouble logging in

Credentials cannot be verified-trouble logging in

Credentials cannot be verified-trouble logging in - Similar Threads - Credentials cannot verified

CANNOT VERIFY MY CREDENTIALS for Windows 10 log-in pin

CANNOT VERIFY MY CREDENTIALS for Windows 10 log-in pin

CANNOT VERIFY MY CREDENTIALS for Windows 10 log-in pin

Credentials could not be verified

Your credentials cannot be verified

Your credentials cannot be verified

Credentials cannot be verified

Credentials cannot be verified

Credentials could not be verified