DisplayCAL and Profileloader icon load sometimes won’t launch

[beepilyboopilydoopy]

I have a strange behavior on my laptop where sometimes DisplayCAL and Profileloader icon won’t launch until either I restart the laptop once or several times, or go through a series of certain steps before and after restart. Could this be due to Comodo Firewall blocking network connections during the first minute of windows startup? I haven’t uninstalled the firewall to see what happens, because it happens maybe once a week since I usually enter sleep mode each night without restarting, so I’d have to go without the firewall for a week to see if the problem stops.

Sometimes the Profileloader icon doesn’t show up on clean startup, or disappears when waking from Modern Standby Sleep. Fast Startup and Hibernate are deactivated. When this problem happens, Profileloader service is running in the background but the icon is missing and when i try to launch it from the start menu, the log shows the error “Not starting another instance.”  When this happens, DisplayCAL also will not launch when I try from Startmenu and then the logfile stops at “Loading” and “Lockfile”.

Sometimes if I restart once or several times, the problem goes away and both DisplayCAL and Profileloader icon will launch again.

Other times, if I restart but Profileloader icon still doesn’t show, the log will stop at “Existing client using port 15411, Connecting to 15411…”

Other times, no matter how many times I restart, Profileloader icon still doesn’t show. In this case, I must attempt to launch DisplayCAL which fails to launch, then restart again. Then Profileloader icon will show up, but the icon is grayscale because it thinks DisplayCAL is running (maybe because of the lockfile from the previous failed launch attempt from DisplayCAL). Then I must launch DisplayCAL and then close it immediately. Then the Profileloader icon will change to colored.

Below, you can see the log where the laptop woke itself up from modern standby at 4:00 in the morning. Profileloader logs the error “Not starting another instance”. When I wake the laptop at 13:14, the Profileloader icon disappeared.

At 18:30 I attempt to launch DisplayCAL but it fails and logs “Loading” and “Lockfile”.

I restart the laptop at 18:31, and the Profileloader icon appears again but in grayscale. At 18:32 I launch DisplayCAL then immediately close it. Then the Profileloader icon changes to colored.

2021-04-07 04:00:01,947 Not starting another instance.
2021-04-07 13:14:11,410 ================================================================================
2021-04-07 13:14:11,410 DisplayCAL-apply-profiles.exe 3.8.9.3 2019-12-14T12:19:18.994Z
2021-04-07 13:14:11,440 Windows 10 Pro Version 2009 Build 19042.867 x86_64
2021-04-07 13:14:11,440 Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
2021-04-07 13:14:11,440 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
2021-04-07 13:14:11,460 Faulthandler 3.2
2021-04-07 13:14:12,252 wxPython 4.0.6 msw (phoenix) wxWidgets 3.0.5
2021-04-07 13:14:12,253 Encoding: cp437
2021-04-07 13:14:12,253 File system encoding: mbcs
2021-04-07 13:14:12,253 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.ini
2021-04-07 13:14:12,253 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.ini
2021-04-07 13:14:12,263 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
2021-04-07 13:14:12,263 Existing client using port 15411
2021-04-07 13:14:12,263 Connecting to 15411...
2021-04-07 18:31:17,892 ================================================================================
2021-04-07 18:31:17,901 DisplayCAL-apply-profiles.exe 3.8.9.3 2019-12-14T12:19:18.994Z
2021-04-07 18:31:17,924 Windows 10 Pro Version 2009 Build 19042.867 x86_64
2021-04-07 18:31:17,924 Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
2021-04-07 18:31:17,924 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
2021-04-07 18:31:17,931 Faulthandler 3.2
2021-04-07 18:31:18,562 wxPython 4.0.6 msw (phoenix) wxWidgets 3.0.5
2021-04-07 18:31:18,562 Encoding: cp437
2021-04-07 18:31:18,562 File system encoding: mbcs
2021-04-07 18:31:18,582 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.ini
2021-04-07 18:31:18,584 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.ini
2021-04-07 18:31:18,604 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
2021-04-07 18:31:18,604 Existing client using port 15411
2021-04-07 18:31:18,604 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.lock
2021-04-07 18:31:18,614 Connecting to 15411...
2021-04-07 18:31:58,591 Connection to 127.0.0.1:15411 failed: [Errno 10061] No connection could be made because the target machine actively refused it
2021-04-07 18:31:59,236 Imported existing <module 'comtypes.gen' from 'C:\Program Files (x86)\DisplayCAL\lib\library.zip\comtypes\gen\__init__.pyc'>
2021-04-07 18:31:59,236 Using writeable comtypes cache directory: 'c:\users\username\appdata\local\temp\comtypes_cache\DisplayCAL-apply-profiles-27'
2021-04-07 18:31:59,375 INFO: Scheduled task "\Microsoft\Windows\WindowsColorSystem\Calibration Loader" has already been disabled.
2021-04-07 18:31:59,375 SUCCESS: The parameters of scheduled task "\Microsoft\Windows\WindowsColorSystem\Calibration Loader" have been changed.
2021-04-07 18:31:59,375 Installing SIGINT handler
2021-04-07 18:31:59,438 Setting up scripting host at 127.0.0.1:51612
2021-04-07 18:31:59,438 C:\Program Files (x86)\DisplayCAL\lib\library.zip\DisplayCAL\profile_loader.py:2066: Warning: Registry access failed: [Windows Error 5] Access is denied: HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration
2021-04-07 18:31:59,438 Display configuration change detection took 0.000000 ms
2021-04-07 18:31:59,438 --------------------------------------------------------------------------------
2021-04-07 18:31:59,438 Enumerating display adapters and devices:
2021-04-07 18:31:59,438
2021-04-07 18:31:59,736 Buggy video driver detected: AMD Radeon(TM) Graphics. Gamma ramp hack activated.
2021-04-07 18:31:59,891 Buggy video driver detected: AMD Radeon(TM) Graphics. Gamma ramp hack activated.
2021-04-07 18:32:00,048 AMD Radeon(TM) Graphics
2021-04-07 18:32:00,048 |- Lenovo Display 1920x1080 (deactivated)
2021-04-07 18:32:00,048 |- 1. 24G2W1G4 @ -1350, 0, 1350x2400
2021-04-07 18:32:00,048 AMD Radeon(TM) Graphics
2021-04-07 18:32:00,048 |- 2. DELL U2515H @ 0, 0, 2560x1440 [PRIMARY]
2021-04-07 18:32:00,313 Caching gamma ramps for profile 24G2W1G4 #2 2021-01-21 20-06 2.2 M-S XYZLUT+MTX s5 regbled 485047-08
2021-04-07 18:32:00,345 Caching gamma ramps for profile U2515H #3 2021-01-20 23-26 2.2 M-S XYZLUT+MTX s5 wled 100-99-100-16
2021-04-07 18:32:00,345 Detected DisplayCAL. Calibration loading disabled.
2021-04-07 18:32:33,431 No longer detecting DisplayCAL. Calibration loading enabled.



2021-04-07 18:30:23,157 ================================================================================
2021-04-07 18:30:23,157 DisplayCAL.exe 3.8.9.3 2019-12-14T12:19:18.994Z
2021-04-07 18:30:23,157 Windows 10 Pro Version 2009 Build 19042.867 x86_64
2021-04-07 18:30:23,157 Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
2021-04-07 18:30:23,157 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
2021-04-07 18:30:23,157 Faulthandler 3.2
2021-04-07 18:30:23,236 wxPython 4.0.6 msw (phoenix) wxWidgets 3.0.5
2021-04-07 18:30:23,236 Encoding: cp437
2021-04-07 18:30:23,236 File system encoding: mbcs
2021-04-07 18:30:23,236 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.ini
2021-04-07 18:30:23,236 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
2021-04-07 18:32:19,989 ================================================================================
2021-04-07 18:32:19,989 DisplayCAL.exe 3.8.9.3 2019-12-14T12:19:18.994Z
2021-04-07 18:32:19,989 Windows 10 Pro Version 2009 Build 19042.867 x86_64
2021-04-07 18:32:19,989 Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
2021-04-07 18:32:19,989 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
2021-04-07 18:32:20,005 Faulthandler 3.2
2021-04-07 18:32:20,255 wxPython 4.0.6 msw (phoenix) wxWidgets 3.0.5
2021-04-07 18:32:20,255 Encoding: cp437
2021-04-07 18:32:20,255 File system encoding: mbcs
2021-04-07 18:32:20,255 Loading C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.ini
2021-04-07 18:32:20,255 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
2021-04-07 18:32:20,255 Existing client using port 51612
2021-04-07 18:32:20,255 Lockfile C:\Users\username\AppData\Roaming\DisplayCAL\DisplayCAL.lock
2021-04-07 18:32:20,457 Imported existing <module 'comtypes.gen' from 'C:\Program Files (x86)\DisplayCAL\lib\library.zip\comtypes\gen\__init__.pyc'>
2021-04-07 18:32:20,457 Using writeable comtypes cache directory: 'c:\users\username\appdata\local\temp\comtypes_cache\DisplayCAL-27'
2021-04-07 18:32:20,755 Starting up...
2021-04-07 18:32:20,927 Audio module: pyglet 1.2.2
2021-04-07 18:32:23,168 Enumerating display devices and communication ports...
2021-04-07 18:32:23,170 C:\Users\username\AppData\Roaming\DisplayCAL\dl\Argyll_V2.1.2\bin
2021-04-07 18:32:28,051 ArgyllCMS 2.1.2
2021-04-07 18:32:28,052 Argyll has virtual display support
2021-04-07 18:32:28,052 ...ok.
2021-04-07 18:32:28,240 Checking video card gamma table access for display 1...
2021-04-07 18:32:28,515 Verify: 'test.cal' IS loaded (discrepancy 0.0%)
2021-04-07 18:32:28,604 ...ok.
2021-04-07 18:32:28,605 Checking video card gamma table access for display 2...
2021-04-07 18:32:28,871 Verify: 'test.cal' IS loaded (discrepancy 0.0%)
2021-04-07 18:32:28,963 ...ok.
2021-04-07 18:32:28,963 Initializing GUI...
2021-04-07 18:32:29,413
2021-04-07 18:32:30,960 ...ok.
2021-04-07 18:32:30,964 Ready.
2021-04-07 18:32:31,226 Setting up scripting host at 127.0.0.1:15411
2021-04-07 18:32:31,384 Check for application update...
2021-04-07 18:32:31,740 DisplayCAL is up-to-date.
2021-04-07 18:32:32,051 ArgyllCMS is up-to-date.
2021-04-07 18:32:32,905 Executing BaseApp.OnExit()
2021-04-07 18:32:32,905 Running application exit handlers
2021-04-07 18:32:32,907 Waiting for thread ScriptingHost.ConnectionHandler to exit
2021-04-07 18:32:33,032 ScriptingHost.ConnectionHandler exited
2021-04-07 18:32:33,032 Exiting DisplayCAL
2021-04-07 18:32:33,272 Ran application exit handlers

[beepilyboopilydoopy]

I haven’t been able to resolve this issue.

Once in a while, could be either when waking from sleep, or from a fresh boot up on a windows 10 pro 19042 notebook, the profile loader tray icon doesn’t show, but the service is running in the background. I cannot tell if the profiles are loading or if they’re being reapplied automatically.

Restarting doesn’t seem to get Profile Loader icon to show up.

Attempting to end it in Task Manager doesn’t end it.

During this time, if I try to run DisplayCAL, no splashscreen or window shows up, but task manager shows it running in the background. Restarting without first ending a stuck DisplayCAL process in task manager doesn’t fix the Profile Loader icon and the stuck DisplayCAL.

The only thing that seems to work for me is to first run DisplayCAL and get it stuck, then end DisplayCAL in task manager. Then restart. Then the Profile Loader icon shows up but grayed out. Then run DisplayCAL again and it actually shows the splashscreen and main window. Close DisplayCAL normally. And now the Profile Loader icon is colored and profiles are loaded.

On the next few restarts, everything works normally. But after several more restarts or wake from sleep, the problem happens all over again.

[beepilyboopilydoopy]

A couple of times, most recently today, DisplayCAL would not launch at all and Profile Loader would not show the tray icon, no matter how many times I attempted to end task the process / restart computer. I tried 5 times. Eventually I have to uninstall, restart, reinstall, to get it to work again.

[beepilyboopilydoopy]

This was still a problem for me.

The only reliable solution I could find when the profile loader tray icon doesn’t show or DisplayCAL would not launch is to run Microsoft / Sysinternals Process Explorer (possibly as admin), suspend profile loader process, delete both the displaycal and profile lock files, and restart the computer.  If the profile loader was not suspended, I could not delete the lock files. It would just throw the error ” The process cannot access the file because it is being used by another process.”.

[beepilyboopilydoopy]

For anyone wanting to use Sysinternals Process Explorer to fix this problem, here is a screenshot.

• Run Sysinternals Process Explorer as administrator
• Select DisplayCAL-apply-profiles.exe
• Right click DisplayCAL-apply-profiles.lock
• Select Close Handle
• Now you can go to your DisplayCAL folder and delete DisplayCAL-apply-profiles.lock
• Restart

Attachments:

You must be logged in to view attached files.

[Author]

Posts