A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Home Updater: Add Option to Uncompress portable apps that comes in zip/7zip/rar
Some portable apps are distributed in compressed format.
can we have an option to automaticaly uncompress in the portables folder if its an archive
Guest
Jul 14, 2025
Patch My PC’s current preview update method is inefficient because whenever users clear the TEMP folder regularly then all the unpacking of the portable app files, mostly DLL's and Json's are lost.
If the end user is on the default version (ex: v5.2.3.0) and switch over to the PREVIEW channel, then 01-5.2.3.1.exe gets downloaded and Update.exe to the Temp folder and when the TEMP folder is cleaned, this must happened again in the background to keep running the PREVIEW portable version.
See attached jpg file (screenshot).
A more robust portable app would manage its own update and dependency storage, not rely on the TEMP folder.
A better design would be for the portable app to manage its own subfolder for unpacked dependencies and updates, perhaps like this:
On first run, create a data or cache folder next to the EXE.
Unpack .NET DLLs and JSON there.
Download and store preview builds in a user-chosen or app-local folder.
Offer an option to “keep preview builds” or “choose update storage location”.
This would reduce unnecessary bandwidth use, improve transparency, and give users more control — all hallmarks of a well-designed portable app.
Patch My PC’s current preview update method is inefficient because whenever users clear the TEMP folder regularly then all the unpacking of the portable app files, mostly DLL's and Json's are lost.
If the end user is on the default version (ex: v5.2.3.0) and switch over to the PREVIEW channel, then 01-5.2.3.1.exe gets downloaded and Update.exe to the Temp folder and when the TEMP folder is cleaned, this must happened again in the background to keep running the PREVIEW portable version.
See attached jpg file (screenshot).
A more robust portable app would manage its own update and dependency storage, not rely on the TEMP folder.
A better design would be for the portable app to manage its own subfolder for unpacked dependencies and updates, perhaps like this:
On first run, create a data or cache folder next to the EXE.
Unpack .NET DLLs and JSON there.
Download and store preview builds in a user-chosen or app-local folder.
Offer an option to “keep preview builds” or “choose update storage location”.
This would reduce unnecessary bandwidth use, improve transparency, and give users more control — all hallmarks of a well-designed portable app.
Marking as planned as we are starting work on this now.