Build tools bug: nuget restore fails with "Illegal characters on path" if you already have NuGet 5 or later on your PATH #1400

Closed
opened 2026-01-30 22:25:06 +00:00 by claunia · 4 comments
Owner

Originally created by @metathinker on GitHub (May 29, 2019).

Environment

Terminal repo commit: 8baba4b46c
NuGet installed from Chocolatey:

  • C:\ProgramData\chocolatey\bin on PATH
  • Running nuget in a fresh command prompt yields NuGet Version: 5.0.2.5988

Reproduction steps

  1. Open a cmd.exe command prompt and use cd to go to your Terminal repo working copy.
  2. Run this command: tools\razzle.cmd & nuget restore

Results

Expected results: NuGet should tell you all the packages are installed already
Actual results: NuGet fails with the error message Illegal characters on path

The run of NuGet by razzle.cmd itself is not affected by this issue, but it could be a problem if you need to run NuGet again after a git clean or similar, especially if and when the checked-in NuGet 4 binary in the repo is removed!

Originally created by @metathinker on GitHub (May 29, 2019). ### Environment Terminal repo commit: 8baba4b46c39999038582345ff63d0adb341b1a2 NuGet installed from Chocolatey: - C:\ProgramData\chocolatey\bin on PATH - Running `nuget` in a fresh command prompt yields `NuGet Version: 5.0.2.5988` ### Reproduction steps 1. Open a cmd.exe command prompt and use `cd` to go to your Terminal repo working copy. 1. Run this command: `tools\razzle.cmd & nuget restore` ### Results _Expected results:_ NuGet should tell you all the packages are installed already _Actual results:_ NuGet fails with the error message `Illegal characters on path` The run of NuGet by `razzle.cmd` itself is not affected by this issue, but it could be a problem if you need to run NuGet again after a `git clean` or similar, especially if and when the checked-in NuGet 4 binary in the repo is removed!
claunia added the Resolution-Fix-CommittedIssue-BugProduct-MetaArea-Build labels 2026-01-30 22:25:06 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (May 29, 2019):

This sounds like a NuGet bug?

@DHowett-MSFT commented on GitHub (May 29, 2019): This sounds like a NuGet bug?
Author
Owner

@metathinker commented on GitHub (May 29, 2019):

This sounds like a NuGet bug?

Yeah, but the workaround is so simple that I made a PR in this repo (#1046) to fix it. I'll also file a bug against NuGet.

@metathinker commented on GitHub (May 29, 2019): > This sounds like a NuGet bug? Yeah, but the workaround is so simple that I made a PR in this repo (#1046) to fix it. I'll also file a bug against NuGet.
Author
Owner

@metathinker commented on GitHub (May 29, 2019):

... and here's the NuGet bug: https://github.com/NuGet/Home/issues/8168

@metathinker commented on GitHub (May 29, 2019): ... and here's the NuGet bug: https://github.com/NuGet/Home/issues/8168
Author
Owner

@DHowett-MSFT commented on GitHub (May 29, 2019):

Thanks for the report and the timely fix!

@DHowett-MSFT commented on GitHub (May 29, 2019): Thanks for the report and the timely fix!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1400