Quite often, users of Windows systems are faced with the problem that when they try to automatically install updates, the system gives a warning about the Windows Script Host service failure (error). How to fix it will now be considered. To do this, you can use several basic methods.
What does Windows Script Host crash mean?
As for the nature of the failure itself and the appearance of errors, the reason can only be that the system either does not find updates or installs them incorrectly.
For example, in case of communication failure, a huge number of messages with a variety of codes can appear. Of all the possible situations, the most common failures are 80070002 and 800A0046 Windows Script Host (error). How to fix this situation?
You will have to use your knowledge of manual management of services. In particular, we are interested in the update system itself.
Windows Script Host. Error. How to fix (code 80070002)
In the simplest case, you need to use the administration section where the services menu is selected (the easiest way to start the services editor is through the Run console, where the services.msc command is written).
Here you need to find the service of the update center and in the right-click menu use the line to stop the process. But to eliminate the failure, this is not all the actions, because the Windows Script Host corruption message (error) may again appear. How to fix the situation?
Next, go to the root directory of the system and find the SoftwareDistribution directory there. It has a Downloads folder, from which you just need to delete all the content. After that, we return to the services section and restart the update client.
Next, we go directly to the "Update Center" and start a manual search for updates. When they are found, they should simply be installed (a system reboot may be required).
Windows Script Host. Error. How to fix (code 800A0046)?
There is another unpleasant situation. Another type of Windows Script Host failure is possible (error). How to fix problems when issuing the above code? First you need to understand the nature of the problem.
It is believed that in this case, the user observes a failure of the system security descriptor. In the simplest case, you just need to delete the account that causes the failure (this uses the group membership section).
However, it is better to use the security policy editor (secpol.msc command in the Run menu). Here you need to use the security policy node, after which, with the choice of the user rights section, set the impersonation of the client after authentication. Then, add the user or group on the local security settings tab to the appropriate list, save the changes and restart the computer.
Finally, you can use the RPC client. To do this, use the same section of services, where a line with an indication of RPC is selected, after which an input with a system account is set in the properties. Again, after saving the changes, a complete reboot of the system follows.
Instead of a total
The error in itself is not critical and can be eliminated quite simply. In some cases, even such a simple option as viewing and manually deleting updates can help (some of them can actually cause system crashes). This is done from the same "Update Center". In extreme cases, if the user knows exactly when the error occurred, you can even use the usual system recovery, only when choosing points you need to display all of them, and then roll back to the specified state. But the above methods work.
Naturally, if the simplest solutions do not give the proper result, it is better to use exactly what was presented. Of course, you’ll have to dig a bit, but a one hundred percent error correction in this case is guaranteed.