How to make sure anchor location is not disabled in trusted configuration

Windows stores anchors in two locations - Track0 and the registry. The purpose of having two locations is so that anchors are redundant. The idea is that if one anchor location's SN becomes invalid or removed, it can be transparently restored by copying the SN from the other anchor location. This is why Flexera recommends as a best practice that neither anchor location be disabled in trusted configuration.

Running health-check gives the complete status of Anchors and Binding elements in the event logs.
For Ex:
appcomptranutil.exe -healthcheck

Running health-check gives the complete status of Anchors in the event-log without activation.
If Anchor failure happens for any reason, corresponding error-codes(can be found in /machind/activation/include/FlxActSystemError.h) are logged in the event logs.

For Ex:

#define LM_TSSE_CHECK_ANCHOR_WRITE 11105 /* Health Check: anchor write error */
#define LM_TSSE_CHECK_ANCHOR_READ 11106 /* Health Check: anchor read error */
#define LM_TSSE_CHECK_ANCHOR_DATA 11107 /* Health Check: anchor data incorrect */
#define LM_TSSE_CHECK_ANCHOR_REMOVE 11108 /* Health Check: anchor remove error */

Output Difference between a disabled  and a working setup

Sample health-check output of not working Anchor:

16:00:44 27-05-2019  [P:404],[T:6456],[V:11.16.2.1 build 245043] 	EventCode: 2000001f, Message: Anchor 1-0x805ecd00 Read fail
16:00:44 27-05-2019  [P:404],[T:6456],[V:11.16.2.1 build 245043] 	EventCode: 1000000d, Message: Anchor 1 not available

Sample health-check output of working Anchor:

12:59:24 19-06-2019  [P:20108],[T:13356],[V:11.16.4.0 build 0]     EventCode: 40000016, Message: #2 Anchoring health check start
12:59:24 19-06-2019  [P:20108],[T:13356],[V:11.16.4.0 build 0]     EventCode: 40000016, Message: #2  Anchor type 2
12:59:24 19-06-2019  [P:20108],[T:13356],[V:11.16.4.0 build 0]     EventCode: 40000016, Message: #2  Anchor type 1