Windows cannot find Microsoft Software License Terms

Discussions about using Windows guests in VirtualBox.
HealisticEngineer
Posts: 2
Joined: 10. Feb 2018, 11:12

Windows cannot find Microsoft Software License Terms

Post by HealisticEngineer »

Hi all,

I think I'm doing something wrong or if I have a bug, so would like some help.
I've created the following unattended install commands into a batch file, so far the VM is created and boots but once the Windows install starts I get the
Windows cannot find the Microsoft Software License Terms.
I've tried creating it with more RAM and checking the ISO work without the unattended install, but neither helped, so I am thinking perhaps I am missing a needed switch.

Code: Select all

VBoxManage createvm --name "W2K16" --register
VBoxManage modifyvm "W2K16" --memory 4096 --ioapic on --acpi on --boot1 dvd --cpus 2 --vram 128
VBoxManage modifyvm "W2K16" --nic1 natnetwork --nat-network1 LabNetwork
VBoxManage modifyvm "W2K16" --ostype Windows2016_64
VBoxManage createhd --filename D:\VM\W2K16\W2K16.vdi --size 51200 --format VDI
VBoxManage storagectl "W2K16" --add sata --controller IntelAHCI --name "SATA Controller"
VBoxManage storageattach "W2K16" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium D:\VM\W2K16\W2K16.vdi
VBoxManage unattended install "W2K16" --iso=D:\Software\ISO\Windows2016.ISO --user=john --password=johan007 --full-user-name="john edward hall" --country=SK --time-zone=UTC --hostname=W2K16.lab.local
VBoxManage startvm "W2K16"
Thanks in advance.
aaarim
Posts: 6
Joined: 28. Jan 2020, 11:33

Re: Windows cannot find Microsoft Software License Terms

Post by aaarim »

Same thing with Windows 10 Enterprise LTSC 2019 64-bit ISO.Works fine with Winows 7.

There are not problems with normal (manual )installation. Only with unattended installation.

I found something:

https://techcommunity.microsoft.com/t5/ ... m-p/164024

> 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

And I have a standoff...
FoxInTheVbox
Posts: 6
Joined: 31. May 2023, 10:14

Re: Windows cannot find Microsoft Software License Terms

Post by FoxInTheVbox »

Good morning

I am hitting this now too, removing the floppy .img file from the floppy controller didn't fix the issue. Neither did removing the floppy controller.

As per other users, a manual creation (so create the VM while NOT running the 'unattended' line) works fine. I'm having the issue on Windows 2016, and a newly downloaded 2019 .iso file too.

ERROR (pop up dialogue): Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.

Any suggestions are most welcome - thanks
VERSION: Version 7.0.8 r156879 (Qt5.15.2). Windows 11 Home 64bit; 32GB RAM; Processor: 12th Gen Intel(R) Core(TM) i7-1260P (16 CPUs), ~2.1GHz

CODE:

Code: Select all

# Add path to Virtualbox to my Powershell Path
$Env:Path += ";C:\Program Files\Oracle\VirtualBox\"

$VBOX_VMNAME = "SQL-SERVER05_SQL2019_WIN2019_SI"

# Create empty VM:
VBoxManage createvm --name $VBOX_VMNAME --ostype Windows2019_64 --register --groups "/SQL"

# ModifyVM Config
VBoxManage modifyvm $VBOX_VMNAME --cpus 4 --memory 8192 --vram 128 --graphicscontroller vboxsvga --nic1 bridged --bridgeadapter1 "Intel(R) Wi-Fi 6E AX211 160MHz"

# Add disk controllers
VBoxManage storagectl $VBOX_VMNAME --name "SATA" --add sata --controller IntelAHCI --portcount 30 --bootable on

# Attach the OS ISO
$isoFile="C:\VirtualBox_FILES\software\OS\Windows_Server_2019_Datacenter_EVAL_en-us.ISO"
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 0  --device 0 --type dvddrive --medium $isoFile

# Add C drive
# FYI: DELETE A MEDIUM: VBoxManage closemedium $temp_path --delete 
$temp_size_GB=40
$temp_path="C:\VirtualBox_FILES\STORAGE\" + $VBOX_VMNAME + "_C_" + $temp_size_GB +"GB.vdi"
VBoxManage createmedium --filename $temp_path --size ($temp_size_GB*1024) --variant Standard
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 1 --device 0 --type hdd --medium $temp_path

# Add D drive, SQLHOME, for DBA files
$temp_size_GB=5
$temp_path="C:\VirtualBox_FILES\STORAGE\" + $VBOX_VMNAME + "_D_" + $temp_size_GB +"GB.vdi"
VBoxManage createmedium --filename $temp_path --size ($temp_size_GB*1024) --variant Standard
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 2 --device 0 --type hdd --medium $temp_path

# Add E drive, SQL DATA
$temp_size_GB=50
$temp_path="C:\VirtualBox_FILES\STORAGE\" + $VBOX_VMNAME + "_E_" + $temp_size_GB +"GB.vdi"
VBoxManage createmedium --filename $temp_path --size ($temp_size_GB*1024) --variant Standard
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 3 --device 0 --type hdd --medium $temp_path

# Add F drive, SQL LOGS
$temp_size_GB=20
$temp_path="C:\VirtualBox_FILES\STORAGE\" + $VBOX_VMNAME + "_F_" + $temp_size_GB +"GB.vdi"
VBoxManage createmedium --filename $temp_path --size ($temp_size_GB*1024) --variant Standard
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 4 --device 0 --type hdd --medium $temp_path

# Add T drive, SQL TEMPDB
$temp_size_GB=20
$temp_path="C:\VirtualBox_FILES\STORAGE\" + $VBOX_VMNAME + "_T_" + $temp_size_GB +"GB.vdi"
VBoxManage createmedium --filename $temp_path --size ($temp_size_GB*1024) --variant Standard
VBoxManage storageattach $VBOX_VMNAME --storagectl "SATA" --port 5 --device 0 --type hdd --medium $temp_path

# Add shard folder
$sharedFolder = "C:\VirtualBox_FILES"
VBoxManage sharedfolder add $VBOX_VMNAME --name VirtualBox_FILES --hostpath $sharedFolder --automount --auto-mount-point='Z'

# Clipboard sharing on
VBoxManage modifyvm  $VBOX_VMNAME --clipboard-mode bidirectional

# Unattended Install: Config files go to: C:\VirtualBox_FILES\SQL\SQL-SERVER04_SQL2019_WIN2016_SI
$isoFile="C:\VirtualBox_FILES\software\OS\Windows_Server_2019_Datacenter_EVAL_en-us.ISO"
$isoFileAdditions="C:\VirtualBox_FILES\software\Accessories\VBoxGuestAdditions.iso"
$userName="Administrator"
$fullUserName="Administrator"
$password="xxx"

VBoxManage unattended install $VBOX_VMNAME --iso=$isoFile --user=$userName --password=$password --full-user-name=$fullUserName --install-additions --additions-iso=$isoFileAdditions --locale=ll_UK --image-index=4

# Start VM
VBoxManage startvm $VBOX_VMNAME
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows cannot find Microsoft Software License Terms

Post by scottgus1 »

FoxInTheVbox wrote:As per other users, a manual creation (so create the VM while NOT running the 'unattended' line) works fine.
Fox, are you able to do an unattended install via the Virtualbox GUI?

Since 2018/2020, Virtualbox 7.0 came out, with an optional unattended install setting in the Create Virtual Machine wizard. I'd be curious if these same ISO's install correctly using this new GUI feature:

Image

If they do, maybe there's a config file that contains the info you all may be missing in the command line installs.

Additionally, if you can get a GUI-based unattended install to work, I'd appreciate if you could report whether your new VM OS has an administrator-privilege account you can access in it. There have been reports of installs with no admin or sudo-level accounts, only since 7.0 came out, and only one such person reports that they used the GUI unattended install feature. A few more reports may show there could be a bug in the unattended install feature.
FoxInTheVbox
Posts: 6
Joined: 31. May 2023, 10:14

Re: Windows cannot find Microsoft Software License Terms

Post by FoxInTheVbox »

Good morning Scott - thanks for your prompt response, and apologies for my tardy one! I will look into this today.

Kind regards

Fox
FoxInTheVbox
Posts: 6
Joined: 31. May 2023, 10:14

Re: Windows cannot find Microsoft Software License Terms

Post by FoxInTheVbox »

Hi again Scott - I used the functionality, and got the same error - screenshots below.

Again, just for clarity, when I said it worked as per other users, I meant the machine created correctly, and I DID NOT run the unattended creation command, and just booted the machine with the ISO, then manually did the whole laborious click thing :-(

Should I raise this as a bug then do you think?

Ta, Fox
Attachments
install6_ERROR.png
install6_ERROR.png (42.06 KiB) Viewed 16665 times
install5_SUMMARY.png
install5_SUMMARY.png (110.64 KiB) Viewed 16665 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows cannot find Microsoft Software License Terms

Post by scottgus1 »

So, just to make sure I understand, please:
FoxInTheVbox wrote: 5. Jun 2023, 12:55 when I said it worked as per other users, I meant the machine created correctly, and I DID NOT run the unattended creation command, and just booted the machine with the ISO, then manually did the whole laborious click thing
Does this mean a full manual typical old-school sit-at-the-computer install worked correctly and had no license terms errors?

And both command-line and GUI unattended installs had the licensing issue?
FoxInTheVbox
Posts: 6
Joined: 31. May 2023, 10:14

Re: Windows cannot find Microsoft Software License Terms

Post by FoxInTheVbox »

Does this mean a full manual typical old-school sit-at-the-computer install worked correctly and had no license terms errors?
Correct

And both command-line and GUI unattended installs had the licensing issue?
Correct
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows cannot find Microsoft Software License Terms

Post by scottgus1 »

Thanks. Assuming you're using the same ISO for each test, I'd say there's a bug somewhere.

Only thing is that the other posters who have theoretically used unattended install haven't reported issue with licensing fails, so I'm not sure what's different here.

Please post a ticket on the Bugtracker, with a link back here to this topic. Maybe something's missing?
FoxInTheVbox
Posts: 6
Joined: 31. May 2023, 10:14

Re: Windows cannot find Microsoft Software License Terms

Post by FoxInTheVbox »

Created a ticket on BugTracker - I will update further when I have something - thanks again. F
CrazydrveB
Posts: 1
Joined: 12. Oct 2023, 04:30

Re: Windows cannot find Microsoft Software License Terms

Post by CrazydrveB »

I too have the same error, for me it happens when I'm using an evaluation ISO. no ms key or license.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows cannot find Microsoft Software License Terms

Post by scottgus1 »

So far we still don't know what causes this problem.
multiOS
Volunteer
Posts: 800
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: WIN11,10, 7, Linux (various)
Location: United Kingdom

Re: Windows cannot find Microsoft Software License Terms

Post by multiOS »

@CrazydrveB

Evaluation versions of Windows do not require a product activation key. They are time limited versions which 'die' when the permitted evaluation period expires, unless you convert them to a licenced installation by obtaining a valid Product Key and using that to fully activate the installation.
tslaikjer
Posts: 1
Joined: 12. Oct 2023, 19:10

Re: Windows cannot find Microsoft Software License Terms

Post by tslaikjer »

Had the same problem when doing unattended install with server 2022 eval image
The problem is only for unattended installations and lies in the xml file generated when using an evaluation version of Windows.
The generated autounattended.xml file contains an empty <key></key> product key, and that is not a valid value.

A way to get around this, is to edit the source xml win_nt6_unattended.xml in "C:\Program Files\Oracle\VirtualBox\UnattendedTemplates" (default path).
Make a backup of the file first - just in case....
Find the line <Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key> in the file and put it in a comment block (<!-- <Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key> -->
Save the file - you need to be administrator to do so.
Now create a new server with unattended install, it should install without problems.

In the same folder you will find win_postinstall.cmd which is executed to install the additions.
I guess you could play around with that and add more lines if you want to customize the installation further. Again, backup before changing.

You can find the actual xml used in the same folder as the .vbox file

/torben
klaus
Oracle Corporation
Posts: 1110
Joined: 10. May 2007, 14:57

Re: Windows cannot find Microsoft Software License Terms

Post by klaus »

Does anyone have a pointer to Microsoft docs stating that empty <key></key> sequences are invalid? Because it'd be easily doable to skip this tag entirely in the generated file when the key is empty. Not needing the "commenting out" trickery.
Post Reply