No it didn't, but it reported access violation after RPCRT4.dll. (This is the RPC API, as per google).
-----Original Message----- From: Lavrentiev, Anton (NIH/NLM/NCBI) [C] <l...@ncbi.nlm.nih.gov> Sent: Friday, December 10, 2021 3:17 PM To: Kutty, Rejeesh <rejeesh.ku...@analog.com>; cygwin@cygwin.com Subject: RE: setup-x86_64.exe does not start in win10 20H2 [External] > Renamed that DLL -- same behavior, and same access violation in WinDbg. > Killed all Beyond Trust Services/Tasks -- same behavior. Does WinDBG still show the DLL loaded? Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
