Upgrade to 1903 monitor color profile not loading from cold boot

From a cold boot the color profile for my monitor won't load/work. If i go in color management and click reload current calibration i get a error: no more endpoints available from the endpoint mapper. So if i want it to work for now if i shutdown my pc once it boot into windows i have to reboot and its going to work properly and no error either even i reload the calibration. Its annoying having to reboot after the first boot everyday.

I don't know if its related or not i had a error with my printer after the upgrade i had to change the driver from PCL 6 to PCL 5 even if it was working fine with the PCL 6 driver before the upgrade otherwise it would print a error code with the document but would still print it anyway but was wasting paper just to print the error. Can't remember the entire error that was printed i only remember the first line was KERNEL with 2 other line under it that i can't remember and 0x0 as the last 4th line. If required i could always change the driver in the printer properties back to PCL 6.

I did try to use the default RPC Endpoint Mapper from Restore Default Services in Windows 10 but before i used it i had made a restore point and took a look mine and the default in notepad++ to see if there was any difference and the only thing that changed was a few hex number less in the default one which was changing C:\WINDOWS\system32\svchost.exe -k RPCSS -p to not have the -p good thing i had a restore point because i was not even able to boot into safe mode. I have no idea what the -p change but for now ill take having to reboot after a cold boot over not being able to boot at all.

I only upgrade to 1903 using the media creation tool to fix my windows that i had 2 different random BSOD and trying to repair using dism and sfc + and a boot drive i made using the tool trying the repair option in it which did not work and overall the system felt like it was getting slower the more i tried to fix it at the end even dism was acting weird finding nothing but stopping at 95.9% and saying it was complete and found nothing.

I have the same issue with my colormunki profile.

Cold boot = no profile is loaded.......reboot = profile is loaded. I believe this is a known issue with 1903.

I almost thought windows update had fix it this morning i had update to install when i shut it down last night. Boot the pc go do other things come back the profile is loaded so i tested it shutdown the pc to make sure but it was not fixed i guess it most have reboot after the install was complete while i was away.

I notice the same issue on my Lenovo laptop but find that simply logging off and on will fix it (until the next cold boot). It's faster than doing a full restart. The Night Light feature is also impacted by the bug (doesn't work) but it too is resolved by logging off/on. I hope it will be resolved soon.

Yes, night light doesn't work here either.......insomnia until it's fixed

Thanks for the tips about logging off/on having no other account on the machine i never think to use it. So much faster

It's a known issue and still not fixed with 1903.
I've left a few posts in the Geforce forums even though it's a Windows issue.
Workaround for now: Turn OFF Fast Startup to fix the cold boot issue.

However when you set your monitor to sleep after xx minutes, when the display awakes sometimes the ICC profile is not applied and sometimes it is. This problem seems random and it's hard to figure out the exact cause. Quite maddening going through this same issue again.

I don't know if any of you have experienced this with Fast startup OFF or maybe its not related to it but twice with a couple days apart which seem random when my computer was running for maybe 10 hours+ sometime in my case i would try to boot a game on steam and it would not boot. It would appear in the task manager barely using any memory i would end the process from there and retry and its still not working so next thing i try is to reboot steam which was unable to boot as well do the same process with steam still unable to boot after making sure it was completely shutdown in the task manager details tab same result. Then i try to close explorer.exe and reboot it to see if it fix it while explorer did launch other the same problem was still there unable to launch steam so i try game from other launcher either the launcher would not open or the game not start either. So since the rest of windows appear to be working i tried to sign out and sign in which would get stuck with a black screen with nothing happening force to hold the power button to shut it down.

So for now i am testing with fast startup back on and signing out and in to fix the color profile on cold boot to see if it happen. The second time i had forgot about it and did try to sign out again instead of restart it had happen and had 5 days apart. While i did not think to try other thing beside gaming related software during that issue i assume since windows was unable to sign out properly its not related to games and the last time an hour earlier i was playing just fine. I did look at the event viewer but the only recent thing that had problem was the fact that windows had not been able to properly shutdown. Also i did run sfc and dism and it found nothing. I have not run any anti virus yet but i highly doubt that i would have any i have not install anything new outside printer driver directly from HP.

I hope microsoft fix the list of known issue related to 1903 soon i run windows update almost everyday when i boot hoping for a update.

Cumulative Update KB4501375 Windows 10 v1903 build 18362.207 - June 27

"Addresses an issue that may cause Night light, Color Management profiles, or gamma correction to stop working after shutting down a device."

This update seems to have fixed the problem:

Restart: Profile kicks in as the UI loads

Cold start after shut down: Profile kicks in as the UI loads

Just noticed that the update is waiting to download but i stopped having problem from cold boot for almost a week now i think, its almost like there was a hotfix. Unless a nvidia driver update had fixed it, because i have no recent update in my windows update history and update KB4501375 as yet to be install.