0x80240029 and 0xC004F034: an unlicensed product stops the update search

Fix it now

Microsoft publishes 0x80240029 as WU_E_INVALID_PRODUCT_LICENSE: the search may have missed updates because there is an unlicensed application on the system. That is not the same statement as “Windows is unlicensed”. Establish which of the two you have before you touch a product key.

slmgr /dlv
dism /online /get-currentedition
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

1. Read the Licence Status line in the slmgr /dlv output first. Licensed means Windows itself is entitled and the unlicensed thing is something else on the machine.
2. If Windows is not licensed, compare the key you hold against the edition dism /online /get-currentedition reports. A key activates only the edition it was issued for, and forcing the wrong one wastes it.
3. Install the matching key with slmgr /ipk <key>, activate with slmgr /ato, then confirm in Settings, System, Activation before rescanning.
4. If Windows already reads Licensed, let the DISM and sfc pass above finish, reboot, and scan again from Settings, Windows Update.
5. If the failure names an application package, remove and reinstall that application rather than changing anything about Windows activation.

Do not lead with a new product key. Microsoft’s own wording for this code is about an unlicensed application, and a Windows licence cannot resolve a package’s licence.

If the scan now completes you are done. The rest of this page explains what the update client is checking, and why two of the three codes here have no published meaning at all.

Why it happens

Windows Update does not simply download whatever it is offered. Before the search completes, the client checks that what it is looking at is licensed, and it asks the software protection platform for that answer. When the answer comes back wrong, the search is abandoned rather than partially completed, which is why you get a code instead of a shorter list of updates.

Microsoft’s published text for 0x80240029 is precise and worth reading slowly: the symbolic name is WU_E_INVALID_PRODUCT_LICENSE and the description is that the search may have missed some updates because there is an unlicensed application on the system. Two things follow from that. The code is about an application, not necessarily about Windows. And it describes an incomplete search, not a blocked install.

The other two codes on this page need stating carefully. 0xC004F034 and 0xC004F080 sit in the range the software protection platform uses for its own results, the same range as the documented activation errors that all begin “The Software Protection Service reported that”. Neither appears in either of Microsoft’s activation error code lists. 0xC004F034 does turn up on Microsoft Learn in one narrower place: the Windows Enterprise subscription activation guidance, where it is the code behind “We can’t activate Windows on this device right now”, shown when the device has no firmware-embedded activation key or when the starting edition was not Windows Pro, and where the stated remedy is to enter a Pro key by hand. 0xC004F080 returns nothing on Learn at all. Treat both as a signal that the licensing store is where to look, and diagnose with slmgr rather than with the code.

Full reference

Reading the licensing state without guessing

The single most useful line is Licence Status. If it reads Licensed, the operating system is entitled and no key you buy will change the update behaviour. If it reads Notification, the reason code printed beside it is the thing to work on, and that is where 0xC004F034 tends to appear on machines whose activation was broken by a hardware change or a reinstall.

What the codes are and are not

It is worth being explicit about the limits of what is published, because this article family is full of confident claims that no vendor page supports. Microsoft documents 0x80240029 in its Windows Update error reference. Neither 0xC004F034 nor 0xC004F080 appears in the two activation error code lists it maintains. 0xC004F034 is documented in one place, the Windows Enterprise subscription activation guidance, which shows it behind the message that Windows cannot be activated on this device right now and gives two examples: no firmware-embedded activation key, and a starting edition that was not Windows Pro. In both of those a Pro key has to be entered manually. 0xC004F080 returns no documentation hit at all. The correct conclusion is not that it means nothing; it is that the only reliable way to find out what the licensing service is unhappy about is to ask it directly with slmgr, and to look at the Application log.

Hardware changes and digital licences

A digital licence is bound to the hardware and, where the user signed in, to a Microsoft account. Replace a motherboard and the binding breaks. The supported route back is the activation troubleshooter in Settings, System, Activation, choosing the option that says the hardware changed recently, signing in with the account the licence is linked to, and selecting the device from the list. That costs nothing when the licence is transferable, and Microsoft’s instructions add one condition worth knowing in advance: the edition has to be the same before and after the hardware change, or neither the digital licence nor the product key will reactivate. Whether a licence that came preinstalled on the machine can move to different hardware at all is decided by the terms it was sold under rather than by anything you can change on the device.

When activation is healthy and the code persists

• Run Get-WindowsUpdateLog and read the newest scan. The line that fails usually names the package the client objected to.
• Check the Application log for software protection platform events around the same timestamp.
• Rebuild the update data store: stop wuauserv and bits, rename C:\Windows\SoftwareDistribution, start both services and rescan.
• On a managed device, confirm the scan is going where you think. A client pointed at a decommissioned update server produces its own family of errors and this is not one of them.
• If several unrelated machines started failing on the same day, look at what changed centrally rather than at the machines.

Servicing on an unlicensed device

Microsoft’s own position is that Windows will always be able to get critical security updates even when the copy is not genuine, while other updates and benefits are reserved for genuine Windows. An activation watermark on its own therefore does not mean patching has stopped. What these codes describe is a stronger condition than “not activated”: the client asked a licensing question and got an answer it could not work with. That is why the fix is to make the licensing answer correct rather than to work around the update client.

Every code this article covers

Confirm the fix worked

1. slmgr /dlv reports Licence Status: Licensed for the edition dism /online /get-currentedition names.
2. Settings, System, Activation states that Windows is activated.
3. A fresh scan in Settings, Windows Update completes and either offers updates or reports the device is up to date.
4. One update installs end to end and appears in the update history.

Questions people ask about this