On the Visual Studio 2026 build image, declaring services: - mongodb in appveyor.yml fails to start MongoDB:

Starting MongoDB
Start-Service : Cannot find any service with service name 'MongoDB'.
At line:1 char:1
+ Start-Service 'MongoDB'
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (MongoDB:String) [Start-Service], ServiceCommandException
    + FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.StartServiceCommand

This error doesn't fail the build outright, but MongoDB never actually starts, causing any test relying on a real DB connection to hang and time out downstream.

Per the pre-installed software docs, MongoDB 8.2.3 is listed as bundled on this image, but no Windows service named MongoDB appears to be registered for it — unlike older images (2015/2017/2019/2022), where services: - mongodb works as documented (services docs).

Reproduction:
- appveyor.yml: image: Visual Studio 2026 + services: - mongodb (see our appveyor.yml file here: https://github.com/romualdnave/sails-mongo/blob/upgrade-mongodb-dri...) - Full build log: https://ci.appveyor.com/project/mikermcneil/sails-mongo/builds/5470...

Is this a known gap in the 2026 image's provisioning, or is there a different service name / setup expected on this image now?