Hi everybody, this is a portableapp-forum, might be the perfect place to ask this:
I want to copy my (non portable) Supermium profile (all profiles in it and the default profile from %localappdata%) to an other machine, but discovered I'm forced to use chrome.exe --disable-machine-id on chrome (Supermium) 126 on the target-machine, if not all my extensions will be destroyed because Supermium recognizes it is running on an other machine. I changed the machine-id code in a config-file, but this didn't work as I remembered back. Even worse: When I use Supermium at the 132 release from win32ss' github, that --disable-machine-id flag won't work anymore and after some launches my extensions got destroyed.
Best regards,
Sven
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
This is by design. Chrome-based browsers lock their profile to a specific machine. As such, it's highly recommended you don't use them unless logging into Google. This applies to local and portable usage.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for your answer! And there is no way around this? So if I use the new supermium releases 132+ I can't just modify the "Local State" file and set a new machine id or somehow generate one that fits to my actual machine?
I don't know Supermium well enough to know what changes they've made to the code that could affect this. Perhaps someone more familiar could respond or you could try asking in their github.
Sometimes, the impossible can become possible, if you're awesome!
My thoughts were "I may ask here because here are more the guys around that know how to make apps portable" instead of asking in win32ss directly. But thanks anyway, will try it there