Readme update.HEADv1.0main

Signed-off-by: Toni Uhlig <matzeton@googlemail.com>

1 files changed, 4 insertions, 4 deletions

diff --git a/README.md b/README.md
index 7b8b757..050c1bb 100644
--- a/README.md
+++ b/README.md
@@ -3,13 +3,13 @@
 It is actually not a real bypass since it does only change the date to 01-01-2014 before signing the driver and restores it afterwards.
 The Kernel driver loader will accept all driver images as long as the code was signed by a *extended validation code signing certificate* which was not revoked.
 
-The DSE "bypass" works **only** on 1803, 1809, 1903. You **won't** be able to load *PastDSE* signed drivers on other Windows versions.
+The DSE "bypass" works **only** on Windows 10 x64: 1803, 1809, 1903. You **won't** be able to load *PastDSE* signed drivers on other Windows versions.
 But it is still possible to use *PastDSE* with other DSE disabling techniques e.g. enabling testsigning or using [EfiGuard](https://github.com/Mattiwatti/EfiGuard).
 It works, because *PastDSE* is basically a manual driver mapper, nothing more.
 
 
-# Dependencies
-- Visual Studio 2017 Community Edition
+# Build Dependencies
+- Visual Studio 2019 Community Edition (Visual Studio 2017 is still supported, see VS-2017 branch)
 - Windows 10 x64 1803, 1809 and 1903 (may work on older versions, not verified)
 - Windows 10 SDK 10.0.17763.0
 - Windows Driver Kit
@@ -21,7 +21,7 @@ The recommended way to install all dependencies is through [vs_community.exe](ht
 
 
 # HowTo
-If you do not want to build it from source, you can skip the text below and run `driver-start.bat` directly.  
+If you do not want to build it from source, you can skip the text below and download the build artifacts from Github.
 
 Assuming a successful (Debug) build, you have to do the automatic sign procedure by running `driver-sign.bat` as Administrator.  
 If the console window outputs something like `Number of files successfully Verified: 1` then the procedure was probably succesful.