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
Well, that's even weirder to me. I have a Windows 10 Pro machine (upgraded from 8.1 Pro, went through the Insiders program, then RTM build 10240, and now on post-RTM Build 10547), and I have only the store_test path. And I never knew anything about that path until today.
Well, my Windows Home PC, the one with the store_test path is also on post-RTM 10547. My Windows pro PC does not have the store__test path and is on RTM (10240). I deliberately keep it away from the post-RTM updates. It is beginning to look as though the strange path difference is not a Windows Home/Pro matter, but a question of the build.
Probably so. I have a masochistic streak, so I joined Windows Insiders. I think this is the best Windows yet, but even so, I have advised others to wait 2 or 3 months post RTM before upgrading. Events like this just reinforce that opinion.
You must write Administrators in german. With the command "net localgroup" you can see all the local groups.
Thank you very much, Nicholas_W_. At last I've could activate my Office.
I've tried your 3rd method (adding a local group) many times, but I experimented "System error 1376: local group doesn't exist" (en español: error de sistema 1376: el grupo local especificado no existe). It must write "Administrators" in the Language of the OS, in my case, catalan, but the group was named in spanish: "Administradores". Then, it has all worked perfectly! Thank you again!!
Thanks Nicholas for these steps. #3 worked for me. Still I feel Microsoft should be more careful before launching a new update as the whole process of licensing Office on my Windows 10 wasn't anywhere close to being "User-friendly". I can not imagine my parents or other non-tech background folks to go through these hassles to license a product.