Failed to schedule Software Protection service for re-start: Error Code: 0x80041316

This post documents how to resolve the following error message, which may appear for no particular reason, and flood the Windows event log: Failed to schedule Software Protection service for re-start at 2116-09-14T16:54:27Z. Error Code: 0x80041316. The following steps will resolve the error on Windows Server 2012r2, but based on other links, similar steps should work for Windows 8, 8.1, or Server 2012.

Root Cause

The root cause, in my case, was a corruption in the XML files that control task scheduling for the Software Protection service. I am not sure what caused this error, but it appeared to start after a domain controller was not shut down cleanly. Microsoft’s official documentation reports that another cause may be a mismatch between the permissions used to run the task and the permissions on the files that control the task. However, most people have reported that the problem is caused by corrupted XML files. Also, note that the Microsoft documentation is inaccurate when it states that the task must run as the NETWORK SERVICEaccount. If the task is triggered by an interactive user logon, it should run as accountInteractive.

Resolution

The most helpful TechNet thread describes several ways to fix the corrupt XML files. I did not have to do anything involving the Registry, so I recommend the following solution. Since I have other domain controllers running Windows Server 2012r2, I did the following:

  1. On the problem system, back up all files in the directory C:WindowsSystem32TasksMicrosoftWindowsSoftwareProtectionPlatform
  2. From a system that is working, copy all files in the directory C:WindowsSystem32TasksMicrosoftWindowsSoftwareProtectionPlatform. Put them in a location where you can access them on the problem system. DO NOT attempt to paste them on top of the existing files in that path!
  3. You can also copy the files from a Windows installation disk.
  4. Re-name the files to add an XML extension so that they can be imported.
  5. Navigate to to Computer Management->System Tools->Task Scheduler->Task Scheduler Library->Microsoft->Windows->SoftwareProtectionPlatform
  6. Right-click on each task and select Delete. You did back them up, right???
  7. Right-click on SoftwareProtectionPlatform and select Import Task…
  8. Import each of the XML task files that you copied from the other computer.
  9. Go to Computer Management->Services and Applications->Services and restart the Software Protection service. It wouldn’t hurt to reboot the system.
  10. Log out, log back in, and check the Event Viewer to see if the errors have stopped.

One TechNet user in that thread reported that they didn’t need to obtain files from a working system. On the problem system, they right-clicked on each task, selected Export, and saved the XML to another location. They then deleted each task and re-imported from the XML files. This would be the easiest solution, but I haven’t verified that it works. Please let me know if it worked for you.

References

Window Server Forum

Comments

Comment #1 by tototonino

tototonino - Jan 3, 2017

In my case the task from the Task Scheduler was missing, but the SvcRestartTask was in the folder. So I have imported the task and reset the schedule. Haven’t seen Event errors since.

Comment #2 by Steve

Steve - Apr 4, 2017

I also exported and then re-imported the tasks, and the error stopped. I got a message event ID 16384 that said “Successfully scheduled Software Protection service for re-start at 2017-04-12T17:50:22Z. Reason: RulesEngine.” Then the service stopped itself, and the errors didn’t return. Thanks a bunch!

Comment #3 by Roberto

Roberto - Nov 1, 2019

Very good hints, thank you!

Comment #4 by Mr P

Mr P - Feb 4, 2020

When doing step 8, logged in as local admin account, I get the following error popup when trying to import either svcRestartTask or svcRestartTaskNetwork : An error has occurred for task [svcRestartTask | svcRestartTaskNetwork]. Error message: The following error was reported: 2147750680 Any ideas please?

Comment #5 by cus2002

cus2002 - Aug 1, 2020

Hallo allgemein, ich habe mal eine Frage bezüglich offizieller Windows -Fehler . Die Datei svcrestarttask von der Software Protection Platform ist ganz offensichtlich falsch programmiert mit Ausführungsdatum 7.8.2120 . Auch bei anderen Rechnern ist dieses Datum falsch programmiert in diesem Task. In der Ereignisanzeige treten nun alle 30 Sekunden Fehler auf wegen falscher Security-SPP Fehler 16385 , tausende bis jetzt . Was passiert nun,wenn man die Aufgabe svcrestarttask einfach löscht in der Augabenplanung ? Microsoft warnt ja davor, diese zu löschen, das gäbe Ärger beim Installieren von Programmen. Nur, was nutzt eine fehlerhafte Datei mit Fehleranzeigen ? Transplantieren von einem anderen Rechner nimmt meiner nicht an. Da kommen sofort Fehlermeldungen bevor ich die Aufgabe importieren kann. scannow und DISM ohne Fehleranzeige.

Comment #6 by craig

craig - Aug 1, 2020

Rough English translation from Google Translate:

Hello general I have a question about official Windows errors. The svcrestarttask file from the Software Protection Platform is obviously incorrectly programmed with execution date 7.8.2120. This date is also incorrectly programmed for other computers in this task. In the event viewer, errors now occur every 30 seconds due to incorrect security SPP error 16385, thousands so far. What happens if you simply delete the svcrestarttask task in the publication planning? Microsoft warns against deleting them, that would be trouble when installing programs. But what does a faulty file with error displays use? I don’t accept transplants from another computer. There are error messages immediately before I import the task can. scannow and DISM without error display.

Comment #7 by 송용근

송용근 - Sep 3, 2020

Thank you, Craig, for your very helpful solution. I finally corrected the problem. Thank you, very much.

Comment #8 by Yahya

Yahya - Oct 2, 2020

worked perfectly. Thank you very much !