Windows OS Hub
  • Windows
    • Windows 11
    • Windows Server 2022
    • Windows 10
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
  • PowerShell
  • Linux
  • Home
  • About

Windows OS Hub

  • Windows
    • Windows 11
    • Windows Server 2022
    • Windows 10
    • Windows Server 2019
    • Windows Server 2016
  • Microsoft
    • Active Directory (AD DS)
    • Group Policies (GPOs)
    • Exchange Server
    • Azure and Microsoft 365
    • Microsoft Office
  • Virtualization
    • VMware
    • Hyper-V
  • PowerShell
  • Linux

 Windows OS Hub / Windows 10 / Windows Cannot Find the Microsoft Software License Terms

April 19, 2023 Hyper-VVMwareWindows 10Windows 11Windows Server 2016Windows Server 2019

Windows Cannot Find the Microsoft Software License Terms

The error “Windows cannot find the Microsoft Software License Terms” may appear when installing the Windows 10/11 or Windows Server 2022/2019/2016 operating system on a bare-metal computer/server or on a Hyper-V/VMware virtual machine. In this case, the installation of Windows from the ISO image is interrupted after selecting the edition of Windows with an error:

Windows Setup
Windows cannot find the Microsoft Software License Terms.  Make sure the installation sources are valid and restart the installation.
The installation was canceled. Any changes made to your computer won't be saved.

Windows setup error - Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation

After clicking OK, the computer is rebooted and Windows installation is restarted. The error “Cannot find License Terms” appeared again and again.

As it turned out, this error can be caused by several completely different reasons. Let’s consider them all separately.

Hyper-V and the “Windows cannot find the Software License Terms”

If you are installing Windows 10/11 or Windows Server 2016/2019 (and older OS versions) in a virtual machine, make sure you have allocated enough RAM to the VM. In my case, only 512 MB of memory was allocated for the VM on the Hyper-V server, and the Enable Dynamic memory option was checked for it with a possible Memory overcommitment situation. Increase the amount of memory allocated to the VM to at least 1024 MB, disable Dynamic Memory, and restart the Windows setup.

Also in the comments, several people wrote that they fixed the problem by reducing the size of the RAM for the VM from 4096 to 2048 GB.

hyper-v vm: increase allocated memory and disable dynamic RAM

Also, try disconnecting your Windows VM from the Hyper-V virtual switch that is allowed to connect to the Internet (through NAT or directly).

Note. You can use the following trick as a workaround. Prior to starting Windows installation, press Shift+F10 and run the command in the command prompt that will create a pagefile: wpeutil createpagefile /path=C:\pf.sys . Then switch to the Windows Setup window and start Windows installation. The installation should continue without any errors, even if not enough memory is allocated to the virtual machine.

Windows clean install canceled on a physical computer

If the error occurs when installing Windows directly on the hardware (on a computer, laptop), and not in a VM, make sure that enough RAM is installed on your device. If there is enough memory, most likely there is a problem with the Windows installation image (distribution) itself. It may be damaged and you should better try using another disk or ISO image.

Also, the product edition in ei.cfg file of your Windows image may not match the product key in the pid.txt file. In this case, you can create a text file on the Windows installation disk (boot ISO image) in the \sources\ directory with the name ei.cfg and the following content:

[Channel]
OEM

windows iso image: ei.cfg file change channel to oem

If there is ei.cfg file in this directory, you need to change the Channel value from Retail to OEM (as it seems that you are trying to install an Enterprise Windows edition from a retail distribution). You can get a list of editions in your Windows ISO image as follows (where E: is the path to the drive where the Windows ISO image or installation USB flash drive is mounted):

DISM /Get-WimInfo /WimFile:"E:\sources\install.esd"

You must manually edit the ISO file of the Windows installation image using any ISO editor (WinISO), add the specified file and overwrite the installation DVD/USB stick.

Or you can specify the Windows installation key as follows:

setup.exe /pkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

“Windows cannot find the Software License Terms” error on VMware VM

When installing Windows as a guest OS on a VMware Workstation/Player/Fusion virtual machine, you may also receive the “License Agreement Could Not Be Found” error. VMware desktop hypervisors add a Virtual Floppy Drive to the VM hardware by default when they are created. Windows Installer may be trying to find a license file on this device.

To get rid of the problem, simply remove the virtual floppy drive from the virtual machine’s hardware or disable the Connect at power on option.

vmware workstation: remove virtula floppy device

Other possible solutions to the problem in VMware Workstation:

  1. When creating a new VM, don’t specify the path to the Windows installation ISO image, but select the option “I will install the operating system later ”;vmware-workstation: new vm wizard - I will install the operating system later
  2. Mount the Windows installation ISO image to a virtual CD/DVD drive after creating VMware VM;
  3. Boot the VM from the installation disk and start installing Windows.

Disconnect your VM from the Internet. To do this, change the network connection mode from NAT to Bridged or Host-Only in the settings of the VM network adapter.

vmware vm: disable nat internet access in network adapter settings

As a result, Windows won’t connect to the network to check the license during installation, (there was such a problem when installing the Evaluation edition of Windows Server).

5 comments
9
Facebook Twitter Google + Pinterest
previous post
How to Install Windows 11 on a VMware Virtual Machine
next post
Mailbox Size and Quotas in Exchange 2019/2016 and Microsoft 365

Related Reading

How to Cancel Windows Update Pending Restart Loop

May 6, 2025

View Windows Update History with PowerShell (CMD)

April 30, 2025

Change BIOS from Legacy to UEFI without Reinstalling...

April 21, 2025

Remove ‘Your License isn’t Genuine’ Banner in MS...

April 21, 2025

Uninstalling Windows Updates via CMD/PowerShell

April 18, 2025

5 comments

Me May 1, 2020 - 2:41 am

Thank you. Issue #1 was mine, only 512MB.

Reply
Widget January 14, 2021 - 6:46 pm

I had it set to 2GB RAM but with the autoscaling RAM starting at 512MB. Turned off the autoscaling RAM and it worked fine. Thanks.

Reply
Cosmic Cowboy February 28, 2023 - 3:31 am

My issue was the floppy drive. As soon as I remove it, it no longer received the error message.

My environment… Windows 10, VMware Workstation 16.2, installing Windows 2022 as a virtual machine.

Thank you!

Reply
Srini March 8, 2023 - 8:58 am

Thanks, it worked after changing the network connection mode from NAT to Bridged or Host-Only in the settings of the VM network adapter.

Reply
Donald March 13, 2025 - 9:21 am

thanks my issue was the floppy disk

Reply

Leave a Comment Cancel Reply

join us telegram channel https://t.me/woshub
Join WindowsHub Telegram channel to get the latest updates!

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMware
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Cannot Install Network Adapter Drivers on Windows Server

    April 29, 2025
  • Change BIOS from Legacy to UEFI without Reinstalling Windows

    April 21, 2025
  • How to Prefer IPv4 over IPv6 in Windows Networks

    April 9, 2025
  • Load Drivers from WinPE or Recovery CMD

    March 26, 2025
  • How to Block Common (Weak) Passwords in Active Directory

    March 25, 2025
  • Fix: The referenced assembly could not be found error (0x80073701) on Windows

    March 17, 2025
  • Exclude a Specific User or Computer from Group Policy

    March 12, 2025
  • AD Domain Join: Computer Account Re-use Blocked

    March 11, 2025
  • How to Write Logs to the Windows Event Viewer from PowerShell/CMD

    March 3, 2025
  • How to Hide (Block) a Specific Windows Update

    February 25, 2025

Follow us

  • Facebook
  • Twitter
  • Telegram
Popular Posts
  • Hyper-V Virtual Machine Stuck in Stopping/Starting State
  • How to Install and Configure Free Hyper-V Server 2019/2016
  • Poor Network Performance on Hyper-V VMs in Windows Server 2019
  • How to Install Windows 11 on a Hyper-V Virtual Machine
  • USB Device Passthrough (Redirect) to Hyper-V Virtual Machine
  • How to Enable and Configure Hyper-V Remote Management
  • Hyper-V: Enabling Routing Between Internal Networks (Subnets)
Footer Logo

@2014 - 2024 - Windows OS Hub. All about operating systems for sysadmins


Back To Top