Forum Discussion
David Molnar
Feb 24, 2018Copper Contributor
Windows Cannot find Microsoft software license terms - During Server 2016 install
I am getting the following error when trying to install Server 2016 Standard. Any idea of the fix?
It's possible the media is corrupt in which case I'd try downloading from another location to avoid the same copy ISP has cached on their systems. I've also seen this with HP intelligent provisioning in which case I'd ask HP about a newer version of tool compatible with server 2016. Also some hypervisors such as VMWare add an additional floppy drive that causes install media to look for licensing on floppy, in this case remove the virtual floppy from guest and try again. Also try;
Bypassing Easy Install
- First start VMware Workstation
- Create A New Virtual Machine
- Select the option “I will install the operating system later”
- Then your new virtual machine will be added to your virtual library.
- Double click on your new Virtual Machine to start it.
- Then it will prompt that an OS is not installed and provide an option to insert the OS installation media.
- Simply click on Change CD/DVD Settings to select your ISO media then Restart VM.
- WELLBOREISCopper ContributorI had the same issue installing a Windows 10 VM on HyperV. Changed to static memory and that took care of it.
- 3495333Copper Contributorok
- Kamleshk1Copper Contributor
The easiest solution is press OK after this error, it will take you to windows\system32
change directory to the boot file directory , it could be c , d or e depending on which type of boot being used.
run setup.exe
follow the process thereafter..
- Guillermo_PinedaCopper Contributor
Go to settings and uncheck the floppy driver that VMWare loads by default, it works for me.
- Matei_MacoveiCopper Contributor
If it helps anyone, I had this problem while installing win 10 on a WM. Apparently, the DVD drive is set by default as the highest boot order. On HyperV, while in windowed mode, go to File, Settings, Firmware, and set the storage unit as the first one to boot.
- jafar1050Copper Contributor
None of the above worked for me. After removing floppy it showed me other errors.
Finally, I chose custom setup in VMware (create new virtual machine wizard) and chose BIOS instead of UEFI. It worked for me.
- gnimmCopper Contributor
The install looks at the floppy drive for some reason.
In the upper right corner of the VM there is a floppy drive icon...
right click on the floppy drive icon and select "disconnect". Windows installer will now find the licensing file.
- Carsten ZimmermannCopper Contributor
I have the same issue on HPE DL360 Gen10 (Server 2016 Standard Eval german).
32 GB RAM, no VMware.
Any ideas?
Best regards,Carsten
Carsten Zimmermann wrote:
I have the same issue on HPE DL360 Gen10 (Server 2016 Standard Eval german).
32 GB RAM, no VMware.
Any ideas?Please start a new question.
- Nigel GoodchildBrass Contributor
Had this same error installing W2K16 eval under VMWare workstation 15.
For me the solution was to remove the virtual floppy drive VMW adds by default
- SaidMuhammedCopper Contributor
Removing the floppy drive cleared this up for me too. Thanks Nigel!!
For Others my setup is:
Server 2022
Installing on VMWare Workstation 17 (Personal use license).
On an LG Gram running Windows 11.
Cheers. thanks again Nigel!
- Phil_RamelCopper ContributorI experienced this issue in VirtualBox 7.0.12r159484. Indeed removing the floppy disk resolved the problem, allowing me to install Windows Server 2022 without any further issues
- TikaMasalaCopper Contributorremoving floppy drive helped me as well. thank you !
Glad to hear, please vote it!
- Jiří DuchoňBrass Contributor
Hello,
this can happen if you use dynamic memory and you have, for example, 512mb ram as start up memory.
VM with Windows Server is sometimes needed at least 700 mb as a start up memory, try to increase to at least 700 MB this should help.
- MartinMistikCopper Contributor
Jiří Duchoň it's true bráška
- metablasterCopper Contributor
This worked also for Hyper-V
I've increased dynamic memory from 512mb to min. 4096mb and max to 8128 and fixed the problem - KevRHCopper ContributorWorked for me, thanks