Home › Forums › Help and Support › Error in the end of 3dlut calibration
- This topic has 29 replies, 2 voices, and was last updated 4 years, 2 months ago by S Simeonov.
-
AuthorPosts
-
2020-01-13 at 17:39 #22220
WindowsError: [Error 32] The process cannot access the file because it is ↲
↳ being used by another process
18:32:39,687 Warning – temporary file ‘c:\users\siso\appdata\local\temp\DisplayCAL- ↲
↳ mfusjv\madVR 2020-01-13 16-55 S XYZLUT+MTX.ti3’ could not be removed: ↲
↳ [Windows Error 32] The process cannot access the file because it is being ↲
↳ used by another process: c:\users\appdata\local\temp\DisplayCAL- ↲
↳ mfusjv\madVR 2020-01-13 16-55 S XYZLUT+MTX.ti3I’m getting this nasty error after almost 2 hours of calibration…
- This topic was modified 4 years, 2 months ago by S Simeonov.
2020-01-13 at 18:12 #22222Some other process on your system is accessing files it shouldn’t access and, even worse, holds exclusive access so that the process who actually created the file can no longer access it. This is something you have to fix. Are you using a 3rd party “security” suite by any chance?
2020-01-13 at 19:17 #22223Some other process on your system is accessing files it shouldn’t access and, even worse, holds exclusive access so that the process who actually created the file can no longer access it. This is something you have to fix. Are you using a 3rd party “security” suite by any chance?
Antivirus is nod32. Other security software is not being used and it is not in the process tab.
The interesting thing is that with the normal calibration 2.2 gamma preset, I ‘ve never had any problems with it, this error happens rarely with madvr 3dlut calibration only…
- This reply was modified 4 years, 2 months ago by S Simeonov.
- This reply was modified 4 years, 2 months ago by S Simeonov.
2020-01-13 at 19:48 #22226Antivirus is nod32
Likely culprit then (honestly, I despise these so-called “security” solutions. In my opinion, they are snake oil, providing a false sense of security, always seem to be developed “on the cheap”, buggy in the best case, and pose an additional security risk to a system at worst).
2020-01-13 at 19:57 #22227Antivirus is nod32
Likely culprit then (honestly, I despise these so-called “security” solutions. In my opinion, they are snake oil, providing a false sense of security, always seem to be developed “on the cheap”, buggy in the best case, and pose an additional security risk to a system at worst).
Is it the antivirus? If it is, I can disable it before the calibration. Would that help?
2020-01-13 at 19:58 #22228Very likely.
2020-01-13 at 20:14 #22229Very likely.
Than you for the fast replies, Florian. I really like your software I’ve been using it for years, and it is awesome. Tomorrow I will try to calibrate for madvr 3dlut again, this time I will stop the antivirus’s protection for a few hours to see what will happen. If there is the same error, how can I show you log files or something, to diagnose completely this problem? I really hate this error it happens rarely…
2020-01-13 at 20:23 #22230If there is the same error, how can I show you log files or something, to diagnose completely this problem? I really hate this error it happens rarely…
It’s unlikely there is anything I can do on my end. In application development, it is considered at least bad etiquette to open files for exclusive access unless your application has created it (and is thus likely the only consumer), and really has to (e.g. “lockfiles” etc). Yet, that seems regularly what antivirus solutions do willy-nilly. There is no fix other than to fix this in the antivirus solution itself (by the vendor), or using another antivirus (e.g. Windows Defender doesn’t seem to have this problem). Note that DisplayCAL already retries up to 20 times in case a file is not accessible due to being in use by another process, but you cannot just keep upping the retry limit if you want to have a responsive application (in terms of file access, UI is decoupled from this).
2020-01-13 at 21:02 #22231If there is the same error, how can I show you log files or something, to diagnose completely this problem? I really hate this error it happens rarely…
It’s unlikely there is anything I can do on my end. In application development, it is considered at least bad etiquette to open files for exclusive access unless your application has created it (and is thus likely the only consumer), and really has to (e.g. “lockfiles” etc). Yet, that seems regularly what antivirus solutions do willy-nilly. There is no fix other than to fix this in the antivirus solution itself (by the vendor), or using another antivirus (e.g. Windows Defender doesn’t seem to have this problem). Note that DisplayCAL already retries up to 20 times in case a file is not accessible due to being in use by another process, but you cannot just keep upping the retry limit if you want to have a responsive application (in terms of file access, UI is decoupled from this).
I understand, I’ll try tomorrow again and post here. Have a good evening.
2020-01-14 at 13:45 #22237And today the same error: WindowsError: [Error 32] The process cannot access the file because it is ↲
↳ being used by another process
14:40:35,898 Warning – temporary file ‘c:\users\siso\appdata\local\temp\DisplayCAL- ↲
↳ tphopu\madVR 2020-01-14 12-46 S XYZLUT+MTX.ti3’ could not be removed: ↲
↳ [Windows Error 32] The process cannot access the file because it is being ↲
↳ used by another process: c:\users\siso\appdata\local\temp\DisplayCAL- ↲
↳ tphopu\madVR 2020-01-14 12-46 S XYZLUT+MTX.ti3Run displaycal as administrator, stopped the nod32 protection for 4 hours…The monitor is LG 34UC99-W.
- This reply was modified 4 years, 2 months ago by S Simeonov.
2020-01-14 at 13:48 #22238Use LockHunter to find out what is locking the file.
2020-01-14 at 14:01 #22240Use LockHunter to find out what is locking the file.
When I try to delete the file in question, it says this –
And the process is in the task manager werfault.exe *32, I think this is locking the file needed for the calibration to be completed.
- This reply was modified 4 years, 2 months ago by S Simeonov.
- This reply was modified 4 years, 2 months ago by S Simeonov.
- This reply was modified 4 years, 2 months ago by S Simeonov.
2020-01-14 at 14:07 #22244Sorry about posting the screenshot twice.
- This reply was modified 4 years, 2 months ago by S Simeonov.
2020-01-14 at 14:13 #22246It’s not normal for werfault.exe (Windows Problem Reporting) to lock non-executable files, so this is likely a side-effect of something else. You can try to disable the Windows Problem Reporting service, or uninstall NOD32 and re-enable Windows Defender and see if the problem goes away.
2020-01-14 at 14:14 #22247It’s not normal for werfault.exe (Windows Problem Reporting) to lock non-executable files, so this is likely a side-effect of something else. You can try to disable the Windows Problem Reporting service, or uninstall NOD32 and re-enable Windows Defender and see if the problem goes away.
Nod32’s protection was paused for 4 hours. I don’t know how to stop completely windows problem reporting…
-
AuthorPosts