0x80004005 office shared computer activation with Windows Virtual Desktop

Reading Time: 2 minutes

I was recently involved in troubleshooting shared computer activation with Office on a WVD hostpool image using the latest 20h2-evd-o365pp-g2 image sku and Microsoft 365 Business Premium for Office.

To start with the Troubleshooting this was the only error that occurred for end user trying to activate.

account issue
error code 0x80004005

The Image was using “20h2-evd-o365pp-g2″ from the Azure gallery image. So all the settings should be correct regarding Shared activation. And I could confirm this by looking into the Registry was applied with the correct settings:

SharedComputerLicensing was set to 1.

The Host pools Virtual Machines was also also behind strict firewall rule set, so I also verified that it could talk to the Microsoft Activation URL activation.sls.microsoft.com on 443.

My last assumption was check the licenses. I was informed that the users were assigned correct license with Microsoft 365 Business Premium that should support Multi-session WVD office version and Office Shared Computer Activation.

However, I was just curious to check what features were enabled on the license SKU. And without a doubt the most obvious was not checked. The Microsoft 365 Business Premium feature to enabled “Office Shared Computer Activation” was set to off / disabled.

Changing the License to “on” / “enabled” in the Group based license Enabled Services, solved the issue immediately!

The last step was to verify that the Licenses was “activated” in the user profile Appdata folder in the following location:



  1. Lee September 15, 2021 at 6:18 pm

    These are great tips and ones that people should look for. I, unfortunately, have one user that is unable to activate their Office 365 on a WVD. Every other user is fine. Accounts are all the same. License gives permissions. No idea what’s going on. Raised a prem ticket with MS. Let’s hope they can work this out.

    1. Stein-Erik Alvestad September 26, 2021 at 5:03 pm

      sorry for the late reply, but I guess that you already checked the Activation logs in Microsoft 365 admin center. And that the problem is solved since you contacted MS support 🙂


Leave A Comment

Your email address will not be published.