This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 55.00000000000001%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
The Windows application log shows a few dozen messages like this each day:
Successfully scheduled Software Protection service for re-start at 2122-01-31T12:48:08Z. Reason: RulesEngine.
What is the purpose of scheduling a restart in 2122, nearly 100 years from today, 2022-02-24?
Example Log Event
The year 2122 appears on lines 11 and 31.
Log Name: Application
Source: Microsoft-Windows-Security-SPP
Date: 2/24/2022 7:48:08 AM
Event ID: 16384
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Joels-Dell-XPS-8940
Description:
Successfully scheduled Software Protection service for re-start at 2122-01-31T12:48:08Z. Reason: RulesEngine.
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">16384</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-02-24T12:48:08.7141596Z" />
<EventRecordID>123645</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Joels-Dell-XPS-8940</Computer>
<Security />
</System>
<EventData>
<Data>2122-01-31T12:48:08Z</Data>
<Data>RulesEngine</Data>
</EventData>
</Event>
Windows Information
Edition Windows 10 Pro
Version 20H2
Installed on 12/14/2020
OS build 19042.1526
Experience Windows Feature Experience Pack 120.2212.4170.0
Related Questions
These questions about the same event ID also show dates a century in the future.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 6%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In my opinion, the scheduling of a restart for the Software Protection service in the year 2122, nearly a century from now, is an intriguing decision. It is likely driven by maintenance considerations, as software and security updates often come with changes that aim to maintain compatibility over extended periods. By setting up such a distant restart, it appears to be a way of ensuring that the Software Protection service can smoothly receive any necessary updates throughout the entire lifespan of the Windows installation. This approach seems forward-thinking, especially if the operating system or security models undergo significant transformations in the coming decades.
Rather than opting for periodic restarts, like on a weekly or monthly basis, this choice of scheduling one update cycle for 100 years in the future seems designed to prevent unnecessary disruptions. At Andersen, we ensure that the service remains up-to-date for the very long term without causing multiple interruptions as long as the system remains operational. It's a strategy that, in my view, minimizes inconvenience while safeguarding the service's effectiveness over the entire lifespan of Windows.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello @Joel Shprentz
This might occur if the Software Protection service is disabled on your device.
Go to Computer Management->Services and Applications->Services and restart the Software Protection service
This service enables the download, installation and enforcement of digital licenses for Windows and Windows applications. If the service is disabled, the operating system and licensed applications may run in a notification mode. It is strongly recommended not to disable the Software Protection service.
The issue might also occur if one or more of the following conditions are true:
-The Task Scheduler service is disabled.
-The Software Protection Platform service isn't running under the NETWORK SERVICE account.
Hope this resolves your Query!!
--
--If the reply is helpful, please Upvote and Accept it as an answer–
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 9%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVF%3C/text%3E%3C/svg%3E)
I see this too. Task scheduler is running. SPPSVC is Automatic (Deleyed Start), logon as Network Service, and stopped. If I start it with the MMC Services applet, it stops after 30 seconds and I get an event log entry:
Successfully scheduled Software Protection service for re-start at 2123-01-31T19:46:36Z. Reason: RulesEngine.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 34%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
El Servicio de protección de software si esta corriendo sobre el SERVICIO DE RED, contantemente lo encuentro sin iniciar aun iniciándolo manualmente, sin embargo el evento sigue siendo muy frecuente y no me permite trabajar con aplicaciones desde las terminales de trabajo, al iniciar a trabajar con una aplicación desde una terminal, el servidor pierde comunicación, inclusive no responde ni con ping, solo reiniciando el servidor se restaura la comunicación, pero se vuelve a perder al ejecutar una aplicación que apunte al server.