question

Hi,

Sorry for the inconvenience brought to you. Please provide me with more details to narrow down the issue

While running the proxy VAMT 2.0 for Windows 10 LTSC 1809

It seems that you are using a proxy installed with VAMT 2.0 to activate Windows 10 LTSC 1809. Please correct me if there are any misunderstanding.

• Does the proxy satisfy system requirements for VAMT 2.0?

  Supported Operating System
  Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista, Windows XP Service Pack 3

• Is the proxy able to activate other versions of Windows?
  

• I’m not familiar with VAMT but

  <LastUpdateTime>0001-01-01T00:00:00</LastUpdateTime>

doesn't make sense. Is the time correct on the proxy?

I have submitted IID files that have worked before and get the same error.

Every time a new activation request is submitted, a new IID will be generated. So I think this is normal.

Before we resolve this issue, you can try to troubleshoot 500 Internal Server Error. Or you can use phone activation to activate Windows 10 LTSC 1809:

• On Windows 10 LTSC 1809, run slui.exe 4
  

• Follow the steps to activate your Windows

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hi AliceYang-MSFT, thanks for the response. VAMT is Volume Activation Management Tool that we use to activate Windows on Lab Laptops that are not connected to the internet. We have used this process for at least 5 years. By using Microsoft's suggested process including scripts, we use a 3 part activation process, run a script on the Lab Laptops to generate an IID file, run a script on a computer connected to the internet to submit the IID file and retrieve the CID file from Microsoft, then run the third script on the Lab Laptop to finally finish the activation process. We have used this on Windows 7 and Windows 10. I understand that Windows 10 is not shown in the supported platforms, but it has worked on Windows 10 for a few years and since VAMT 3 requires a database, we decided to stay with VAMT 2.0.
The Last Update time was an interesting flag. It seemed to support the fact that the returned time from the Microsoft Server was in fact an error on the Microsoft side.
A saved IID file from a successful activation was re-ran using the second script. This was a proven IID file that should have returned a CID file for activation. But instead, it created the same server error. We have installed the VAMT 2.0 on another computer and we get the same server error on that computer as well.
We have successfully activated via the phone method. But we need this process to work as it is used for testing and activation on other computers in other areas.
Is there anyone at Microsoft that can assure us that the servers are functioning that validate Windows activation using this method?
Thank you