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. So, clearly something had written to the SvcRestartTask file with incorrect names for these elements. So I went hunting in a file from a system that didn’t have that problem. Odd – two values for Priority, one numeric, one text. So I moved this file to a document SvcRestartTask.xml in a different folder.Īmong other lines in the file, these stood out: 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. Or for the search engines to find, title: “Task Scheduler”, text: “Task SvcRestartTask: The task XML contains an unexpected node.” “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: So, on to tracing the cause of the problem. I’m not reinstalling unless there’s something hugely wrong, and the refresh didn’t help at all. Then they suggested Refreshing or Reinstalling the PC. 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.Ī Microsoft representative had answered indicating that the cause could be (of all strange things) a partition with no name. Presumably, then, the occurrence that caused this was prior to that. 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. #OFFICE SOFTWARE PROTECTION PLATFORM SERVICE 1003 INSTALL#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. 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.īecause that’s actually where developers put information relating to problems you’re experiencing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |