# Latest (Oct 2, 2025) Windows nightly toolchain DOA? **URL:** \ **Category:** Windows\ **Tags:** windows, toolchain\ **Created:** [October 31, 2025, 7:04pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977 "2025-10-31T19:04:16Z")\ **Posts on this page:** 7\ **Page:** 1
**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:** [October 31, 2025, 7:04pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/1 "2025-10-31T19:04:16Z")
Hello, I don't know where else to post this, but I installed the latest main nightly Swift Windows toolchain (October 2, 2025) and there appears to be an issue with the toolchain's command line ```swift PS C:\Users\jenkins> swift --version PS C:\Users\jenkins> swift build --help PS C:\Users\jenkins> swift build --build-tests PS C:\Users\jenkins> swift --help PS C:\Users\jenkins> ``` Restarting did not fix the issue. The toolchain is a month old. Has this been fixed/addressed? I created [swiftlang/swift#85252](https://github.com/swiftlang/swift/issues/85252) to track it > > > \### Description > > Hello, > > I installed the latest main nightly Swift Windows tool…chain (October 2, 2025) and there appears to be an issue with the toolchain's command line > \`\`\` > PS C:\\Users\\jenkins\\workspace\\swift\_oss\\swift-package-manager-functionality-matrix\\swift-package-manager\> swift --version > PS C:\\Users\\jenkins\\workspace\\swift\_oss\\swift-package-manager-functionality-matrix\\swift-package-manager\> swift build --help > PS C:\\Users\\jenkins\\workspace\\swift\_oss\\swift-package-manager-functionality-matrix\\swift-package-manager\> swift build --build-tests > PS C:\\Users\\jenkins\\workspace\\swift\_oss\\swift-package-manager-functionality-matrix\\swift-package-manager\> swift --help > PS C:\\Users\\jenkins\\workspace\\swift\_oss\\swift-package-manager-functionality-matrix\\swift-package-manager\> > \`\`\` > > Restarting did not fix the issue. > > For what it's worth, I was running on MacOS Host with Windows installed in a Parallel Desktop VM. > > > > > > > \### Reproduction > > 1. Install the toolchain, > 2. Run any \`swift\` command. > > > \### Expected behavior > > The command executes as expected > > \### Environment > > \*\*Device Specifications:\*\* > \`\`\` > Device name JENKINS711F > Processor Apple Silicon (3.20 GHz) (8 processors) > Installed RAM 32.0 GB > Device ID B6D617E7-B0D5-4838-8FF9-981C8A22CC94 > Product ID 00331-20250-33879-AA139 > System type 64-bit operating system, ARM-based processor > Pen and touch Pen support > \`\`\` > > \*\*Windows Specifications:\*\* > \`\`\` > Edition Windows 11 Pro > Version 24H2 > Installed on ‎6/‎12/‎2025 > OS build 26100.6899 > Experience Windows Feature Experience Pack 1000.26100.253.0 > \`\`\` > > \### Additional information > > \_No response\_ Cheers, Sam ---
**Author:** ![compnerd](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/compnerd/32/2165_2.png) [@compnerd](https://forums.swift.org/u/compnerd)\ **Post date:** [October 31, 2025, 8:04pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/2 "2025-10-31T20:04:43Z")
Hi @bkhouri, Yes, it seems that a new library was added and missed in the distribution. While the CI has been stable for Windows, the nightly builds have not been produced due to other issues. @mishal_shah should be able to give more details on that. I know that I and others are also waiting on a new toolcahin snapshot. Hopefully we get one soon! Saleem ---
**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:** [November 3, 2025, 4:14pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/3 "2025-11-03T16:14:35Z")
A few questions: 1. This is not the first time I encountered this symptom([swiftlang/swift#80356](https://github.com/swiftlang/swift/issues/80356)). What strategy is in place to ensure we don't re-introduce this behaviour when a new library will be added in the future? 2. Do we know what is preventing a new Windows nightly toolchain? ---
**Author:** ![compnerd](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/compnerd/32/2165_2.png) [@compnerd](https://forums.swift.org/u/compnerd)\ **Post date:** [November 3, 2025, 4:56pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/4 "2025-11-03T16:56:36Z")
> [@bkhouri](#): > > - This is not the first time I encountered this symptom([swiftlang/swift#80356](https://github.com/swiftlang/swift/issues/80356)). What strategy is in place to ensure we don't re-introduce this behaviour when a new library will be added in the future? The best option is to actually consider using [GitHub - thebrowsercompany/swift-build: Swift toolchain builds by The Browser Company · GitHub](https://github.com/thebrowsercompany/swift-build) for your toolchain needs as that is currently being smoke tested and did catch this issue when it occurred. That CI is much more open and allows you to see what is happening on the releases. IMIO, in general, you should be testing your toolchain on all the platforms when you add a new library. > [@bkhouri](#): > > 1. Do we know what is preventing a new Windows nightly toolchain? No, we do not know what is going on there. The nightly release process on [swift.org](http://swift.org) is not public and you would need to ask @mishal_shah about the details. ---
**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:** [November 5, 2025, 5:26pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/5 "2025-11-05T17:26:02Z")
@mishal_shah , @compnerd : The November 3 nightly windows toolchain image is still unusable due to [Nighty Windows toolchain is not usable · Issue #85252 · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/issues/85252) When can we expect a fix for this? ---
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [November 5, 2025, 5:31pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/6 "2025-11-05T17:31:51Z")
Do we know which change introduced this regression? ---
**Author:** ![compnerd](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/compnerd/32/2165_2.png) [@compnerd](https://forums.swift.org/u/compnerd)\ **Post date:** [November 5, 2025, 5:32pm UTC](https://forums.swift.org/t/latest-oct-2-2025-windows-nightly-toolchain-doa/82977/7 "2025-11-05T17:32:49Z")
> [@mishal\_shah](#): > > Do we know which change introduced this regression? I don't remember the PR, but it was the one that Doug made to the swift-syntax repo to introduce a new type of construct.