This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When I try to activate Office after I upgraded to Windows 10 I receive this error: We are sorry ,something went wrong and we can't do this for you right now. please try again later (0X8004FC12). How can I get past this?
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hello,
Please try the steps in this article: Office error code 0x8004FC12 "We’re sorry, something went wrong" error when activating Office
I have made a posting within Windows Feedback which draws attention to this posting, in the hopes that someone at MS might look at it and act on it rapidamente!
Let me add my voice to the chorus of thanks to Nicholas_W_ for his outstanding contribution. Like so many of you, I have run the whole gamut of install, re-install, Fixit and Easyfixit (!!??), disabling virtually everything bar the kitchen sink, restarting, re-installing, (in vain) spending over an hour on a poor line to somewhere in the world with an apparently not-very-knowledgeable MS technician, who basically ran the Fixit (015 ... cab) file, uninstalled, reinstalled and then terminated the call, I trust not in anger! I have spent several days on this issue ... and then, like so many others discovered ... this post. And, as with so many of you, it was the 3rd step Add Net Local group which did the trick. What a joy to see the apps activated and to be able to use them again! That is after all what subscribers to Office 365 are subscribing for.
I heartily endorse all that others have said by way of congratulations to the author of the post, and by way of urging MS to do something radically different about "support" for what is after all supposed to be their flagship product. It is vital that this solution be conveyed toMS, for the sake of doubtless thousands of other sufferers, who are wrestling with this issue. Perhaps Nicholas_W_ 's solution can be compiled into some code by someone at Redmond so that a file can be released urgently which really will FIXIT!! I am sure that Nicholas_W_ will not demand too hefty a fee! Has anyone any way of ensuring that MS hear about this, given that they do not seem to monitor postings like this very actively.
One afterthought. I had actually succeeded in installing Office 365 (2016) on another PC without meeting the activation issue. I have been puzzled as to why it should install on that (lower spec machine, which incidentally was running on Windows 10 build10547) and not on a much superior spec PC (which was running the RTM) and the only surmise which I have had is that, since the solution seems to relate to Group Policy, the problem may only occur under Windows Pro, since that other PC (the one without the activation issue) was running Windows Home. But I am probably totally wrong. Has anyone else had success with Home while receiving the dreaded 0x8004FC12 with Pro?
Any way, many thanks. We are all extremely grateful to you.
The third option worked for me too. thanks.
Wonderful! Step 3 fixed it for me as well. Thank you.