ISLC Not Working? Startup, Memory and Purge Fixes

ISLC not working: identify the failure first

A program that never opens has a different problem from a program that opens but never purges. Start with the visible symptom and avoid applying every tweak in an old forum reply. Record the version, package type, executable path, Windows version and any message in Event Viewer. If the issue began after an update or folder move, include that change in the diagnosis.

ISLC allows one application instance. If the window seems missing, check the system tray and Task Manager before launching repeated copies. Version 1.0.4.6 adds Show UI to the tray icon. A minimized instance may be working normally even though the main window is not visible.

When ISLC is not working, define what working behavior should look like for that feature. A working monitor shows changing memory values, a working automatic purge waits for both thresholds, and working startup opens the expected executable from its permanent path. These separate checks prevent a healthy feature from being mistaken for a failure elsewhere.

Verify the ISLC file and current version

Troubleshooting an old or repackaged build wastes time. The current official support thread lists 1.0.4.6. Compare the filename, download host and SHA-256 against the versions page. If the hash differs, delete the file and download it again from Wagnardsoft rather than adding antivirus exclusions or changing Windows settings.

The portable build must finish extracting before the application is used. Keep all included files together. Older publisher support responses note that missing companion files and running from protected locations caused problems in early builds. A normal user-controlled folder is easier to maintain than a temporary download or a partially extracted archive.

• Use version 1.0.4.6 unless Wagnardsoft support requests another build.
• Confirm the domain is download.wagnardsoft.com.
• Keep extracted portable files together.
• Move the folder only while ISLC is stopped, then review startup configuration.

Fix ISLC showing zero memory values or closing

First exit every ISLC process, restart Windows and open the current build from its permanent folder. Check Event Viewer under Windows Logs and Application for an entry at the same time as the failure. Preserve the exception text before attempting a repair. A current build that still fails should be reported with the Windows version, ISLC version and relevant log entry.

Older ISLC versions used Windows Performance Counters and could fail when those counters were disabled or damaged. Historical Wagnardsoft guidance recommended running LODCTR /R twice from an elevated Command Prompt and rebooting. It also suggested checking disabled counters with lodctr /q | find "Disabled". However, the 1.0.4.0 changelog says Performance Counters are no longer used. That makes LODCTR a legacy, symptom-specific repair rather than the first step for 1.0.4.6.

Do not paste commands into an elevated terminal without understanding their scope. Rebuilding counters affects Windows performance-counter configuration across the system. Create a restore point, capture the error and prefer current publisher support when the failure does not match the documented legacy pattern.

1. 1

   Restart with the current build

   Exit duplicate processes, reboot and open ISLC 1.0.4.6 from a complete folder.

2. 2

   Read the application log

   Use Event Viewer to capture the module and exception associated with the close event.

3. 3

   Check current release notes

   Determine whether the error matches a known issue or already-fixed old-version problem.

4. 4

   Use legacy repair only when relevant

   Apply LODCTR guidance only for a confirmed performance-counter symptom and with administrative care.

5. 5

   Report reproducible details

   Provide Windows build, ISLC version, package type, path and error text to Wagnardsoft support.

Why ISLC is not purging the standby list

No purge does not automatically mean ISLC is broken. Automatic cleaning can be working correctly while it waits for both conditions at the same time: the standby list is at least the configured amount and free memory is lower than its configured amount. If available memory remains healthy, ISLC should not purge solely because standby cache exists.

Confirm that monitoring is started and that the displayed values update. Then compare each value with its threshold. If one condition never becomes true, the observed behavior is expected. Avoid raising the free-memory threshold until ISLC purges constantly; that can turn useful cache into unnecessary churn. Use the settings guide to choose values based on real workload measurements.

• Check that Start monitoring is active.
• Read both current values and both thresholds.
• Remember the two conditions use AND logic.
• Use manual Purge only as a controlled diagnostic action.
• Do not treat a zero purge count on a healthy system as a failure.

Fix ISLC not starting with Windows

ISLC can create or remove a Windows scheduled task when its startup setting changes. Portable users commonly break that reference by moving, renaming or deleting the folder after the task is created. Put the current executable in its permanent location, open ISLC manually and toggle the startup option so the task can be recreated with the correct path.

Open Task Scheduler and inspect the action path if startup still fails. Confirm that the user account, executable location and permissions match the current installation. A working task points to the current executable and permitted user context. Do not create multiple overlapping startup entries in the Startup folder, registry and Task Scheduler. One documented method is easier to disable and diagnose.

1. 1

   Stop and exit ISLC

   Ensure the tray process is closed before moving or updating files.

2. 2

   Set the final folder

   Place the portable build where it will remain, or complete the installer setup.

3. 3

   Recreate startup

   Open ISLC and disable then re-enable its startup/minimized setting.

4. 4

   Inspect Task Scheduler

   Confirm the action points to the existing 1.0.4.6 executable.

5. 5

   Test a normal sign-in

   Restart Windows and use Show UI from the tray to confirm the process loaded.

Fix update checks and a missing ISLC window

Version 1.0.4.6 specifically improves update-check robustness, so an older build that cannot find updates should be replaced through the publisher release thread rather than trusted to repair itself. Firewall, DNS or security filtering can still block an update request. The download page can be checked manually when the built-in notification is unavailable.

When ISLC is running but the window is missing, open the system tray overflow area, find the ISLC icon and use Show UI. If the icon is absent, check Task Manager. End a stuck process only after noting its state, then reopen the current executable. Repeatedly launching new copies will not work because ISLC is designed to allow one instance.

ISLC troubleshooting FAQ