We had reports that a Bonsai startup or install failure can be caused by an empty global NuGet configuration at %appdata%\NuGet\NuGet.Config. This mostly affects people upgrading from older Bonsai versions or running PowerShell 5.1 or earlier, where cmdlets such as Install-Module can create an empty <configuration /> file that then prevents Bonsai from generating its default configuration. The upstream cause is described in NuGet/Home#12809.
The workaround is to delete %appdata%\NuGet\NuGet.Config so that Bonsai can recreate a correct default the next time it starts.
This should be added to the installation page at https://bonsai-rx.org/docs/articles/installation.html so anyone affected can resolve it themselves. The underlying detect-and-repair fix is tracked in bonsai-rx/bonsai#2329; this issue covers the documentation only.
We had reports that a Bonsai startup or install failure can be caused by an empty global NuGet configuration at
%appdata%\NuGet\NuGet.Config. This mostly affects people upgrading from older Bonsai versions or running PowerShell 5.1 or earlier, where cmdlets such asInstall-Modulecan create an empty<configuration />file that then prevents Bonsai from generating its default configuration. The upstream cause is described in NuGet/Home#12809.The workaround is to delete
%appdata%\NuGet\NuGet.Configso that Bonsai can recreate a correct default the next time it starts.This should be added to the installation page at https://bonsai-rx.org/docs/articles/installation.html so anyone affected can resolve it themselves. The underlying detect-and-repair fix is tracked in bonsai-rx/bonsai#2329; this issue covers the documentation only.