AME v23.3 won't load after splash screen

How do you clear up the queue without getting past the splash screen?

Do you have something pointed to this external drive and do an export or access to it before, like an export, or do you selected it in the MediaBrower panel in AME? Possible something was still in the AME queue and referencing it. If so, please clear up the queue and launch AME again to see if it works with and without the drive connected. Other places could be MediaCache path (Preferences) or setup WatchFolders.

Have just tried again and now it launches. Haven't changed anything, no rebooting. The only thing I've done is plug in an external drive. Log and Log-last below:

Log file created: 05/05/2023 15:53:17
---------------------------------------
Ticks = 454 <20432> <DynamicLink> <5> Increase wait time to 2
Ticks = 2188 <20432> <AnywhereLocalClient> <5> Local Hub HTTP port retrieved, port: 64310
Ticks = 3235 <27164> <MF.WinDirectoryChangeMonitor> <4> System call CreateFile() failed -- drive could not be monitored, driveLetter: "S", lastError: "Error 53: The network path was not found.\r\n"
Ticks = 18422 <22140> <DisplaySurface> <5> [DirectX] Initializing DirectXContext...
Ticks = 18719 <22140> <DisplaySurface> <5> [DirectX] Initialize DirectXContext succeeded.
Ticks = 20282 <22140> <AMEApp> <0> Time taken to load MediaCore plugins: 1549.09 milliseconds.
Ticks = 20313 <22140> <OCIOWrapper> <5> OpenColorIO Library Version: 2.1.2
Ticks = 20313 <22140> <OCIOWrapper> <5> OpenColorIO Library VersionHex: 33620480
Ticks = 22360 <22140> <AMEApp> <1> Entering RunEventLoop
Ticks = 23407 <22140> <dvacore.utility.RunProcessSynchronously> <5> Process C:\windows\system32\wbem\WMIC.exe timed out
Ticks = 23657 <29392> <GPUFoundation> <5> Done loading modules, sec: 1.63617, device: CUDA(0)
Ticks = 23657 <29392> <GPUFoundation> <5> Done loading modules, sec: 3.5902, device: OpenCL(1)
Ticks = 23969 <29392> <EACL> <5> Connecting local hub to remote hub, requestID: "30d07deb-b90b-4255-9d77-e7c0fc8501d5", server: "https://cc-api-teamprojects.adobe.io:443", serverType: 2, user: "paul.lightowler@nikon.com", machineID: "8aa836ca-b122-4c98-94d7-ef442e9cca0d"
Ticks = 24907 <20432> <EACL.CloudProjectsLogin> <5> Finished sending new access token to LocalHub, result: 0, requestID: "dvanet-30d07deb-b90b-4255-9d77-e7c0fc8501d5-b9825c01-2dca-4eae-b9fd-4a0d5033cace-6", duration: 0.40699999999999997, httpStatusCode: 200, httpLibCode: 0, payload: "[{\"authorized\":true,\"connected\":true,\"forbidden\":{\"error_code\":\"\",\"message\":\"\"},\"lastAuthorizationStatusCode\":200,\"serverURL\":\"https://cc-api-teamprojects.adobe.io:443\",\"serverVersion\":\"2016.84.0.1210\"}]"

Log file created: 05/05/2023 15:26:07
---------------------------------------
Ticks = 359 <29404> <DynamicLink> <5> Increase wait time to 2
Ticks = 2218 <29404> <AnywhereLocalClient> <5> Local Hub HTTP port retrieved, port: 63780
Ticks = 3156 <22364> <MF.WinDirectoryChangeMonitor> <4> System call CreateFile() failed -- drive could not be monitored, driveLetter: "S", lastError: "Error 53: The network path was not found.\r\n"

Running nothing extra, the AME is a standard install, and tried running from shortcut and from within the Creative Cloud Desktop app.

Thanks for the crash files. From this it looks like it crashes on the system, while AME is still in the init phase at different stages. Do you run any script or 3rd party plugin/extension in the AME context?