Using Windows Agent Causes Failure When Create artifact from portal

### Release version

LATEST

### Question Details

I wanted to use the windows extractor file locally in an Azure DevOps repo rather than calling out to the internet with the Git URL. To use this, I must also set the Pool Image to windows-latest as using windows agents in Azure DevOps. But by doing this I'm constantly getting a pipeline error (extractor pipeline) ##[error]--output was unexpected at this time , ##[error]Script has output to stderr. Failing as failOnStdErr is set to true.

When using windows-latest and only using the windows extractor.exe file, are there any other amendments that need to be made?

### Expected behavior

All stages pass in pipeline

### Actual behavior

Failing at 'Set Extraction Variables'

### Reproduction Steps

Change to windows-latest
Run windows extractor file locally rather than using git URL

Inizia con la fase “Set Extraction Variables” della pipeline dell’estrattore e con l’extractor.exe di Windows usato localmente sull’agente windows-latest. Confronta il comportamento della pipeline con la configurazione documentata dell’agente Windows e determina quale modifica alla configurazione evita gli errori “--output was unexpected at this time” e stderr; il lavoro è completato quando tutte le fasi della pipeline vengono superate.

Scritto dal modello di indicizzazione a partire dal testo della issue.