Images

Vcpkg easy to use and widely used to manage project dependencies. Having vcpkg available via visual studio workloads would help developer productivity.

A windows image for Windows Server 2022 Cuda, that also includes VS 2022. A GPU in the image would also be immensely helpful for testing.

Much like how MacOS has System Integration Protection (SIP) and how CircleCI already provide support (see https://circleci.com/docs/2.0/testing-macos/#supported-xcode-and-macos-versions ), it would be great for us to support Test-signing for Windows images too. References: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/introduction-to-test-signing https://docs.microsoft.com/en-us/windows-hardware/drivers/install/test-signing

Currently, the windows image is updated every ~ 30days . This can sometimes lead to a breaking change. We would like the ability to pin to a specific version of a windows image.

Install Visual Studio Spectre-mitigated libraries https://devblogs.microsoft.com/cppblog/spectre-mitigations-in-msvc/ "Microsoft.VisualStudio.Component.VC.Runtimes.ARM.Spectre", "Microsoft.VisualStudio.Component.VC.Runtimes.ARM64.Spectre", "Microsoft.VisualStudio.Component.VC.Runtimes.x86.x64.Spectre", "Microsoft.VisualStudio.Component.VC.v141.ARM.Spectre", "Microsoft.VisualStudio.Component.VC.v141.ARM64.Spectre", "Microsoft.VisualStudio.Component.VC.v141.x86.x64.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.ATL.ARM.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.ATL.ARM64.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.ATL.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.MFC.ARM.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.MFC.ARM64.Spectre", "Microsoft.VisualStudio.Component.VC.14.26.MFC.Spectre"

Add Windows Driver Kit to the default CircleCI windows image https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk

No shell prompt "$" is shown when users SSH into a Windows machine using the bash terminal.It is currently a known issue that no prompt appears when a user reruns and connects to a job via SSH: https://support.circleci.com/hc/en-us/articles/360044419354-SSH-into-Windows-with-bash-This can be quite confusing and is not documented in the Enable SSH step of a build. Hopefully this would be a straightforward fix! CCI-I-1663

The CircleCI's official Windows image shows the latest version of Windows Server and Visual Studio are supported. There are cases where users want to build on an older OS or Visual Studio, so I want customers to be able to create and build their own AMI. CCI-I-1623

Some customers would like to test on older versions of Visual Studio, such as Visual Studio 2015 and 2017 Build Tools, for backwards compatibility. It's not currently possible as there is only one Windows image available. CCI-I-1532

It would be good to have a Windows 2019 Server that has Chrome installed on it. There is a large class of browser-based end to end (e2e) testing that can be supported on Windows Server 2019 if the Chrome browser can run. This is because the Chrome browser can be invoked HEADLESS so that no display is needed and e2e tests with Selenium or Protractor can run successfully. However, the list in https://circleci.com/docs/2.0/hello-world-windows/#software-pre-installed-in-the-windows-image , shows that currently on the 'Windows Server 2019 with VS 2019' machine, Chrome is not installed. This is currently the only Windows image available for use in CircleCI. This is a request to add Chrome to the installed software or to provide another Windows server image that hasChrome on it. Thanks, CCI-I-1311