Read the same instructions without playing the video, or jump back to the part you need.
CHAPTER 01 · 0:00
Install the dependencies an app needs
PisoTrack Runtime Installer groups common application runtime packages in one interface. This reference-screen guide follows scan, selection, installation, and verification. Start with the dependency your application actually needs rather than assuming every error requires every package.
Scan installed runtimes
Choose required packages
Verify the original application
CHAPTER 02 · 0:19
Run a fresh system scan
Open Runtimes and select Scan. Wait for the detection process to finish, then read the status on each package card. The installed counts in this reference screen are examples; your machine may need a different set.
Open Runtimes
Select Scan
Read the detected status
CHAPTER 03 · 0:33
Match the package to the application
Check the runtime family, version, and architecture required by the application. A sixty-four-bit PC can still run a thirty-two-bit program that needs its own x86 runtime. Keep existing versions that other programs may still depend on.
Check runtime family and version
Match the required architecture
Review installed versus missing
CHAPTER 04 · 0:50
Prefer a deliberate selection
Check the required package cards and choose Install Selected. Install All is broader, so use it only when the full set is intended. Make sure Uninstall Mode is off when your goal is to add dependencies.
Check the needed packages
Review the selection
Choose Install Selected
CHAPTER 05 · 1:04
Allow required downloads and installers
Some packages are bundled or cached, while others may require a download. Allow the required access and wait for installer results. Do not assume all packages work offline or that the first successful item means the entire selection finished.
Packaged or cached files may be used
Some packages need internet
Wait for each installer result
CHAPTER 06 · 1:21
Read the log and save useful details
Open Console Logs and review each package outcome. Copy Logs or Save to TXT preserves useful details for support. If an installer reports a restart requirement, complete it during maintenance before checking the final package state again.
Review success or failure
Copy Logs or Save to TXT
Keep the exact error message
CHAPTER 07 · 1:37
Use Uninstall Mode deliberately
Uninstall Mode changes the operation to removal for supported installed packages. Other applications may depend on those runtimes. Use it only for a specific maintenance reason, and review selected items before starting the removal operation.
Existing apps may depend on runtimes
Only supported items can be removed
Review before starting removal
CHAPTER 08 · 1:54
Test the application that needed help
After installation and any required restart, rescan if needed and launch the application that prompted the task. Confirm the original error is resolved. If it remains, use the exact message to investigate the next cause rather than repeatedly installing unrelated packages.
Guides reviewed 24 September 2026. Check current plans before subscribing. Walkthroughs use reference screenshots; they do not show your own connected PC.