Windows Module Installer Error 1450 (Insufficient Resources)

[stingreddog]

Hi everyone,

I'm having a bit of an issue that just came up out of the blue. First, my system specs:
http://imgur.com/a/JsBAw

One day, Windows Update just stopped working. I received an error message like this:
http://imgur.com/a/aAiJQ

After digging through Google, I find that it has something to do with Windows Module Installer (TrustedInstaller). I run services.msc and find it in the list. But when I tried to start it, it gave me this error 1405:
http://imgur.com/a/tIj0X

I then research this error and there is very little that helped me. There was one solution that came up multiple times that helped some but not others:
http://imgur.com/a/tjH0X

I tried this (note the example is missing a couple "f"'s for the hex but using the decimal format is correct) and I still could not get WMI to run nor does SFC /scannow:
http://imgur.com/a/Rv0gq

So basically, I don't know what to do at this point. Without WMI being able to start - Windows Update just doesn't work. Anyone else run into this problem have solutions I can try?

Many thanks!

 

[SkyNetRising]

You updated BIOS on 2017.03.06.
And Windows update after that on 2017.03.21 was unsuccessful.
Coincidence?

BTW your system time is 2017.05.14. BIOS battery probably dead.

 

[stingreddog]

It could possible be it. There has been no reports of this happening on the ASUS forums with this particular update. Also, I was getting successful updates after that anyway. Just as time went on, the updates starting hanging/failing more and more. You can see here https://imgur.com/a/j0f44 that my last successful update was back in August/September.

However, since then I have 8 Important updates that will just hang https://imgur.com/a/bzgDl . They will never download, just sit there for hours. I still can't get sfc /scannow to start nor can I get Windows Module Installer to start.

Oh and the BIOS time is that date because that's when I took the screenshot. I check my BIOS time and it is current.

If anyone else has fixed this on their end, I would appreciate the help!