Maintaining a Stable Hardware Fingerprint in Bottles?

[snakeeyes021]

I'm attempting to get some Steinberg software running on Linux using Bottles, but as far as I can tell their activation manager application (which is necessary to run any of their software post-2022ish) relies on some sort of hardware fingerprinting. On actual hardware, it will for instance detect changes like swapping out a hard drive, RAM, or motherboard and refuse to retain old license activations and so forth; this could always be reverted by reconnecting the old hardware in its previous configuration, so the licenses weren't gone, just... hiding somewhere and only usable on the exact hardware configuration they were created under.

So the issue is that when running it through Bottles, the fingerprint seems to be inconsistent, leading to the aforementioned disappearing licenses. That said, I'm not fully sure of what questions I should be asking to get to the bottom of this, but I suppose I'd wonder things like: Is this intended behavior (or is it even known behavior)? Do we imagine it originates in Bottles or WINE? If Bottles, do we have any idea on why hardware might not appear to a program as consistent across runs or even just across time in general? Any ideas on what to look into? Any advice is appreciated! Many thanks!

[orowith2os]

This is probably a problem with Wine, but unless we know what (and how) it's fingerprinting from the machine, there's no way to know.