*driver* did not meet the Store signing level requirements - Windows 10 Code Integrity

**This error message is related to Device Guard Code Integrity in Windows 10 and shows up in the Event Viewer under the Code Integrity folder. As of writing this article, the error message is not described in online documentation of Microsoft.** In the current scenario, the built-in Windows 10 apps like the Calculator, Alarms & Clock or the Photos app will instantly crash after opening it. This error message tells that the sysfer.dll is not trusted by Microsoft and therefore cannot interfere with the Alarms & Clock app. ...

21-04-2018 · 2 min · Jean-Paul van Ravensberg

Unknown Devices when installing Hyper-V on Windows 10

The following unknown device IDs will pop-up when you run the script or when you open Device Manager: ROOT\VMBUS\0000 ROOT\VID\0000 ROOT\VPCIVSP\0000 ROOT\STORVSP\0000 ROOT\SYNTH3DVSP\0000 If you want to find all Unknown Devices, open PowerShell as an Administrator and run: Get-WmiObject Win32_PNPEntity | Where-Object { $_.ConfigManagerErrorCode -ne 0} | Select DeviceID On my work notebook, all drivers were correctly populated so it had to be something with my test laptop. It’s a fresh Windows 10 machine deployed by a Task Sequence - enabled with Device Guard and Credential Guard. ...

11-09-2017 · 1 min · Jean-Paul van Ravensberg

Screen display flashes or blinks if Device Guard or Credential Guard with Hyper-V has been enabled

When you enable Device Guard or Credential Guard with Hyper-V on your system, your screen will blink every X seconds. This is a really annoying bug and has been fixed by Intel. Solution: Upgrade your Intel(R) HD Graphics driver to version 20.19.15.4352.

25-01-2016 · 1 min · Jean-Paul van Ravensberg

Enable Hyper-V during Task Sequence in SCCM 2012 R2

Because I wanted to configure Device Guard with Windows 10, I need the Hyper-V Hypervisor to be enabled on Windows 10. I tried to do this with DISM and an answer file, but it’s not possible to enable Hyper-V during the Task Sequence Deployment because Hyper-V requires a couple of reboots. Solution Create a new “Set Task Sequence Variable” task in your Task Sequence. This will run the PowerShell command after the Task Sequence ends. I’ve set this task before enabling the Driver Package, but it should be possible to place this task anywhere you like. ...

25-01-2016 · 1 min · Jean-Paul van Ravensberg