First-time installation requires executing the IoT Inspector launcher twice

[crazyideas21]

Feature

• New functionality with network package processing for IoT traffic
• UI/UX improvements
• Performance enhancements
• Other (elaborated below)

Describe the feature you'd like During the initial installation process, I like that IoT Inspector can be launched from a shortcut without manually configuring things. However, one major pain point is that after installing uv, the installer currently requires the user to close the terminal window and then re-run the shortcut. While I personally understand why this is needed (an environment refresh is required after uv installation), the instructions are not clear to an average technical user.

For someone with only average technical capabilities, it may not make sense why the terminal must be closed and reopened just to continue running the program. This can create confusion at a critical first step.

I suggest improving the UI/UX in one of the following ways:

1. Make instructions clearer. After uv is installed, explicitly clear the screen (e.g., inject ~50 empty lines) and display a very clear message such as:

   Installation complete.
   Please close this window and relaunch IoT Inspector by clicking the shortcut again.
   

   This way, the instructions are obvious and not buried in other terminal output.

2. Automate the relaunch. Once uv is installed, the installer could automatically re-run itself in a new process and then terminate the original one. For example, if the user runs IoT Inspector via a PowerShell script, the script could:

   • Install uv
   • Call the same PowerShell script again in a fresh process
   • Close itself. This ensures that the second process has the correct environment variables and is already ready to run IoT Inspector, without the user doing anything.

Both approaches would make the process less confusing and more user-friendly.

Additional context Currently, when the user first runs IoT Inspector from a shortcut, the installer in the terminal window first installs uv. Because uv requires an environmental refresh, the installer asks the user to close the terminal and re-execute the same shortcut. While this works, the instructions are not very clear and can confuse users who are not familiar with environment refreshes.

• Problem: The need to manually close and re-run feels unintuitive.
• Impact: Users may get stuck during the first-time installation, wondering if something went wrong.
• Proposed fixes: Either make the message much clearer and visually obvious, or automate the relaunch so users don’t have to close/reopen anything manually.

This change would improve first-time usability, reduce confusion, and make the installation process feel more polished.

[AndrewQuijano]

Unfortunately, we can only really do this once we can sign the executable.

https://www.sectigo.com/knowledge-base/detail/CODE-SIGNING-APPLICATIONS-USING-SIGNTOOL-WITH-CODE-SIGNING-CERTIFICATE/kA0Uj0000003Nph

Also, when following this guide, make sure to update your PATH to include the path:
C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64