diff --git a/windows/deployment/volume-activation/images/vamt-known-issue-message.png b/windows/deployment/volume-activation/images/vamt-known-issue-message.png
new file mode 100644
index 0000000000..5ce1a31e1f
Binary files /dev/null and b/windows/deployment/volume-activation/images/vamt-known-issue-message.png differ
diff --git a/windows/deployment/volume-activation/vamt-known-issues.md b/windows/deployment/volume-activation/vamt-known-issues.md
index 70933d12f6..8022121cb3 100644
--- a/windows/deployment/volume-activation/vamt-known-issues.md
+++ b/windows/deployment/volume-activation/vamt-known-issues.md
@@ -1,25 +1,69 @@
----
-title: VAMT Known Issues (Windows 10)
-description: VAMT Known Issues
-ms.assetid: 8992f1f3-830a-4ce7-a248-f3a6377ab77f
-ms.reviewer: 
-manager: laurawi
-ms.author: greglin
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: activation
-audience: itpro
author: greg-lindsay
-ms.date: 04/25/2017
-ms.topic: article
----
-
-# VAMT Known Issues
-
-The following list contains the current known issues with the Volume Activation Management Tool (VAMT) 3.0.
--   The VAMT Windows Management Infrastructure (WMI) remote operations may take longer to execute if the target computer is in a sleep or standby state.
--   Recovery of Non-Genuine computers is a two-step process. VAMT can be used to install a new product key and activate the computer. However, the computer itself must visit the [Windows Genuine Advantage](https://go.microsoft.com/fwlink/p/?linkid=182914) Web site to revalidate the computer's Genuine status. Upon successfully completing this step, the computer will be restored to full functionality. For more information on recovering Non-Genuine Windows computers, go to [Windows Volume Activation](https://go.microsoft.com/fwlink/p/?linkid=184668).
--   When opening a Computer Information List (.cil file) saved in a previous version of VAMT, the edition information is not shown for each product in the center pane. Users must update the product status again to obtain the edition information.
--   The remaining activation count can only be retrieved for MAKs.
- 
- 
+---
+title: VAMT known issues (Windows 10)
+description: Volume Activation Management Tool (VAMT) known issues
+ms.assetid: 8992f1f3-830a-4ce7-a248-f3a6377ab77f
+ms.reviewer: 
+manager: laurawi
+ms.author: greglin
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: activation
+audience: itpro
+author: greg-lindsay
+ms.date: 12/17/2019
+ms.topic: article
+ms.custom: 
+- CI 111496
+- CSSTroubleshooting
+---
+
+# VAMT known issues
+
+The following list and the section that follows contain the current known issues regarding the Volume Activation Management Tool (VAMT), versions 3.0. and 3.1.
+
+- VAMT Windows Management Infrastructure (WMI) remote operations might take longer to execute if the target computer is in a sleep or standby state.
+- When opening a Computer Information List (CIL file) that was saved by using a previous version of VAMT, the edition information is not shown for each product in the center pane. Users must update the product status again to obtain the edition information.
+- The remaining activation count can only be retrieved for MAKs.
+
+## Can't add CSVLKs for Windows 10 activation to VAMT 3.1
+
+When you try to add a Windows 10 Key Management Service (KMS) Host key (CSVLK) or a Windows Server 2012 R2 for Windows 10 CSVLK into VAMT 3.1 (version 10.0.10240.0), you receive the following error message:
+
+> The specified product key is invalid, or is unsupported by this version of VAMT. An update to support additional products may be available online.
+
+![VAMT error message](./images/vamt-known-issue-message.png)
+
+This issue occurs because VAMT 3.1 does not contain the correct Pkconfig files to recognize this kind of key.
+
+### Workaround
+
+To work around this issue, use one of the following methods.
+
+**Method 1**
+
+Do not add the CSVLK to the VAMT 3.1 tool. Instead, use the **slmgr.vbs /ipk \<*CSVLK*>** command-line tool to install a CSVLK on a KMS host. In this command, \<*CSVLK*> represents the specific key that you want to install. For more information about how to use the Slmgr.vbs tool, see [Slmgr.vbs options for obtaining volume activation information](https://docs.microsoft.com/windows-server/get-started/activation-slmgr-vbs-options).
+
+**Method 2**
+
+On the KMS host computer, follow these steps:
+
+1. Download the hotfix from [July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/3172614/).
+
+1. In Windows Explorer, right-click **485392_intl_x64_zip**, and then extract the hotfix to **C:\KB3058168**.
+
+1. To extract the contents of the update, open a Command Prompt window and run the following command:
+
+   ```cmd
+   expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\
+   ```
+
+1. To extract the contents of Windows8.1-KB3058168-x64.cab, run the following command:
+
+   ```cmd
+   expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168
+   ```
+
+1. In the "C:\KB3058168\x86_microsoft-windows-s..nent-sku-csvlk-pack_31bf3856ad364e35_6.3.9600.17815_none_bd26b4f34d049716\" folder, copy the **pkeyconfig-csvlk.xrm-ms** file. Paste this file to the "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig" folder.
+
+1. Restart VAMT.