Error 1611: -1073741502

[Graceyin39]

Hi,

I got error 1611: -1073741502 Failure when installing updates. In the BatchPatchError I got the message below.

> -100: CoCreateInstance failed to return an IUpdateSession interface pointer

> CoCreateInstance failed to return an IUpdateCollection interface pointer. HRESULT: -2147221008

BatchPatch server can access BatchPatch folder on the target computer, however I didn’t see “BatchPatchTempAvailableUpdates” or “BatchPatchTempResult.log”file in it.

Please help!

Thanks,

[doug]

What OS is on the target computer? Has the computer not been updated in a very long time?

0xC0000142 -1073741502 STATUS_DLL_INIT_FAILED

These are not really BatchPatch errors, but rather they are errors that indicate that the target computer operating system might have some deeper issues. I would suggest you try the following things:

1. Make sure the target computer has the latest Windows Update Agent (WUA):

https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-version

2. If that does not solve the problem (there is a good chance that it will not) then I would suggest running the Windows Update troubleshooter:

https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

3. If that does not solve the problem (there is a good chance that it will not) then I would suggest looking at repairing the operating system and/or using the system file checker and/or other system fixit utilities to try to repair problems with the operating system.

[Graceyin39]

Hi Doug,

Thank you for your reply. It is Windows 2008 R2 server. This server has been updated last month and it was successful.

Thanks,

[doug]

If the server was updated last month with BatchPatch but now this month it’s failing with the error you mentioned above, then I would be concerned about the state of that server. BatchPatch has not changed, but clearly something has become either corrupt or broken on the target server, and there is a pretty good chance that the problems with that server are not going to be just limited to Windows Update. Maybe you’ll get lucky and a simple reboot will fix the issue. However, assuming that does not work then I would suggest you follow the recommendations I made in my previous posting to you.

Thanks,

Doug

[Author]

Posts