In Windows, colour support is very passive, nothing like the active colour management capabilities of ColorSync on Mac OS X. From what I know, the Windows CMM is basically just a pre-installed software library that's called under the control of applications needing it to perform colour management functions. But that's not necessarily all that common. For most people running an Adobe Photoshop or Lightroom workflow with application-managed colour, they are by default using the Adobe-supplied ACE CMM. As another example, Qimage also uses its own included CMM (if I recall based on LittleCMS). The Firefox browser doesn't use Windows CMM either, as far as I know it has its own. Etc.
There are many CMM's and the Windows-included one is only one of them, nor does Windows in any way force that theirs is the one used by applications. So as it nets out for people taking even a slightly active role in colour managed output on Windows, I suspect there are relatively few situations where people would be relying on Windows' internal colour capabilities.
Even in the cases where the Windows CMM would be used for something, I'm still curious what problem Microsoft thinks they are solving by blocking the installation of ICC profiles...