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-07-26T06:34:07+00:00
Thank you, this solved the problem for me too.
- Running command prompt as administrator
-Running cscript ospp.vbs /act in C:\Program Files (x86)\Microsoft Office\Office14
Was this answer helpful?

0 comments No comments
Anonymous

2013-07-25T14:00:47+00:00

I will try the cscript process later today and report my results. Thanks!
Was this answer helpful?

0 comments No comments
Anonymous

2013-07-25T13:59:22+00:00

Any ideas are welcome. *smiles*

I see that at least two other people are now reporting a similar problem on this thread. I am going to try the cmd line activate suggestion when I go up to school later this morning and see how that works out. Otherwise, my next step is to uninstall Office 2010 on that machine and start over. If that appears to fix it, at least I will know what my process order will need to be for the next 100+ machines I have to update and deploy.

Every solid hit I check on Google keeps pointing back to Office 2010 SP2 Beta - I am still wondering if there is a Beta code indicator in the update package? Or (worse) is this a problem that showed up during the Beta run and has never been fully resolved?
Was this answer helpful?

0 comments No comments
Anonymous

2013-07-25T08:45:01+00:00

I have the same issue. Also school, MAK, all computers where I activated Office 2010 before SP2 activated OK. The poor thing that I tried to activate after installing SP2 failed with the above mentioned errors.

I did the registry fix with no luck.

The following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS{4D36E967-E325-11CE-BFC1-08002BE10318}: UpperFilters **** has the value PartMgr
Was this answer helpful?

0 comments No comments