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.
I have found a tricky workaround.. This error has cost my time for whole day.. I did run the excel.exe as administrator and magically excel run very smooth as expected. Then I run the activation process and so on and this problem was resolved accidentally :)
Thanks
Budi Santoso
Very interesting! I don't have that path, though. Could it be C:\Windows\System32\spp\store_test\2.0\tokens.dat ? That's the first time I've ever seen that.
Interestingly, I have just checked my own system, and notice that I have the ....\store\2.0\tokens.dat on my Win Pro machine - the one which gave me the trouble with upgrading Office 365, whereas on the Windows Home PC it is ...**store_test\2.0\tokens.dat**as you suggest. (See my earlier posting on this thread in which I suggest that there may be issues in Windows Pro, which are not found in Windows Home.)
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.
Finally Solved my issue by following the below instructions found on another thread. Shame it took 12 hours of stress to finally get Office365 to work.
Renamed the tokens.dat file found at C:\Windows\System32\spp\store\2.0\ to tokens.dat.old let me do an install that worked.
Hope this works for others
Very interesting! I don't have that path, though. Could it be C:\Windows\System32\spp\store_test\2.0\tokens.dat ? That's the first time I've ever seen that.
Interestingly, I have just checked my own system, and notice that I have the ....\store\2.0\tokens.dat on my Win Pro machine - the one which gave me the trouble with upgrading Office 365, whereas on the Windows Home PC it is ...**store_test\2.0\tokens.dat**as you suggest. (See my earlier posting on this thread in which I suggest that there may be issues in Windows Pro, which are not found in Windows Home.)