Trophies and Medals qazw125825 1 Posted July 27, 2020 Posted July 27, 2020 Hello, I have a problem. I can't play today. "V5 runtime error an error occurred. Could not connect to cimv2 WMI" appears namespace:0x80070422 "Please help, thank you Share this post Link to post Share on other sites
Administrator Trophies and Medals Faceless 4,131 Posted July 27, 2020 Posted July 27, 2020 Please try the following steps after opening CMD as administrator: 1. Disable and stop the WMI service. sc config winmgmt start= disabled net stop winmgmt 2. Run the following commands. Winmgmt /salvagerepository %windir%\System32\wbem Winmgmt /resetrepository %windir%\System32\wbem 4. Re-enable the WMI service and then reboot the PC 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 %windir%\System32\wbem\repository) to repository.old. 3. Re-enable the WMI service. sc config winmgmt start= auto 4. Reboot the PC to see if the problem remains. Share this post Link to post Share on other sites
Trophies and Medals qazw125825 1 Posted July 28, 2020 Posted July 28, 2020 17 hours ago, 𝐅𝐚𝐜𝐞𝐥𝐞𝐬𝐬 said: Please try the following steps after opening CMD as administrator: 1. Disable and stop the WMI service. sc config winmgmt start= disabled net stop winmgmt 2. Run the following commands. Winmgmt /salvagerepository %windir%\System32\wbem Winmgmt /resetrepository %windir%\System32\wbem 4. Re-enable the WMI service and then reboot the PC 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 %windir%\System32\wbem\repository) to repository.old. 3. Re-enable the WMI service. sc config winmgmt start= auto 4. Reboot the PC to see if the problem remains. Thank you. The problem is solved 1 Share this post Link to post Share on other sites
Recommended Posts