Hi All, Barring any last minute QA issues, we expect to begin a beta for our 64 bit Win7 AppGuard next week (Wednesday). The beta will also include 32 bit Win7 because of a new feature called MemoryGuard found in AppGuard for 32 bit Win Vista, 32 bit Win 7, and 64 bit Win 7. It may never support WinXP (we're researching it though). MemoryGuard is NOT a 'memory firewall' like that of Comodo or others. It doesn't seek to improve upon what ASLR, DEP, SEPx, etc do. Instead, it prevent code injection attacks by one process on another process. Also in the beta, one can customize AppGuard policies such that one can add an exception rule that allows a guarded application to write to a specific file, whereas before this one could only define a directory. We expect to release the new AppGuard at the end of this month, which will be version 2.0.x. One of the features that will be included in the release but not in next week's beta will be the long awaited parental controls. We'd like your feedback such that we might improve/tweak it before the concrete dries. Also to be in the release, but NOT in the beta: - New AppGuard Version Alert - MBRguard Integration - Ignore specific AppGuard blocks ('right-click on a log event, click ignore') Parental Controls Description: There is no password that locks AppGuard policies. We wish to avoid issues associated with lost passwords. Instead, our approach leverages the existing Windows user account credentials on a PC. So, "family" computers must have at least two Windows user accounts to utilize our parental controls, which SHOULD always be so, though it isn't. Folks new to having a separate local admin account should make certain their password is never lost as consequences can be disastrous (a public service announcement!). Until a user clicks on the AppGuard 'Advanced' button and activates the 'Parental Controls', no user is restricted in what may be done via AppGuard. Once 'parental controls' are activated, one must enter "super user mode" to edit parental controls. The Windows account used to first activate parental controls is endowed with "super user mode" privileges. AppGuard associates those that may run "super user mode" with Windows user accounts, which are not required to have Windows local admin rights. To enter "super user mode", one must click on the AppGuard "Advanced" button, answer the Windows authentication challenge (does not involve logging in or out of a Windows account), and then the parental controls dialog is displayed. Parental control is a variant of our TamperGuard technology. Only a Windows account with local admin rights and with "super user mode" enabled may uninstall AppGuard. If AppGuard detects that there are no longer any "super user" accounts, the uninstall feature as well as parental controls in general would be disabled. A user that has simply logged into a Windows account with the "super user mode" privilege has not enabled this mode. One has to click on a button in the AppGuard GUI, which initiates a Windows authentication challenge prompt, "super user mode" is activated, and then one may edit parental controls, allowing one to: - Enable, disable, and edit parental controls - Uninstall AppGuard - Designated specific Windows accounts as having "super user mode" privileges Thus, from an AppGuard parental controls perspective, there are two types of AppGuard users (or Windows user accounts), those with and those without the "super user mode" privilege. Windows accounts with the "super user mode" privilege are in no way restricted by parental controls; other Windows accounts are. If someone without "super user mode" privileges needs assistance from someone with the privileges to temporarily remove an obstacle, that person with the privileges does not have to log out of that person's account and into their own. Instead, that person simply navigates to AppGuard, clicks on the 'Advanced' button, gets an authentication challenge, and then has "super user mode" enabled. When no longer needed, return there and log out of there (not the Windows account) to return things to normal. Cheers, Eirik PS I may be a little slow in responding to questions this afternoon/evening as I will shortly be reliant on unknown Wi-Fi. I'll be online off and on all weekend.