steves1977uk wrote:Easiest way... https://www.sordum.org/9480/defender-control-v1-4/
Of course there's other ways like you and me know BM But I'm trying to keep it simple and straightforward for SM
Steve
Burgerman wrote:For future reference.
Open any image editor or viewer.
Burgerman wrote:http://www.burgerman.info/
Also worksin case anyone cares. For at least 15 years?
Burgerman wrote:Depends what that crack actually does. Some have a few options. And they re run the activator automatically every few days so you aways have 6 months to go. Some use volume licence keys, and good to go forever theoretically. Some need to be rerun manually every 6 month or sooner.
SM, try the attached Win10 activator, this one renews itself via the task scheduler. Extract and run the cmd file as administrator.
Dont install a crack that sets a scheduler that run every day and eat up CPU cycles and your computer will run slow.
SM, try the attached Win10 activator, this one renews itself via the task scheduler. Extract and run the cmd file as administrator.
Thats a bad idea...
Which is why I said:Dont install a crack that sets a scheduler that run every day and eat up CPU cycles and your computer will run slow.
And CPU will sit at a 3 or 5 % high percentage at idle
If you did this, go to the task scheduler, find the entry and delete it... Or disable it. And run it only after you get a 180 day warning. Then disable it again. Or it starts running every logon, and then conflicts with the "system interupts" all day long.
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.3" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Source>Microsoft Corporation</Source>
<Author>Microsoft Corporation</Author>
<Version>1.0</Version>
<Description>This task restarts the Software Protection Platform service when user logon occurs</Description>
<URI>\Microsoft\Windows\SoftwareProtectionPlatform\SvcTrigger</URI>
<SecurityDescriptor>D:P(A;;FA;;;SY)(A;;FA;;;BA)(A;;FRFW;;;S-1-5-80-123231216-2592883651-3715271367-3753151631-4175906628)(A;;FR;;;S-1-5-4)</SecurityDescriptor>
</RegistrationInfo>
<Triggers>
<LogonTrigger>
<Enabled>true</Enabled>
</LogonTrigger>
</Triggers>
<Principals>
<Principal id="InteractiveUser">
<GroupId>S-1-5-4</GroupId>
<RunLevel>LeastPrivilege</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>false</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>true</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
<UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
<Priority>7</Priority>
<RestartOnFailure>
<Interval>PT1M</Interval>
<Count>3</Count>
</RestartOnFailure>
</Settings>
<Actions Context="InteractiveUser">
<ComHandler>
<ClassId>{B1AEBB5D-EAD9-4476-B375-9C3ED9F32AFC}</ClassId>
<Data>logon</Data>
</ComHandler>
</Actions>
steves1977uk wrote:SM, try the attached Win10 activator, this one renews itself via the task scheduler. Extract and run the cmd file as administrator.
Steve
I only use the windows partition for mob equip programming
Scooterman wrote:That seems to have done the trick Steve
It was really easy.
I only use the windows partition for mob equip programming so if the widget file slows down my cpu a tad I'm not bothered. And Steve's fix seems to have worked well and was really easy to do for someone like me.
Users browsing this forum: No registered users and 49 guests