Thanks for looking into this last month. As suspected, the issue stemmed from problems loading the DLL. The user had a 3rd party application called AppSense that was blocking the dll from running. They had whitelisted the executable, but the unpacked components in the tempdir were still being blocked.
A realization from debugging this is that the error surfaced is different depending on how the DLL is blocked. When I tried blocked the python36.dll with Windows AppLocker or other Software Restriction Policies, I was getting the below error: Error loading Python DLL %TEMP%\_MEIxxxxx\python36.dll LoadLibrary: This program is blocked by group policy. For more information, contact your system administrator. When blocked with AppSense, the following error was surfacing which is what I initially asked about. Failed to get address for Py_DontWriteBytecodeFlag GetProcAddress: The specified procedure could not be found. Regards, Ryan On Monday, November 9, 2020 at 10:05:34 AM UTC-8 bwoodsend wrote: > Hmm, I wouldn’t be surprised if this is just a convoluted permission > error. I’ve checked the python36.dll inside the application you sent and > the flag is definitely there so whatever the problem is, it’s not what it > says it is. Looking back at the source code I notice that that flag is the > first attribute/function to be loaded from said DLL so it’s quite likely > that Py_DontWriteBytecodeFlag is a red-herring and the real problem is > it’s not able to load the DLL at all. I do see a fail-safe for failing to > load the DLL although I can’t verify if it works… > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pyinstaller/a0f1db50-1011-4f35-b320-178abe7b62a2n%40googlegroups.com.
