diff --git a/WindowsPort.md b/WindowsPort.md
index b2989e3d..4e7f9696 100644
--- a/WindowsPort.md
+++ b/WindowsPort.md
@@ -1,9 +1,16 @@
+
+
 Compiling PicoTLS with Visual Studio 2017
 
 The source contains a Visual Studio 2017 solution (picotls/picotlsvs/picotlsvs.sln)
-which itself contains 5 projects:
+which itself contains 10 projects, including:
 
-* Three libraries, picotls.lib and its dependencies cifra.lib and uecc.lib;
+* picotls-core, building the core library
+* picotls-openssl, the library for the open-ssl backend
+* picotls-minicrypto, the library for the minicrypto backend
+* picotls-minicrypto-deps, the dependencies for the minicrypto backend
+* picotls-bcrypt, implementation of some crypto functions using Windows' bcrypt library
+* picotls-fusion, for the AES fusion code
 
 * A test project, testopenssl.exe, which will run on a console and
   execute the OpenSSL tests;
@@ -11,8 +18,8 @@ which itself contains 5 projects:
 * And, an example project, picotlsvs.exe, which will perform a TLS exchange
   in memory, and demonstrate how to use PicoTLS in windows.
 
-The code has a dependency on OpenSSL. When building the 32 bit projects (WIN32) it 
-expects to find:
+The example code has a dependency on OpenSSL. When building the 32 bit
+projects (WIN32) it expects to find:
 
 * OpenSSL header files under $(OPENSSLDIR)\include
 
@@ -28,7 +35,7 @@ You will need also to copy libcrypto.dll to the library that contains your
 executable, or to otherwise register that library. Be sure to copy the 32 bit 
 library or 64 bit library, depending on which type of project you build.
 
-Only two configurations are tested: "X86 Debug" and "X86 Release". The X64 configurations
-will compile, but are not tested yet.
+The integration tests with Appveyor check four configurarions: "X86 Debug",
+"X86 Release", "X64 Debug" and "X64 Release".
 
 Feel free to provide feedback and contribute.