Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0x803F81F5

0x803F81F5 to 0x803F81F9: Device Limit Reached on Your Account

11 min read Updated October 5, 2026 Windows Activation & Licensing

Fix it now

All five codes carry one published message: you have reached the maximum number of devices that can be used with games and apps from the Store, and you should remove another device from the account first. Microsoft publishes the cap as ten devices attached to a Microsoft account.

  1. Sign in at account.microsoft.com and open the Devices page. That is where the registrations live and where the count is visible.
  2. Remove PCs you no longer own: select the device, then Remove device. A machine that was sold, scrapped or reimaged is still occupying a slot until somebody deletes it.
  3. Unlink Store content separately at account.microsoft.com/devices/content. Removing a PC from the device list and unlinking it from Store content are two different actions in two different places.
  4. For phones and tablets, use account.microsoft.com/devices/android-ios and choose Unlink.
  5. Wait a few minutes for the change to register, then retry the download or the sign-in that failed.

Unlinking a device does not deactivate Windows on it, delete anything, or stop it working. It withdraws the account registration and frees a slot. If you later download an app on that device it counts again.

If that fixed it you can stop here. If not, the next section explains which cap you have actually hit, because there are two and they are commonly confused.

Why it happens

This is not a fault. It is a limit being enforced, and the five codes are one message reported at five points in the same flow. Microsoft publishes identical text for 0x803F81F5, 0x803F81F6, 0x803F81F7, 0x803F81F8 and 0x803F81F9: you have reached the maximum number of devices that can be used with games and apps from the Store, and to use this game or app on the current device you should first remove another device from your account. The v1 version of this article gave each of the five a different meaning. None of those distinctions exist.

The number behind it is published too, and it is worth knowing rather than guessing: Store apps and content can be downloaded to ten devices attached to a Microsoft account. Once you are at ten, new downloads stop until something is unlinked. There is no setting that raises it and no support call that lifts it.

The reason this catches people who own three computers is that removing a machine from your desk does not remove it from the list. A laptop that was sold, wiped, replaced under warranty or simply reimaged is still a registration. On a device that gets rebuilt regularly the same physical machine can occupy several slots at once, which is how a household with four PCs arrives at a cap designed for ten.

There is a second, entirely separate cap that produces a similar-sounding complaint and has nothing to do with these codes. Windows subscription activation covers up to five devices for each user licence, and if the licence is used on a sixth, the computer where that user has not signed in for the longest reverts to Windows Pro or Pro Education. That one produces a quiet loss of Enterprise on a machine nobody was watching, not a Store error. Clearing the Store device list does nothing for it, and vice versa.

The list is full of devices that no longer exist

You have this one if You have far fewer machines than the list shows, and several entries carry names you recognise from earlier builds of the same computer.

  1. Open account.microsoft.com and go to Devices. Remove every PC you cannot account for physically.
  2. Remove entries for machines that were reimaged. The rebuilt device registers itself again when it needs to.
  3. Separately, unlink stale entries at account.microsoft.com/devices/content, because Store content is tracked in its own list.
  4. Allow a few minutes, then retry the download that failed.

Removing a device does not deactivate it or delete anything on it. Store apps licensed to that account stop being licensed there, which is exactly what you want for a machine you no longer own.

You cleared the device list and the content list is still full

You have this one if The Devices page looks tidy, the count still reads as maxed out, and the same code comes back.

  1. Go to account.microsoft.com/devices/content and unlink there. This is a separate list from the device list.
  2. Unlink everything you do not currently use for Store content.
  3. Give it a few minutes, then try the download again.

One account is being used by several people

You have this one if A single account is signed in on machines belonging to different people, and the cap comes back however often you clear it.

  1. Stop sharing the account. Consumer entitlements are attached to one person and a shared account keeps hitting the same wall.
  2. Give each person their own account, with their own entitlements.
  3. In a business, move to per-user subscriptions in a tenant so assignment and device use are managed centrally.
  4. Unlink the registrations the shared account left behind once everyone has moved.

You have hit the subscription activation cap, not the Store cap

You have this one if No Store error at all. A device that was Enterprise quietly reverted to Pro after the same user signed in somewhere new.

  1. Count how many devices that user actually signs into, including virtual desktops and test builds.
  2. The subscription cap is five devices per user licence. On a sixth, the least recently used one reverts.
  3. Retire a device from the rotation, or assign a licence to the identity that is really using the machine.

Unlinking devices from account.microsoft.com has no effect on this cap. They are different mechanisms with different limits.

Every device on the list is genuinely in use

You have this one if Ten real machines, all in daily use, nothing legitimate left to unlink.

  1. Accept that ten is the published cap for Store apps and content on a Microsoft account and that no purchase raises it.
  2. Decide which devices actually need Store content from this account and unlink the rest.
  3. For an organisation, look at whether per-user seats in a tenant fit how people really work better than one consumer account spread across machines.

Full reference

The five codes, side by side

Code Published text
0x803F81F5 You have reached the maximum number of devices that can be used with games and apps from the Store
0x803F81F6 Identical published text
0x803F81F7 Identical published text
0x803F81F8 Identical published text
0x803F81F9 Identical published text

There is nothing to decode. If you have any of the five, the diagnosis is the same and so is the remedy. Where an article tells you that one of them means registration failed and another means licence issuance failed, it is inventing a distinction to fill a table.

The two caps, and which one you have

Microsoft account Store cap Subscription activation cap
Limit Ten devices attached to the account Five devices per user licence
What you see A 0x803F81F5 to 0x803F81F9 code, and downloads stop No error. The device quietly reverts to Pro or Pro Education
Which device is affected The one you are trying to use now The one that user has signed into least recently
Where you fix it account.microsoft.com, Devices and Devices then content The tenant, or by using fewer devices per user
Does buying help No. The cap is not raised by a purchase Yes, if the extra devices belong to a second person who needs their own seat

Where each list lives

  • account.microsoft.com/devices – the PCs attached to the account. Select a device and choose Remove device.
  • account.microsoft.com/devices/content – the devices linked for Microsoft Store content. Choose Unlink.
  • account.microsoft.com/devices/android-ios – phones and tablets. Choose Unlink.
  • For a work account, licence assignment lives in the Microsoft 365 admin centre under Users then Active users then Licenses and Apps.

Unlinking is reversible in the sense that matters: if you later download an app on a device you unlinked, it counts towards the limit again. You are managing a list, not burning an entitlement.

Why a reimaged PC is the usual culprit

Each rebuild presents as a new device. A test machine that gets flattened monthly can occupy several of your ten slots on its own, and none of those entries names itself helpfully. The practical habit is to unlink a machine before you wipe it, the same way you would deauthorise it from any other content service. Where that has not happened, work through the list and remove anything you cannot point at in the room.

What this is not

  • It is not a corrupted licence. Nothing needs repairing on the machine.
  • It is not Windows activation. Removing a device from the account does not affect whether Windows is activated on it.
  • It is not raised by contacting support, changing a setting, or buying an additional consumer plan.
  • It is not the same as the five-device subscription activation limit, even though people describe both as ‘too many devices’.

When a licence is the actual fix

Freeing a slot costs nothing and should always come first: if half the list is machines you no longer own, that is the entire fix. Be clear about what a purchase does and does not do here. Nothing you can buy raises the ten-device Microsoft account cap for Store apps and content. What a purchase does solve is the other case – several people sharing one account and one entitlement, where each of them should hold their own. We supply additional Microsoft 365 licences and can work out whether per-user seats or a device-based subscription fits your situation, which matters most where shared and hot-desk machines are involved.

Every code this article covers

Code What it points at Source
0x803F81F5 You have reached the maximum number of devices that can be used with games and apps from the Store. Remove another device from your account first Microsoft Learn
0x803F81F6 Microsoft publishes the same text as for 0x803F81F5 Microsoft Learn
0x803F81F7 Microsoft publishes the same text as for 0x803F81F5 Microsoft Learn
0x803F81F8 Microsoft publishes the same text as for 0x803F81F5 Microsoft Learn
0x803F81F9 Microsoft publishes the same text as for 0x803F81F5 Microsoft Learn

Confirm the fix worked

  1. Reload the Devices page and confirm only machines you can account for remain.
  2. Check account.microsoft.com/devices/content separately and confirm the content list is also clear of machines you no longer use.
  3. Retry the download or sign-in that failed and confirm it now completes.
  4. Open the app on the new device and confirm it runs licensed rather than in a reduced state.
  5. If you were chasing a reverted Windows edition rather than a Store error, check slmgr /dlv instead – that is the other cap and a different fix.

Questions people ask about this

Does removing a device deactivate it?

No. It withdraws the account registration and frees a slot. Windows activation on that machine is a separate thing and is unaffected. Store apps licensed to that account stop being licensed there, which is the point when the machine is one you no longer own.

Can I raise the limit?

No. Microsoft publishes the figure as ten devices attached to the account for Store apps and content. There is no setting, no support route and no purchase that changes it. You manage the list instead.

Why does my one laptop appear three times?

Because it has been reimaged or reset. Each rebuild registers as a new device. Remove the old entries; the current build keeps working and re-registers itself if it needs to.

I cleared the device list and it still says I am at the limit. Why?

Because Store content is tracked in a separate list. Go to account.microsoft.com/devices/content and unlink there as well. Clearing one list does not clear the other.

Is this the same as the five-device limit I read about for Windows Enterprise?

No. That is subscription activation, which covers up to five devices per user licence and quietly reverts the least recently used device to Pro when a sixth is added. It produces no Store error and is fixed in the tenant, not in your Microsoft account.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x803FABB8 and 0x803FABBA: Digital Licence Transfer Refused After Rebuild Free Fix 0xC004F301 and Event ID 12321: Token-Based Activation Will Not Complete Free Fix 0x80070422 and 0x80070426: The Software Protection Service Will Not Start Free Fix 0xC004F074 and 0x8007232B: No KMS Host Could Be Found on Your Network
โ† Back to Knowledge Base