New versions of Wireshark no longer working on unpatched Windows system( api-ms-win-crt-runtime-l1-0.dll )

asked 2018-11-11 19:04:10 +0000

dixo
1

updated 2018-11-19 19:17:21 +0000

grahamb

flag of United Kingdom of Great Britain and Northern Ireland

23835 ●4 ●973 ●227 https://www.wireshark.org

Hi all

Happy wireshark user here.. but recently i've been getting the error on starting that I can't use it as the above dll is missing. This never used to be a problem!

Can't install the MS update as I have to have about a gazillion other updates installed which I don't have and installed various c++ runtimes hasn't helped either.

So whats the beef here? Why did it previously work and now refuses throwing its toys out the pram over a dynamic link library? Seems odd. Total pain as I'm trying to debug DNS requests from my phone over a vpn to my desktop machine..

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2018-11-12 22:44:35 +0000

Guy Harris
19890 ●3 ●659 ●207

From what Graham is saying, it appears that we need to change the way we build and package Wireshark so that either 1) Wireshark works on the OS version you're running or 2) the Wireshark installer won't install Wireshark if an update is needed and will indicate what update is required.

Please file a bug on this on the Wireshark Bugzilla; please give full details as to the version of Windows that you're running, including the build number, what updates are installed, etc., so that we have some hope of figuring out why it's not working.

edit flag offensive delete link

Comments

We run the CRT installer in silent mode. We could run it in noisy mode so those with broken systems can see what's up.

We also check (in the NSIS installer) the CRT installer for a return value indicating a reboot is required, but don't appear to check for any other error code.

grahamb ( 2018-11-12 22:49:52 +0000 )edit

Hi all,

The problem I have is that to install the runtime required, I have to have a shed load of windows updates patches installed. Experience has taught me they can be problematic so I don't bother with them but that again brings its own problems with products like WS are compiled needing those dependencies.

So.. I did something else most wouldn't recommend.. I went with an older version - works flawlessly and has the better and easier looking interface! Problem solved!

Windows7 Home Premium, no build number known.

dixo ( 2018-11-19 12:20:56 +0000 )edit

And to do this is entirely your choice, but hopefully you'll keep your likely insecure Windows installation away the internet.

The old GTK UI has been dropped due to lack of support for our platforms and thus the Qt UI is now standard on all platforms.

grahamb ( 2018-11-19 13:55:57 +0000 )edit

To be honest i've had my systems online for years like this, they work fine - i run regular scans and nothing ever turns up that is nasty. With that said, i'm not all over the internet, i just visit the same regular websites each day so hardly a big risk taker. There is more risk of 3rd party software (such as yours lol) doing something bad.

There is also the argument that the updates actually introduce security lapses - where the CIA / NSA etc can gain access. The reality is that nobody knows what is going on inside those MS updates.

dixo ( 2018-11-23 17:58:40 +0000 )edit

I give you exhibit 1; Wannacry and it's affects on the NHS in the UK. From the official investigation and report:

All NHS organisations infected by WannaCry had unpatched or unsupported Windows operating systems so were susceptible to the ransomware.

grahamb ( 2018-11-26 18:39:31 +0000 )edit

see more comments

answered 2018-11-12 10:25:17 +0000

grahamb

23835 ●4 ●973 ●227 https://www.wireshark.org

Your issue is that your machine doesn't have the system components of the C runtime library that Wireshark uses. As Wireshark evolves we update the builds to use the most recent versions of Visual Studio and they require the most recent C runtime libraries.

If you provide the OS and version and bitness of Wireshark you are attempting to use I can point you to the correct C runtime installer, but if your machine is so far out of date with updates then there will probably be many pre-requisites that you will need to install.

edit flag offensive delete link

Comments

As Wireshark evolves we update the builds to use the most recent versions of Visual Studio and they require the most recent C runtime libraries.

Then shouldn't we include the C runtime we require in the Wireshark installer, either by installing the runtime ourselves, providing the runtime dll as one of the dlls we provide, or statically linking with the runtime?

Guy Harris ( 2018-11-12 22:17:37 +0000 )edit

We do run the appropriate CRT installer from the Wireshark installer, but there have been various reports of this not installing, for reasons we've never been able to discover. For VS 2015 onwards there is also an OS component to the CRT, and I guess it's possible that if pre-requisites are not met the CRT installation will fail. That seems to be the issue for the OP.

grahamb ( 2018-11-12 22:33:29 +0000 )edit

If we depend on the OS component of the CRT, and can't force that to be upgraded, we need either to somehow make our builds work on OSes with older versions or make our installer fail to install Wireshark and to indicate that you have to update the OS.

Guy Harris ( 2018-11-12 22:42:18 +0000 )edit

add a comment