I admit that itâs a little strange to look at your event log fairly often, but I occasionally find interesting behaviour there, and certainly whenever I encounter an unexpected error, thatâs where I look first.
Because thatâs actually where developers put information relating to problems youâre experiencing.
So, when I tried to install Windows 8.1 and was told that I would be able to keep âNothingâ â no apps, no settings, etc â I assumed there would be an error in the log.
But all I saw was this:
So, yes, thatâs an error with:
Event ID: 16385
Error Code: 0x80041316
This goes back to September 2, but only because the Application log that itâs in has already run out of room and ârolled overâ with too many entries. Presumably, then, the occurrence that caused this was prior to that.
Searching online, I find that there are some others who have experienced the same thing, the most recent of which is in January 2013, and who posted of this error to the TechNet forums.
A Microsoft representative had answered indicating that the cause could be (of all strange things) a partition with no name. Odd. Then they suggested Refreshing or Reinstalling the PC.
Iâm not reinstalling unless thereâs something hugely wrong, and the refresh didnât help at all.
So, on to tracing the cause of the problem.
âScheduleâ suggests it might be a Task Scheduler issue, and sure enough, when I open up the Task Scheduler (itâs under the Administrative Tools in the Control Panel, so making it very hard to find in Windows 8), I get the following error:
Or for the search engines to find, title: âTask Schedulerâ, text: âTask SvcRestartTask: The task XML contains an unexpected node.â
Itâs a matter of fairly simple searching (as an Administrator, naturally) to find this file âSvcRestartTaskâ under C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform.
So I moved this file to a document SvcRestartTask.xml in a different folder.
Time to edit it.
Among other lines in the file, these stood out:
Odd â two values for Priority, one numeric, one text. So I went hunting in a file from a system that didnât have that problem. I found these lines in the same place:
So, clearly something had written to the SvcRestartTask file with incorrect names for these elements. Changing them around in my XML version of the file, I reopened the Task Scheduler UI, navigated down to Microsoft / Windows / SoftwareProtectionPlatform, and imported the XML file there. [This is under âActionsâ, but you can also right-click the folder SoftwareProtectionPlatform and select âImportâ, then âRefreshâ]
Sadly, this wasnât quite the end of things, because the Task Scheduler UI fails to talk to the Task Scheduler service. Nor can I restart the Task Scheduler service directly.
So a restart will take care of that, and sure enough, now that Iâve restarted, I see no more of these 16385 errors from Security-SPP.
Itâs just a shame it took so long to get this answer, and that the Microsoft-supplied answer in the forums is incomplete.
Oh, and of course, one last thing â what does SPP (Software Protection Platform) actually do?
Since this is an element of the Windows Genuine Advantage initiative, with the goal of preventing use of pirated copies of Windows, you might consider you donât really need / want it around. Either way, you definitely donât want it clearing your Application event log out every three weeks!