New
#10
Hello cottonball, :)
TustedInstaller (Windows Modules Installer) is protected by default. If it's messed up, it'll usually take a repair install to fix.
Hello cottonball, :)
TustedInstaller (Windows Modules Installer) is protected by default. If it's messed up, it'll usually take a repair install to fix.
Thanks, Brink!
Will keep that in mind.
Trying a workaround, and see what happens:
Open Command Prompt (Admin) again.
Once at the Command Prompt, type:Press: Entercd c:\Windows\servicing
At c:\Windows\servicing> type in and Enter:Hopefully, this will start the executable in the background.TrustedInstaller.exe
Next, type in and Enter:You should no longer received the error message as before.sfc /scannow
It will also make you restart your computer if it finds anything wrong.
Now, press the Windows key and the R key at the same time.
Type in:At the System Configuration console, click on the Services tab.msconfig
If the list of Services is not in alphabetical order, double click the Services column.
Look for the Windows Module Installer, it should now be on the list.
If it is not started, right-click and select: Start
If still no joy, we may need to replace the TrustedInstaller.exe in C:\Window\Servicing, or do a repair install.
Here is a link to Black Viper’s Updated Service Configurations: http://www.blackviper.com/service-co...onfigurations/
Hi there
I can see on first images configuration of service as Matual Trigger Start. Howeber, I have only this ootion for Automatic services. What I do wrong?
Hello valtf, and welcome to Ten Forums. :)
Leaving it set to "Automatic" will be fine to let Windows automatically start and stop the service as needed.
What service is this for?