Windows 10: Windows keeps refreshing due to "Security-SPP Error 16385." (Every 30 seconds)

Sometime last year i was constantly having issues with my pc which was forcing me to just reinstall windows using my normal product key. The problem is it's windows 8.1. Nobody likes it and the plan is to upgrade to 10 using the media gen tool from Microsoft. The issue came about when apparently windows was being annoying and saying i used the key too many times. I wanted windows 10 now because i'm impatient and want to get my pc up and running again without windows 8 in my life. So i used a KMS service and got it up running up until now. I noticed my taskbar refreshing occasionally and it annoyed me. So i thought it was malware. It was not. I attempted to use the product key on windows 10 and surprisingly. it worked. I cleaned up the kms stuff however the refreshing continued. I noticed it was an Event in event viewer "Security-SPP Error 16385". So this was the thing the kms service left behind. Sadly, Security Protection cannot be disabled on startup. And even if i did it would just create more errors. I would like to know how to fix this/revert it back to a normal pc. I shouldn't have to give any permissions in the folder directory as the kms service is gone. I think the kms server didn't uninstall correctly or something. I will have to do this manually but i don't know where to start. I tried going into cm to see if there was anything i could do but nothing was in the SoftwareProtectionPlatform. I don't think reinstalling windows is and option for me because i don't want to go through this again.

:)

 

Error Security-SPP in Windows Server 2016 (Event ID: 16385)

Hello,

I am running Windows Server 2016

The error is showing up every 30 seconds and I can't Remove This Event

When I go to Event Properties for the Security-SPP error I'm getting the following information is presented:

"Failed to schedule Software Protection service for re-start at 2118-05-13T04:05:27Z. Error Code: 0x80070002."

Source: Security-SPP

Event ID: 16385

Level: Error

User: N/A

OpCode: Info

Task Category: None

Keywords: Classic

I hope someone can help me to stop and remove this event now.

Regards,

MooLectro

 

Information 13/03/2018 08:19:22 Security-SPP 16384 None and 16385

#

Information 13/03/2018 08:19:22 Security-SPP 16384 None

#

General

Successfully scheduled Software Protection service for re-start at 2118-02-17T08:19:22Z. Reason: RulesEngine.

#

Details

- <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="2018-03-13T08:19:22.607760400Z" />

<EventRecordID>4433</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>Application</Channel>

<Computer>xx</Computer>

<Security />

</System>

- <EventData>

<Data>2118-02-17T08:19:22Z</Data>

<Data>RulesEngine</Data>

</EventData>

</Event>

#

36500 day error? 25 days short of 100 years before restart?

#

Similar for 16385 i.e. 36500 days

#

Should SPP 16384 and 16385 be scheduled for a restarts in 100 years time?

#

 

Microsoft Edge TLS Security


After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.