Share via

Office 2016 Won't Activate - Software Protection Service?

Anonymous
2018-04-15T03:57:03+00:00

I have a new Windows 10 PC. Windows 10 was installed by HP. All updates to Windows have been applied. 

I have a license for Office 2016 Standard through the Windows Volume Licensing Service Center (VLSC). I downloaded the ISO for 32-bit Office 2016 Standard to my hard drive. Mounted the ISO and ran setup. Everything installed successfully. I have a MAK key from VLSC. I open Word or Excel. See the message that Office needs to be activated. Click Enter a Product Key and enter the MAK into the field. A green check mark appears. Click Install and then OK in UAC. Open a sheet or a document. A yellow warning that Excel or Word will be disabled today followed by an Activate button. Repeat...

I have used the VLSC download and ISO on a number of machines over the years. VLSC Relationship Summary warns the license will expire in 90 days but it shows currently Active. 

I have verified that Windows 10 is activated. From Settings/Apps I have run Repair Office 2016 Standard. 

I have looked in the System Events and see an Event from Software Protection Service. 

Log Name:      Application

Source:        Microsoft-Windows-Security-SPP

Date:          4/14/2018 11:42:58 PM

Event ID:      1003

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      PC-MinAssist-18

Description:

The Software Protection service has completed licensing status check.

Application Id=0ff1ce15-a989-479d-af46-f275c6370663

Licensing Status=

1: 0ed94aac-2234-4309-ba29-74bdbb887083, 1, 0 [(0 [0x00000000, 1, 0], [(?)( 1 0x00000000)(?)( 2 0x00000000 3 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)(?)(?)])(1 )(2 )(3 )]

2: 28f64a3f-cf84-46da-b1e8-2dfa7750e491, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

3: 4c1d1588-3088-4796-b3b2-8935f3a0d886, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

4: 52287aa3-9945-44d1-9046-7a3373666821, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

5: 537ea5b5-7d50-4876-bd38-a53a77caca32, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

6: 77f47589-2212-4e3b-ad27-a900ce813837, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

7: 7ab38a1c-a803-4ca5-8ebb-f8786c4b4faa, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

8: 86af9220-9d6f-4575-bef0-619a9a6aa005, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

9: 951c0fe6-40a8-4400-8003-eec0686ffbc4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

10: 95820f84-6e8c-4d22-b2ce-54953e9911bc, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

11: 96353198-443e-479d-9e80-9a6d72fd1a99, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

12: a96f8dae-da54-4fad-bdc6-108da592707a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

13: ae9d158f-9450-4a0c-8c80-dd973c58357c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

14: b4af11be-5f94-4d8f-9844-ce0d5e0d8680, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

15: b58a5943-16ea-420f-a611-7b230acd762c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

16: c85fe025-b033-4f41-936b-b121521ba1c1, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

17: d7279dd0-e175-49fe-a623-8fc2fc00afc4, 1, 0 [(0 )(1 )(2 )(3 [0x00000000, 0, 0], [( 6 0xC004F009 5 0)( 1 0x00000000)( 6 0xC004F009 5 0)(?)(?)(?)( 10 0x00000000 msft:rm/algorithm/flags/1.0)( 11 0x00000000 0xC004F009)])]

18: dedfa23d-6ed1-45a6-85dc-63cae0546de6, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

19: fb3540bc-a824-4c79-83da-6f6bd3ac6ccb, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" />

    <EventID Qualifiers="16384">1003</EventID>

    <Version>0</Version>

    <Level>4</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-04-15T03:42:58.118191300Z" />

    <EventRecordID>5278</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>PC-MinAssist-18</Computer>

    <Security />

  </System>

  <EventData>

    <Data>0ff1ce15-a989-479d-af46-f275c6370663</Data>

    <Data>

1: 0ed94aac-2234-4309-ba29-74bdbb887083, 1, 0 [(0 [0x00000000, 1, 0], [(?)( 1 0x00000000)(?)( 2 0x00000000 3 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)(?)(?)])(1 )(2 )(3 )]

2: 28f64a3f-cf84-46da-b1e8-2dfa7750e491, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

3: 4c1d1588-3088-4796-b3b2-8935f3a0d886, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

4: 52287aa3-9945-44d1-9046-7a3373666821, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

5: 537ea5b5-7d50-4876-bd38-a53a77caca32, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

6: 77f47589-2212-4e3b-ad27-a900ce813837, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

7: 7ab38a1c-a803-4ca5-8ebb-f8786c4b4faa, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

8: 86af9220-9d6f-4575-bef0-619a9a6aa005, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

9: 951c0fe6-40a8-4400-8003-eec0686ffbc4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

10: 95820f84-6e8c-4d22-b2ce-54953e9911bc, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

11: 96353198-443e-479d-9e80-9a6d72fd1a99, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

12: a96f8dae-da54-4fad-bdc6-108da592707a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

13: ae9d158f-9450-4a0c-8c80-dd973c58357c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

14: b4af11be-5f94-4d8f-9844-ce0d5e0d8680, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

15: b58a5943-16ea-420f-a611-7b230acd762c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

16: c85fe025-b033-4f41-936b-b121521ba1c1, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

17: d7279dd0-e175-49fe-a623-8fc2fc00afc4, 1, 0 [(0 )(1 )(2 )(3 [0x00000000, 0, 0], [( 6 0xC004F009 5 0)( 1 0x00000000)( 6 0xC004F009 5 0)(?)(?)(?)( 10 0x00000000 msft:rm/algorithm/flags/1.0)( 11 0x00000000 0xC004F009)])]

18: dedfa23d-6ed1-45a6-85dc-63cae0546de6, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

19: fb3540bc-a824-4c79-83da-6f6bd3ac6ccb, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )(3 )]

</Data>

  </EventData>

</Event>

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 No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2018-04-15T19:54:29+00:00

    Searched some more and found the answer! After the install I had initially used an expired MAK key. At that time I realized this and then tried to use the currently active key. Using the two keys totally confused Office 2016 activation.

    The discussion at https://gist.github.com/giordanocardillo/c3209cb215226d47322d98499c7a1df7 provided the answer.

    I ran the following script to get the Office Key status for Office 2016 (32-bit) on a 64-bit version of Windows

    cscript "C:\Program Files (x86)\Microsoft Office\Office16\OSPP.VBS" /dstatus

    The output showed two keys were installed. One currently active key and one expired key.

    The last 5 characters of the expired key were obtained from the output of the /dstatus script above. 

    I then ran the script:

    cscript "C:\Program Files (x86)\Microsoft Office\Office16\OSPP.VBS" /unpkey:<LAST 5 CHARACTERS> 

    The /unpkey version was run and problem has been resolved with only one, currently active key installed. Excel, Word, etc. report that Office is Activated.

    This clearly is a bug in the check that is made for an activation key. 

    This begs the question why doesn't the activation process have  "dstatus" button or pointer to a web page for OSPP.VBS? Why does anyone need to spend a couple of hours search to find this out? If more than one key is installed and one of the installed keys is good, then obviously that good key is the one and only key that Office should be using. And in a perfect world the expired keys would be removed automatically. One can only wish.

    Steve

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Vijay A. Verma 104.8K Reputation points Volunteer Moderator
    2018-04-15T20:28:26+00:00

    Glad that you got the solution. Appreciate you posting the solution. This will benefit all others having the same problem.

    Thanking you again.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Vijay A. Verma 104.8K Reputation points Volunteer Moderator
    2018-04-15T07:46:36+00:00

    For this issue, I would recommend that you touch base with VLSC Support. They are the best experts to assist you in this issue. Below page has the contact info for VLSC Support. Choose the country appropriate for your need.

    https://www.microsoft.com/Licensing/servicecent...

    Was this answer helpful?

    0 comments No comments