[BUG] - Agent wont install

[maix-me]

To Reproduce

Steps to reproduce the behavior:

I update server to v0.21.59.0 Release and need to reinstall agent, in 1 pc everithing ok. But on other 1 pc agent removed, but wont install. In powershell screen I don't have time to figure out if there's an error, and there are no logs in the temp folder after trying to install.

Client Info

Browser:
Language/Locale of Browser:

Agent Version: 0.21.59.0
Agent OS: win10
Language/Locale of Agent OS: RU

Server Info (if self-hosting)

Server OS: ubuntu 24.04
Language/Locale of Server OS: EN
Docker image tag: image: bitbound/controlr:latest

[mattish91]

I have noticed this too, it seams like some AV's are noticing the update download as malicious when it's saved to a system temp folder.

I had to add a exclusion in Kaspersky, Panda and Avast (tho i did uninstall Avast as that in it's self is malware in my opinion) and Yes, I know Kaspersky should be considered as malware or any other type of malicious software, but you can't deny it has been working great as the leader on the market until quite recently.

It would be great if these vendors could get some sort of attention of ControlR (i have tried with Kaspersky and Panda, no luck yet).
It seams thy are flagging Avalonia* dlls.

[bitbound]

FYI, installer logs are now written to C:\ProgramData\ControlR\{instance}\Logs\ControlR.Agent.Installer.

But yeah, I've seen this when Smart App Control is enabled:

In previous releases, some of the DLLs weren't getting signed.

In the next release, all binaries that are missing a valid signature will be signed with my commercial, including unsigned binaries from NuGet packages (like Avalonia DLLs).

Also, this will now include the DLLs that get bundled into the single-file EXEs for the agent and installer. These weren't getting signed previously.

So after this release, every binary should have a valid signature. Most of them will either be signed by Microsoft or myself.

[mattish91]

That's awesome to know, my setting for Smart App Control is currently set to "Evaluation" but that most likely is because i just re-installed my machine.

[maix-me]

I found a bug where I don't specify Device Tags in the Deploy settings.

If enabled, the device will be assigned the selected tags upon installation. Tags are used to link devices to users for access control.

Add device tags

Then the installation fails, even though the key is optional. That's strange.
I'd like to assign the tag after installation.

[mattish91]

Did you set that tag for that installation ID?

I would suggest to create a new installation key without selecting a tag, and try again. You can then manage tags afterwards (that's what i do at all times).