WMI System.Managment error Windows 22H2 last update

[ghost]

After installing the latest Windows updates, the miner and checker stopped working, using the builder version 3.4.1. The checker encounters a System.Managment access denied error. The miner connects to the proxy and immediately disconnects, although the installation is successful, everything worked properly before the update. There should be no problems with the firewall because I use TLS/SSL on port 443. Perhaps someone has already encountered this problem and there is a solution, here is a proxy config "http": { "enabled": false, "host": "127.0.0.1", "port": 0, "access-token": null, "restricted": true }, "background": false, "bind": [ { "host": "0.0.0.0", "port": 4444, "tls": true }, { "host": "::", "port": 4444, "tls": true } ], "colors": true, "title": true, "custom-diff": 0, "custom-diff-stats": false, "donate-level": 0, "log-file": null, "mode": "simple", "pools": [ { "algo": "rx/0", "coin": "XMR", "url": "", "user": "", "pass": "x", "rig-id": null, "keepalive": false, "enabled": true, "tls": true, "tls-fingerprint": null, "daemon": false } ], "retries": 2, "retry-pause": 1, "reuse-timeout": 0, "tls": { "enabled": true, "protocols": null, "cert": null, "cert_key": null, "ciphers": null, "ciphersuites": null, "dhparam": null Nicehash in the pool is not supported

[UnamSanctam]

It's possible that your Windows was corrupted by the Windows update, it's pretty common. Try opening a CMD with administrator privileges and run these commands: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth

After that run this command: winmgmt /verifyrepository If it reports any problem then run this command: winmgmt /salvagerepository

[ghost]

Thank you very much for the answer, I also followed these instructions and everything worked

WMI corrupt - how to reinstall/repair?

To resolve the issue, follow the steps in this section.
Try the following steps:

1. Disable and stop the WMI service.

sc config winmgmt start= disabled

net stop winmgmt

2. Run the following commands.

Winmgmt /salvagerepository C:\WINDOWS\System32\wbem

Winmgmt /resetrepository C:\WINDOWS\System32\wbem

3. Re-enable the WMI service and then reboot the server to see how it goes.

sc config winmgmt start= auto

If the problem remains, then try the following steps to rebuild the repository:

1. Disable and stop the WMI service.

sc config winmgmt start= disabled (note that there is a blank between '=' and 'disabled')

net stop winmgmt

2. Rename the repository folder (located at C:\WINDOWS\System32\wbem\repository) to repository.old.

3. Re-enable the WMI service.

sc config winmgmt start= auto

4. Reboot the server to see if the problem remains.

[UnamSanctam]

Great!