Information 13/03/2018 08:19:22 Security-SPP 16384 None

General

Successfully scheduled Software Protection service for re-start at 2118-02-17T08:19:22Z. Reason: RulesEngine.

Details

• <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">16384</EventID>

  <Version>0</Version>

  <Level>4</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2018-03-13T08:19:22.607760400Z" />

  <EventRecordID>4433</EventRecordID>

  <Correlation />

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

  <Channel>Application</Channel>

  <Computer>xx</Computer>

  <Security />

  </System>

• <EventData>

  <Data>2118-02-17T08:19:22Z</Data>

  <Data>RulesEngine</Data>

  </EventData>

  </Event>

36500 day error? 25 days short of 100 years before restart?

Similar for 16385 i.e. 36500 days

Should SPP  16384 and 16385 be scheduled for a restarts in 100 years time?

We appreciate you for getting back to us. The reason that the scheduled Software Protection service was set for re-start at 2118-02-17 is because the Microsoft-Windows-Security-SPP component will resets licensing values that were set during system installation and image testing. 

About your query about the wrong version number, based on the given information, the Windows 1709 16299.309 was installed 13-Mar-2018 22:00 that’s why the event data still reflects version number 10.0.16299.248 since event data started “13/03/2018 21:57:59    Security-SPP    902    None.”

Kindly get back to us if you need more information or clarification and we'll be happy to assist you.

• 1 What task are you trying to perform that you’ve encountered this issue?
• 2 What troubleshooting steps have you done so far?
• 3 Did you make any changes to the computer prior to this issue?

1 Run Windows

13-Mar-2018 23:23 running BBC iplayer

2 Win Pro was "clean installed" 01-Mar-2018

3 Now running 1709 16299.309 as of 13-mar-2018 22:00

Win 10 home & pro

1709

16299.309 after updates from 16299.248

#

#

Information    13/03/2018 21:57:59    Security-SPP    902    None

The Software Protection service has started.

10.0.16299.248

• <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">902</EventID>

  <Version>0</Version>

  <Level>0</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2018-03-13T21:57:59.304124200Z" />

  <EventRecordID>4626</EventRecordID>

  <Correlation />

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

  <Channel>Application</Channel>

  <Computer>xxxxx</Computer>

  <Security />

  </System>

• <EventData>

  <Data>10.0.16299.248</Data>

  </EventData>

  </Event>

• <EventData>

  <Data>10.0.16299.248</Data>

This is showing the wrong version number it should be 10.0.16299.309 should it not?

Win 10 Home

16299.309

Information    13/03/2018 21:58:29    Security-SPP    16384    None

Successfully scheduled Software Protection service for re-start at 2118-02-17T21:58:29Z. Reason: RulesEngine.

Information    13/03/2018 21:58:29    Security-SPP    903    None

The Software Protection service has stopped.

 no sign of restart at 22:27:00

Win 10 Pro

13-mar-2018 21:59:56 16384 Security SPP

 ... software Protection service for restart 2118-02017T21:59:56Z -- 100 years time

13-mar-2018 22:04:44 916   ESENT

22:21:00 Software Protection still stopped ...

16384 happens during re-starts followed by 903 Win 10 Pro

Hi Willim,

For us to assist you further with your concern, we’ll need the following details:

• What task are you trying to perform that you’ve encountered this issue?
• What troubleshooting steps have you done so far?
• Did you make any changes to the computer prior to this issue?

We’ll wait for your reply.