In a custom installation mode a have a feature with two subfeatures. They are not self-excluding!
What I tried to do is checking for a certain registry key in a custom action function and use the function
MsiSetFeatureState(hMSI, "Feature\\SubFeat1", INSTALLSTATE_ABSENT);
when the registry entry doesn't exist. The function is fired up when the user selects "Custom Installation" and hits Next.
This approach works fine on a parent feature, but it seems not to work on a subfeature...

Any ideas?
Thanks in advance