Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 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).

4 comments
4
Facebook Twitter Google + Pinterest
previous post
How to Install Windows 11 on a VMware Virtual Machine
next post
Settings App Won’t Open/Crashes on Windows 10/11

Related Reading

Zabbix: How to Get Data from PowerShell Scripts

October 27, 2023

Tracking Printer Usage with Windows Event Viewer Logs

October 19, 2023

Reset Root Password in VMware ESXi

October 12, 2023

How to Use Ansible to Manage Windows Machines

September 25, 2023

Installing Language Pack in Windows 10/11 with PowerShell

September 15, 2023

4 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

Leave a Comment Cancel Reply

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

  • Zabbix: How to Get Data from PowerShell Scripts

    October 27, 2023
  • Tracking Printer Usage with Windows Event Viewer Logs

    October 19, 2023
  • PowerShell: Configure Certificate-Based Authentication for Exchange Online (Azure)

    October 15, 2023
  • Reset Root Password in VMware ESXi

    October 12, 2023
  • How to Query and Change Teams User Presence Status with PowerShell

    October 8, 2023
  • How to Increase Size of Disk Partition in Ubuntu

    October 5, 2023
  • How to Use Ansible to Manage Windows Machines

    September 25, 2023
  • Installing Language Pack in Windows 10/11 with PowerShell

    September 15, 2023
  • Configure Email Forwarding for Mailbox on Exchange Server/Microsoft 365

    September 14, 2023
  • How to View and Change BIOS (UEFI) Settings with PowerShell

    September 13, 2023

Follow us

  • Facebook
  • Twitter
  • Telegram
Popular Posts
  • Hyper-V Virtual Machine Stuck in Stopping/Starting State
  • How to Install Windows 11 on a Hyper-V Virtual Machine
  • How to Install and Configure Free Hyper-V Server 2019/2016
  • Poor Network Performance on Hyper-V VMs in Windows Server 2019
  • USB Device Passthrough (Redirect) to Hyper-V Virtual Machine
  • How to Install VMWare ESXi in a Hyper-V Virtual Machine?
  • Import, Export and Clone Virtual Machines in Hyper-V
Footer Logo

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


Back To Top