If you check property NativeClrObject.Name for AudioArchitect.wndCrownControls, i believe it has same value as AutioArchitect.CrownControls has. Obviously AutioArchitect.CrownControls can map more controls because it has looser constraints.
You should check value for WndCalss and WndCaption when it says AudioArchitect.wndCrownControls does not exist, to see which value is different.
If AutioArchitect.CrownControls and AudioArchitect.wndCrownControls are referening to same object in your tested applicaiton, i would suggest you remove one of them because we no need to maintain two copies of name mapping for same object.
Of couse you need to correct you name nampping by:
1. Use properties that do not change during running
2. Use wildcard in your mapping (e.g. WndClass=WindowsForms*)
3. Use conditional filter in your mapping (e.g. WndCaption=abc or WndCaption=def)
4. Use Required Children if controls that we can't tell apart contain different child controls
-Ocean