If the binPath isn't quoted, sc.exe will first look for a file at C:\Program.Starting that will yield CreateProcess error 193 (aka invalid Win32 program).By properly quoting the binPath, we guarantee that the correct file will be loaded.

The primary reason is that Component Detection(https://github.com/microsoft/component-detection) pointed out that theversion we used is missing legal information.As ofclearlydefined/curated-data#23677, version6.2.1 of this package has a documented license. Therefore, this issueshould be hereby resolved.Besides, it's always good to stay up to date with dependencies.Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

The primary reason is that Component Detection(https://github.com/microsoft/component-detection) pointed out that theversion we used is missing legal information.Noticing thathttps://www.nuget.org/packages/LibGit2Sharp.NativeBinaries/2.0.278/Licenseshows only a link into the repository, but the full license is shown athttps://www.nuget.org/packages/LibGit2Sharp.NativeBinaries/2.0.322/Licensethis issue should be hereby resolved.Besides, it's always good to stay up to date with dependencies.Since libgit2 is very careful about backwards-compatibility (andtherefore LibGit2Sharp, too), this update should not result in anychange of behavior.Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Now that we addressed the Component Detection issues, let's just goahead and proactively update the remaining dependencies, too.Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Update dependencies

The v2 version of `upload-artifact`/`download-artifact` is no longersupported and stopped working. Let's update to v4, which _does_ work.Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Every once in a while, the GitHub Actions we use (such as `checkout`,`upload-artifact`, etc) require updates as the old versions stopworking.Let's ask Dependabot to take care of this tedious task.Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

`HttpClientHandler` will automatically resubmit an HTTP request thatfails in certain circumstances. One such circumstance is when`UseDefaultCredentials` is set to `true``, alternative credentials wereprovided on the request, and the request failed with "401 Unauthorized",then it will resubmit using the default credentials. If an exception isthrown when getting the default credentials that exception is nothandled, but is wrapped in `HttpRequestExceptio`n and thrown by`SendAsync` instead of returning the original response with the failingstatus code. See the following code snippet from `HttpWebRequest`:https://referencesource.microsoft.com/#System/net/System/Net/HttpWebRequest.cs,5535When this happens in GVFS, the result is that GVFS does not recognizethe failure as being authentication related, so it does not refresh thecredential. Instead, it loops through all its retries, and eventuallyfails the request. This is typically visible to users as a file systemexception (e.g. file not found) if the GVFS trigger was accessing avirtual file or other operation on an individual file, or various errors(including "this repository requires the GVFS protocol") for a `gitpull`. The symptoms will continue for the user until they remount theGVFS enlistment, which forces GVFS to refresh its credential.This commit adds an exception handler for `HttpRequestException`` to`client.SendAsync`, which attempts to find the original failed responseembedded in the inner exception properties. If it does so, it logs awarning and continues processing using the original failed response,which will trigger the logic for handling the various possible statuscodes. If it can't extract the original failed response, then it willlet the exception bubble up.Signed-off-by: Tyrie Vella <tyrielv@gmail.com>Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

…argumentsPoint GVFS.Service to the correct executable when C:\Program exists

Handle nested failures in HttpRequestException

Bumps [actions/setup-dotnet](https://github.com/actions/setup-dotnet) from 1 to 4.- [Release notes](https://github.com/actions/setup-dotnet/releases)- [Commits](actions/setup-dotnet@v1...v4)---updated-dependencies:- dependency-name: actions/setup-dotnet  dependency-type: direct:production  update-type: version-update:semver-major...Signed-off-by: dependabot[bot] <support@github.com>

Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 4.- [Release notes](https://github.com/actions/checkout/releases)- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)- [Commits](actions/checkout@v2...v4)---updated-dependencies:- dependency-name: actions/checkout  dependency-type: direct:production  update-type: version-update:semver-major...Signed-off-by: dependabot[bot] <support@github.com>

Bumps [microsoft/setup-msbuild](https://github.com/microsoft/setup-msbuild) from 1.0.2 to 2.0.0.- [Release notes](https://github.com/microsoft/setup-msbuild/releases)- [Changelog](https://github.com/microsoft/setup-msbuild/blob/main/building-release.md)- [Commits](microsoft/setup-msbuild@v1.0.2...v2.0.0)---updated-dependencies:- dependency-name: microsoft/setup-msbuild  dependency-type: direct:production  update-type: version-update:semver-major...Signed-off-by: dependabot[bot] <support@github.com>

…ions/setup-dotnet-4build(deps): bump actions/setup-dotnet from 1 to 4

…ions/checkout-4build(deps): bump actions/checkout from 2 to 4

…rosoft/setup-msbuild-2.0.0build(deps): bump microsoft/setup-msbuild from 1.0.2 to 2.0.0

[Release] Milestones M195