I thought the problem was:
I have an installer that has 3 features, which can be installed depending on the serial key entered. When you enter a less-priviliged serial key, you get only 1 or 2 features instead of all 3. It's a bit more complex than that, but this will do for the explanation
To disable a feature so the user can't just enable it again in the Custom Install dialog, it needs to be removed from the Feature table (see also
this topic).
Now, I accidentally added a required merge module while I had feature 3 (the most priviliged one) selected. As a result, the application would fail or the merge module prevented the feature from being removed (I didn't test this thoroughly).
There were also some custom actions that referenced the feature 3 folder.
Now, if there was some kind of view that would allow me to see all components, features, actions, etc that have some relation with a specific feature, this would have been clear.
The actual problem turned out to be:

When removing an item from the feature table at run time, the installer will crash with a 2711 error when you try to set the install level. Apparently the installer will try to update all features that it thinks should be there, instead of just the features that are there.
I had a 32-bit installation button and a 64-bit installation button, which would both set the install level. After I removed the install levels and used automatic detection (AMD64) for the 32/64-bit choice, the 2711 error vanished and everything works again.
Concluding:
The feature I requested would be useful (I think), but it would not have solved my problem, except that it might have saved me the time I spent trying to find the items related to the feature I was trying to remove.
FOLLOW US
Get the latest news in Application Packaging