COM component registered outside this install
What it means
Tables run from this folder actually load a different copy of this component than the one sitting right next to them.
Why it happens
This isn't necessarily a problem — it's typical of a deliberate multi-install setup, several VPX folders on the same machine, where only one install's copy of the component was ever registered.
How Pincab Toolbox detects it
The component's registered path exists but points outside this install's root, even though this install also has its own local copy.
What to do
A component is registered in Windows, but points at a copy OUTSIDE this install. Your tables will load that other copy, not this folder's. It works, but you are not editing what you think you are editing.
- This almost always comes from an older Visual Pinball install still on the machine.
- The path actually in use is given in the Pincab Toolbox scan result. Open it in Explorer to see which install it belongs to.
- If that other install is no longer useful: rename its folder by adding "_inactive" at the end, rather than deleting it.
- Then, from the install you actually want to use, run the component's registration tool as administrator. That is what points Windows at the right copy.
- Run a new scan: the line should disappear.
- As long as you change nothing, just remember your settings must be made in the OTHER folder, not this one.
Check your own pincab
Pincab Toolbox is a free Windows scanner for Visual Pinball X and PinUP Popper. It finds and explains problems like this one. No account, no telemetry.
Download for freeCovered: Visual Pinball X (10.x) and PinUP Popper. Not covered: Future Pinball, Pinball FX, Visual Pinball 9 and the other frontends (PinballX, PinballY).