I have no idea what to issue is, but it is unlikely to be Thunderbird. Even though closing Thunderbird is changing the issue.

I suggest you run a virus scan on your computer with something other than MSE.

MBAM: No problems Kaspersky: No problems

Consider: 'This' is Thunderbird running or having been running and 'That' is MSE failing to complete an update.

Prior to 'This' being loaded there was no problem. Immediately after 'This' the problem showed up. Indeed, EVERY time 'This' happens, 'That' is true. Conversely, when 'This' does NOT happen, 'That' does NOT happen.

Not only does the situation make it likely that 'This' is a problem, it makes it so highly likely as to approach 'This' certainly being a problem.

There being 'no idea' of what the problem is makes the problem no less evident and no less true.

I see your point, but I disagree. The automatic response is to go "yep found the cause". but personally I think you will find the cause is MSE scanning files in the Thunderbird profile as they are constantly being update while the program is open.

It is hanging the update because it is busy. Closing Thunderbird stops the update and so the scanning stops.

Try creating an exclusion for the imapmail and mail folder in your Thunderbird profile.

Not sure where that is? Go to the help menu, click on Troubleshooting information and click the show profile button.

Thank you for your reply.

I do understand the observation of the obvious tends to make one stop looking..and may well have nothing to do with the problem.

It may be helpful to better explain the situation. Closing TB does NOT change the fact that the MSE update fails.

The MSE update fails if TB is running or HAD been running. With TB open and the MSE update failing, closing TB does not change the MSE fail result. The MSE update still fails.

While MSE does indeed report 'network connection failed', that may be misleading. The update does take place, at least as far as server contact and data download. I can see that happening on my router. MSE changes to '..installing...' for a bit, then attempts to reload the update. Again, based on router activity and what MSE says it is doing. It is after the second attempt at the update that MSE complains.. and the error I noted is displayed on the screen. The connection failed in that the process did not complete..but a connection IS made and data is transferred.

That the MSE update fails to complete may be handily reported as a 'network connection' problem, while the connection TO the network has nothing to do with the problem.

I will try the exclusion you mention. TB is set up for a POP server, btw, not imap.

Thanks again for your time. I do appreciate it.

Another possibility is that Thunderbird installs DLLs of a differing version than MSE update requires. They would only be installed if Thunderbird was running.

Try the following.

Reinstall Thunderbird. Do a full install of MSE so the latest DLLs in the system folder are the ones MSE likes. What should happen is both programs install their shared DLLs side by side. What may be happening is neither of them are. (in the days of windows XP is was called DLL hell.)

The question has become moot.

MSE will not install. I've been through the usual clean-ups, service stops, and associated error fixes that are problematic with MSE.

No dice.

I should have left the sleeping dog lie...something I knew before I started this process. I prefer that things work as they should as opposed to half fast. Given that preference and the fact that Microsoft still exists presents a mutual dichotomy that will never be resolved.

Thank you for your input.