The case of Running the Device and Credential Guard Hardware Readiness Tool and unknown architecture

Fri, 31 May 2019 15:47:53 +0000

To close this week, let me share my findings with you about running the Windows Device and Credential Guard Hardware Readiness Tool and the unknown architecture error.

Believe it or not, there are still people, probably more than I assume, that run Windows in their native language instead of English. I can understand when end users do so, but honestly when administrating an infrastructure? Anyway, I recently worked for a client where the UI is set to German language, well after 10 minutes I felt so lost that I had to install the English language pack to become productive. While supporting the client to get ready for the Deployment of Windows Defender Credential Guard, following best practices I executed the Device Guard and Credential Guard Hardware Readiness Tool on one of their devices and got the following error:

Configuring Windows Defender Credential Guard with ConfigMgr

Wed, 27 Mar 2019 21:23:16 +0000

I’m currently engaged in multiple customer projects where Windows 10 is already in production, but unfortunately without Windows Credential Guard enabled. For those who think “Credential ….what?”

Windows Defender Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them. Unauthorized access to these secrets can lead to credential theft attacks, such as Pass-the-Hash or Pass-The-Ticket. More details can be found here.

Some of you might think, why wasn’t it enabled in the first place when they deployed Windows 10? From speaking to several people, here are some of the reasons.

Credentialguard on Anything About IT

The case of Running the Device and Credential Guard Hardware Readiness Tool and unknown architecture

Configuring Windows Defender Credential Guard with ConfigMgr