# Windows setup failures

**URL:** <https://forums.swift.org/t/windows-setup-failures/83660>\
**Category:** Windows\
**Tags:** toolchain, help-needed\
**Created:** [December 10, 2025, 7:36pm UTC](https://forums.swift.org/t/windows-setup-failures/83660 "2025-12-10T19:36:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkhouri](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/bkhouri/32/45895_2.png) [@bkhouri](https://forums.swift.org/u/bkhouri)\
**Post date:** [December 10, 2025, 7:36pm UTC](https://forums.swift.org/t/windows-setup-failures/83660/1 "2025-12-10T19:36:49Z")

</div>

Hello,

I'm configured a Windows 11 VM running in Parallels Desktop in on macOS.

When following the instructions on [Swift.org](http://Swift.org), I encounter the following error

```swift
PS C:\Mac\Home\Documents\git\public\swiftlang\swift-build> winget install --id Microsoft.VisualStudio.2022.Community --exact --force --custom "--add Microsoft.VisualStudio.Component.Windows11SDK.22621 --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.VisualStudio.Component.VC.Tools.ARM64"
Failed when searching source: msstore
An unexpected error occurred while executing the command:
0x8a15005e : The server certificate did not match any of the expected values.

The following packages were found among the working sources.
Please specify one of them using the --source option to proceed.
Name Id Source
-------------------------------------------------------------------------
Visual Studio Community 2022 Microsoft.VisualStudio.2022.Community winget

```

Is this an issue with my VM, the command on Windows 11, or something else?

Thanks,

Sam

---

<div class="post-metadata">

**Author:** ![bkhouri](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/bkhouri/32/45895_2.png) [@bkhouri](https://forums.swift.org/u/bkhouri)\
**Post date:** [December 10, 2025, 7:37pm UTC](https://forums.swift.org/t/windows-setup-failures/83660/2 "2025-12-10T19:37:59Z")

</div>

I was able to workaround the issue with

```swift
winget settings --enable BypassCertificatePinningForMicrosoftStore

```