[1.0.2.x] Issue purging SBL with exclusion list

[Wagnard]

Hey ! I was able to get repro this morning. Trying to fix it...

Edit: I have recoded part of the WMI process detection stuff.
On my end it seems to work good now.
Let me know for you.
Note: I added a little number when ISLC is started near the exclusion button. It shows the number of detected process from the exclusion list.

https://www.wagnardsoft.com/ISLC/ISLC%20v1.0.2.8.exe

[vmech]

Got it, I'll try to check this weekend.

[vmech]

I have a bad news. Again.

It works in a session, but freeze purging after sleep.

[Wagnard]

I have a bad news. Again.

It works in a session, but freeze purging after sleep.

Before sleep, you know if the number was 0 or 1?

[vmech]

Before sleep, you know if the number was 0 or 1?

Near the button "Exclusion list" ? Was 1.

I started the game, number immediately increased to 1, played for a while, closed the game, copied the file - purging worked for a first time, watched a movie - purging worked for a second time, sent computer to sleep.
After waking up, started the game again - number is still 1, played for a while, closed the game, copied the file - you can see result in screenshot.

[Wagnard]

Before sleep, you know if the number was 0 or 1?

Near the button "Exclusion list" ? Was 1.

I started the game, number immediately increased to 1, played for a while, closed the game, copied the file - purging worked for a first time, watched a movie - purging worked for a second time, sent computer to sleep.
After waking up, started the game again - number is still 1, played for a while, closed the game, copied the file - you can see result in screenshot.

Thanks for the report. I think there could be something breaking in ISLC when the computer goes to sleep, I'll try to find out what.

[vmech]

Thanks for the report. I think there could be something breaking in ISLC when the computer goes to sleep, I'll try to find out what.

Maybe. Or maybe something is wrong with the OS.
In any case, the symptoms of dysfunction are as follows:

• Starting excluded program
• Closing excluded program
• Falling asleep
• Awakening
• Starting excluded program
• Closing excluded program
• ISLC dysfunctioning

However, if any action is performed between awakening and starting excluded program that triggers the purging, then dysfunction does not manifest itself in any way, and ISLC continues to work as expected.

[vmech]

I understood how works counter near Exclusion button. I want to add to the above that it is this counter that freezes, i.e. program from exclusion list is already closed, its own process is unloaded from memory, but the counter is not cleared/decreased.

How you get processes info from WMI. By regular ExecQuery inside internal program loop with polling rate delay ? Or by own WMI Provider with events notification ?

[Wagnard]

I understood how works counter near Exclusion button. I want to add to the above that it is this counter that freezes, i.e. program from exclusion list is already closed, its own process is unloaded from memory, but the counter is not cleared/decreased.

How you get processes info from WMI. By regular ExecQuery inside internal program loop with polling rate delay ? Or by own WMI Provider with events notification ?

I subscribe to a wmi event for when a new process start or exit
Maybe after some time at when the computer sleep the event unlink.
I'm thinking or refreshing it after a sleep/unsleep is detected.

[Wagnard]

There is a question quite obvious I didn't ask you...
Windows 10 or Windows 11 ?

I updated with the experimental fix: https://www.wagnardsoft.com/ISLC/ISLC%20v1.0.2.8.exe