Collection / Studio / Motion
← Windows

How to Import Apps with WinGet on a New PC

This page explains the simple WinGet import workflow after you already have an exported app list file from another Windows setup.

Start here

Start with the fastest command or direct open action

This block comes first on purpose. Copy one command, open PowerShell, Windows Terminal, Run, or Start search, paste the exact text, press Enter, then do the slower click-by-click checks underneath only if you still need them.

Import app list from JSON
Run this in: Windows Terminal or PowerShell Admin: No
winget import -i apps.json

What this command does

Reads a saved package list and starts reinstalling matching apps from that file.

What to do after running it

Let the installs finish, then sign in to the apps you care about and check for anything that still needs manual setup.

Import with a full path
Run this in: Windows Terminal or PowerShell Admin: No
winget import -i "C:Users%USERNAME%Desktopapps.json"

What this command does

Reads a saved package list and starts reinstalling matching apps from that file.

What to do after running it

Let the installs finish, then sign in to the apps you care about and check for anything that still needs manual setup.

Check WinGet before import
Run this in: Windows Terminal or PowerShell Admin: No
winget --version

What this command does

Runs the exact Windows action used in this guide so you do not have to guess the wording.

What to do after running it

Check the exact Windows page or result this guide mentions before moving to the next step.

Overview

What this guide helps you do

Importing a saved WinGet package list can speed up new PC setup and reduce how many apps you reinstall by hand.

  • Importing restores app installs faster, not your personal files inside those apps.
  • Package availability can change over time.
  • You may still need to handle a few apps manually.

When to use this

When to use this guide

Useful after a clean Windows install, on a replacement PC, or when standardizing a repeatable software setup.

Before you start

What to review first

Some apps still need manual sign-in, licensing, or additional setup after installation. The import only helps with the install part.

Do this exactly

Open the right Windows area first, then follow the changes one by one

  1. Copy the exported WinGet JSON file to the new PC first. A Desktop folder or a dedicated setup folder works fine.
  2. Press Start, type Terminal, and open Windows Terminal. You can use the regular terminal first unless your setup specifically requires administrator rights.
  3. If the JSON file is in the current folder, type winget import -i apps.json and press Enter. If it is elsewhere, use the full-path version from this page.
  4. Read the prompts and let WinGet install what it can. Some apps may still ask for sign-in, permissions, or extra setup afterward.
  5. When the import finishes, open the most important apps you need and verify that they actually launched and kept working on the new PC.

Exact click path

Tell the user exactly what to open and press

Do not change ten things at once. Open the exact Windows page first, make one clear change, then check whether it solved the problem before moving on.

Fast open: Copy your saved apps.json file to the new PC, open Windows Terminal, then type winget import -i apps.json and press Enter. If the file is on the Desktop or another folder, use the full-path version from the command card so WinGet can find it correctly.

Try a faster path

Useful after a clean Windows install, on a replacement PC, or when standardizing a repeatable software setup.

How to use

Some apps still need manual sign-in, licensing, or additional setup after installation. The import only helps with the install part.

Related pages

Keep going with the next useful page

Use these links when you want the matching script, another Windows help page, or a browser tool for the same job.

FAQ

Questions about How to Import Apps with WinGet on a New PC

Do I need the same Windows version?

Not always, but matching Windows setups usually makes the flow cleaner and reduces package differences.

Can WinGet import everything exactly the same?

No. It helps automate a lot of app installs, but some packages or settings still need manual work.