Test Case 20: Verify application does not try to write to or replace any WRP registry keys or files (Req:2.9)
The application must not attempt to write to WRP Registry Keys or replace any system files during install/execution in order to pass this test case. You need to use AppVerifier with LuaPriv option checked. In the AppVerifier log you need to check for LayerName="LuaPriv" Severity="Error"
Question: The AppVerifier log file generated is too large to trace for error. How can I see the exact errors violating TC 20?
Answer: You can first filter out those with Severity="Error". However, not all these errors violate Windows Resource Protection (WRP). That is, all errors may not affect any protected locations (files/registry keys). The protected locations include Windows/System/Program Files locations and few Registry locations. You need to make sure that your application does not write/update the WRPs. You can confirm this from the file or registry location mentioned in the message in the AppVerifier log.
You can check whether a file or registry key is under WRP in either of the ways as follows.
Trusted Installer is a service that hosts code for install, update, and un-install of OS components. The service is trusted by the system to check for all the prerequisites such as package authenticity, signing authority and dependencies before making system changes
Resources:
About Windows Resource Protection
Windows Resource Protection on Windows Vista