You couldn't really describe it as a bug since the SPP service is only doing what it should, which is logging requests that are being made to it.The real task you have is to identify what the calling task is and then determine if there's a reason it's checking the licencing status so often and potentially lessening those checks. Going back to the previous post as an example,if it's Server Manager, then you can actually configure the refresh interval or turn it off entirely (you'd have to tell the people running it to do this as there's no central way of doing so as far as I know).One thing you can do purely as a testing mechanic is to disable the firewall rules for 'Windows Remote Management' (there's two of them: port 5985 and port 80).If you do this, then keep an eye on the event log and see if that stops the licensing events from generating. Just don't forget to re-enable the firewall rule once you're done.Cheers,Lain. Okay, that probably explains why the scheduled task is disabled then, as there's no recurrent checks once a MAK key has been initially activated. That still leaves your original problem, of course.What are the actual event IDs that are being generated?

1. Microsoft Software Protection Platform Service High Cpu Windows 8

Microsoft Software Protection Platform Service eating 50%+ CPU. Ok, so I'm seeing the Microsoft Software Protection Platform Service putting a lot of load on my CPU. I haven't noticed it before and I got a forced update reboot about a week ago. I can stop the service but not disable it.

(They should still be from the Security-SPP source)I'll have to go away with those event IDs and see how they bear relevance to MAK activations, as we only use a KMS infrastructure here, and I'd expect to see some differences in the generated events given the 12288 and 12289 that we get only relate to KMS(as far as I understand it).Cheers,Lain. Hi,So, I've done a little reading but I don't have anything definitive. What are I do have are two links and some speculation. First, the links:.For the first post, I took the easy path and run Server Manager locally thinking it'd use the same behaviour and trigger the events, but it didn't. I made sure I had the Refresh option (down the bottom of Server Manager) enabled,but it made no difference.Running it remotely did yield quite a different result.

You couldn't really describe it as a bug since the SPP service is only doing what it should, which is logging requests that are being made to it.The real task you have is to identify what the calling task is and then determine if there's a reason it's checking the licencing status so often and potentially lessening those checks. Going back to the previous post as an example,if it's Server Manager, then you can actually configure the refresh interval or turn it off entirely (you'd have to tell the people running it to do this as there's no central way of doing so as far as I know).One thing you can do purely as a testing mechanic is to disable the firewall rules for 'Windows Remote Management' (there's two of them: port 5985 and port 80).If you do this, then keep an eye on the event log and see if that stops the licensing events from generating. Just don't forget to re-enable the firewall rule once you're done.Cheers,Lain. The Software Protection service (SPP) is designed to verify activation of any app that is registered with it. This includes Office and many Windows services.

I would guess that services like Exchange, SQL, and most others are also a part of this.Every time a registered app starts, it will send a request to SPP to verify the activation. If your copy of Windows is not activated, SPP will not start. If SPP does not start for any reason, SPP registered apps will fail to verify activation and they willnot be permitted to run. After 30 seconds of inactivity, SPP will shut down.The problem is that SPP can take a long time to start and will often time out, even though your system is properly registered. A second attempt will usually get it started, but I don't want to retry 2 and 3 times just to open a Word doc. Server apps willnot automatically retry once they fail the activation check.My workaround is to increase the InactivityShutdownDelay for the SPP. The setting is located at HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform.

I set the InactivityShutdownDelay to 0x0000). Once it starts,the SPP will run for 24 hours without shutting down. This should be enough for a workstation. For server apps, try this and check your logs. If needed, you can try a longer timeout.I do agree with Lain from an earlier posting. Even with this, you should check the logs and make sure what apps are calling for the service.

Microsoft Software Protection Platform Service High Cpu Windows 8

Hi Guys,I too have the same problem, in my case it started after I change ACL Rule is my ASA 5505 Firewall for SQL Server which is running on my DC. The SQL Server communicates with our web server for live data.We are running a Software that uses SQL Service. Recently, I was asked to permit only https to communicate with the web server and the SQL Server in the Office. All for good reasons (Have been seeing loads of Log on request coming to SQLServer from varies countries, masked of course)Once I include a sub-rule only to use https i saw the SPP Log been created. At one point the SPP did a licence stack check with Event ID 1003.Afterwords, SPP was creating logs. At present It has stopped. So far I do not know if there is any problem for our web server to communicate with the SQL Server in office.

I do not know how to check that.I do not know if I should go ahead andincrease the InactivityShutdownDelay for the SPPI am confused.

Windows 7 Professional (x64) - (Pre-installed by HP.) My automatic Microsoft Updates stopped working sometime after 2/9/2010, with a Error Code C0000022. My system still runs good, just can't get updates. After digging around, I found that it is because Software Protection Service is failing to start (error 0xD0000022) on bootup and cannot be started manually, with 'Error 5: Access is Denied'. This OS was fully (legally) licensed and now it states that the Windows Activation - Status Not Available. (I have NOT used any cracks.) Can anyone help me with this? Hello 77thor,'Validation Code: 0x8004FE21' and 'HrOffline: 0x8004FE21' lines are telling me that Windows detected that one or more of it's protected system file(s) has been modified (rewritten, replaced or become corrupt) and that when Windows tried to repair thefiles, it failed. These files can no longer be trusted because they have been modified in some way.

Or in other words, the files are Non-Genuine.Below are things you can try to repair the files and resolve the issue:First try repairing Windows using System Restore:1) Click the Start button2) In the Start Search field, type: System Restore and hit “Enter”3) Select 'Choose Different Restore Point', Put a check in the box that says'Show restore points older than 5 days', select the restore point that corresponds to the date Before you first noticed the issue.4) Click the 'Next' button.5) Reboot and see if that resolves the issue.If that doesn't work, try doing a System Scan. The scan will look for bad system files and will attemptto repair them, if possible.1) Click the Start Button2) Type: cmd.exe3) Right-click the cmd.exe file and select 'Run as Administrator'4) In the CMD window, type: sfc /scannow5) Reboot and see if that resolves the issue.If neither of these sets of steps resolvesthe issue, my only other suggestions would be to either create a (no cost) support request ator reinstall Windows.Thank you,Darin MS.

Hello 77thor,'Validation Code: 0x8004FE21' and 'HrOffline: 0x8004FE21' lines are telling me that Windows detected that one or more of it's protected system file(s) has been modified (rewritten, replaced or become corrupt) and that when Windows tried to repair thefiles, it failed. These files can no longer be trusted because they have been modified in some way. Or in other words, the files are Non-Genuine.Below are things you can try to repair the files and resolve the issue:First try repairing Windows using System Restore:1) Click the Start button2) In the Start Search field, type: System Restore and hit “Enter”3) Select 'Choose Different Restore Point', Put a check in the box that says'Show restore points older than 5 days', select the restore point that corresponds to the date Before you first noticed the issue.4) Click the 'Next' button.5) Reboot and see if that resolves the issue.If that doesn't work, try doing a System Scan. The scan will look for bad system files and will attemptto repair them, if possible.1) Click the Start Button2) Type: cmd.exe3) Right-click the cmd.exe file and select 'Run as Administrator'4) In the CMD window, type: sfc /scannow5) Reboot and see if that resolves the issue.If neither of these sets of steps resolvesthe issue, my only other suggestions would be to either create a (no cost) support request ator reinstall Windows.Thank you,Darin MS.