What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
In most cases, “Windows cannot find the Microsoft Software License Terms” is a Windows Setup source, installation-media, virtual-machine, or edition-selection problem—not evidence that you need to buy another Windows license. Start by recreating the USB from an official Microsoft download. If you’re installing in a VM, check its memory and ISO attachment; if you’re using custom media, check the image and edition selection.
What the error means—and what it doesn’t
Windows Setup displays this message when it cannot successfully use the licensing or edition information it needs from the installation source. It can appear after you click Install now, after choosing an edition, or later in Setup, whether you’re installing on a physical PC or in a virtual machine.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft Windows 11 PRO (Ingles) FPP 64-BIT ENG INTL USB Flash Drive | $149.99 | Buy on Amazon |
| 3 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | $119.99 | Buy on Amazon |
The message alone does not prove that your product key is invalid, your PC lacks a license, or Microsoft has blocked the installation. Setup and activation are separate: a valid license cannot repair an incomplete ISO, unreadable USB, malformed image, or VM that has too little memory. Nor does seeing—or not seeing—a file named license.rtf settle the diagnosis.
Reported causes vary. Microsoft Q&A discussions associate this error with invalid installation media, VM memory, and custom images or edition selection, but these reports are diagnostic patterns, not a definitive Microsoft error specification. See media-related reports, Hyper-V reports, and a custom-image example.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Start here: recreate clean installation media
This is the safest first step for a physical PC and for most ordinary Windows client installations:
- Download the Windows ISO or Media Creation Tool from Microsoft. Use the Windows 11 download page, the Windows 10 page, or Microsoft’s Windows Server Evaluation Center for evaluation media.
- For a standard Windows client install, let the Media Creation Tool create the USB directly when that option is available. Availability and supported versions can change; check Microsoft’s current page for the release you need.
- Recreate the USB rather than reusing an old boot drive or copying selected files onto it. A USB can boot successfully but still contain a damaged or inaccessible installation image.
- Retry with a different USB drive and a directly connected USB port if the error persists. Avoid mixing files from different releases or adding custom setup files while testing.
- If Microsoft publishes a checksum for that exact ISO, compare it with your download. A hash is useful only when you have an authoritative expected value for the same image.
Microsoft Q&A responders commonly recommend rebuilding installation media, but that does not mean media corruption is the cause in every case. Recreating the drive also helps rule out a bad write or failing USB. For standard client media, use Microsoft’s Windows 11 or Windows 10 ISO download page rather than an unofficial or modified image.
If you’re installing Windows in a virtual machine
First verify that the ISO is mounted as the VM’s virtual CD/DVD drive and that the VM can read it. Then make these low-risk checks:
Recommended Free Tools
- Shut down the VM and assign adequate fixed startup memory. Temporarily disable dynamic memory and retry with a fixed allocation.
- As a baseline, Windows 10 64-bit lists 2 GB of RAM as its minimum, while Windows 11 lists 4 GB. These are OS minimums, not guarantees that every VM setup will work well at that amount. Windows 11 also has other requirements. See Microsoft’s Windows 10 specifications and Windows 11 specifications. For Windows Server, consult the requirements for the specific release and installation mode rather than applying a client Windows minimum.
- Disconnect an unused virtual floppy drive. Some VM configurations expose one unnecessarily; community reports describe removing it as a possible fix, not a universal Setup requirement.
- Confirm that the ISO is attached to the virtual optical drive, not merely present on the host.
- If the VM software offers an automated or “easy install” workflow, create the VM without it for one test. Such a workflow may inject a key or answer file. Attach the ISO manually and retry.
- Reboot the VM after changing virtual hardware. If the error remains, test a newly created VM with an untouched official ISO.
Low VM memory and disabling Hyper-V dynamic memory are reported troubleshooting paths, not guaranteed causes or cures. Microsoft’s Hyper-V requirements provide platform context. A discussion of a particular virtual floppy or device setup is available in this Microsoft Q&A report; treat it as a configuration-specific lead.
If the problem involves a custom ISO or edition choice
The point at which Setup fails is a useful clue. If every edition fails on clean official media, investigate the source, VM, or hardware. If the error occurs only after you manually select one edition, suspect the image index, edition metadata, or a key or configuration file that is forcing a mismatch.
Edition selection can be affected by several things:
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
- A Windows key embedded in the PC’s firmware may cause Setup to select an OEM edition, such as Home, automatically.
- A multiedition ISO may not contain the edition you expect, or a custom WIM may have been captured or exported incorrectly.
- An
ei.cfgfile can influence channel or edition selection. Apid.txtfile can provide a key to Setup and influence which edition it selects. - An automated VM setup or unattended-install answer file may also inject a key or select an edition.
For diagnosis, remove custom ei.cfg, pid.txt, answer files, and modified images, then test an untouched Microsoft image. These files do not create a license or activate Windows. Forcing an edition that conflicts with the image or the device’s embedded key can add confusion. Generic installation keys are not a routine fix: they may select an edition, but they do not activate Windows.
To list the editions and indexes in a custom WIM, run this from Command Prompt, replacing the path with the actual file location:
dism /Get-WimInfo /WimFile:X:sourcesinstall.wimCheck that the expected edition appears. A successful result means DISM can read the WIM structure; it does not prove every Setup file or component is intact. See Microsoft’s DISM image-management options.
If install.wim is larger than 4 GB
FAT32 is commonly used for UEFI-bootable Windows USB media, but a single FAT32 file cannot exceed about 4 GB. If a custom source contains a larger install.wim, the media-creation method may require another approach. NTFS can accommodate the file, but whether an NTFS USB boots depends on the firmware and bootloader method. NTFS by itself is not established as a universal cause of this error.
One supported approach is to split the WIM into smaller files, then use media and a boot method compatible with the target firmware. Run the command from a Windows environment with DISM, changing the source and destination drive letters as needed:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Dism /Split-Image /ImageFile:"X:sourcesinstall.wim" /SWMFile:"Y:sourcesinstall.swm" /FileSize:4000Here, X: is the source containing the WIM, often a mounted ISO, and Y: is the destination USB. DISM can create additional files such as install2.swm; keep the generated sequence together. Follow Microsoft’s WIM split-image instructions. Splitting adds files and complicates manual servicing; NTFS avoids the single-file limit but can require additional firmware or bootloader support.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Check what Setup can actually read
If rebuilding the media and checking the VM or edition do not help, collect evidence before changing firmware settings or buying a key. At the Setup screen, press Shift+F10 to open Command Prompt. Drive letters in Windows PE may differ from their usual Windows letters; identify them with:
diskpart
list volume
exitThen substitute the correct letter for D: and inspect the source:
dir D:sources
dir D:sourceslicense.rtf
dir D:sourcesinstall.wim
dir D:sourcesinstall.esdDo not treat the absence of license.rtf alone as proof of the cause. Setup’s licensing and edition data depend on the source and selected image; a file listing is only one observation.
Setup logs may help identify whether the source or selected image is failing. Common locations in the Setup environment are:
X:WindowsPanthersetupact.log
X:WindowsPanthersetuperr.logAlso try the same media on another PC or VM, or test another known-good ISO on the target. If only one image index fails, focus on that custom image or edition. If known-good media fails across multiple attempts, then investigate hardware and firmware—such as unreliable USB reads, memory, or storage—rather than assuming the license terms are the problem.
What not to change first
- Don’t buy a new Windows license just because of this message. The message is not proof of an activation failure.
- Don’t use a random generic key as a fix. It may change edition selection but will not activate Windows.
- Don’t assume
license.rtfalone explains the failure. Source integrity, image metadata, edition choice, and VM setup can all matter. - Don’t disable Secure Boot or switch to Legacy boot by default. These changes can cause new boot problems and are not the first troubleshooting step for this message.
- Don’t conclude that every NTFS USB is defective. The relevant issue is whether the specific media and boot method work with the target firmware.
If you are installing Windows 11 and have separate setup errors, check its TPM, Secure Boot capability, CPU, RAM, and storage requirements. Those requirements can cause other failures, but do not by themselves establish the cause of this license-terms message.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
