New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Russian accont\group names #3
Comments
Hi, See also notes on pages 16 and 17 in the documentation. |
Sorry for getting to this so late - I wasn't getting notifications - hopefully I've got that straightened out. Dees7 does rmoreas' suggestion fix your issue? |
Hello. |
What does the output of this command look like by itself: AccessChk.exe /accepteula -nobanner -w -d -s c:\windows\tasks |
|
OK. Confirmed that it's a bug in AccessChk.exe that doesn't handle Unicode properly. Bug filed and hopefully resolved soon. Thanks for the alert. |
Does the "AaronLocker" rule generation still work correctly in spite of this bug? The design intent is to rely on SIDs and not have to depend on successful SID-to-name conversion. The bug here makes it harder for a human to review the results of the scans of the Windows and Program Files subdirectories, but it shouldn't otherwise block generation of correct rules. Is that what you're seeing? |
Hello. |
OK. Sysinternals team has fixing the Unicode issue in their backlog now. |
Hello.
I use Windows10 (ltsb) and if I generate reports I see "??" instead of groups
The text was updated successfully, but these errors were encountered: