When launching DxO Photolab 3 it crashes upon start showing dialog offering to submit ticket to support. After submitting ticket along with screenshot I receive very formal reply which amounts to nothing all my subsequent calls for help are ignored. I am professional software developer and offered to assist with doing Teamviewer session so they can identify bug right in place. Alternatively I would expect refund as the software just stopped working and completely useless for me.
So whoever is responsible pleas either fix the problem or issue the refund
Okay, could you, please, provide the info they’ve asked you in the latest post - it’s really necessary for the developers.
And in the meantime try the following:
Rename/move:
%LocalAppData%\DxO\DxO PhotoLab 3\ and
%appdata%\DxO\DxO PhotoLab 3\Database and then try to launch the application.
Renaming did not help. In fact I did it before trying to reinstall the software, basically cleaning any traces of DxO PhotoLab from hard drive and the registry.
Here is the link to error log: https://support.dxo.com/attachments/token/80KuH9vzbfnJCNp4Di1m8PuDl/?name=0dd4cf18-d969-4b90-a35d-14f79fcf9832.zip
The error code is: 07A37202-DADB-4347-862B-68C97A3090B1 and I clicked send button.
System info:
OS Name Microsoft Windows 10 Home
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-BBJDKON
System Manufacturer HP
System Model OMEN by HP Laptop 15-dc0xxx
System Type x64-based PC
System SKU 4BQ16UA#ABL
Processor Intel® Core™ i7-8750H CPU @ 2.20GHz, 2208 Mhz, 6
Core(s), 12 Logical Processor(s)
BIOS Version/Date AMI F.09, 6/11/2019
SMBIOS Version 3.2
Embedded Controller Version 93.22
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 84DB
BaseBoard Version 93.22
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume5
Locale United States
Hardware Abstraction Layer Version = “10.0.18362.387”
User Name DESKTOP-BBJDKON\kp
Time Zone Eastern Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 25.2 GB
Total Virtual Memory 36.6 GB
Available Virtual Memory 27.6 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
I do not remember installing any drivers as the Windows did install on its own. Anyways I did install drivers from the link you just supplied to the same result: no luck
Thank you for the data. @alex could you, please, have a look at the logs and give instructions to Konstantine. But as the info or even TV session is a personal info, it’s better to continue the discussion via #204551
Could you please share with us the last crash report after you moved\renamed\removed your database and user.config files as @sgospodarenko had asked you?
I clicked “send report” in your crash handler. You should now have file: 7c968bd9-7864-4310-ab4b-e411c20d6043.zip
the code generated by crash handler is 07A37202-DADB-4347-862B-68C97A3090B1
I did put user.config into the same zip file
Unfortunately, I couldn’t find the file 7c968bd9-7864-4310-ab4b-e411c20d6043.zip in the crash reports received from our users. There are 3 crash reports associated with 07A37202-DADB-4347-862B-68C97A3090B1 but none of them contains user.config. Could you please attach your crash report 7c968bd9-7864-4310-ab4b-e411c20d6043.zip (or just user.config) here?
I have to disagree here with you First by sending the report you display us a picture if the issue is global or just a personal case. Second, it allows us to make a comparison of different reports of the same kind to dig to the problem faster.
But when you address an issue in the Forum or via support it’s far more effective if you attach the crash report directly.
According to the attached crash report you still use DxO PhotoLab 3.0.2. Could you please try to install the latest DxO PhotoLab 3.1 and let us know whether you still experience your problem?
Thanks for your response, Svetlana. I appreciate the value any crash info provides, but your last sentence is the crux of the matter IMO. When a crash occurs, we’re given the option of sending the report in immediately or saving it to the local computer. DxO seems to consistently prefer that we save the local report and provide that to support. But to a customer, sending the report in immediately looks like the right approach. So we end up duplicating our efforts frequently if not always to provide sufficient info to DxO. I think the handler should recommend saving the crash data or make the crash info easier for support to retrieve (since that’s also been a problem in my experience). Thanks as always for listening.
First by sending the report you display us a picture if the issue is global or just a personal case. Second, it allows us to make a comparison of different reports of the same kind to dig to the problem faster.