Error occuring when Updating Windows

[BriMac72]

I am occuring a strange error when I use Windows Update on a fresh installation of Windows 7 Pro. What happens is that when I install the first batch major updates. which is around 100 security and straight updates before Service Pack 1. I restart Windows to install them and during Stage 3 my computer restarts and then goes back and finishes the installation. Then when I get back into Windows I have a Error in Event Viewer with the ID of 7023 stating that Windows Modules Install had exited with error code %%16405. Windows Updater says that everything installed correctly and has no failed updates and doesn't show a error. Searching the internet has only given me a few hits and the one suggested installing SP1 before updating which I did and did not stop this problem.

I am wondering why this is occuring and is there anything I can do to try and prevent this and well if this a normal occurance.

 

[NoelDP]

Heh - I was going to point you at this thread - Repeatedly offer windows update Windows Modules Installer error - Microsoft Answers
- and then realised you were the OP there
The 16405 error appears to be undefined, so it's not going to be any help to us.
TrustedInstaller failing is a bit of an odd one - I suspect that it may be the result of a race condition. Is there any AV installed at this point? Any non-MS software?
What happens if you use a Clean Boot to do the update/install?

 

[BriMac72]

All I have said in that thread you linked is pretty much how it goes, but after said error nothing seems to be a problem with updating. I can go through the remainder of the updates without a single problem or error with or without AVs or other programs installed. As for a clean boot, I have not had anything installed other than the wireless drivers to get the updates so I do not know if it can help.

One thing does come to mind involving AVs is that I do download the Microsoft monthly malware remover during said updates and all updates after and sometimes before, if I decide to not manually check, do not have it and do not have problems.

As for that topic, well they changed the topic to the current title from "Windows Modules Installer error %%16405" and marked it as answered when clearly I am not so that is why I am here.

 

[NoelDP]

You always have the option to unmark it. - you do tend to find that if an MS techie gets involved, a thread that doesn't get any activity for a couple of days is tagged as Answered (by another MS techie, usually) by the techie. There have been many long discussions about the practice in the Feeback forum and eslewhere.
MSRT is usually the last update to run in WU, to prevent timeouts, as it does a scan of the system while it's 'installing' - although if there's a product also being installed which requires it (e.g. IE9) then it is shifted up the order, and may be quite near the top of the list.

So long as the error is a onetime thing, I don't honestly think there's much point in pursuing it - it may simply be that one of the updates has problem closing TrustedInstaller, and has to wait for a timeout - then WU starts the next instance up again as normal.

 

[BriMac72]

I usually don't install IE9 during the first update when the problem occurs, mainly because it has a wonderful prompt and I usually do something away from the computer for the hour or so that it takes to install. I should now try installing both or neither the next time I try, but that is going to be in 2-3 days since it is busy around here at Thanksgiving. One thing I will say is that the win32_exit_code stays around until I boot up Windows Update in Windows even, so it stays around even after the mid-update restart for whatever that is worth.

Lastly I tried to unmark the answer, but the problem is that I cannot unmark my reply to the answer so it just looks like a wash for that thread.

 

[NoelDP]

I have to be honest here - and say that I have NO IDEA what you're talking about!
Please rephrase ti - that way I may get a glimpse of teh problem you are seeing.

IE9 installs ALWAYS require user input - if that input is not forthcoming, then that is the cause of your timeout error.

 

[BriMac72]

Sorry about that, it was a rushed response since I though I had enough time to to type out something but I then got called away.

What I was trying to say was that I never installed IE9 during the first round of updates due to needing a user prompt because I leave my computer after starting the 100~ updates due to how long they take. Then I was going to say that the next time I try to install I will installing IE9 along with the Malware Removal Tool and if that doesn't work I will try installing neither to rule the Removal Tool as a source of the problem but that will be in a few days due to the holidays currently happening.

I then brought up a point that may or may not help you involving something from the Event ID 7023 article on Microsoft's site involving win32_exit_code and how the error state persists until I have logged into Windows and then bring up Windows Update, even after successfully completing the updates.

My last point was involving how you said that you can unflag a correct answer on Microsoft's Answers Forum and how I cannot due to my reply to the marked answer is now being shown as the answer.

Yet again sorry about the bad reply, but I have managed to secure a little time to type out a much better reply.

 

[NoelDP]

Makes more sense now.
You should be able to unmark any answer in your own thread.... no matter who it's from and who marked it as an answers (in this case another MS idiot techie who I've crossed swords with before, for bad answer-marking<g>)

I have to admit that i'm struggling to envision the exact problem that you're seeing, but if I remember right, IE 9 isn't usually offered in the first round of updates anyhow. at least in RTM Win7. (but I could be wrong)

Let me see...... On this machine it didn't actually get installed until after SP1 (the machine is is only 9 weeks old, but still only came with RTM), but I don't remember whether that was my choice or not.

I have 2 7023 errors on the first day - the second one had the same error, and was after a reboot (for updates) when the system changed the startup type for Windows Modules Installer from Auto to Demand. This appears to have been the effect of one of the updates, but I can't work out which one. (RTM was released with WMI defaulting to Auto start, SP1 with WMI set to Demand.... haven't found out which update made the change).

 

[BriMac72]

I would say it is debatibly good to hear that I am not alone with this error just for the fact that is not just two people that have had this possible problem.

What I will say with IE9 is that it used to be offered to me but I had to manually check it to get it installed on the first round of updates, then in the past 1-2 weeks it has become a checked inclusion in first round of updates.

 

[NoelDP]

I would be inclined to believe that it's in the category of "expected behaviour" - it's an update that changes a fundamental part of Windows in a significant way, and this may be the inevitable result.

I wasn't aware that IE9 was being 'pushed' in RTM yet - but I'm not surprised to hear it. MS tend to do things like that in stages - first offering it as an optional update, then as a Recommended one, then as an Important one, and staggering it aorund the world. This reduces strain on the servers and support staff when the inevitable calls come in.

 

[BriMac72]

First I want to say I haven't gotten around to testing IE9 and the Removal Tool because things managed to be more crazy than expected and getting everything back in order has taken much longer.

I have 2 7023 errors on the first day - the second one had the same error, and was after a reboot (for updates) when the system changed the startup type for Windows Modules Installer from Auto to Demand. This appears to have been the effect of one of the updates, but I can't work out which one. (RTM was released with WMI defaulting to Auto start, SP1 with WMI set to Demand.... haven't found out which update made the change).

I will say that it has to be something post-SP1 due to having installed SP1 before using Windows Update and it still occuring unless using the downloaded version from Microsoft's site does not change the Installer to Demand. However if the changing of the Installer's Statup option would it be possible to change it beforehand and stop the error from happening?

 

[NoelDP]

I will say that it has to be something post-SP1 due to having installed SP1 before using Windows Update and it still occuring unless using the downloaded version from Microsoft's site does not change the Installer to Demand. However if the changing of the Installer's Statup option would it be possible to change it beforehand and stop the error from happening?

Now I'm confused

 

[BriMac72]

Sorry for another hurried post

I was saying that the problem has to involve something past SP1 since I have tried installing SP1, with a manual version downloaded from Microsoft, before using Windows Update and still had this error. Then I bring up if manually changing Updater's Startup option before having the update apply it would make it so that there is not a error when updating.

 

[NoelDP]

Then I bring up if manually changing Updater's Startup option before having the update.....

Updater's Startup option??
You've lost me - unless you mean the automatic rebboot option in SP1?

 

[BriMac72]

Then I bring up if manually changing Updater's Startup option before having the update.....

Updater's Startup option??
You've lost me - unless you mean the automatic rebboot option in SP1?

I mean through MSconfig but seeing the confusion it has caused you I don't think it is possible, but I haven't really gone through MSConfig all that much since I have never had the need to.

However I am beginning to agree with you that this is expected behavior but I really wish there was a easier way to figure out which update is causing this. This is because I just did the the update with and without IE9 and Malware Removal tool with no change in the error.

 

[seavixen32]

If I can jump in rather late in the thread, you might want to consider installing the Windows Updates Readiness Tool.

Not sure what your internet speed is as it's a 315MB download so it make take a little time if you're on a slow connection.

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011] - Microsoft Download Center - Download Details

 

[BriMac72]

If I can jump in rather late in the thread, you might want to consider installing the Windows Updates Readiness Tool.

Not sure what your internet speed is as it's a 315MB download so it make take a little time if you're on a slow connection.

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011] - Microsoft Download Center - Download Details

I just tried it and there was no change with the error I am having, though it looked like a good shot a fixing it.

 

[seavixen32]

You could try and get some answers from Microsoft.

Support for Microsoft Update technical problems - troubleshooting

 

[BriMac72]

You could try and get some answers from Microsoft.

Support for Microsoft Update technical problems - troubleshooting

I'm going to try that and post back here when and if I get any answers.

Still though you guys have been very helpful and here is hoping for an answer to finally come out.