Unexpected Internal Software Issue (EX_SOFTWARE)

[B6692]

I am trying to install the templates in VS 2022 using the command: dotnet new install Microsoft.AspNetCore.Components.Templates. But I get the error with exit code 70, although I don't think it is only related to this command:

Error reading JObject from JsonReader. Path '', line 1, position 18.
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Microsoft.TemplateEngine.JExtensions.ReadObject(IPhysicalFileSystem fileSystem, String path)
at Microsoft.TemplateEngine.Edge.BuiltInManagedProvider.GlobalSettings.GetInstalledTemplatePackagesAsync(CancellationToken cancellationToken) at Microsoft.TemplateEngine.Edge.BuiltInManagedProvider.GlobalSettingsTemplatePackageProvider.InstallAsync(IEnumerable1 installRequests, CancellationToken cancellationToken) at Microsoft.TemplateEngine.Cli.TemplatePackageCoordinator.EnterInstallFlowAsync(InstallCommandArgs args, CancellationToken cancellationToken) at Microsoft.TemplateEngine.Cli.Commands.InstallCommand.ExecuteAsync(InstallCommandArgs args, IEngineEnvironmentSettings environmentSettings, TemplatePackageManager templatePackageManager, InvocationContext context) at Microsoft.TemplateEngine.Cli.Commands.BaseCommand1.InvokeAsync(InvocationContext context)

What is possibly wrong here?

[marcpopMSFT]

This issue is being closed as not actionable. It may be a question that was answered, lacks sufficient information to reproduce, or is a duplicate of another issue.

The dotnet/templating repository has been consolidated into dotnet/sdk. If this is still an issue, please open a new issue in dotnet/sdk with a complete reproduction.

Triage details

Summary: User asks for help with a JSON parse error when running dotnet new install, likely caused by a corrupted local settings file.

Reasoning: This is a user support question ('What is possibly wrong here?') about a corrupted JSON settings file causing an install error. There are no repro steps beyond the error, zero community interest (0 upvotes, 0 comments), no labels, and no maintainer engagement. The issue is nearly 3 years old with no activity since creation. This belongs on Stack Overflow or GitHub Discussions, not as a tracked work item.