I’m not sure whether this should have been posted in the General section, since it involves an apparent compatibility problem with another app. If I guessed wrong, mea culpa, please feel free to move it.
When I’m defragging, or just checking fragmentation status, I like to use Puran since it permits boot-time defrag which will clean up the page file and registry hives if necessary, possibly also the MBT.
Unfortunately, every time I start Puran, avast immediately immediately kicks out an HIPS warning because of Puran’s changes to “critical startup functions”, which is understandable considering the auto-reboots required. Is there a setting somewhere in avast which would allow me to “permit-and-remember”, rather than having to freshly approve it each time? Thanks.
What version of Puran do you have ?
Mine is 7.7 and is the latest and so far I haven’t experienced any issues with it. Though I haven’t done a boot-time defrag since the start of this month (first Sunday of the month) on both win 7 and XP Pro.
@DavidR - I’ve got Puran 7.7, same as you, and think it’s been ages since it was last updated. I’d only encountered this the last week or two, which is why I suspected any changes would have been in avast.
@Rednose - I found that my HIPS sensitivity was set to max. (3 bars) – while I don’t specifically remember changing it from the default, which you say is one bar, it’s consistent with most of my sensitivity settings being as high as possible. Resetting it back to minimum and rebooting eliminated the conflict with Puran, many thanks.
(edit, after-thought) One of these days I’ll have to see if two bars, as a compromise, would work.
Given what is said in the first post I suspect it is getting hit before the boot-time scan (reboot is even initiated) runs.
Unfortunately, every time I start Puran, avast immediately immediately kicks out an HIPS warning because of Puran's changes to "critical startup functions", which is understandable considering the auto-reboots required.
Update, finally tried the intermediate (2-bar) HIPS sensitivity setting. On my system, at least, that still permits Puran to work normally while presumably giving more protection against other behavioral problems than the one-bar setting does. So obviously that’s now my preferred setting.
David, you’re correct in that I was getting the HIPS warning about Puran immediately upon opening the latter, regardless of whether or not I then selected any of its boot-time options. I suspect Puran inherently has access to editing the bootexec while it’s running, which is why avast was complaining … if you do select boot-time disk check and defrag, that would seem to require no less than 3 changes to the bootexec setup, to generate the sequence reboot > chkdsk > reboot > defrag > normal reboot (or shutdown as the last step, if you prefer).
