1) http://forums.lenovo.com/t5/IdeaPad-Y-and-U-series-Laptops/y550p-Color-Calibration-settings-ignored-after-restart/td-p/202531/page/2

2) Pasted from

It turns out it wasn’t, and perhaps isn’t, Windows 7′s fault. It looks like some cards, particularly Intels, load their own gamma parameters whether you like it or not. So, in my case what I was seeing was on boot the colors come up correctly via Windows 7′s color management (without having to use “ColorVisionStartup” to load the LUT for my custom profile), however a few seconds later it would get overridden with the uncalibrated profile.

Well I did some digging and it became clear that the problem seemed to be something starting up after Windows 7 loaded the LUT. Moreover if I set the RGB gamma in Intel GMA control panel to bizarro values and rebooted, well low and behold those bizarro gamma values were the ones getting shoved in after the correct custom profile.

So that pretty much cinched it that Intel’s driver was mangling the LUT. More Googles later and I ran into this:

> just wanted to tell how I stopped losing the gamma when I restart the computer. I learned from this blog to uncheck igfxpers.exe from the autorun. > (Start > Run… > msconfig > Startup) > http://neosmart.net/blog/2007/windows-vist…amma-table-bug/

From:

http://www.neowin.net/forum/index.php?showtopic=808104

And oddly enough, disabling “igfxpers.exe” via “msconfig” does the trick. This makes sense – Windows 7 loads the LUT at boot, later as you’re logging in “igfxpers.exe” starts up and trashes you LUT.

Now, for most PCs, disabling “igfxpers.exe” is said to be safe, however been warned for UMPCs it seems to be used to switch Intel GMA “Scheme”s at boot from low to high resolution and can cause problems if you disable it. However normal PCs should be a non-issue (to note, I ran the Intel GMA control panel to look up the “Scheme” info I just wrote and it just trashed my LUT again! – clearly it’s Intel’s stupid control stuff).

Anyway, now the problem seems to be finding a way to report this bug with Intel (to note some NVidia cards also seem to use “igfxpers.exe” causing similar problems). And if by some miracle I can find a way to report the problem, getting them to care is probably even harder!