cc @compnerd

I suspect that the crux of the issue is that there is something wrong with your package setup, and that is causing a diagnostic to be emitted. However, the diagnostic cannot be emitted because you do not have the English language available.

The RegQueryValue calls are not from the Swift compiler or Swift runtime, we do not call into the registry directly ever. The likely places where this is occurring is either Foundation or Swift Package Manager. I would suspect that this is more likely SPM, with the path being in swift-tools-support-core with something related to paths. What is also interesting is that there is no call to `FormatMessage` that I could see that would require the English language support. I wonder if this is a Swift standard library issue?

+@abertelrud @neonichu @millenomi

One thing that may be useful is to set a conditional breakpoint on RegQueryValue and see what is calling into it.

Comment by Stefan Springer (JIRA)

I suspect that the crux of the issue is that there is something wrong with your package setup, and that is causing a diagnostic to be emitted

On macOS, no error is committed when running `swift build -c release` for the package, even after removing `/Users/<user>/Library/Caches/org.swift.swiftpm`. And the repository and the dependent repositories are really simple. And there are no non-ASCII characters in the filenames. I think the packages are OK.

Comment by Stefan Springer (JIRA)

I think the packages are OK.

Aha, you seem to be right, after starting Windows again, indeed an error war printed (Swift wanted to have swift-tools-version:5.4.0 instead of 5.3), I fixed that (also in the dependant repositories and changed "target" to "executableTarget" to avoid warnings). So I think the problem persist that SPM is not working correctly on Windows when no English language is present (and you have errors?).

BTW: Now SPM says "Dependencies could not be resolved because no versions of 'SwiftXMLParser' match the requirement 0.1.18..<1.0.0 and root depends on 'SwiftXMLParser' 0.1.18..<1.0.0" which is not correct. OK, that has nothing to do with the issue described here (but still a main point for me since I cannot build on Windows 🙁 ).

Comment by Stefan Springer (JIRA)

Update: When trying again, SPM again gets stuck with the mentioned errors in Process Monitor. Seems to be a sporadic thing? (I did not change anything in the Windows settings, and no restart of Windows).

Comment by Stefan Springer (JIRA)

Any progress on this issue? I now tried Swift version 5.6-dev, and swift build seems to go a little bit further now, displaying "Computing version for ..." but then again stuck and doing nothing, meanwhile displaying errors in Process Monitor: swift.exe: RegQueryValue / BUFFER TOO SMALL, swift.exe: RegQueryValue / BUFFER OVERFLOW, etc. etc.. What can I do to make Swift (with SPM) usable on Windows? Any idea? Thanks!

Comment by Stefan Springer (JIRA)

See a newer discussion on a new Swift forums entry.

Comment by Stefan Springer (JIRA)

Some of the issues I ran into were solved by things that should be documented on the Getting Started page, see the new ticket #SR-15125 for suggestions of what to add there.

Still remains one issue for me, see the new ticket #SR-15126.

For this ticket: I do not know if the above BUFFER OVERFLOW errors are related my persisting problem or if they are somehow substantial. But somehow I think there should not be those errors.

This warning is not from the Swift tooling but from other processes on the host. There is nothing that we can do here.

Comment by Stefan Springer (JIRA)

This warning is not from the Swift tooling but from other processes on the host. There is nothing that we can do here.

The process monitor says that it is coming from swift.exe. But OK; I am not an expert here.