M
mr_slyfox
In every case of us running a Windows Server 2016 virtual machine (using VMware, if that matters) the "Downloaded Maps Manager" service does not start correctly during boot. If I manually start the service, it will sometimes show up again as having failed and being stopped.
I know how to set the service to "Disabled" or "Manual" startup type, but I want to know what it does, what applications tried to use it, and why it is failing. I have not found a log anywhere that answers the second and third questions, and I have only read speculation online about what the service does.
The best answer I've heard about what the service does is that it is "leftover" from Windows 10, since Windows 10 has built-in location services such as Cortana and an actual "Maps" application that might use this service. But this seems strange that a Windows 10 service somehow got ported over to Windows Server 2016. Could Microsoft really not have customized their build of Windows Server 2016 to not include unnecessary fluff from Windows 10? If that is the case, what other services or programs are "left over" from Windows 10 that should be disabled or removed?
Please only answer if you have actual information to add to the discussion, or if you have authority to represent Microsoft and clarify what decisions were made and why, as far as Windows Server 2016 product development is concerned.
Regards,
Sly Fox
Continue reading...
I know how to set the service to "Disabled" or "Manual" startup type, but I want to know what it does, what applications tried to use it, and why it is failing. I have not found a log anywhere that answers the second and third questions, and I have only read speculation online about what the service does.
The best answer I've heard about what the service does is that it is "leftover" from Windows 10, since Windows 10 has built-in location services such as Cortana and an actual "Maps" application that might use this service. But this seems strange that a Windows 10 service somehow got ported over to Windows Server 2016. Could Microsoft really not have customized their build of Windows Server 2016 to not include unnecessary fluff from Windows 10? If that is the case, what other services or programs are "left over" from Windows 10 that should be disabled or removed?
Please only answer if you have actual information to add to the discussion, or if you have authority to represent Microsoft and clarify what decisions were made and why, as far as Windows Server 2016 product development is concerned.
Regards,
Sly Fox
Continue reading...