Color Management is broken (GetICMProfile always returns WCS Default Device Profile)
Hi, It looks that color management logic is changed and many many graphics apps are not compatible with color management logic of Windows 11, Windows Server 2022, Windows Server vNext. There are quite a few references in internet: https://techcommunity.microsoft.com/t5/windows-11/windows-11-color-management-not-working-chrome-on-secondary/m-p/2869159 https://www.reddit.com/r/Windows11/comments/qg8dcg/for_those_of_you_going_crazy_over_icc_profiles/ https://community.adobe.com/t5/photoshop-ecosystem-discussions/color-management-not-working-with-photoshop-and-windows-11/m-p/12469301 https://www.eizoglobal.com/support/compatibility/software/win/windows11/ In short GetICMProfile Win32 API method doesn't return the expected value anymore on mentioned systems. I'm quite surprised to see no comment from Microsoft as the color management is very important aspect of OS Functionality. It might be that Microsoft is deprecating GetICMProfile in favor of WcsGetDefaultColorProfile, but there are so many apps in the wild that already use old method, so I don't think it a wise decision and so far looks more like an issue that has not been noticed by Microsoft yet.
ICM fails on call back to local PC
Hi there. I've an odd issue with Powershell. I discovered that I cannot ICM from the domain controller to a remote workstation - and I also cannot ICM from the actual workstation PC console back to itself. This had been properly configured & working until... (Recent details: We had an SBS 2008 DC, migrated to WS2019. When I finally transferred DNS & DHCP and took the old server offline is when the ICM problem began. Before the SBS 2k8 came offline and the two DCs were still replicating AD & etc., I could ICM from the WS2019 DC with no problem.) Not sure what to make of it. On a side note, the DHCP snap-in strips the domain from the server name and replaces it with 'mshome.net' no matter how many times I delete it and add it back in - and does not allow any interaction. But the Get-DHCPServer(...) cmdlets report all the correct settings, scope, exclusions, etc. - so I've ignored this for the most part.) -------------------------------- Back to the initial question, this is an example of events pulled from WinRM / ICM where the client & destination are the same computer: Thinking perhaps User & Computer domain mismatch? Any ideas? Thanks! P.S. This might be correlated - RDP attempt from the DC to remote PC. Strange error since the DC is the computer being used, but says the DC can't be contacted for NLA.
