this means Dynamo has not even gotten far enough to create the log folder, or failed to do so -
I would:
remove packages from the 1.3 / 2.3 folder
verify you unzipped with 7zip or unblocked the entire .zip before unzipping
when the core starts up it will try to migrate packages - there could be some issue in trying to copy these old packages for some reason that is causing a crash - you can just take all previous 1.3 - 2.3 folders out of this DynamoCore folder temporarily.
As @Michael_Kirschner2 has indicated, i usually use point 2 when trying to open Dynamo sandbox after download, which is to unzip with 7zip then i do not have a issue where the exe wont load/open.
you could try running as admin or moving the dynamo 2.4 folder to another location - like c:
were you also running dynamo core 2.3 from your downloads folder?
It’s possible the download is not complete - have you downloaded a fresh copy since trying the first time?
I just checked the 2.4 stable and of course it runs fine on my machine
I just don’t know what it is with me and new builds of Dynamo
I tried running as admin - No Luck
Tried moving the folder - No luck
Each time I reply I have downloaded a new version of the Stable build of Sandbox 2.4
I do have Civil 2020 and the Dynamo version of it installed? I was hoping not to have to uninstall that as it means a complete uninstall (and then reinstall) of C3D
Sorry you’re having so much trouble here - I hope in the future we can provide an easier experience - but for now, I think what might help is to record your screen - all steps you take from fresh download forward - you can send it to me directly if you don’t want to post it publicly.
okay, thanks for the video - a couple things to try
try downloading directly from dynamobuilds.com under the stable section
don’t both unblock before hand AND use 7zip (do either or) - I don’t know what interaction that might have… it likely does not matter, but let’s try to get remove any variations from our processes.
move the zip to the desktop before doing anything, and try running it from there - sometimes the downloads folder is extra restricted
if that all fails, try downloading and master build (2.5) to compare with.
We are going to make some improvements so that even if the dlls fail to load, we will still show a warning dialog with some hopefully useful log info.