mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1618] Incorrect display Russian text in command output #2955
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2955
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @crackco00n on GitHub (Aug 30, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1618
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
When I send a command to WEBUI or execute a script, I get incorrect content display. (Usernames and group names)
A similar issue has been #1472
But I have everything else displayed correctly, except for the listed.
To Reproduce
Steps to reproduce the behavior:
Get-LocalGroupExpected behavior
Correct display of command output in any language.
Screenshots

Additional context
The standard output of scripts has the same incorrect display of the Russian language.
@vsychov commented on GitHub (Dec 13, 2023):
The problem arises due to the Windows code page; the TacticalRMM agent removes all non-UTF-8 symbols (
github.com/amidaware/rmmagent@f0736faf4b/agent/utils.go (L225)). To fix this issue, you can try the following PowerShell script and then restart your PC:@P6g9YHK6 commented on GitHub (Oct 28, 2024):
this worked
@P6g9YHK6 commented on GitHub (Nov 4, 2024):
ok this was a bad idea it broke so many other things XD
@P6g9YHK6 commented on GitHub (May 22, 2025):
working solution in
https://github.com/amidaware/community-scripts/pull/287
UTF8 on it's own is not enough
powershell 7 same
but both fixes the issue.