How to Fix Windows Cannot Read the ProductKey Error in VirtualBox

You click OK on the VirtualBox product key error. The VM restarts, and the same message is back. Again and again. The VirtualBox product key error has nothing to do with your ISO or your license. No reinstall of VirtualBox needed.

• Delete the generated “Unattended” files and uncheck Floppy.
• Patch the win_nt6_unattended.xml template.
• Skip unattended installation.

“Windows cannot read the <ProductKey> setting from the unattend answer file. Clicking OK reboots the machine.”

VirtualBox wrote an answer file for an unattended install, and the key block inside it is empty. Windows Setup can’t read that. Below are the three ways we fix it: delete the generated files, patch the template, or skip unattended mode.

Which of the three fixes to pick

The message shows up before anything is installed. So nothing inside the VM is at risk yet.

Where the VirtualBox product key error comes from

A malformed answer file. Unattended installation is on. The product key field is empty. VirtualBox then generates an XML file whose ProductKey section has no Key element.

Windows Setup can’t parse that section. It shows the error and reboots, and the loop repeats on every boot.

VirtualBox 7.0 moved unattended installation into the New Virtual Machine wizard. The step is switched on whenever you pick a Windows ISO.

Older 6.x builds offered the same feature through a command:

VBoxManage unattended install

The idea is nice: VirtualBox answers the setup screens for you. Leave the key box blank, though, and the generated file comes out broken. It looks something like this:

<UserData>
    <ProductKey>
        <WillShowUI>OnError</WillShowUI>
    </ProductKey>
    <AcceptEula>true</AcceptEula>
</UserData>

See the missing Key tag? Windows reads that, gets confused and throws the error. Reboot. Same thing again.

VirtualBox feeds the file to Setup through a virtual floppy drive. That’s why removing the floppy from the boot order is part of the fix.

How to fix the VirtualBox product key error quickly

Most people are done in about three minutes. No need to reinstall VirtualBox or recreate the VM.

1. Shut the VM down completely. Right-click it in VirtualBox Manager and choose Stop, then Power Off. The state must read Powered Off, not Saved.
2. Open Settings, or press Ctrl + S with the VM selected. Go to System, Motherboard and uncheck Floppy in Boot Order. That floppy is where the broken answer file lives.
3. Open the VM folder on disk. The paths are in the table below.
4. Delete every file that starts with “Unattended”. Usually there are one to three of them, with timestamps in their names, plus an aux image.
5. Start the VM. If a warning about a missing medium pops up, click OK. When “Press any key to boot from CD or DVD” appears, press a key quickly.
6. On the product key screen, click the small link “I don’t have a product key” and finish setup. Add your key later in Settings.

“Press any key” flashes past, and the VM drops into the EFI shell? Use Machine, Reset and keep tapping a key as the VM starts. On EFI VMs the prompt lasts only a few seconds.

Stopping the VirtualBox product key error for every new VM

Creating VMs often? Repeating the quick fix gets old fast. The lasting fix is in the template VirtualBox uses to build answer files.

The file is win_nt6_unattended.xml, in the UnattendedTemplates folder. It sits in a different place on each host.

1. Copy the file somewhere safe before touching it.
2. Open it with admin or root rights. On Windows, run Notepad as administrator first, then open the file from inside Notepad.
3. Find the line that inserts the Key element. It’s the first line in the listing below.
4. Comment it out, as in the second line.
5. Save and close.

<Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key>
<!-- <Key>@@VBOX_INSERT_PRODUCT_KEY_ELEMENT@@</Key> -->

New Windows VMs created without a key then boot to the normal product key screen. No loop.

VirtualBox updates often overwrite the template folder. After upgrading to a new 7.x release, we’d check the line again or copy the edited file back in.

Skipping unattended installation in the New VM wizard

You can. In the New Virtual Machine wizard, choose the Windows ISO and tick “Skip Unattended Installation”.

VirtualBox then writes no answer file and attaches no floppy image. Windows Setup runs exactly as on a physical PC, product key screen included. It costs a few extra clicks and nothing else.

For one VM with no need for automation, we’d call this the cleanest route. Setup asks for language, edition and disk. You click “I don’t have a product key” or type yours.

Settings for a Windows 11 guest

• EFI.
• Secure Boot.
• The virtual TPM 2.0 that VirtualBox 7.x offers.

Windows 11 checks for all three. Our Windows 11 hardware requirements guide lists the full set.

Generic keys for test VMs

Microsoft publishes Generic Volume License Keys, GVLKs for short. They let Windows Setup continue without stopping for a key.

Type one in the VirtualBox wizard, and the answer file gets a valid Key element. The error never appears.

A GVLK installs the edition. It activates only against a KMS host on your network, never as a retail license.

These come from Microsoft’s own KMS client activation keys list, not from a keygen. Without a KMS server, though, the VM stays unactivated.

For a VM you plan to keep and use daily, a retail key is the practical answer. You can switch later in Settings, or from the command line.

Need a key? Our Windows 11 Pro key comes as a genuine license. We email it instantly after payment.

Other errors from the same answer file

Several setup errors share this root cause: a broken or unexpected answer file.

For activation codes such as 0xC004F074 or 0xC004C008, see our guide to fixing Windows 11 activation errors.

About that last row. Driver discs and modified ISOs sometimes carry their own autounattend.xml. Setup reads it first.

Windows cannot read the product key outside VirtualBox

Same message, no VM at all. It happens on real PCs too, and the trigger is still an answer file. Just not one VirtualBox wrote.

Setup hunts for Autounattend.xml on its own. Before the first screen, even. Nobody points it there. Full search order? On the Windows Setup automation page on Microsoft Learn, and the part that matters here is short:

• USB sticks and other writable removable drives. Checked first, root folder only, in drive letter order.
• Read-only media. A DVD or a mounted ISO, root folder again.
• The Sources folder of the install media. Custom ISOs love to hide one here.
• The drive setup.exe runs from. Last stop.

So a stick left over from some old automated install can hijack a perfectly clean Windows USB. Plug both in, boot, and Setup reads the wrong file.

Why an empty Key element breaks Setup

UserData, then ProductKey, then Key. That’s where it lives. The reference page is blunt about blanks: “This string type does not support empty elements.” Empty tag, or no tag at all? Setup stops with the ProductKey message. Physical PC, same restart loop. Feels very familiar.

A valid entry is one 25-character key, five groups of five. Something like this, with your own key in place of the zeros:

<ProductKey>
  <Key>00000-00000-00000-00000-00000</Key>
  <WillShowUI>OnError</WillShowUI>
</ProductKey>

That value only picks the edition. Activation comes later. A generic key from the table above installs Windows and leaves it unactivated.

Clearing it on a USB install

1. Unplug every USB drive except the Windows one. Spare sticks first.
2. On another PC, open the Windows stick. Root folder.
3. Autounattend.xml there? Rename it, or move it off the stick.
4. Check the Sources folder too. Same file name, same treatment.
5. Boot again. Setup should now stop at the normal product key screen.

Want a stick with nothing extra on it? We’d rebuild it with the Windows 11 Media Creation Tool instead of fixing a downloaded image by hand. Our bootable USB guide walks through it.

Which VirtualBox versions get the product key error

Every version that offers unattended installation of Windows can produce the error when the key field is left empty.

Users have reported the problem on the VirtualBox forums and on Microsoft Q&A for years. The workarounds have stayed the same across releases.

Rarely does an update change the template behaviour. So assume the bug is still there until you’ve tested your own build.

We’d not stay on an old release just to dodge it. Newer versions bring the TPM 2.0 and Secure Boot support that Windows 11 guests need.

Avoiding the VirtualBox product key error next time

Give the wizard what it expects.

• Have a key ready. With a key in the wizard, VirtualBox writes a valid Key element. The install runs hands-free.
• No key? Skip unattended. It takes maybe five extra minutes and works every time.
• Get the ISO from Microsoft. We use the Windows 11 Media Creation Tool as the clean source. Modified ISOs from random sites often have answer files baked in.
• Turn on EFI for Windows 11. In the VM settings, enable EFI, then Secure Boot and TPM 2.0, before the first boot.
• Attach no other discs. One ISO, nothing else.

Is the fix safe

It is, for the VM and for the host. The files you delete are temporary answer files and an aux image. They hold no disk data.

VirtualBox regenerates them only when you run another unattended install.

Editing the template affects new VMs only. Your backup copy restores the original in seconds if anything looks wrong.

This error looks scary. It’s just VirtualBox writing a bad config file. Once you know what’s wrong, the whole thing takes about five minutes.

Typical cases of the setup loop

The loop on a fresh Windows 11 VM

A new VM and a Windows 11 ISO. The wizard stays on its defaults. The first boot ends in the ProductKey message, and so does every boot after it. Three files deleted, floppy unchecked, and Setup starts normally.

The evaluation ISO

A Windows Server evaluation ISO needs no key. The wizard still writes the broken block. Skipping unattended mode gets the server installed.

The second disc

The unattended files are gone, and the error is still there. A driver disc is attached next to the Windows ISO. It carries its own answer file. With the disc removed, Setup behaves.

The template that came back

The template was patched months ago. After a VirtualBox upgrade the loop returns on a new VM. The update had replaced the file, and the backup copy fixes it again.

VirtualBox versions and guests this guide covers