Win 10 – Bad Image messages

[rockonbazza]

Hi,

In the last couple of days I have been getting a couple of messages popping up, and not sure why. The latest ones say:

“jusched.exe – bad image, C:\Windows\System 32\ntasn1.dll  is either not designed to run on windows, or it contains an error, etc etc.”

and also when launching Windows Live Mail I get “wlmail.exe – Bad Image” with the same DLL file as listed above (ntasn1.dll)

Win Live Mail opens, but until I close the “bad image” window it wont receive any emails. When I do receive them and open the emails some of them wont show any pictures/images, whilst some others do.

Can anyone help? Thanks

 

 

[Dave Rice]

Are you running McAfee antivirus?

I remember this from work a few years ago. McAfee got snippy about some apps that hadn’t been updated for a while.

[rockonbazza]

Hi Dave,

Nope, using Avast antivirus and have been for years with no issues.

[Dave Rice]

It could well still be Avast.

Something is intervening and looking at these files as they execute and that’s exactly what antivirus does.

Have a look in Avast’s logs and the Windows System logs in Event Viewer.

Whatever it is will have left a trail.

[Wheels-Of-Fire]

Must admit I havent seen this one before but I did a bit of digging and found a couple of things. jusched.exe is the Java updater and its trying to call home using a secure connection but failing. From what i read it’s because of a problem with the Microsoft SSL/TLS secure channel library in windows. Several people have said running sfc /scannow from a comnand prompt fixes it.

[Dave Rice]

You’ll find a ton of conflicting posts on the internet, most of which revolve around virus activity, which this isn’t.

IIRC whatever is causing the error message, and it isn’t justsched, believes the security certificate (or something similar, I forget the exact term) is way out of date and starts objecting.

So scannow could well fix the issue by updating the exe file that is being objected to. It won’t fix whatever is doing the objecting.

The problem we had is that it’s quite common in the Corporate world to be unable to update even seemingly mundane apps like Adobe Reader because another bit of (usually bespoke) software needs a certain version. Adobe update Reader and change the way things work. Company Z won’t upgrade the bespoke software until someone pays them to. Result is areas of the business on different versions of software.

That’s why I’m suggesting looking at the logs, which no-one ever does, to see if the reason is actually written down rather than guessing.

[Wheels-Of-Fire]

Your quite right Dave

There is a load of rubbish about this on the internet and lots of it is on the Microsoft forums like technet !

I picked the answer I did because it sounds plausable and others were having the same problem with Live Mail too which SFC fixed for them.

Speaking of logs your right again.

I always look at obvious one’s when i’m stumped. I almost never get much out of Windows system logs though. It could be because I was spoilt at my last company who paid for a log search filter program that I could point at any log dump and get what I wanted. I Still have a look anyway though.

[Dave Rice]

I know what you mean about logs, but if you have a look immediately after it’s happened (or know the exact time of the last one) it’s easier. Also you’re looking for anything involving a specific filename.

The thing to do is not get distracted by the red and yellow alerts which you think are show stoppers but are usually just time outs of no consequence. It’s what the scammers do to scare the sh1t out of their victims.

I’m recalling a bit more about it now. It started happening when the customer wanted the McAfee reporting paranoia level increased and these non problems (they weren’t really false positives because they did meet the criteria) started being flagged up by pop ups on the customers screen.

The pain of dealing with it was out weighed by the increased security, but I’m convinced that’s only because us out sourcers were dealing with the issue not the retained security staff (who never had to talk to an end user).

[rockonbazza]

Hi, Thanks for replies. I am running sfc /scannow as we speak. I did look at windows events log, but wasnt sure what I should be looking for ! I noticed that SKYPE is not working now, “Sorry, we couldnt connect to Skype” message. Tried to install it again and that  bl**** .dll message appears again, so it looks like it is preventing SKYPE working too.

 

 

[rockonbazza]

Ran Scannow – at the end it sayd “Windows Resource Protection could not perform the requested operation” ! Last update on it was 81 % complete

 

 

[rockonbazza]

So, Scannow didnt work, as per my update above. Did a system restore from restore point at the end of January, issue still there. Did virus and malware scan, nothing found. Guess I will have to trawl through the numerous websites and links that I found regarding this .DLL problem and try to find one solution. Its not a major problem (link up on Skype with son upstairs when playing MMO, so will have to resort to typing on the in-game party chat). Pops for emails, but I can get into the emails once I spend 2 minutes repeatedly clicking the “close box” icon for the .dll error message. I wonder if a windows update might solve it, but I thought Win 10 does them automatically. Anyway, if you think of anything else guys, let me know. Thanks.

[Wheels-Of-Fire]

Hmm

Seeing as Skype won’t work either im still leaning towards an SSL (secure sockets layer) problem. Looks like when a program tries to open a secure channel it can’t because of a Windows problem. ntasn1.dll is part of Windows internal error handling system amongst other things.

Its a shame that SFC (system file scan) didn’t complete first time and it may be worth running it again but if it still fails please let me know what version of windows your running.

 

[Wheels-Of-Fire]

Oops looks like our posts crossed in the post. So its W10 then.

[Richard]

I am not sure that it is relevant in this case, but sometimes you have to run SFC several times and even do so in safe mode when fewer drivers have been loaded. It was a while back when I last did that, so I cannot now remember why it was needed. It can be that SFC does a partial job then hits a problem but that when it reruns it can access the reloaded/corrected version and bypass the obstruction.

I would try it in safe mode and see if you can make more progress.

[It has been a trying afternoon one PC has downloaded the software removal tool a dozen times and keeps wanting to repeat and another one refused to complete its back up. CHKDSK has now allowed some progress on that issue, that is progress not yet completion. Arghhhh]

Richard

[Dave Rice]

I suspect it’s time for a Windows reset.

[Wheels-Of-Fire]

Seeing as its W10 you may like to try an upgrade repair. Look at this linkHow to: perform a repair upgrade using the Windows 10 ISO file – Microsoft Community

https://answers.microsoft.com/en-us/insider/wiki/insider_wintp-insider_install/how-to-perform-a-repair-upgrade-using-the-windows/35160fbe-9352-4e70-9887-f40096ec3085.

 

[Dave Rice]

I wonder if that will still work.

The article is nearly 2 years old and refers to the technical preview.

W10 has changed a lot since then, the Anniversary Edition is more like Windows 11. For instance going back to the Corporate world it changes the way you deal with roaming profiles, it’s that different.

[Ed P]

Thanks Graham a useful tip. My wife’s PC keeps behaving very badly (An Intel NUCwith Samsung M2 drive – a combination that frequently seems to have Windows 10 issues – her problems came after the carp Anniversary updates). I can see that an inplace repair may well be my next attempt to stabilize the darned thing.

[rockonbazza]

Thanks for the replies etc so far. I also had an issue with Discord (which I use for my MMO’s). Last couple of days it has got stuck in a loop when launching it, saying “trying to update”. I had to go into the app/local/discord folder and rename update.exe to update1.exe and Discord would then launch as normal. It seems to be updates that are being affected  – i.e Java, Discord, and the other programmes are Windows Live Mail (which comes up with the .dll error but I can still use), and Skype (which keeps saying error, and retry). I uninstalled Skype, and re-installed it, but getting same error.

I upgraded from Vista to Win 10 using the free upgrade  – so I am not sure how I go about doing a fresh windows 10  install as I dont have the CD – I will have to look into it. I am running Scannow again. Ah, actually – My son upstairs with his new budget PC has a WIN 10 disc, so I can use that. !

Quick edit, re Skype it says error, retry etc, and below that says check yr internet connection. By the way I stopped avast from running, plus zone alarm firewall, but Skype still didnt work – in case avast and zone alarm were causing the issues.

[Dave Rice]

You don’t need anything extra to do a reinstall, W10 will do it itself.

Settings – Update and Security – Recovery – Reset this PC. You have the choice to keep your files but all the apps will go.

This is a true re-installation, exactly as if you’d done it with an ISO on a USB stick or DVD.

[Author]

Posts