New Antiexecutable: NoVirusThanks EXE Radar Pro

Hi all...I have no Win10...I have only 8.1 on laptop...so there is a sense to use new beta version in it?

 

if you were selected , yes, feedback on other OSes are always welcomed.

 

Suggestion #1 - A big timesaver would be if the user were able to close the Rule Editor with the ESC key.
Suggestion #2: The "save" button in the Rule Editor is only clickable if the user has changed the rule, else the button is "greyed out" or not clickable.

 

Yes, great job guys, I can't help because I don't use any virtual machines. If it's a bit more mature I will also try to give some feedback.

If there is one thing I hate in the Windows OS, it's the ugly focus rectangle! The person who "invented" this should be in jail.

 

LOL, I'm using a real machine

 

No sorry, not willing to risk my only machine. I do have an older laptop, but it's slow as hell without a SSD.

 

I must admit, I have never used an imaging app, except for Rollback RX on virtual machines back in the days. I have never really had full trust in them. But if ERP gets more mature I will for sure install it, I have never really had major problems with beta versions, but this version seems to be more of an alpha version, not ready for primetime.

 

@Rasheed187

Even if you have zero trust in imaging apps you can always grab even a recommended (from a guru's suggestion) freebie one and drop the backup someplace, preferably even a cheapie external drive and if anything would happen to toast, you could always even manually at the very least pull out that/your imaged data files and start back up again with preserved digital matter (your files)

And I thought I used to be the only one who chanced destiny with the likes of SD and no fallback image

 

If @Rasheed187 doesn't feel confident, don't force him, he will just wait the public beta, i'm testing ERP on real machine with RX installed, and i have to do some cold shutdown, so i can understand him.

 

Yes, I don't feel confident that's the problem. I just don't want to deal with certain stuff. The reason why I don't use virtual machines is because I don't want to stress my SSD too much. Perhaps in the future when SSD's are more durable, who knows. And once again thanks to all people who are already testing ERP.

 

@ichito

Please test this first ERP beta on virtual machines only or using an imaging program, it may create some known issues.

@Rasheed187

No problem The next one or two beta versions should make ERP pretty stable.

Will have a new beta version on the next days, it will include most bugs\enhancements and improved support for W10 and FUS.

 

Can't wait! BTW, is it possible with this new version to stop all processes from running explorer.exe and svchost.exe as a child process?

 

I've sent a new beta build to @mood @guest @Peter2150 @Mister X

This is the changelog so far:

It should also have fixed the LogonUI.exe issue.

This new beta build is still private and should still be tested in VMs.

The next build should have improved FUS and user logons support, along with the other suggestions added.

@Rasheed187

Yes, with ERP v4.0 you can fully control parent process executions.

 

Just great! Thank you very much. Testing in a couple of hours.

 

I'm back home and now i have time to test it

 

Fixed bugs as stated.

Findings:

• When user clicks on "-" (minimize) icon, the main window is hidden (not minimized).
• ProcPermitSvc.exe - 3.3 MB (Memory usage) - Is this correct? It seems a bit too much to me.
• ProcPermitDialog.exe - 10 MB (Memory usage) - Is this correct? It seems a bit too much to me.

Alright, testing on LUA no black screen but usability is near zero. Start menu won't open and a mem leak msg when right-click systray app > Exit:




Note: I always use a black solid color as desktop background.

 

Is there an ETA for version 4? It kind of puts users in an awkward position knowing that they'll have to recreate their rules for the new version. So, our choices are, either stick with version 3 (which has it's flaws), wait for four, or move on to another product. That kinda puts us in limbo because we know version three is outdated, yet version four cannot be tested completely (especially on Win10).

 

What flaws? 3.1 works okay for me.

 

I disagree. Remember, 3.1 is beta, so that designation seems to mean very little in this case. 3.0 was officially released in 2014, three and a half years ago. There will be flaws just based on evolution of the OS, and the widening gap between that and outdated software. I don't think it unreasonable to want to know the direction the software in going, which is something we cannot yet tell from 4 beta because not all the protection modules have been added.