See Key (microsoft-windows-setup-userdata-productkey-key), section "Values".
Windows cannot find Microsoft Software License Terms
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows cannot find Microsoft Software License Terms
Re: Windows cannot find Microsoft Software License Terms
Then this is a genuine bug in VirtualBox. Easily fixable without needing to touch code... if you need an instant solution you can edit win_nt6_unattended.xml - search for <Key> and insert a line before which contains
and a line after which contains
That should do the trick of leaving out the tag when there is no key.
Code: Select all
@@VBOX_COND_HAS_PRODUCT_KEY@@
Code: Select all
@@VBOX_COND_END@@
-
- Posts: 1
- Joined: 27. Oct 2023, 00:29
Re: Windows cannot find Microsoft Software License Terms
hello, i was having this problem but i found something that works. just make a new vm. don't put the iso. once you create it, right click, settings, then go to storage, click on the optical drive and add your iso. start it up and it should work. it worked for me, but your millage may vary
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows cannot find Microsoft Software License Terms
Hmm. That sounds a great deal like "my solution to the unattended installation problem is to revert to attended installation".
Yes, that always works, but unattended installations are popular for some reason.
Yes, that always works, but unattended installations are popular for some reason.
Re: Windows cannot find Microsoft Software License Terms
If you don't want unattended install then you can still point to the ISO but tick "Skip Unattended Installation". Saves quite a few mouse clicks and achieves the same result.
Anyway, the current VirtualBox 7.0 test builds should have the fix mentioned above already integrated. Would be great if someone could confirm.
Anyway, the current VirtualBox 7.0 test builds should have the fix mentioned above already integrated. Would be great if someone could confirm.