In later versions of micromamba for Windows, it's expected the install system has the VS C++ compiler on path. There's a few options for us to consider here:

• Can we rollback Micromamba to before there was need for a Windows compiler?
• Including the installer as part of the Windows build?
• Install it for Windows when trying to install a plugin?

Some context from James on our previous history with VCRedist

RE: VCRedist, this is not surprising, but it is frustrating. We used to have to do this for InVEST as a part of our NSIS installed (not sure if it was technically legal for us to do so, though), so maybe we will just need to figure out vcredist installation as a part of the micromamba install?
Related discussion on github, along with a scripted solution

I was able to use the following script silently, except that it prompted a pop up of whether I wanted to allow this program to make changes to my comptuer.

Invoke-WebRequest -URI "https://aka.ms/vs/17/release/vc_redist.x64.exe" -OutFile "$env:Temp\vc_redist.x64.exe"; Start-Process "$env:Temp\vc_redist.x64.exe" -ArgumentList "/quiet /norestart" -Wait; Remove-Item "$env:Temp\vc_redist.x64.exe"