The problem was in 130. It introduced additional data integrity control that appeared to be more paranoid than useful. Fortunately, even in case you lose all the Programs, the only bad outcome is new popups for the programs that already were allowed.

Fortunately, even in case you lose all the Programs, the only bad outcome is new popups for the programs that already were allowed.

Click to expand...

Hm, I don't see the funny side.

Why did oasrv.exe crash when I wanted to start my internet connection?
I tried to restart the service, but this paralysed my system and I had to push the power button.
Therefore I wasn't even able to save the crash log, lost in clipboard.

What's next up on the agenda to get a little less corrupted OA installation?
Uninstall OA, forget about all rules for programs, firewall etc., install OA, run the SCW and start all over again?
Or keep 2.1.0.130 corruption build.

This is your choice. My choice is to see funny side in everything. Some long time ago I was seriouse like you, but then I used a lot of s/w, visited a lot of support forums, and if I didn't stop to be too seriouse I'd got heart attack.

All I wanna say -- there is nothing dangerous in losing program list comparing to the install situation, when you have everything set to default. No unknown program will be allowed. And yes, this is upsetting that your lovely settings were lost. But I cannot take it too seriously comparing, for example, to HDD crash, or RAM fault, or the whole system corruption. Just 10 minutes for me to restore my lovely program settings. The same time to write this message.

BTW, I have discovered that not all the program settings were really lost. When absent programs started they appeared to restore their manualy trusted status and there "allow" status. Those programs that were blocked before were blocked when they tried to run. So there is actually some recovery engine, I think.

BTW, I have discovered that not all the program settings were really lost. When absent programs started they appeared to restore their manualy trusted status and there "allow" status. Those programs that were blocked before were blocked when they tried to run. So there is actually some recovery engine, I think.

Click to expand...

I'm seeing the same behavior. I've not received prompts for some programs, and they reappear in the programs list as fully trusted. Most result in a prompt however. I'm also seeing some of the GUI problems being reported under the same thread at the OA forum.

I understand testing on version .032 is already underway, and an internal update is coming out soon that deals with the new Comodo test.

I'm seeing the same behavior. I've not received prompts for some programs, and they reappear in the programs list as fully trusted. Most result in a prompt however. I'm also seeing some of the GUI problems being reported under the same thread at the OA forum.

I understand testing on version .032 is already underway, and an internal update is coming out soon that deals with the new Comodo test.

Click to expand...

Ehehe. 132 is already in beta and it passes the test, but I don't think it will be released too soon after such unlucky update.

But due to the test I discovered this Run Safer thing in OA. I didn't pay too much attention to it before. Surprisingly for me, when the test was run with Run Safer checked it passed. This is not enough, of course, at least because you can just forget to set the checkbox, but I'll try not to forget about it in the future, when starting unknown things. Second snapshot with RunSafer