I am using Chrome and it shows that it is "managed by your organization". My suspicion is that some program (maybe FDM?) changes some "policy" in such a way, that Chrome thinks it is "managed by your organization".

So I uninstalled and re-installed Chrome after FDM was uninstalled, and noticed that the FDM extension still gets installed right after Chrome is installed!

Also, Chrome still says "managed by your organization".

How can I uninstall FDM in such a way, that it removes that Chrome behavior/policy? How can I get rid of the FDM extension remnants?

Mind you, I don't want to get rid of FDM altogether - I just want to find out what causes Chrome to think it is "managed by your organization" - and I suspect FDM is the culprit?

Hello,
FDM does not alter any Chrome files in any way. It never installs Chrome extension on its own. The only it can do is to open FDM's extension web page. But user has to install it manually. No automatic install process is involved.
I don't know what is happening in your case, I'm not a Chrome browser developer. You probably should ask on some Chrome-related forum instead.

Thank you for your reply!

The reason for Chromes' "managed by your organization" was not FDM, but an entry in the registry at "HKLM\SOFTWARE\Policies\Google\Chrome". Deleting these entries got rid of "managed by your organization".

As for "auto-installing" the FDM plugin right after a fresh install, I have given up. I tried everything, a thorough wipe after uninstalling both Chrome and FDM, to no avail. Google mentions a simple uninstall and re-install should fix the issue. It did not. This is how it looks btw right after a fresh Chrome install:

Screenshot:

https://ibb.co/gwRprHw

I think this is caused by the browser's synchronization process. E.g. some device tells Google servers that you have FDM extension installed. And that's why Chrome tries to automatically install it on a new device.

I am not sure the synchronization process is responsible for that, since right after a fresh install the Chrome profile is not yet associated with a Google user - neither is synchronization turned on by default.
It's puzzling to me what could cause this, however, I doubt it's anything that FDM does wrong, since I could not reproduce this behaviour on other machines.