Intelligent standby list cleaner (ISLC) v1.0.3.2 Released (updated)

[DonCrime]

Windows 10 1809 Build 17763.55

[Wagnard]

Windows 10 1809 Build 17763.55

Try this:
Ensure that the counters are not disabled in the registry


The counters may be disabled via registry settings. Please check the following registry locations to ensure that the counters have not been disabled.

HKLM\System\CurrentControlSet\Services\%servicename%\Performance

%servicename% represents any service with a performance counter. For example: PerfDisk, PerfOS, etc.


There may be registry keys for "DisablePerformanceCounters" in any of these locations. As per the following TechNet article, this value should be set to 0. If the value is anything other than 0 the counter may be disabled.

To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command.

Rebuilding the counters:
cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

Resyncing the counters with Windows Management Instrumentation (WMI):
WINMGMT.EXE /RESYNCPERF

Stop and restart the Performance Logs and Alerts service.
Stop and restart the Windows Management Instrumentation service.

[DonCrime]

I have these steps running the program starts and then works synonymous ... but when I close the program or reboot the situation is as before

Rebuilding the counters:
cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

Resyncing the counters with Windows Management Instrumentation (WMI):
WINMGMT.EXE /RESYNCPERF

Stop and restart the Performance Logs and Alerts service.
Stop and restart the Windows Management Instrumentation service.

[Wagnard]

I have these steps running the program starts and then works synonymous ... but when I close the program or reboot the situation is as before

Rebuilding the counters:
cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

Resyncing the counters with Windows Management Instrumentation (WMI):
WINMGMT.EXE /RESYNCPERF

Stop and restart the Performance Logs and Alerts service.
Stop and restart the Windows Management Instrumentation service.

If it's working correctly after doing the previous procedure, than something is breaking the counters when you are rebooting. This can be anything, anti-virus, some applications that start with your system.
Can't tell, you will have to check what program. Is causing this as ISLC required theses and cannot be fixed by me.

The reason it worked for you on older versions is because I was using different and imprecise way to get memory information.

[DonCrime]

yesterday it still worked without problems today no longer (then I have to look what it is

[Wagnard]

yesterday it still worked without problems today no longer (then I have to look what it is

In a future version, I'll add some more error handling so it won't crash silently and instead pop a box with some error / reasons of why it crashed

[avrion]

Hi,

thank you very much for the program, it works great.
I do however have a little bug-report.
With W10 1809 you can specifically increase the font size of windows (not overall dpi) and well the picture below shows what that looks like.

Annotation.png (40.87 KiB) Viewed 10184 times

[Wagnard]

Hi,

thank you very much for the program, it works great.
I do however have a little bug-report.
With W10 1809 you can specifically increase the font size of windows (not overall dpi) and well the picture below shows what that looks like.


Annotation.png

Thanks, I'll see what I can do.

[DonCrime]

Hey Wagnard the Programm in the new Version is working now

Thank You

[Wagnard]

Hey Wagnard the Programm in the new Version is working now

Thank You

Honestly, nothing is really changed to fix your issue there, so maybe you are just lucky or the x64 executable maybe did the trick for you , who knows...