Unable to uninstall meshagent on windows 8.1

[KonVei82]

Everything was working great until we decided to change our domain, as a result we had to issue new agents for all the PC since all the agents were pointing to the old domain.

The issue is that we are unable to uninstall meshagents on a 8.1x64 PC, we are getting a very odd error:

[2023-08-07 09:20:14 AM] [AD262CB981431433] ..\microstack\ILibParsers.c:2776 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00007ff648230a4d / BaseAddr: 0x00007ff648270160 / Delta: 259859]

The message repeats itself each time we try to uninstall the agent, we tried uninstalling via the windows add/remove programs and are getting same issue.

We tried updating to agent via the the Update option on the new client but it doesnt make any difference.

UPDATE:

Just some additional info, tried to uninstall same agent on a different Windows 8.1 x64 and got exactly the same issue, it is a completely different machine.

Same agent on a windows 10 x64 is uninstalling perfectly fine.

There must be something with the uninstall script and Windows 8.1 x64 that does not work.

Let me know if u need more details.

Thanx in adavance.

[tomsik-radek]

Have you tried uninstalling it with CLI? Some dependency that Windows 8 ships with might be broken in MC.

meshagent64.exe -uninstall

[KonVei82]

I did and it didnt help, but i figured out the issue, i have firewall disabled on both machines due to them running a separate application firewall that requires u to disable the windows firewall.

My guess is that mesh agent is trying to locate windows firewall entries during uninstall and when fails to do so cannot proceed, i fixed my issue by editing the config file of the mesh agent on each pc and change the domain address and thus have everything working, i cannot enable the windows firewall to test my theory since that would instantly cause a conflict.

[tomsik-radek]

Huh, now that is an interesting issue. I guess there is nothing else you can do then, apart from enabling FW temporarily and uninstalling it. Or yeah, renaming the agent service name, I guess that is a workaround