Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais
Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.
Solved Arquivadas

Unable to open a specific URL in private mode from the command line

Firefox Ligações
tomhonour replied 10 meses atrás
Levedura
Levedura

I'm having trouble opening urls in a private window from the command line on Windows 11.

Firefox version: 144.0.2

Starting a new private window works fine with "C:\Program Files\Mozilla Firefox\firefox.exe" -private-window

But doing: "C:\Program Files\Mozilla Firefox\firefox.exe" -private-window "https://www.google.com"

just opens the link in the last selected window if the last window selected is non private it just opens the link there instead of a new or existing private window

I have also tried with no success: "C:\Program Files\Mozilla Firefox\firefox.exe" -private "https://www.google.com"

I'm having trouble opening urls in a private window from the command line on Windows 11. Firefox version: 144.0.2 Starting a new private window works fine with "C:\Program Files\Mozilla Firefox\firefox.exe" -private-window But doing: "C:\Program Files\Mozilla Firefox\firefox.exe" -private-window "https://www.google.com" just opens the link in the last selected window if the last window selected is non private it just opens the link there instead of a new or existing private window I have also tried with no success: "C:\Program Files\Mozilla Firefox\firefox.exe" -private "https://www.google.com"

Todas as respostas (2)

SuMo Bot
SuMo Bot

Solução escolhida

See if this works. 

   firefox --private-window "https://example.com"
tomhonour
tomhonour

I'm also experiencing this issue and quoting the URL doesn't solve it.

Looks like it's a known bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1977140

Modificado por tomhonour a