setup-x86_64.exe does not start in win10 20H2

Kutty, Rejeesh
Mon Dec 13 23:26:45 GMT 2021

I uninstalled Beyond Trust with our IT help, rebooted, same behavior.

I then came upon another thread that talks about the compression.
I didn't build it, I just decompressed it and now setup-64bit works fine.
For some reason, 32bit doesn't have any of this problem.

If it is not too much of trouble, I would request that you provide an uncompressed version too.
The file size is not that bad, It came to be about 5MB only.

Perhaps,  suggest in the installation instructions to try in case it doesn't launch?

Thanks for all your help.

-----Original Message-----
From: Cygwin <> On Behalf Of Brian Inglis
Sent: Saturday, December 11, 2021 12:39 AM
Subject: Re: setup-x86_64.exe does not start in win10 20H2


On 2021-12-10 13:19, Kutty, Rejeesh wrote:
>>> Renamed that DLL -- same behavior, and same  access violation in WinDbg.
>>> Killed all Beyond Trust Services/Tasks -- same behavior.

You will probably need to restart Windows after any changes in order to unload or reload DLLs and associated data.

>> Does WinDBG still show the DLL loaded?

 > No it didn't, but it reported access violation after RPCRT4.dll.
 > (This is the RPC API, as per google).

Many of these apps have difficulty handling dynamic modification, cleanly removing themselves from the call or message chains they insert themselves into, transparently passing along arbitrary calls, data, events, or messages, especially when application code is multithreaded and reentrant using mutexes and waits.

Beyond Trust is on the Cygwin Big List of Dodgy Apps: poorly written (often so-called "anti-malware", "anti-virus", or "security") software that monitors, logs, blocks, and/or interferes with normal operation of many applications, with effects sometimes indistinguishable from malware, and known to prevent Cygwin working properly; see:*faq.using.bloda__;Iw!!A3Ni8CS0y2Y!uPaRC6ohLqsjqrbgUACGkx243avIO2jUMYZ09x5cgOrHWncL_fmuGb_5k5qPX0GSDDg$ 

Beyond Trust has caused problems because its certs became outdated unless you kept the product and its certs updated. Try updating the product and check its certs are up to date in the cert store.
If that fails you may need to raise a case with the product vendor regarding Cygwin 64; especially useful to mention:*faq.api.fork__;Iw!!A3Ni8CS0y2Y!uPaRC6ohLqsjqrbgUACGkx243avIO2jUMYZ09x5cgOrHWncL_fmuGb_5k5qP00bIrrM$ 

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

Problem reports:;!!A3Ni8CS0y2Y!uPaRC6ohLqsjqrbgUACGkx243avIO2jUMYZ09x5cgOrHWncL_fmuGb_5k5qP-FRJ2uE$ 
FAQ:        ;!!A3Ni8CS0y2Y!uPaRC6ohLqsjqrbgUACGkx243avIO2jUMYZ09x5cgOrHWncL_fmuGb_5k5qPOErRlRs$ 
Unsubscribe info:*unsubscribe-simple__;Iw!!A3Ni8CS0y2Y!uPaRC6ohLqsjqrbgUACGkx243avIO2jUMYZ09x5cgOrHWncL_fmuGb_5k5qP1DBErDc$ 

More information about the Cygwin mailing list