Windows 10: Windows credentials repeating every day

PaigeSmith4 · Apr 15, 2021

So i logged into my work laptop and its given mr a windiws credentials error i can connect to my vpn just fine

a colleague force changed my password for me and unlocked my active directory account. They also cleared my cache credentials that are to do with old password. However, every single day my AD needs unlocking, theres no cache credentisls saved in manager and i have logged off all other servers i use to make sure these arent causing the problem!

It comes up with the “change your password via lock screen” and every time i do that it then says “this account is locked”

any help is appreciated!

:)

Ryan Fra · Apr 15, 2021

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.

Brink · Apr 15, 2021

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

MarcinMrowiec · Apr 15, 2021

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

Start Credential Manger and add some Windows share credentials.

In a console window type 'cmdkey /list', which should list the added credentials

Create a task in a task manager:

Trigger: on user logon

Action: run cmd.exe

Tick the 'run with highest privileges' option

Reboot the machine and log in

In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
This looks like a bug

Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.

Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.

Windows 10: Windows credentials repeating every day

Windows credentials repeating every day

Windows credentials repeating every day

Windows credentials repeating every day

Windows credentials repeating every day - Similar Threads - credentials repeating every

Repeating BSOD every few days "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" And "VIDEO_TDR_FAILURE"

BSOD repeatedly within a day

Windows BSOD every day

Crashes every day

Credential Manager Repeatedly asks for "fix"

BSOD Every Day

Microsoft requesting credentials for every program, every day

Repeated Network Credentials Input

Endless repeating Credentials Prompt in Office365