Do you have a file UCRTBASE.DLL in your Windows\System32 directory?
If so, can you view it in File Explorer, right click it and select properties and then the Details tab and report back the "File Version" and "Product Version"?
The file is installed by the "Universal C runtime" update, KB 299926, and is found here.
Graham, I didn't have UCRTBASE.DLL in C:\Windows\System32 so I copied it over from another server where Wireshark runs successfully. As soon as I copied it over, Wireshark fired up and I was able to capture! Thank you so much for the solution, Graham - you are a lifesaver!
The missing file is part of the Visual C++ runtime. On Win 10 or later it's part of the OS, on downlevel versions it should be installed either by Windows Updates or by the VC redist installer, which should be run by the Wireshark installer. Not sure why it's missing for you.
Installing by copying might cause issue down the line as the file is updated by Windows Update for security and bug fixes etc.
Looking at things a bit more, it seem ucrtbase.dll is installed by a Windows Update on downlevel platforms. The update is KB 299926 and is found here. Do you have that update installed?
Also, if an answer has solved your issue, please indicate so by accepting it, to help others, by clicking the checkmark icon by the answer.
Asked: 2017-12-08 04:05:18 +0000
Seen: 3,024 times
Last updated: Feb 14 '18
Is this a distributed version of Wireshark or a version you have built yourself. What is the Wireshark version?
I have the same issue on Windows 10 running Wireshark version 2.4.4.
Can you show the exact error message you get?
I'm having this exact same issue on a server. 2.4.4 downloaded right from www.wireshark.org, C++ 2015 is installed (both x86 and x64), uninstalled, reinstalled, rebooted, etc and I still get the "The procedure entry point _lseeki64 could not be located in the dynamic link library C:\Program Files\Wireshark\zlib1.dll" error message.
Windows Server 2012R2, nothing unusual in terms of server setup or OS.
Does anyone have any ideas or tricks to try to get Wireshark up and running?
Does the error come when you start Wireshark, or when you attempt to do something else?