offtopic
The discussion of which rights a user should have versus AD maturity can be extended for a long time

So a little example of my approach with crap software that needed admin rights to function properly:
The software package i have here running needs admin rights because the software updates itself when the application manager puts the update files in a certain directory, this happens monthly.
With Windows 7 this automatic updating was not possible since a normal user cant write files in the program files directory, FINALLY, without admin rights.
I solved this issue like this:
i created a global group and a domain local group in AD. I put the users that use the program in the global group, made the global member of the domain local group.
On the specific stations i added the domain local group to the ACL of the directory and gave it WRITE/CHANGE rights.
My problem was solved without giving users admin rights.
Basicly the software that is for regular users, should never need to run with admin rights. Its from the past (xp and before) that this behavior is incorporated in the software and the lazyness of the devellopment party to comply to OS regulations.
On the other side its the unwillingness of the buyer party to demand OS compliancy in the software since the bill probably goes to the demanding party.
Maybe its wise to investigate why the software needs to have admin rights and possibly solve it like the way i did with my package.
ontopic
The password protection of uninstalling AVAST is however still wanted, if a system gets corrupted then there is already something running with elevated rights, meaning the AV product can be silently uninstalled too.
The protection was present in the v6 version too so it is possible to incorporate that code into the v7 version too.
WISHED