Office 2010 activation fails after SP2 with error 0x80070190

Anonymous

Windows 7 Pro, Office 2010 Pro Plus

I put Office 2010 SP2 on three identically configured machines this morning. Two of them had previously had Office 2010 activated, the third had not yet been activated. After SP2 was installed, the two machines with previously-activated versions of Office 2010 continue to work correctly; the third machine demands that I activate Office - the process appears to run, but then fails with error code 0x80070190.

An initial call to Support yielded a request for me to install Hotfix for Windows KB947821. That installed correctly, but did not fix the problem. Before I call back, I thought I would put something out here to see if others have come across this problem.

A Google search on the error code keeps coming up with information implying that this may be related to a Beta status in Office 2010. Is it possible that today's release of SP2 was not final code?

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.

0 comments

Answer accepted by question author

Anonymous

Aha!

I tried using the cscript cmd line process described elsewhere in this thread, and got a new error:

Last 5 characters of installed product key: XXXXX (they matched my MAK key, so the correct product key is already in place)

ERROR CODE: 0xC004F025

ERROR DESCRIPTION: The Software Licensing Service reported that the action requires administrator privilege.

So apparently UAC is getting in the way.

I found this thread:

http://social.technet.microsoft.com/Forums/windowsserver/en-US/8f2a5c3e-4e33-4fdb-8eb2-760dbeca0713/error0xc004f025-access-denied-the-requested-action-requires-elevated-priviliges

which led me to this post:

http://www.blogsdna.com/2168/windows-7-how-to-open-elevated-command-prompt-with-administrator-privileges.htm

Which FIXED THE PROBLEM!

The remaining question is, Why is UAC suddenly putting itself in charge of activation *after* SP2 when it did not appear to get involved previously? I made no changes to UAC on any of the machines where SP2 was installed; I try to avoid touching UAC as much as possible.

0 comments

77 additional answers

Anonymous

2013-10-10T18:11:35+00:00
Another way to fix this...
1. Temporarily disable UAC (start > in the run line > UAC > enter > Move slider down > ok
2. Log off/on or reboot then log in
3. Search for 'winword' > when the icon comes up right click on it and select "Run as admin.."
4. Run online activation and allow it to finish.
5. Go back and re-enable UAC (same process, move slider up).
6. log off/on or reboot.
This worked for me on a fresh install that had not been activated before i applied SP2.

-Strobe74
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-25T14:47:54+00:00

This is a major issue in a VDI deployement where users are not administrators and no local administrator account is enabled.

MS 2012 RDS VDI will not allow you to preserve activation, which makes sense in a way, but the systems now will not activate without administrator rights. This seems to be true even with a KMS server.

Can anyone confirm this? Is there a fix coming?

Thanks.
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-23T11:06:47+00:00

It's actually easier than running the script: just navigate to the Office folder in Program Files (or X86), right-click on an Office application (such as WinWord) Run as Administrator and proceed to activate it.
Was this answer helpful?

0 comments No comments
Anonymous

2013-09-19T16:49:42+00:00

Thanks for the tip. I fixed it running WINWORD.EXE, in Microsoft Office folder, as administrator (right-click > Run as Administrator).
Was this answer helpful?

0 comments No comments