Office 2010 activation fails after SP2 with error 0x80070190

Anonymous
2013-07-23T21:05:23+00:00

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?

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

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
2013-07-25T16:07:34+00:00

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.

Was this answer helpful?

4 people found this answer helpful.
0 comments

77 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-05-12T15:21:41+00:00

    I tried to follow this and was unsuccessful. When I tried to run the ospp.vbs file all it did was open an HTML text file that explained it's usage. I could not figure out how to make it actually run. SO I caved and used the call in tool. OMD!! What a hassle. Why hasn't this been fixed yet if it has been a known issue for over a year now?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-05T12:24:28+00:00

    Works Perfect. Thanks a ton Paul

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-30T09:32:58+00:00

    Try starting Winword as and administrator. It is located in

    C:\Program Files (x86)\Microsoft Office\Office14

    or

    C:\Program File\Microsoft Office\Office14

    Search for the application named WINWORD, right-click, run as administrator

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-04-29T14:35:26+00:00

    You nailed it with the cscript command!  Thanks for this exceedingly helpful post.

    Was this answer helpful?

    0 comments