supermium: Supermium 122 does not start on Windows XP SP3 x32
Describe the bug
Latest Supermium 122 Release installed from installer does not start on Windows XP Professional SP3 x32 with all the latest updates (for XP until 2014 + for Embedded POSReady unitl 2019).
It fails to find _wsplitpath_s export in msvcrt.dll.
Also, the log provides the following information:
[0307/232557.825:ERROR:crashpad_client_win.cc(476)] InitializeProcThreadAttributeList (size): Для указанной программы требуется более поздняя версия Windows. (0x47E)
[0307/232602.293:ERROR:crashpad_client_win.cc(144)] crash server failed to launch, self-terminating
[0307/232606.934:ERROR:crashpad_client_win.cc(476)] InitializeProcThreadAttributeList (size): Для указанной программы требуется более поздняя версия Windows. (0x47E)
[0307/232610.090:ERROR:crashpad_client_win.cc(144)] crash server failed to launch, self-terminating
[0307/233309.779:ERROR:crashpad_client_win.cc(476)] InitializeProcThreadAttributeList (size): Для указанной программы требуется более поздняя версия Windows. (0x47E)
[0307/233312.904:ERROR:crashpad_client_win.cc(144)] crash server failed to launch, self-terminating
It fails due to VerifyVersionInfoW from kernel32.dll returns ERROR_OLD_WIN_VERSION.
It runs properly only on Windows Server 2003 SP2 however, without any updates, for comparison.
To Reproduce Steps to reproduce the behavior:
- Download Supermium 122 here: https://github.com/win32ss/supermium/releases/download/v122/supermium_122_32_setup.exe.
- Install it by double-clicking on the installer.
- After installing, try to run it by double clicking on chrome.exe or on the link to it.
- An error about missing
_wsplitpath_sexport in msvcrt.dll should now appear. Then the browser does not start. Also, the error logging described above appears in debug.log.
Expected behavior Browser should start properly without any errors/error logging.
Screenshots
Desktop:
- OS: Windows XP SP3 x32.
- Bitness of browser: x32.
Additional context
Regarding an error from the log, it seems to be already a known issue, but missing export error was not reported yet.
Perhaps it makes sense to switch on non-secured _wsplitpath, which exists on Windows XP SP3 too? 🤔
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 28 (2 by maintainers)
But what is more interesting,
_wsplitpath_sis not shown as unresolved red export. There is only_wsplitpath, which is resolved correctly:Awww, it was my bad, sorry! 😅 My XP installation was unclean. I simply had the directory with OneCoreAPI dlls on C:\ and it was added in Path environment variable! So those dlls caught this problem! After removing that (and the directory with files), the problem got solved for me! Latest Supermium 122 Hotfix now starts properly! 😃 Please sorry again that I needlessly toke your time. I guess the issue can now be closed as invalid.
OK, here are SHA256 hashsums of my msvcrt.dll, imagehlp.dll and psapi.dll:
As I see, all hash sums are matching. In case the system files are not original, the sums should be different I guess? 🤔
It looks like the msvcrt.dll file has been replaced with something non-original… Is it possible to check the checksum of this file and provide versioninfo with a screenshot? Or the virus caused damage…
In my winxpsp3:
So the guilty module is imagehlp.dll, which is delay-loaded btw.
Just checked that menu when error appears: there is only one window named “chrome”:
I doubt where these MDI windows are, because I did not see any of them during startup, only message box. Also, after closing the message box, there appear some errors in the further logging. The full log before an error appears and after I close it:
I don’t see any issues with msvcrt there. But Dependency Walker should also create new MDI windows for debugging child processes at the same time, where problems may be occurring.
The problem is that Supermium components do not import directly from msvcrt, relying solely on the statically-linked VC++ 14 runtime. Only system components such as setupapi import from msvcrt in the Supermium dependency tree.
I would recommend trying to launch chrome.exe in Dependency Walker to identify the module that does import from msvcrt.