Thank You for response, I have already submitted a ticket for DxO, but didn’t get answer yet. That problem is pretty common in previous versions, i saw a lot of forum topics about it, but none about DxO PL 4, so it’s good to keep conversation online on forum, to let others see solutions. IF I will get answer i will share, but right now, i can’t use it.
I have done all , but no succes, still error at startup and crash/close. I can’t see the reason, i know DXO is sensitive to some other programs. Maybe anyone had isssues like me? And know solutions or any super sensitive programs for DXO Photolab 4? I am waiting for response from DXO, but post on forum to give an image of situation and share hints also what to do first af all.
Well, thank You kindly for Your tip, pretty strange it was colliding, but unfortunately that won’t help for me, coz I already use that specific color space in the Windows Color System Defaults
Still, good hint, i guess there can be something so small like this what You wrote and it’s hard to find, that’s why posting on forum is important to share. I have read about many people being
surprised how small was the thing causing error.
Only thing I can think of is my Microsoft Visual C++ causing DXO Photolab 4 error, coz i got few of them from different years as needed for some programs to run. But i dont want to uninstall them yet, as I will crash few programs by that. That would have to be one of dramatic, ultimate steps to check what is causing error.
Well, seems I will stuck with runing DXO Photolab 4 on my Windows 10, as I tried totally everything I can think of, have read a lot and tested many types and ways of installing components like Direct X, Framework, including installing old versions, fresh install also. Nothing helps, it just keeps crashing, an issue i didn’t have with DxO 3. Maybe I will be forced to drastic step of refreshing windows to the fresh install state in order to check if it will run I updated all that can be, including windows and removed things like additional components of geforce drivers and leaving only driver. DxO has very good e mail service, responding quickly, but they have asked me to scan whole system and send log file of the whole system , but I am not permitted to perform this operation on the computer I work on.
If anyone had the issue of DxO Photolab 4 crashes, can’t run, error, crash at startup, please write me on this forum account.
I’m having a similar (but not identical) issue - I’ve recently installed PL4 but cannot get past the start up. I get the DXO PL4 splash screen, and the main screen for the program, then a DXO error reported application appears but gets pushed into the background. At that point none of the DXO PL4 windows (Splash screen, main program or error reporter) are active and need to be closed by Task Manager.
I submitted a report to DXO support (with screen shots, log files) who responded with a pretty generic reply to reinstall, make sure everything is up to date etc which is what I’d expect for a 1st response from support. Windows, drivers etc all up to date, plenty of CPU/Disk/RAM etc. My GPU (GForce 710) is significantly underpowered but that should not stop the program from starting up.
However, the error log always has the same error issue which is failure to load ‘Dop.Correction.Crop.resources’. A dll file (Dop.Correction.Crop.dll) is in the resource folder of the install.
I wondered if this was the same error which you have in your log file? I’m go back to support but while I wait for them I’m trying to find a fix! If you have the same error in the log then it may help DXO support to know that it’s not just me. Perhaps we can help support resolve both of our issues.
FYI - Photolab 1,2,3 all work perfectly on this system as do various other photo editing programs which have GPU acceleration.
I found the problem with my PL4.0 install. I’d tried uninstalling, reinstalling, checking .Net, Direct-x, Windows version, drivers etc to ensure everything was upto date and still had the problem.
I removed the database for Photolab 4, reinstalled and it worked. It had never launched fully so I’m not sure how it managed to put anything in the database which would cause it to hang on startup but after removing it from the roaming profiles area I’ve had no more problems. As expected PL4 simply created a new database on first run and since then all is good!
Thanks for a post. Good to know it can be a cause like in Your case. By database, you mean you deleted all c/appdata/roaming/dxo folder or is it something else? It can be useful to know it just in case.