From 4ca36ec74056be20a92f947bbe641accb9c0a505 Mon Sep 17 00:00:00 2001 From: John Tobin Date: Fri, 16 Jun 2017 16:59:00 -0700 Subject: [PATCH] Remove reference to WSH --- ...nd-getting-started-on-the-device-guard-deployment-process.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/device-security/device-guard/planning-and-getting-started-on-the-device-guard-deployment-process.md b/windows/device-security/device-guard/planning-and-getting-started-on-the-device-guard-deployment-process.md index b8c330f882..d3919505b8 100644 --- a/windows/device-security/device-guard/planning-and-getting-started-on-the-device-guard-deployment-process.md +++ b/windows/device-security/device-guard/planning-and-getting-started-on-the-device-guard-deployment-process.md @@ -73,3 +73,5 @@ This topic provides a roadmap for planning and getting started on the Device Gua > Virtualization-based protection of code integrity may be incompatible with some devices and applications. We strongly recommend testing this configuration in your lab before enabling virtualization-based protection of code integrity on production systems. Failure to do so may result in unexpected failures up to and including data loss or a blue screen error (also called a stop error). For information about enabling VBS features, see [Deploy Device Guard: enable virtualization-based security](deploy-device-guard-enable-virtualization-based-security.md). + +
\ No newline at end of file