# \[Resolved\] Main & 6.0 Snapshots broken on Windows **URL:** \ **Category:** Windows\ **Created:** [August 9, 2024, 1:20am UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850 "2024-08-09T01:20:12Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 9, 2024, 1:20am UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/1 "2024-08-09T01:20:12Z")
UPDATE: The August 7th snapshots are now usable! The current (August 6th) x86\_64 snapshots for main and 6.0 are completely unusable on Windows. I uninstalled 5.10.1 (working great) and then ran the installer exe from [Swift.org - Install Swift](https://www.swift.org/install/windows/). A simple `swift --version` results in ```swift remark: In-process target-info query failed (open("LoadLibraryW failure: 126")). Using fallback mechanism. ``` Then a prompt from swift-frontend.exe ![image](https://global.discourse-cdn.com/swift/original/3X/e/a/ea0511ee31da3580638d53e100f91fc57e51fafb.png) And then an additional line in the console: ```swift error: frontend job retrieving target info failed with code 309: ``` What's going on? ---
**Author:** ![stevapple](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/stevapple/32/31979_2.png) [@stevapple](https://forums.swift.org/u/stevapple)\ **Post date:** [August 9, 2024, 5:31am UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/2 "2024-08-09T05:31:03Z")
Swift 6.0 adds a bunch of new libraries to the toolchain (part of Swift toolchain modularization, I would say). For tarballs we’re simply copying the whole built directory, but Windows installer (WiX) requires a list of files to collect, so most added files will appear in the Windows installer a few days later, causing frequent breakage on the toolchain. I do agree that we need to add full testing on the **Windows installer package** , instead of the built toolchain, before a toolchain is released. ---
**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:** [August 9, 2024, 3:54pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/3 "2024-08-09T15:54:22Z")
This was broken recently with some changes that @Douglas_Gregor made, and then @Alex_L fixed subsequently. I suspect that we haven't had a newer release (CC: @mishal_shah). @stevapple yes, a simple smoke test would be great (e.g. building a docker container with the installer and building say swift-win32 and running its test suite within the container). We do this in the builds that we do at The Browser Company, but have not managed to integrate that into the Apple CI. ---
**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\ **Post date:** [August 9, 2024, 4:09pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/4 "2024-08-09T16:09:47Z")
> [@compnerd](#): > > This was broken recently with some changes that @Douglas_Gregor made, and then @Alex_L fixed subsequently. I suspect that we haven't had a newer release (CC: @mishal_shah). > > @stevapple yes, a simple smoke test would be great (e.g. building a docker container with the installer and building say swift-win32 and running its test suite within the container). Is there a way to derive the list of libraries for WiX from CMake, since CMake is the source of truth for what libraries we're linking? Yes, we can throw a specialized CI job at it, but better to define away the problem if we can. Doug ---
**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:** [August 9, 2024, 4:13pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/5 "2024-08-09T16:13:13Z")
No, unfortunately that is not. Furthermore, we do not perform the proper installation in CMake either, and until we can completely change the build and install process for the toolchain and all it’s components, I fear that CMake is not a good source for the information. ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 10, 2024, 11:51pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/6 "2024-08-10T23:51:48Z")
Well folks, I wonder if a band-aid patch in the interim is in order... It would be very useful to run the latest and greatest Swift on Windows. ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 13, 2024, 6:09pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/7 "2024-08-13T18:09:19Z")
Can someone suggest a place to open an issue to get a new Windows snapshot posted to [swift.org](http://swift.org)? @mishal_shah? ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 14, 2024, 9:29pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/8 "2024-08-14T21:29:46Z")
Can anyone in here suggest how to successfully use a new Swift 6.0 or Main snapshot? Where should I raise the issue? [GitHub - swiftlang/swift: The Swift Programming Language](https://github.com/swiftlang/swift)? ---
**Author:** ![dschaefer2](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dschaefer2/32/46516_2.png) [@dschaefer2](https://forums.swift.org/u/dschaefer2)\ **Post date:** [August 15, 2024, 2:18pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/9 "2024-08-15T14:18:01Z")
Depends on what's crashing. I've been successfully using the x86\_64 Windows toolchain from Aug 7 on swift-package-manager. ARM has a compiler crash that I've raised against `swiftlang/swift`. Anything else you can raise on `swiftlang/swift-package-manager` and I can reroute as necessary. I'm currently working on making the Window swiftpm better and would love to hear if there are issues I'm not running into. ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 15, 2024, 5:09pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/10 "2024-08-15T17:09:54Z")
Take a look at my original post up top. That's the issue I'm running into with the August 7th distribution from [swift.org](http://swift.org). ---
**Author:** ![dschaefer2](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dschaefer2/32/46516_2.png) [@dschaefer2](https://forums.swift.org/u/dschaefer2)\ **Post date:** [August 15, 2024, 5:50pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/11 "2024-08-15T17:50:23Z")
Yes please raise an issue on `swift` since it appears to be the compiler frontend crashing. ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 15, 2024, 5:52pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/12 "2024-08-15T17:52:00Z")
@compnerd claims the issue has been fixed actually, but we just need a newer release posted. Where do I ask for that? ---
**Author:** ![dschaefer2](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dschaefer2/32/46516_2.png) [@dschaefer2](https://forums.swift.org/u/dschaefer2)\ **Post date:** [August 15, 2024, 5:57pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/13 "2024-08-15T17:57:11Z")
That'll come when the builds pass. But I'm confused why it's working for me. Mind you I'm running Windows 11 ARM in Parallels. I'll double check on a x86 machine we have around here. ---
**Author:** ![dschaefer2](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dschaefer2/32/46516_2.png) [@dschaefer2](https://forums.swift.org/u/dschaefer2)\ **Post date:** [August 15, 2024, 6:23pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/14 "2024-08-15T18:23:01Z")
Nope, works for me there too. I can run `swift --version` and get ```swift Swift version 6.0-dev (LLVM 73a346c9caf32cc, Swift 3e21fc6610cc917) Target: x86_64-unknown-windows-msvc ``` I still suggest raising an issue and capturing your configuration so we can see what's different. ---
**Author:** ![gregcotten](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gregcotten/32/13288_2.png) [@gregcotten](https://forums.swift.org/u/gregcotten)\ **Post date:** [August 15, 2024, 6:29pm UTC](https://forums.swift.org/t/resolved-main-6-0-snapshots-broken-on-windows/73850/15 "2024-08-15T18:29:11Z")
Indeed you're right. It must have been the August 6th snapshots that were failing which were the latest available at the time of my posting. I've updated the original post to reflect this.