Hello,
What do you mean by "won't launch"? Do you see the splashcreen? Do you have a crash? Do you have nothing happenning?
I am currently using PS 2.3.0-rc2 with a dual monitor (2560x1440 and 1680x1050) under Win10 2004 without issue.

I have the same issue. It just crashes when opened on seccond monitor.

I have a similar issue which seems to be linked to multiple displays.

PrusaSlicer version
PrusaSlicer-2.3.0-rc2+win64-202012221641

Operating system type + version
Windows 10 (build 19042), 64-bit edition (freshly installed).

Other system information + Hardware
OpenGL installation
GL version: 4.6.0 NVIDIA 460.89
Vendor: NVIDIA Corporation
Renderer: GeForce RTX 3070/PCIe/SSE2
GLSL version: 4.60 NVIDIA
CPU: Ryzen 3700x
Monitors: 2 monitors (both at 1440p)

Problem
After downloading Prusaslicer 2.3 RC-2 and attempting to run it, process hangs and responds as "Not responding" in task manager.
Splash screen shows up, but application hangs while loading.

Work Around

1. Disconnect secondary display.
2. Start prusaslicer.

Prusaslicer does not start on the secondary display like @horviskoadrianko mentioned.

Clarification: When prusaslicer is started with the work around, move the window to the secondary screen, close prusaslicer and it won't start again without the work around.

Maybe the dreaded Nahimic issue?

#2522
#5091
#4793
#3689

#2142

If this is the Nahimic driver issue, then please bug https://www.nahimic.com/

Is your motherboard or laptop Asus made?

Thanks. Unfortunately these issues are difficult to solve without having access to such a device.

@bubnikv
I have never heard about Nahimic but yes, i found a service running on my machine. It must be included in the realtek drivers from my motherboard manufacturer (Asus).
After stopping the service, prusaslicer starts as expected on my secondary monitor.

Since i cannot find any newer drivers, i'll try to get rid of nahimic.
But before i do, would you like me to debug something for you? I have compiled a version of prusaslicer 2.3.0 rc-2 that i prepared in order to troubleshoot this.
Please note that i am not really a software dev, so i might need some instructions to get you what you need.
Br

@schneidp20
I did not think i was running any Nahimic software at first either, so i suspected the issues were related. Later on i found a service named "NahimicService" which was listed in services.msc.
I would take an extra look just to be sure, Nahimic lists Dell as a vendor on their website.

Regarding Dev environment.
I just followed the How to build - Windows.md noob-guide-step-by-step guide.
I had two issues.

1. When building the dependencies, git needs to be in the environment variable "path", i had to manually add it. Also make sure to build the dependencies via a terminal opened via Start Menu and Click on "Visual Studio 2019" folder, then select the ->"x64 Native Tools Command Prompt" like the instructions say, otherwise the environment vars might load correctly.
2. First time i built the actual prusaslicer solution, something failed and prusaslicer-console reported that prusaslicer.dll was not loaded when started. I am not sure what went wrong, i just performed a cleanup and rebuilt the solution and prusaslicer started as expected in debug mode.

Hope it helps.

@obgr

I have never heard about Nahimic but yes, i found a service running on my machine. It must be included in the realtek drivers from my motherboard manufacturer (Asus).
After stopping the service, prusaslicer starts as expected on my secondary monitor.

Cool.

BTW
https://rog.asus.com/forum/showthread.php?107802-Nahimic-Service-causing-programs-to-startup-slow
and possibly many others

This may be a quick test, that anybody could try. Just run the following from the command line:

taskkill /f /im "NahimicService.exe"
taskkill /f /im "NahimicSvc32.exe"
taskkill /f /im "NahimicSvc64.exe"

Since i cannot find any newer drivers, i'll try to get rid of nahimic.

You may also try to bug Asus and/or Nahimic. I am really interested in their response.

But before i do, would you like me to debug something for you? I have compiled a version of prusaslicer 2.3.0 rc-2 that i prepared in order to troubleshoot this.

Frankly I don't know. Is it crashing? Or hanging? I remember from analyzing some crash logs that it was crashing inside either the Nahimic or OpenGL driver.

It would be best if we can get hands on one of these computers and debug it ourselves.

process explorer
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
shows list of loaded DLLs into a process. The issue with the Nahimic service is that it injects a DLL into PrusaSlicer process, which somehow interferes with OpenGL. Maybe we can somehow block the Nahimic service to inject the Nahmic DLL. It is likely technically possible, but it would require some experiments and access to the Nahimic plagued machine would be needed.

We can likely detect the Nahimic DLL loaded into our PrusaSlicer process and report it, possibly with a notification or in System info. That may give user a hint, but it does not really help to resolve the issue.

It is not just Asus, but also MSI that preinstalls the Nahimic drivers.

Most likely the Nahimic service injects a DLL using 1, 5 or 6 method described in
https://www.elastic.co/blog/ten-process-injection-techniques-technical-survey-common-and-trending-process
The method 1 is detailed in
https://dzone.com/articles/windows-api-hooking-and-dll-injection

It would help us, if somebody documents the names of the DLLs injected into PrusaSlicer by Nahimic service and possibly documents the way the DLL is injected. A "fix" may consist of creating phony Nahimic DLLs and loading them into PrusaSlicer before Nahimic, however I am not sure how reliable this would be.

https://github.com/microsoft/Detours
may be used to hook the LoadLibraryA/LoadLibraryW/LoadLibraryExA/LoadLibraryExW Win32 API functions to refuse to load the Nahimic DLL. That may help if the Nahimic service is using the method 1 to inject the DLL. That may be worth trying.

@bubnikv
If you want to move this to another Issue, please tell me and i can open a new one.

Frankly I don't know. Is it crashing? Or hanging? I remember from analyzing some crash logs that it was crashing inside either the Nahimic or OpenGL driver.

I do not really know since i have yet to see any logs that tells me anything, event viewer is not helping much. but it looks like it is hanging. prusa-slicer-console is showing nothing, the process is listed in taskmanager but in a "not responding" state. I included some debug output from when i attempted to start prusaslicer and later on killed the task.

'prusa-slicer-console.exe' (Win32): Loaded 'C:\Users\Olle\Downloads\PrusaSlicer-version_2.3.0-rc2\build\src\Debug\prusa-slicer-console.exe'. Symbols loaded.
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msvcp140d.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140d.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140_1d.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. 
The thread 0x4c58 has exited with code 0 (0x0).
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\uxtheme.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msctf.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\oleaut32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\A-Volute.SonicRadar3DevProps2.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ws2_32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\shlwapi.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\shell32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\NahimicOSD.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\ProgramData\A-Volute\A-Volute.28054DF1F58B4\Modules\ScheduledModules\x64\ProductInfo.dll'. 
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_3920e95365a48b95dd51020986e9e351>::operator ()
'prusa-slicer-console.exe' (Win32): Loaded 'C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\A-Volute.SonicStudio3DevProps2.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks64.dll'. Module was built without symbols.
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\winmm.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\opengl32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\glu32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\clbcatq.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\AppXDeploymentClient.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\AppXDeploymentClient.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvoglv64.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvoglv64.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvoglv64.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\setupapi.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\bcrypt.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\wtsapi32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\version.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msasn1.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\cryptnet.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\crypt32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\cryptbase.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\devobj.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\wintrust.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ntmarta.dll'. 
The thread 0x1074 has exited with code 0 (0x0).
The thread 0x49a4 has exited with code 0 (0x0).
The thread 0x32e8 has exited with code 0 (0x0).
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\windows.storage.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\wldp.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\SHCore.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DXCore.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\nvspcap64.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\profapi.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\dwmapi.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\powrprof.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\umpdc.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\winsta.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Users\Olle\Downloads\PrusaSlicer-version_2.3.0-rc2\build\src\Debug\PrusaSlicer.dll'. Symbols loaded.
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\Wldap32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Users\Olle\Downloads\PrusaSlicer-version_2.3.0-rc2\build\src\Debug\libgmp-10.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Users\Olle\Downloads\PrusaSlicer-version_2.3.0-rc2\build\src\Debug\libmpfr-4.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\normaliz.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\comdlg32.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\comdlg32.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\winspool.drv'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.488_none_ca04af081b815d21\comctl32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\oleacc.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\msimg32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\comdlg32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\secur32.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\sspicli.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\mswsock.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\TextInputFramework.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\CoreMessaging.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\CoreUIComponents.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\WinTypes.dll'
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\WinTypes.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\TextShaping.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DataExchange.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\d3d11.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\dcomp.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\dxgi.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\twinapi.appcore.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\WindowsCodecs.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\hid.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\hid.dll'
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\d3d9.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvldumdx.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\imagehlp.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\cryptsp.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\rsaenh.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvd3dumx.dll'. 
'prusa-slicer-console.exe' (Win32): Loaded 'C:\Windows\System32\ResourcePolicyClient.dll'. 
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Windows\System32\ResourcePolicyClient.dll'
The thread 0x57f0 has exited with code 0 (0x0).
onecore\windows\directx\database\helperlibrary\lib\perappusersettingsqueryimpl.cpp(121)\d3d9.dll!00007FFC576478D0: (caller: 00007FFC57606442) ReturnHr(1) tid(4a44) 8000FFFF Catastrophic failure
onecore\windows\directx\database\helperlibrary\lib\perappusersettingsqueryimpl.cpp(98)\d3d9.dll!00007FFC5760646B: (caller: 00007FFC57604C2D) ReturnHr(2) tid(4a44) 8000FFFF Catastrophic failure
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(1410)\d3d9.dll!00007FFC57606597: (caller: 00007FFC57604C2D) ReturnHr(3) tid(4a44) 8000FFFF Catastrophic failure
The thread 0x51c4 has exited with code 0 (0x0).
The thread 0x2850 has exited with code 0 (0x0).
The thread 0x5670 has exited with code 0 (0x0).
The thread 0x32a4 has exited with code 0 (0x0).
The thread 0x6d8 has exited with code 0 (0x0).
The thread 0x4fd0 has exited with code 0 (0x0).
'prusa-slicer-console.exe' (Win32): Unloaded 'C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks64.dll'
The thread 0x4250 has exited with code 0 (0x0).
The thread 0x56d0 has exited with code 0 (0x0).
The thread 0x2650 has exited with code 0 (0x0).
The thread 0x19fc has exited with code 0 (0x0).
The thread 0x56fc has exited with code 0 (0x0).
The thread 0x2260 has exited with code 0 (0x0).
The thread 0x3294 has exited with code 0 (0x0).
The thread 0x51b8 has exited with code 0 (0x0).
The thread 0x296c has exited with code 0 (0x0).
The thread 0x1a9c has exited with code 0 (0x0).
The thread 0x42bc has exited with code 0 (0x0).
The thread 0x9a8 has exited with code 0 (0x0).
The thread 0x5424 has exited with code 0 (0x0).
The thread 0x46c8 has exited with code 0 (0x0).
The thread 0x2950 has exited with code 0 (0x0).
The thread 0x2494 has exited with code 0 (0x0).
The thread 0x78c has exited with code 0 (0x0).
The thread 0x5024 has exited with code 0 (0x0).
The thread 0x5570 has exited with code 0 (0x0).
The thread 0x4d94 has exited with code 0 (0x0).
The thread 0xbc0 has exited with code 0 (0x0).
The thread 0xc24 has exited with code 0 (0x0).
The thread 0x4110 has exited with code 0 (0x0).
The thread 0x1354 has exited with code 0 (0x0).
The thread 0x2e9c has exited with code 1 (0x1).
The thread 0x56ec has exited with code 1 (0x1).
The thread 0x4a48 has exited with code 1 (0x1).
The thread 0x4a44 has exited with code 1 (0x1).
The thread 0x45f8 has exited with code 1 (0x1).
The program '[11988] prusa-slicer-console.exe' has exited with code 1 (0x1).

It would be best if we can get hands on one of these computers and debug it ourselves.

My computer is a Custom built PC, My motherboard is a Asus Rog Strix B550-i Gaming if you want to try to get hold of the hardware.

This may be a quick test, that anybody could try. Just run the following from the command line:

taskkill /f /im "NahimicService.exe"
taskkill /f /im "NahimicSvc32.exe"
taskkill /f /im "NahimicSvc64.exe"

This does not help, the processes restarts as soon as they are killed.

It would help us, if somebody documents the names of the DLLs injected into PrusaSlicer by Nahimic service and possibly documents the way the DLL is injected. A "fix" may consist of creating phony Nahimic DLLs and loading them into PrusaSlicer before Nahimic, however I am not sure how reliable this would be.

I can provide you with a full or mini dump generated by process explorer for prusa-slicer-console if you like. But as far i can see, there are four dlls loaded from Nahimic into prusa-slicer-console (prusaslicer is in a hanged state but prusa-slicer-console is running)
A few dlls of interest:

Is there anything that you like me to look further in?
BR

@obgr Would you please check whether the DLL is referenced in registry? See the section 6 of
https://www.elastic.co/blog/ten-process-injection-techniques-technical-survey-common-and-trending-process

@bubnikv
No, i cannot find any of the listed dlls referenced in the registry.
BR

@obgr maybe we will put together an experimental build patching the LoadLibrary API to filter out the Nahimic DLL, but it will not be soon.

@bubnikv i'd be happy to help.
Mention me when the time comes and i'll do my part.
as a work around, i'll disable the service.

@enricoturri1966 would you please investigate the call stacks?

My experience mirror's @jozsefhabit's, however I found that I can use external monitors in 'Extend' mode provided my laptop is set as the 'main display' (set via Display Settings).

So for those chasing a workaround - I find that having the laptop as my main display is less cumbersome than temporarily undocking or changing the external monitor projection mode in order to launch PrusaSlicer.

We have one computer available in house, where PrusaSlicer hangs if a USB 3 based docking station is connected with specifically 2 monitors connected and it has to be specific monitors. With other 2 monitors PrusaSlicer starts just fine. We are investigating it further. It is supposed to work before the last big Windows 10 update, it broke after the Windows 10 update.

We have a handful of ASUS based desktops around, but as for now we did not find any, for which the ASUS Sound Studio would be available.

@bubnikv
I am considering to switch motherboard. the Nahimic issue is one of the reasons but not the only one.
Would it be interesting for you to use that motherboard for troubleshooting if i replace it (only the motherboard itself)?

@obgr Maybe. I would have to check with our IT department whether they could build a test setup around it.
What motherboard is it?

@bubnikv
Its a ROG STRIX B550-I GAMING. so you basically need a newer Ryzen cpu (3000 or 5000 series) and a ddr4 ram stick.

Some of the issues here may not be Nahimic related, but similar to #2939

This Might be an nvidiaproblem; when trying to delete that dll, i get the error message:" can't be deleted, because it is opened in nvidia Container"

@obgr

Its a ROG STRIX B550-I GAMING. so you basically need a newer Ryzen cpu (3000 or 5000 series) and a ddr4 ram stick.

I am on AMD Ryzen 9 3900X, board TUF GAMING X570-PLUS, NVIDIA GPU, my 3 colleges have similar setup and we don't experience such issues. I am not saying that there is no issue, I am just saying that it is quite rare as far as I can judge, only we have so many installations that the issue pops up often enough.

Hello,

I've had the same problem for quite some time now, but was just made to look by the prompt on v2.4.

Stopping the Naimic service did solve the issue, but I also found this link where they point to a BlackApps.dat file where you can add the executable that have the issue with this Nahimic services.

I tried it and it solve the problem for for me (with prusaslicer but also fusion 360 and openscad).
Also looking at the looong list of .exe already in the file I wonder how they can release such a driver …

Hope this helps !

The BlackApps.dat solution worked for me also. No more problems on my secondary monitor. This seems to be the proper solution. Now only the startup prompt is remaining. Perhaps a "do not show again" option on that dialogue would be nice to hide it in the future.

Hi Guys, I'm having a similar issue to other folks here. I've never had an issue with Prusa Slicer but this holiday season I ended up picking up two monitors and extending my desktop. Now, my setup is a little bit different from some folks. I have these stacked vertically, not sure if that is what is causing my issue. When I start the slicer the splash screen displays and then disappears with no slicer window. I checked the windows event viewer in the application log and I saw that Prusa Slicer had crashed. I am running Prusa Slicer Version 2.4.0.

Here is the windows event log information:

Faulting application name: prusa-slicer.exe, version: 2.4.0.0, time stamp: 0x61c1feea
Faulting module name: PrusaSlicer.dll, version: 0.0.0.0, time stamp: 0x61d4237f
Exception code: 0xc0000005
Fault offset: 0x0000000001e53a1d
Faulting process id: 0xd78c
Faulting application start time: 0x01d8069670a5f5e3
Faulting application path: C:\Program Files\Prusa3D\PrusaSlicer\prusa-slicer.exe
Faulting module path: C:\Program Files\Prusa3D\PrusaSlicer\PrusaSlicer.dll
Report Id: 610d98b8-3f81-42e9-82a1-9cc3d7356015
Faulting package full name:
Faulting package-relative application ID:

One interesting thing to note, if I delete "window_mainframe" property in the PrusaSlicer.ini file, I am able to launch the slicer until the next time after it writes its window position into the file again.

Hope that helps.

EDIT: Just to note, I do not have nahimic or anything like that and my Fusion360 and OpenScad works just fine.

We tried to workaround this problem in upcoming 2.4.1 release by making the position restoring optional (and on by default). When the crash described here occurs, PrusaSlicer will suggest to turn the feature off on the next start. It is not exactly a fix, but it is better than nothing.

Because we cannot reproduce the issue, could you guys please test the following build and let us know if it helped?
https://prusaslicer:slicer@slicerbuilds.prusa3d.com/files/lm/PrusaSlicer-2.4.1-alpha0+4-win64-g200cbd165-202201141630.zip
If the download requires login use login: prusaslicer password: slicer.

If the build crashes on the very first try, run it again. Thanks a lot.

Fusion 360 has the same problem on my System, same solution works. Location:
"C:\ProgramData\A-Volute\DellInc.AlienwareSoundCenter\Modules\ScheduledModules\Configurator\BlackApps.dat"

Glad it worked for you, but there is no such file (BlackApps.dat) on my system, plus I can't find Nahimic or any of the 'Sonic" apps listed in the link. It's not just Pusua though. Fusion 360 has the same problem and no response from their customer support. Dell XPS 15 9500, Windows 10. I'm still stuck with the work-around of starting the apps un-docked.
…

We tried to workaround this problem in upcoming 2.4.1 release by making the position restoring optional (and on by default). When the crash described here occurs, PrusaSlicer will suggest to turn the feature off on the next start. It is not exactly a fix, but it is better than nothing.

Because we cannot reproduce the issue, could you guys please test the following build and let us know if it helped? https://prusaslicer:slicer@slicerbuilds.prusa3d.com/files/lm/PrusaSlicer-2.4.1-alpha0+4-win64-g200cbd165-202201141630.zip If the download requires login use login: prusaslicer password: slicer.

If the build crashes on the very first try, run it again. Thanks a lot.

The build "fixes" the problem on my machine!

@valberg Thanks for the info, glad to hear it.

For anyone who has this problem ill give you method i used to fix it.

1. Go to task manager
2. Find Nahmic services and go to the dropdown menu for the services
3. Once your in the services menu on your computer find Nahmic services and disable it.

Hope this helps someone :)