attack_monitor
attack_monitor copied to clipboard
raw_decode raise JSONDecodeError(
Traceback (most recent call last):
File "madvr.py", line 254, in <module>
main()
File "madvr.py", line 166, in main
load_initial_exception_rules(cc, EXCEPTION_RULES)
File "madvr.py", line 67, in load_initial_exception_rules
rules = json.load(open(exception_path, 'r', encoding='utf8'))
File "C:\Users\Mehran\AppData\Local\Programs\Python\Python37-32\lib\json\__init__.py", line 296, in load
parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
File "C:\Users\Mehran\AppData\Local\Programs\Python\Python37-32\lib\json\__init__.py", line 348, in loads
return _default_decoder.decode(s)
File "C:\Users\Mehran\AppData\Local\Programs\Python\Python37-32\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Users\Mehran\AppData\Local\Programs\Python\Python37-32\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Having the same issue. Win10 1909 Python 3.8.0
how we can fully uninstall it?
After studying the installer script...it’s seems there is no automated way for complete uninstalling....unfortunately. Delete the related schedule task and remove the install folder.
Hi guys,
Solving problem guide: This problem can be solved by removing file FORCE_EMPTY_DIR from C:\Program Files\Attack Monitor\config\exceptions
like described in issue 1 - https://github.com/yarox24/attack_monitor/issues/1
Uninstall guide:
- Delete folder: C:\Program Files\Attack Monitor\
- Delete scheduled task: "Attack Monitor - Autostart"
- Remove sysmon by launching sysmon.exe -u
- PowerShell/ Windows event logs audit policy was changed - it needs to be undone manually
- WMI audit policy was changed it needs to be undone manually
Hi guys,
Solving problem guide: This problem can be solved by removing file FORCE_EMPTY_DIR from C:\Program Files\Attack Monitor\config\exceptions
like described in issue 1 - #1
Thx yarox24...you're right - I missed it. My fault - sorry. Removing the file solve the issue for me. Keep it running...
Any chance to keep the cmd-windows hidden after autostart?