Error in Hyper-V 2019 - C:\Windows\System32\ru-RU\sconfig.vbs (1213, 5) (null): 0x80041013

Question

Hello everyone. I ran into a problem. Windows Admin Center has stopped functioning, errors start pouring in when logging in to the server:

(1) RemoteException: The "DNSHostName" property for this object cannot be found. Make sure it exists. (2) RemoteException: The "Name" property for this object cannot be found. Make sure it exists. (3) RemoteException: Exception when calling "GetHostEntry" with "1" arguments: "The value cannot be undefined. Parameter name: address" (4) RemoteException: The "AddressList" property for this object cannot be found. Make sure it exists. (5) RemoteException: The "HostName" property for this object cannot be found. Make sure it exists. (6) RemoteException: Provider loading failed (7) RemoteException: Provider loading failed (8) RemoteException: The "SystemFamily" property for this object cannot be found. Make sure it exists. (9) RemoteException: The "SystemSKUNumber" property for this object cannot be found. Make sure it exists. (10) RemoteException: The "Fqdn" property for this object cannot be found. Make sure it exists.

and there are not many points as it was before.and on the hypervisor itself, writes an error in the terminal C:\Windows\System32\ru-RU\sconfig.vbs (1213, 5) (null): 0x80041013

tell me what can be done?
DISM /online and sfc tried, finds nothing.

Answer 1

Hello,

When DISM or SFC doesn't work, there are two other options for the error 0x80041013:

-Reintall the feature on the affected machine:
1- DISM /Online /Disable-Feature /FeatureName:MicrosoftWindowsPowerShell

2- DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShell

3- reboot the server

4- running again sconfig

WMI Provider issues:

• Repair the WMI repository on the affected machine:

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.

Hope this helps with your query,
--If the reply is helpful, please Upvote and Accept as answer--