Everything, Everything

2024: January February March April
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Windows Cannot Find The Microsoft Software License Terms
Thursday 17th August, 2017 22:28 Comments: 0
I tried to install Server 2016 on my Hyper-V server and I got the error message "Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation". I should have checked the hash of the ISO I'd downloaded from Microsoft (using my MSDN subscription), but I decided it wouldn't take long to grab the ISO again so I kicked off the download. I go to try it again with the new ISO and I get the same error message. Coincidentally, I had some issues getting it to accept the product key too at one point. I did some searching and saw a suggestion of using 2GB of RAM, as I'd only configured 512MB at this point as it's for setting up a very basic domain controller. I increased the VM to 2GB and skipped the product key and I then got the license terms. It's now happily installing. Presumably it's my fault for not giving it enough RAM to begin with (the documentation does say that the Desktop Experience, which I went for, does require 2GB), but I would have expected a better error message than that. Maybe some kind of warning about the amount of RAM before I got that far?
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3