summaryrefslogtreecommitdiff
path: root/general/tracing/evntdrv/README.md
diff options
context:
space:
mode:
authorDen Delimarsky <[email protected]>2019-03-13 21:54:14 -0700
committerDen Delimarsky <[email protected]>2019-03-13 21:54:14 -0700
commit41c29cb92feff490270b4ce31f67d7baddecc457 (patch)
tree3601c61d3cf6919f2bea780cbdc3f4f3922d914f /general/tracing/evntdrv/README.md
parent18cabc43191fd82420adcfac56c0361de98360c9 (diff)
Diffstat (limited to 'general/tracing/evntdrv/README.md')
-rw-r--r--general/tracing/evntdrv/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/general/tracing/evntdrv/README.md b/general/tracing/evntdrv/README.md
index ba3dcd65..13c9542f 100644
--- a/general/tracing/evntdrv/README.md
+++ b/general/tracing/evntdrv/README.md
@@ -72,4 +72,4 @@ Evntdrv registers as a provider by calling the [**EtwRegister**](http://msdn.mic
## Notes
-If you are building the Eventdrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202). \ No newline at end of file
+If you are building the Eventdrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202).