Bug #98280 Runtime Exception: Unable to execute command chcp

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\laris\AppData\Roaming\MySQL\Workbench\log\wb.log]

How to repeat:
I just installed MySQL workbench 6.1 on my win7 64 bit system. I successfully created and tested a MySQL connection. However, each time i open the SQL editor for this connection and select server status, I get the following errors:

(1) Runtime Exception: Unable to execute command chcp. Please make sure that C:\Windows\System32 directory is in your PATH environment variables

(2) Unhandled exception: current profile has no WMI enabled.

Thank you for the bug report. Please upgrade to version 8.0.21.

Hi Miguel,

My environment hit this problem. wb.log is here.

10:11:59 [ERR][SQL Editor Form]: Unable to create db_mgmt_SSHConnectionRef object
10:11:59 [ERR][wb_server_management.py:local_run_cmd_windows:400]: Exception executing local command: chcp.com: 'utf-8' codec can't decode byte 0x8c in position 0: invalid start byte
Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 8.0\modules\wb_server_management.py", line 397, in local_run_cmd_windows
    retcode = OSUtils.exec_command(command, output_handler)
  File "C:\Program Files\MySQL\MySQL Workbench 8.0\workbench\os_utils.py", line 353, in exec_command
    for line in iter(process.stdout.readline, ""):
  File "C:\Program Files\MySQL\MySQL Workbench 8.0\Python\Lib\codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8c in position 0: invalid start byte

After these procedure.
(1) Uninstall All mysql related items. (MySQL 8.0.22)
(2) Install MySQL 8.0.23 with Developer profile.

If you want to need more information, please let me know.

The root cause looks same for me.

https://bugs.mysql.com/bug.php?id=102300

Bug #105237 marked as duplicate of this one.

Bug #105233 marked as duplicate of this one.

Bug #112611 marked as duplicate of this one.

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.