Loading Profile broken by Windows 10 ?

Home Forums Help and Support Loading Profile broken by Windows 10 ?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #25410

    Walt Wright
    Participant
    • Offline

    I’ve been using DisplayCAL successfully for a couple of months now. A few days ago I noticed my displays didn’t match, and further investigation seems to show that the profiles are no longer being loaded. DisplayCAL *thinks* they are, and does not report any errors, however if I unload and re-load the profiles there is no difference at all to my displays. Previously (until a week or so ago), the difference was very visible. There have been some major Windows 10 updates recently. Wondering if that could have broken something in the profile loader? Is there any way I can diagnose what is going on? Some logfiles perhaps? Not sure where to start to try and fix this.

    • This topic was modified 3 years, 8 months ago by Walt Wright.
    #25412

    Walt Wright
    Participant
    • Offline

    Further update after locating the logfiles. It looks like a permissions problem on the registry?

    2020-07-07 14:20:06,900 DisplayCAL-apply-profiles.exe 3.8.9.3 2019-12-14T12:19:18.994Z
    2020-07-07 14:20:06,900 Windows 10 Home Version 2004 Build 19041.329 x86_64
    2020-07-07 14:20:06,900 Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
    2020-07-07 14:20:06,900 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
    2020-07-07 14:20:06,915 Faulthandler 3.2
    2020-07-07 14:20:07,040 wxPython 4.0.6 msw (phoenix) wxWidgets 3.0.5
    2020-07-07 14:20:07,040 Encoding: cp850
    2020-07-07 14:20:07,040 File system encoding: mbcs
    2020-07-07 14:20:07,040 Loading C:\Users\Walter\AppData\Roaming\DisplayCAL\DisplayCAL.ini
    2020-07-07 14:20:07,040 Loading C:\Users\Walter\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.ini
    2020-07-07 14:20:07,040 Lockfile C:\Users\Walter\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
    2020-07-07 14:20:07,040 Existing client using port 15411
    2020-07-07 14:20:07,040 Connecting to 15411…
    2020-07-07 14:20:07,040 Connected to 15411
    2020-07-07 14:20:07,040 Getting instance name
    2020-07-07 14:20:07,040 Sent scripting request, awaiting response…
    2020-07-07 14:20:07,040 Got response: ‘DisplayCAL-apply-profiles’
    2020-07-07 14:20:07,040 Closing existing instance
    2020-07-07 14:20:07,040 Sent scripting request, awaiting response…
    2020-07-07 14:20:07,243 Got response: ”
    2020-07-07 14:20:07,243 Waiting for existing instance to exit and delete lockfile C:\Users\Walter\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.lock
    2020-07-07 14:20:07,306 Existing instance exited.
    2020-07-07 14:20:07,545 Imported existing <module ‘comtypes.gen’ from ‘C:\Program Files (x86)\DisplayCAL\lib\library.zip\comtypes\gen\__init__.pyc’>
    2020-07-07 14:20:07,545 Using writeable comtypes cache directory: ‘c:\users\walter\appdata\local\temp\comtypes_cache\DisplayCAL-apply-profiles-27’
    2020-07-07 14:20:07,681 INFO: Scheduled task “\Microsoft\Windows\WindowsColorSystem\Calibration Loader” has already been disabled.
    2020-07-07 14:20:07,681 SUCCESS: The parameters of scheduled task “\Microsoft\Windows\WindowsColorSystem\Calibration Loader” have been changed.
    2020-07-07 14:20:07,681 Reloading C:\Users\Walter\AppData\Roaming\DisplayCAL\DisplayCAL-apply-profiles.ini
    2020-07-07 14:20:07,681 Installing SIGINT handler
    2020-07-07 14:20:07,763 Setting up scripting host at 127.0.0.1:15411
    2020-07-07 14:20:07,767 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
    2020-07-07 14:20:07,767 Display configuration change detection took 0.000000 ms

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS