Windows thinks 64 bit wucheck is 16 bit

[MarkRiffey]

When I try to test wucheck_ssl /c, I get a message about the exe being 16 bit. Wucheck_ssl.sbp has been compiled as 64 bit and has "Enable x64 mode()" as the first line in the script.

When I turn off "Enable x64 mode" - this message does not appear.

Note: I have "file dummy" mode on in the product installer, but not for wucheck_ssl, though I dont know why that would cause this. (in fact, it doesnt - I turned it off, same result)

This test is running on Win11 Pro.

Mark

5100

[linder]

Hi Mark,

perhaps it is a corrupt .exe (or blocked by your protection software)? What does the code-signature of the file say? It it valid? If this is the case, please send your .exe to support [at] lindersoft [dot] com and I'll analyze it.

BTW, there is not any 16-bit code in the SetupBuilder compiled executables <g>.

Friedrich

[MarkRiffey]

Thanks Friedrich. I've moved on from that, having learned not to use Enable x64 Support in a 64 bit installer.

I dont get why windows task manager says wucheck_ssl is a 32 bit app, despite the fact that the installer config says "Windows 64 bit installer". Perhaps I read too much into "Windows 64 bit installer" and should understand that ALL SB installers are 32 bit apps with some magic to make 64 bit updates happen. I mean, it makes sense given Clarion.

Currently, I am battling the desire of wucheck_ssl to decline to send messages or read the wud file. I have malware bytes service stopped and disabled. I have exceptions for wucheck_ssl.exe in both windows and malwarebytes. Ive tried disabling every bit of Windows security as well, to no avail.

Despite turning all these things off and adding the various exceptions, it's hard not to see this as something interfering with the execution of wucheck_ssl - but there is nothing left that isnt off or excluded. It's sure not the sort of thing Id ask a user to do.

5101

I have never had this volume and scope of problems with 32 bit wucheck_ssl. Pretty frustrated after fighting this and other 64 bit wucheck_ssl issues all day.

Mark

[linder]

Hi Mark,

if the "Display Message" commands after the "Download File" function do not display, then I think the "Download File" function (the underlying WinSock components in Windows) did not return (perhaps timeout not reached, etc.). Just for fun, you can comment-out the "Download File" function to check this.

BTW, the created executables are always native 32-bit. Specific 64-bit tasks are processed through native 64-bit modules. You can switch from 32-bit to 64-bit processing and vice versa from a 32-bit application. But native 64-bit apps can't do 32-bit tasks (you can't switch to 32-bit to handle required 32-bit tasks).

BTW, "Enable x64 Support" in a 64-bit installer should not cause any problem. We are doing this on a regular basis. For example, if we have to process 32-bit tasks from a 64-bit installer then we switch to 32-bit processing and later back to 64-bit (using "Enable x64 Support).

Friedrich

[linder]

BTW, I Googled and there are millions of "Unsupported 16-Bit Application" findings.

If you are interested, please send your compiled "wucheck_ssl.exe" and the project file to support (at) lindersoft (dot) com and we'll check your source codes.

Friedrich

[MarkRiffey]

if the "Display Message" commands after the "Download File" function do not display, then I think the "Download File" function (the underlying WinSock components in Windows) did not return (perhaps timeout not reached, etc.).

I agree, it seems like its never getting back from there - which makes no sense, given that the tempfile I traced was up to date. When I have time to get back to this, Ill try all of this again I guess. For now, the 64 bit users will get over it.

Mark