<?php http_response_code(404); exit; ?>
a:2:{s:3:"sig";s:32:"927aa6a53d2ebe17b7e7fcaba9e758c9";s:5:"posts";a:20:{i:0;a:15:{s:4:"slug";s:14:"7-zip-portable";s:5:"title";s:14:"7-Zip Portable";s:4:"date";s:16:"2026-10-21 09:50";s:7:"updated";s:16:"2026-10-23 15:48";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:9:"Utilities";}s:11:"description";s:0:"";s:5:"image";s:59:"/~daemondevin/portableapps/uploads/2026/10/7-zip-9b5911.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:31:"7-Zip Portable v26.04 released!";s:5:"words";i:1573;s:7:"minutes";i:8;s:5:"plain";s:4000:"7 zip portable v26.04 released < more 7 zip portable 7 zip portable is a portable build of 7 zip https://www.7 zip.org/ , the open source file archiver by igor pavlov. one package carries the x86, x64 and arm64 builds, runs the one that is native to the computer, and keeps itself up to date. it's built with the portableapps compiler https://github.com/daemondevin/pac man pac man : every change it makes to windows is recorded first and undone when 7 zip closes, or on the next launch if something went wrong. download downloads are in the releases section https://github.com/daemondevin/7 zipportable/releases/latest . the package is in portableapps.com https://portableapps.com/ format, so it installs into the portableapps.com platform or any folder you like. features the full 7 zip file manager, plus the 7 zip command line and gui tools. native on every pc: x86, x64 and arm64 builds in one package. arm64 pcs run the arm64 build instead of x64 under emulation. see builds builds updates itself: checks the official 7 zip releases at start and updates all three builds. a failed or interrupted update keeps the version you had. see updates updates leaves nothing behind: file associations, the explorer context menu and the sendto shortcut exist only while 7 zip runs. if 7 zip or the pc crashes, the next launch cleans up before it starts. no administrator rights: everything, the context menu included, is registered for the current user only. portable settings: 7 zip's settings travel with the package in data\settings , including the folder history when the drive letter changes. command line support: parameters passed to the launcher go to 7zg.exe , so 7 zipportable.exe a backup.7z myfolder works as it would with an installed 7 zip. see command line command line runs from a usb drive, a cloud folder or a hard drive. system requirements microsoft windows 10 or later: x86, x64 or arm64. portableapps.com platform https://portableapps.com/download optional . an internet connection for updates optional . configuration 7 zipportable.ini , next to the launcher 7 zipportable\7 zipportable.ini , holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\7 zipportable.ini over it. ini 7 zipportable additionalparameters= runlocally=false fileassociations=true shellextension=false updatecheck=true architecture=auto banner=false key values default what it does fileassociations true , false true "open with" entries for archive types while 7 zip runs. see associations associations . shellextension true , false , auto false the 7 zip menu in explorer's context menu while 7 zip runs. auto adds it only when no installed 7 zip already provides one. see context menu context menu . updatecheck true , false true check for a new 7 zip at start and offer to update. architecture auto , x86 , x64 , arm64 auto which build to run. auto picks the native one. banner true , false false show a banner while 7 zip starts. additionalparameters text empty extra command line switches passed to 7 zip. runlocally true , false false copy 7 zip to the temp folder and run it from there. builds the package holds three builds: folder build runs on app\7 zip x86 every windows pc app\7 zip64 x64 64 bit windows: x64, and arm64 under emulation app\7 ziparm64 arm64 arm64 windows the launcher runs the build that matches the architecture windows itself runs on, so an arm64 pc is told apart from an x64 one. if that build is missing, it falls back to the next one arm64, then x64, then x86 instead of failing to start. to force a build, set architecture=x86 , x64 or arm64 in 7 zipportable.ini . the arm64 build can only be forced on arm64 windows. updates with updatecheck=true , the launcher looks up the latest release on 7 zip's github page https://github.com/ip7z/7zip/releases each time it starts. when there's a newer version, or one of the three builds is missing in copies made before the arm64 build existed, for example , it asks before doing anyt";}i:1;a:15:{s:4:"slug";s:5:"about";s:5:"title";s:5:"About";s:4:"date";s:16:"2026-10-23 21:21";s:7:"updated";s:16:"2026-10-25 23:36";s:6:"status";s:9:"published";s:4:"type";s:4:"page";s:4:"tags";a:0:{}s:11:"description";s:0:"";s:5:"image";s:66:"/~daemondevin/portableapps/uploads/2026/10/portableapps-6d7527.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:158:"I build portable versions of Windows apps. This page explains how I do it, what I promise about every release, and how to stop Windows warning you about them.";s:5:"words";i:819;s:7:"minutes";i:4;s:5:"plain";s:4002:"i build portable versions of windows apps. this page explains how i do it, what i promise about every release, and how to stop windows warning you about them. what pac man is pac man stands for portableapps compiler & management . it is the launcher framework i use for my portable apps. it is built on top of the official portableapps.com launcher pal , not instead of it, and it is not associated with portableapps.com. if you have a problem with one of my launchers, please bring it to me and not to them. pal deliberately leaves out apps that need to reach deep into windows. pac man is for those. a launcher built with it can handle: windows services, scheduled tasks, dll and com registration, and device drivers registry and file system redirection, including 32 and 64 bit, plus fragile registry keys that are copied to a safe place before the app starts symlinks, junctions and hardlinks fonts that are installed when the app starts and removed when it closes firewall rules, java, ghostscript, qt and xml configuration cleanup of leftover files and folders after the app exits each of these is its own segment, and a launcher only contains the segments it turns on, so a simple app does not carry the weight of a complex one. when an app needs something unusual, there is a hook for custom code. the point of all of it is that the app behaves like a guest on your machine. it runs from its own folder or drive, and when you close it, your system goes back to how it was, even if the app crashed on the way out. my promise: no cracked software every release i publish is made from software obtained legitimately. that means: no cracks, keygens, patched binaries or license bypasses. ever. no repackaged pirated installers. if an app needs a license, you bring your own, or it ships as the vendor's own free or trial edition. the app itself is not modified to remove protections, ads, checks or telemetry unless the vendor allows it, and if i do change something, the release notes say so. what i add is the launcher. the pac man launcher, its settings and its cleanup are my work, and you can read what they do. if you ever find a release of mine that breaks this promise, tell me and i will pull it. signed releases and the warning you may see i sign my launchers with a code signing certificate, using the signing tools built into pac man. the signature proves two things: the file came from me, and it has not been changed since i signed it. if someone tampers with a release or passes off their own build as mine, the signature breaks. my certificate is not one that windows trusts out of the box, so the first time you run one of my launchers, windows may warn you about an unknown publisher. that warning is windows saying it does not know me yet. it is not saying the file is bad. stop the warnings if you trust my releases and want the warnings to go away, add my certificate to your certificate manager. 1. download the certificate: daemon.devin certificate https://envs.net/ daemondevin/portableapps/uploads/daemon.devin.p7b 2. check it is mine before you trust it. open the file, go to the details tab and compare the thumbprint with this one: 070f1dc3f30dd5da9beae822cf2de256b8ad434b . if they differ, do not install it. 3. press win + r , type certmgr.msc and press enter. this installs it for your account only. use certlm.msc to install it for every user on the pc, which needs administrator rights. 4. open trusted root certification authorities , right click certificates , choose all tasks → import , and pick the file i gave you. 5. repeat the import into trusted publishers . 6. run one of my launchers. the unknown publisher warning should be gone. a few honest notes: only do this if you trust me. a certificate in your trusted store tells windows to believe whatever is signed with it. that is the whole idea, and it is also why you should check the thumbprint and not take a certificate from anyone else's page. you can undo it any time. open the same store, find my ";}i:2;a:15:{s:4:"slug";s:30:"adobe-illustrator-cs3-portable";s:5:"title";s:30:"Adobe Illustrator CS3 Portable";s:4:"date";s:16:"2026-10-22 22:15";s:7:"updated";s:16:"2026-10-23 19:22";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:21:"Graphics and Pictures";}s:11:"description";s:0:"";s:5:"image";s:65:"/~daemondevin/portableapps/uploads/2026/10/illustrator-a3fc1f.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:40:"Adobe Illustrator CS3 Portable released!";s:5:"words";i:909;s:7:"minutes";i:5;s:5:"plain";s:4000:"adobe illustrator cs3 portable released < more a portable launcher for adobe illustrator cs3, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when illustrator closes, or on the next launch if something went wrong. the package doesn't include or handle illustrator's licensing: use it with a copy of illustrator cs3 you're licensed to run. pacman : https://github.com/daemondevin/pac man system requirements windows, 32 bit or 64 bit. illustrator cs3 is a 32 bit application. administrator rights for the launcher. illustrator itself runs with your normal rights see drag and drop drag and drop . data on a local drive a usb drive is fine; a network share isn't . see data data . portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/illustratorportable cs3 english.paf.exe drag and drop windows doesn't let explorer, or any other program running with normal rights, drag files into a program that runs as administrator. so a launcher that runs illustrator elevated also breaks drag and drop. the launcher still needs administrator rights, for the shared files in common files and program data and the language setting in the machine wide registry. but once it has set those up, it starts illustrator the way explorer would: with the rights of the signed in user, using explorer's own credentials. drag and drop from explorer, the desktop and other programs then works as it does with an installed illustrator. a second launch while illustrator runs opening a file from the portableapps.com platform, for example isn't elevated at all, so there's no uac prompt. it hands its files to the running illustrator. if the launcher was elevated with a different account's password a standard user typing an administrator's password , illustrator has to run as that administrator, and drag and drop from your own explorer can't work. signing in with an account that is an administrator avoids that. configuration illustratorportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\illustratorportable.ini over it. ini illustratorportable additionalparameters= disablesplashscreen=false runlocally=false productlanguage=en us key default what it does productlanguage en us the language adobe's shared code is told illustrator runs in, written the way adobe writes it en us , de de , fr fr and so on . it has to be a language the illustrator in the package has. additionalparameters empty extra command line switches passed to illustrator. disablesplashscreen false don't show the launcher's splash screen. runlocally false copy illustrator to the temp folder and run it from there, for read only media. changes made in that session aren't saved back. launching the package again while illustrator runs passes the files to the running illustrator. data while illustrator runs, these are linked into data with ntfs junctions, so nothing is copied back and forth: illustrator uses kept in %appdata%\adobe\adobe illustrator cs3 settings data\adobe illustrator cs3 settings %programdata%\adobe\adobe pdf data\adobe pdf common files\adobe\plug ins\cs3 data\commonfiles\plug ins\cs3 common files\adobe\typesupport data\commonfiles\typesupport common files\adobe\xmp\custom file info panels data\commonfiles\xmp\custom file info panels common files\adobe\help\en us\illustrator data\commonfiles\help\illustrator common files is the 32 bit one program files x86 \common files on 64 bit windows , which is where illustrator cs3 looks. if an installed adobe application already has one of these folders, it's moved aside for the session and put back when illustrator portable closes. close installed adobe applications before starting illustrator portable, so they don't run without their shared files in the meantime. important junctions can only point to a local d";}i:3;a:15:{s:4:"slug";s:28:"adobe-photoshop-cs3-portable";s:5:"title";s:28:"Adobe Photoshop CS3 Portable";s:4:"date";s:16:"2026-10-22 22:06";s:7:"updated";s:16:"2026-10-23 19:22";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:21:"Graphics and Pictures";}s:11:"description";s:0:"";s:5:"image";s:63:"/~daemondevin/portableapps/uploads/2026/10/photoshop-d93089.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:28:"Adobe Photoshop CS3 Portable";s:5:"words";i:892;s:7:"minutes";i:5;s:5:"plain";s:4000:"adobe photoshop cs3 portable < more a portable launcher for adobe photoshop cs3, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when photoshop closes, or on the next launch if something went wrong. the package doesn't include or handle photoshop's licensing: use it with a copy of photoshop cs3 you're licensed to run. pacman : https://github.com/daemondevin/pac man system requirements windows, 32 bit or 64 bit. photoshop cs3 is a 32 bit application. administrator rights for the launcher. photoshop itself runs with your normal rights see drag and drop drag and drop . data on a local drive a usb drive is fine; a network share isn't . see data data . portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/photoshopportable cs3 english.paf.exe drag and drop windows doesn't let explorer, or any other program running with normal rights, drag files into a program that runs as administrator. so a launcher that runs photoshop elevated also breaks drag and drop. the launcher still needs administrator rights, for the shared files in common files and the language setting in the machine wide registry. but once it has set those up, it starts photoshop the way explorer would: with the rights of the signed in user, using explorer's own credentials. drag and drop from explorer, the desktop and other programs then works as it does with an installed photoshop. a second launch while photoshop runs opening a file from the portableapps.com platform, for example isn't elevated at all, so there's no uac prompt. it hands its files to the running photoshop. if the launcher was elevated with a different account's password a standard user typing an administrator's password , photoshop has to run as that administrator, and drag and drop from your own explorer can't work. signing in with an account that is an administrator avoids that. configuration photoshopportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\photoshopportable.ini over it. ini photoshopportable additionalparameters= disablesplashscreen=false runlocally=false productlanguage=en us key default what it does productlanguage en us the language adobe's shared code is told photoshop runs in, written the way adobe writes it en us , de de , fr fr and so on . it has to be a language the photoshop in the package has. additionalparameters empty extra command line switches passed to photoshop. disablesplashscreen false don't show the launcher's splash screen. runlocally false copy photoshop to the temp folder and run it from there, for read only media. changes made in that session aren't saved back. data while photoshop runs, these are linked into data with ntfs junctions, so nothing is copied back and forth: photoshop uses kept in %appdata%\adobe\adobe photoshop cs3 settings, presets, actions data\appdata\adobe\adobe photoshop cs3 %appdata%\adobe\color data\appdata\adobe\color %appdata%\adobe\save for web data\appdata\adobe\save for web %appdata%\adobe\adobe pdf data\appdata\adobe\adobe pdf %appdata%\adobe\workflow data\appdata\adobe\workflow %localappdata%\adobe\color data\localappdata\adobe\color common files\adobe\adobe pcd , caps and backup data\commonfiles\adobe\... common files is the 32 bit one program files x86 \common files on 64 bit windows , which is where photoshop cs3 looks. a folder that data doesn't have yet is filled from app\defaultdata first. photoshop's registry settings hkcu\software\adobe\photoshop and hkcu\software\adobe\iac are kept in data\settings\hkcu.reg and iac.reg . they're loaded when photoshop starts and saved when it closes. if an installed adobe application already has any of these, it's moved aside for the session and put back when photoshop portable closes. close installed adobe applications before starting photos";}i:4;a:15:{s:4:"slug";s:13:"aimp-portable";s:5:"title";s:13:"AIMP Portable";s:4:"date";s:16:"2026-10-25 18:59";s:7:"updated";s:16:"2026-10-25 20:35";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:15:"Music and Video";}s:11:"description";s:0:"";s:5:"image";s:58:"/~daemondevin/portableapps/uploads/2026/10/aimp-1dcd9a.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"AIMP Portable v5.40.2722 released!";s:5:"words";i:965;s:7:"minutes";i:5;s:5:"plain";s:4000:"aimp portable v5.40.2722 released < more a portable launcher for aimp https://www.aimp.ru/ , the music player with its own audio library, audio converter and tag editor, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when aimp closes, or on the next launch if something went wrong. aimp isn't included: its license only allows aimp's original installer to be passed on. you add aimp yourself, once see adding aimp adding aimp . pacman : https://github.com/daemondevin/pac man system requirements windows 7 or later. portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/aimpportable 5.40.2722.paf.exe mirror https://drive.proton.me/urls/gg2rarhmnw 5yjskm4snsis adding aimp 1. download aimp from aimp.ru https://www.aimp.ru/?do=download . 2. run its installer and choose the portable install, into this package's app\aimp folder. or copy the program folder of an aimp that's already installed to app\aimp . 3. start aimpportable.exe . until aimp is there, the launcher says which folder to copy and where, offers to open the app folder, and stops. it checks for aimp.exe , aimp.runtime.dll and aimp.shared.dll , so a copy of only aimp.exe is caught too. an aimp.ini that comes with the copied program is taken over the first time; from then on the one in data is used, set to keep aimp's profile in the package. configuration aimpportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\aimpportable.ini over it. ini aimpportable additionalparameters= systemintegration=false key default what it does systemintegration false let aimp register itself with windows. see system integration system integration . additionalparameters empty extra command line switches passed to aimp. data aimp keeps everything in its profile. with usermode=0 in the aimp.ini next to aimp.exe , that profile is the profile folder beside it rather than %appdata%\aimp . both live in data and are moved into place while aimp runs: aimp uses kept in app\aimp\aimp.ini data\aimp.ini app\aimp\profile settings, playlists, audio library, skins you add data\profile recordings data\recorded when the package moves another drive letter, another folder , the paths stored in aimp's settings, tag editor and converter settings are updated to match. note aimp's audio library data\profile\audiolibrary\local.adb stores the full path of every file in it, in a format the launcher doesn't change. if your music is on the same drive as the package and that drive gets a different letter, rescan the library folders in aimp. system integration in its settings aimp can register itself with windows: as the player for file types, in explorer's right click menu, as an autoplay handler, and in default programs. it does that through elevator.exe , which asks for administrator rights and changes windows for every user. the launcher runs with your normal rights, so it couldn't undo those changes. that's why, with systemintegration=false the default , elevator.exe is set aside while aimp runs and those options do nothing. it's renamed to elevator.exe.disabled for the session and put back when aimp closes; if aimp updated itself meanwhile, the new elevator.exe is kept. with systemintegration=true , aimp can make those changes, and they stay until you turn the options off in aimp again. what aimp changes, and how it's undone aimp changes put back when it closes "run aimp at windows startup": the aimp value in hkcu\software\microsoft\windows\currentversion\run removed, or put back exactly as it was an installed aimp's entry, for example elevator.exe set aside see above put back a portable aimp can't start with windows from a drive that may not be there, which is why the startup entry is removed. updates aimp can update itself in place; its update checker is in its setti";}i:5;a:15:{s:4:"slug";s:18:"bearsampp-portable";s:5:"title";s:18:"Bearsampp Portable";s:4:"date";s:16:"2026-10-23 19:45";s:7:"updated";s:16:"2026-10-23 20:43";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:63:"/~daemondevin/portableapps/uploads/2026/10/bearsampp-871900.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:39:"Bearsampp Portable v2026.9.13 released!";s:5:"words";i:1270;s:7:"minutes";i:6;s:5:"plain";s:4000:"bearsampp portable v2026.9.13 released a portable launcher for bearsampp https://bearsampp.com/ , the portable wamp style development stack apache, mysql, mariadb, postgresql, php, node.js, mailpit, memcached and more , built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when bearsampp closes, or on the next launch if something went wrong. it also keeps bearsampp itself up to date from its github releases. pacman : https://github.com/daemondevin/pac man system requirements windows 10 or later, 64 bit. bearsampp has no 32 bit version. administrator rights. bearsampp installs windows services and sets machine wide environment variables, and refuses to start without them. an ntfs drive a usb drive formatted ntfs is fine; fat32, exfat and network shares aren't . bearsampp creates current links inside its own folders for the module versions in use. portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/bearsamppportable 2026.9.13.paf.exe configuration bearsamppportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\bearsamppportable.ini over it. ini bearsamppportable updatecheck=true updateedition=lite keeprootca=false key default what it does updatecheck true check github for a newer bearsampp each time it starts, and offer to update. updateedition lite the release download an update is taken from: lite , basic or full . see updates updates . keeprootca false leave bearsampp's development root certificate trusted on this computer after it closes. see certificates certificates . what bearsampp changes, and how it's undone bearsampp is a server stack, so unlike most portable apps it has to change the computer while it runs. before it starts, the launcher records the state of everything below; when bearsampp closes, it puts each one back. bearsampp changes put back when it closes services bearsamppapache , bearsamppmysql , bearsamppmariadb , bearsampppostgresql , bearsamppmailpit , bearsamppmemcached , bearsamppxlight stopped and deleted, if they weren't there before launch. services that already existed are left alone. machine environment variables bearsampp path and bearsampp bins restored to their previous value and type, or deleted if they weren't set. %bearsampp bins% added to the machine path only that entry is removed. everything else in path , including changes other programs made during the session, is kept in order. "launch on startup" shortcut in your startup folder deleted, if it wasn't there before launch. bearsampp's root certificate added to your trusted certificates removed, unless keeprootca=true or it was already trusted before launch. after the environment is restored, running programs are told it changed, so new command prompts see the original path . bearsampp normally deletes its services itself when you choose exit . the launcher's cleanup is what covers a crash, a forced shutdown, or bearsampp being killed. not undone windows firewall rules. if you let apache or mysql through the firewall when windows asks, those rules are created by windows, not bearsampp, and stay. remove them from windows defender firewall if you don't want them. firefox settings. when bearsampp installs its certificate it may also turn on security.enterprise roots.enabled in firefox profiles so firefox trusts it. that setting is harmless and is left as it is. certificates bearsampp uses mkcert https://github.com/filosottile/mkcert to make https://localhost and your virtual hosts trusted in the browser. it creates a development root certificate, app\bearsampp\ssl\rootca.pem , and adds it to your trusted root certificates. with keeprootca=false , the certificate is only trusted while bearsampp portable runs: when bearsampp closes, the certificate is removed. windows shows a confirmation dialog f";}i:6;a:15:{s:4:"slug";s:16:"discord-portable";s:5:"title";s:16:"Discord Portable";s:4:"date";s:16:"2026-10-21 09:40";s:7:"updated";s:16:"2026-10-22 22:28";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:8:"Internet";}s:11:"description";s:0:"";s:5:"image";s:61:"/~daemondevin/portableapps/uploads/2026/10/discord-da4f6d.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:42:"Discord Portable v1.0.9264-rev.3 released!";s:5:"words";i:1755;s:7:"minutes";i:8;s:5:"plain";s:4000:"discord portable v1.0.9264 rev.3 released < more discord portable discord portable is a portable build of discord https://discord.com/ , the voice, video and text chat app. it runs the build that's native to the computer x64 or arm64 , keeps itself up to date, and can load betterdiscord https://betterdiscord.app/ , vencord https://vencord.dev/ or equicord https://equicord.org/ if you want it to. it's built with the portableapps compiler https://github.com/daemondevin/pac man pac man : every change it makes to windows is recorded first and undone when discord closes, or on the next launch if something went wrong. i was given permission by discord inc. to continue developing this project. they can't officially endorse it because, "...we do not have a hand in development directly." they go on to say: "as a result, if they happen to be released, we recommend to all of our users to be cautious when using third party applications with discord in general and any usage is at their own risk." download downloads are in the releases section https://github.com/daemondevin/discordportable/releases/latest . the package is in portableapps.com https://portableapps.com/ format, so it installs into the portableapps.com platform or any folder you like. features the full discord desktop app. native on every pc: x64 and arm64 builds. on windows on arm the launcher downloads and runs the arm64 build instead of running x64 under emulation. see builds builds updates itself: checks discord's official downloads at start, and also runs any update discord installs for itself. a failed or interrupted update keeps the version you had. see updates updates repairs itself: if discord's files are missing or damaged, the launcher offers to download discord again instead of failing to start. optional client mods: betterdiscord, vencord or equicord, chosen with one setting. see client mods client mods your data travels with it: settings, sign in and your client mod's plugins, themes and settings are kept in data . leaves nothing behind: the discord:// link, the "open discord" at startup entry, the uninstall entry and the shortcuts discord makes for itself only exist while it runs. an installed discord's are put back exactly as they were. no administrator rights: everything is done for the current user only. system requirements windows 10 or later, 64 bit x64 or arm64 . discord has had no 32 bit build since december 2023. portableapps.com platform https://portableapps.com/download optional . an internet connection. data on a local drive a usb drive is fine; a network share isn't . see data data . configuration discordportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\discordportable.ini over it. ini discordportable additionalparameters= updatecheck=true architecture=auto clientmod=none key values default what it does updatecheck true , false true check for a new discord at start and offer to update. architecture auto , x64 , arm64 auto which build to run. auto picks the native one. clientmod none , betterdiscord , vencord , equicord none load a client mod into discord. see client mods client mods . additionalparameters text empty extra command line switches passed to discord. builds folder build runs on app\discord x64 x64 windows, and windows 11 on arm under emulation app\discordarm64 arm64 arm64 windows each folder is laid out the way discord's installer leaves it, with one app <version folder per version. the launcher always starts the newest one. the package ships the x64 build. the first time it starts on arm64 windows with updatecheck=true , it offers to download the arm64 build; until then the x64 build runs under emulation. to force a build, set architecture=x64 or arm64 . the arm64 build can only be forced on arm64 windows. updates discord updates its own modules every time it starts, and sometimes installs a new version of itself too. the launcher always starts the n";}i:7;a:15:{s:4:"slug";s:31:"emsisoft-emergency-kit-portable";s:5:"title";s:31:"Emsisoft Emergency Kit Portable";s:4:"date";s:16:"2026-10-23 19:27";s:7:"updated";s:16:"2026-10-23 20:43";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:8:"Security";}s:11:"description";s:0:"";s:5:"image";s:66:"/~daemondevin/portableapps/uploads/2026/10/emergencykit-147a1c.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:57:"Emsisoft Emergency Kit Portable v2025.7.0.12683 released!";s:5:"words";i:943;s:7:"minutes";i:5;s:5:"plain";s:4000:"emsisoft emergency kit portable v2025.7.0.12683 released a portable launcher for emsisoft emergency kit https://www.emsisoft.com/en/emergency kit/ , emsisoft's second opinion malware scanner and cleaner, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when emergency kit closes, or on the next launch if something went wrong. the package contains only the launcher. emergency kit itself comes from emsisoft, and its license applies: it's free for private, non commercial use, and businesses need emsisoft's commercial license. pacman : https://github.com/daemondevin/pac man system requirements windows 10 or later, 64 bit. emergency kit has no 32 bit version. administrator rights. emergency kit needs them to scan memory, other users' files and the registry. a local drive a usb drive is fine; a network share isn't . portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/emergencykitportable 2025.7.0.12683.paf.exe two scanners start what runs emergencykitportable.exe the emergency kit scanner, with its full window clscannerportable.exe a menu for the emsisoft commandline scanner a2cmd.exe , in a command prompt the menu offers a quick scan, a malware scan, or a scan of a folder or drive you choose, with options for potentially unwanted programs, archives and ntfs alternate data streams. detected objects can be quarantined, deleted or only reported. it can also list, restore and delete quarantined objects, and update the signatures. each scan's log is saved in data\logs . clscannerportable.exe starts emergencykitportable.exe /clscanner , so both go through the same launcher, with the same clean up. configuration emergencykitportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\emergencykitportable.ini over it. ini emergencykitportable additionalparameters= language= key default what it does language empty the language emergency kit uses, for example de de . see language language . additionalparameters empty extra command line switches passed to emergency kit. language started from the portableapps.com platform, emergency kit uses the platform's language, if it has a translation for it; otherwise english. started on its own, it keeps the language you chose in emergency kit. language= in emergencykitportable.ini overrides both. emergency kit has czech, dutch, english, farsi, finnish, french, german, hungarian, italian, japanese, korean, polish, portuguese brazil , russian, simplified and traditional chinese, slovenian, spanish and turkish. data emergency kit keeps everything in its own folder, app\eek . your settings, logs, reports and quarantine are kept in data and moved into place while it runs: emergency kit uses kept in app\eek\a2settings.ini and its other settings files data\settings app\eek\logs data\logs app\eek\reports data\reports app\eek\quarantine data\quarantine note the quarantine holds the malware emergency kit found, stored so it can't run. copying data copies it too. updates emergency kit updates its signatures and its own program files itself, in app\eek\bin64 : use update in its window, or in the command line menu. nothing else is needed. after each session the launcher reads the version of a2emergencykit.exe and writes it to appinfo.ini , so the portableapps.com platform shows the version emergency kit has updated itself to. moving from an older package older versions of this package kept the signatures and translations in app\defaultdata or data , and moved them into emergency kit's folder for each session. emergency kit updates both itself, so they now stay in app\eek\bin64 . the first launch moves them there once. what emergency kit changes, and how it's undone before emergency kit starts, the launcher records the state of each of these. when it closes, everything ";}i:8;a:15:{s:4:"slug";s:18:"fl-studio-portable";s:5:"title";s:18:"FL Studio Portable";s:4:"date";s:16:"2026-10-25 20:35";s:7:"updated";s:16:"2026-10-25 20:42";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:15:"Music and Video";}s:11:"description";s:0:"";s:5:"image";s:62:"/~daemondevin/portableapps/uploads/2026/10/flstudio-3fa831.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"FL Studio Portable v25.1 released!";s:5:"words";i:915;s:7:"minutes";i:5;s:5:"plain";s:4000:"fl studio portable v25.1 released < more a portable launcher for fl studio https://www.image line.com/fl studio/ , the digital audio workstation by image line, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when fl studio closes, or on the next launch if something went wrong. the package doesn't include or handle fl studio's licensing: use it with a copy of fl studio you're licensed to run. pacman : https://github.com/daemondevin/pac man system requirements windows 10 or later, 64 bit. fl studio has no 32 bit version; on windows 11 on arm the x64 version runs emulated. no administrator rights. fl studio runs with your normal rights, so dragging samples, presets and projects into it from explorer works. data on a local drive a usb drive is fine; a network share isn't . see data data . portableapps.com platform https://portableapps.com/download optional . downloads direct link https://github.com/daemondevin/portableapps/releases/download/1.0/flstudioportable 25.1 english.paf.exe mirror https://drive.proton.me/urls/zv53s7tf0w r8kw0f6g3duk configuration flstudioportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\flstudioportable.ini over it. ini flstudioportable additionalparameters= disablesplashscreen=false runlocally=false scaled=false symlinks=true key default what it does scaled false start fl64 scaled .exe instead of fl64.exe . windows scales that version up on high dpi screens, like the "fl studio scaled " shortcut of an installed fl studio. symlinks true link fl studio's folders into data while it runs. with false , fl studio uses the folders on the computer and nothing in them travels with the package. additionalparameters empty extra command line switches passed to fl studio. disablesplashscreen false don't show the launcher's splash screen. runlocally false copy fl studio to the temp folder and run it from there, for read only media. changes made in that session aren't saved back. opening a project or sample from the portableapps.com platform while fl studio runs hands it to the running fl studio. data while fl studio runs, these are linked into data with ntfs junctions, so nothing is copied back and forth: fl studio uses kept in documents\image line the user data folder: projects, presets, recordings, renders, hardware scripts, settings files data\image line %appdata%\image line data\appdata\image line %programdata%\fl cloud plugins data\programdata\fl cloud plugins if an installed fl studio already has one of these folders, it's moved aside for the session and put back when fl studio portable closes. the one exception is fl cloud plugins : an installed fl studio's copy of it belongs to the administrator, so the launcher can't always move it. then it's left in place and fl studio portable uses it for that session. fl studio's registry settings, hkcu\software\image line its preferences, and its registration once you've unlocked it , are kept in data\settings\image line.reg . they're loaded when fl studio starts and saved when it closes, whatever fl studio version wrote them. an installed fl studio's settings are put back afterwards. close an installed fl studio before starting fl studio portable; the launcher won't start while one is open. important junctions can only point to a local drive. running from a network share isn't supported. coming from an earlier fl studio portable the first launch takes over what earlier packages kept, so nothing has to be moved by hand: data\settings\flstudio.reg and ilreg.reg are loaded once and saved as image line.reg . the old files are left alone and can be deleted afterwards. data\appdata and data\programdata held the contents of %appdata%\image line and fl cloud plugins directly. they're moved one folder down, to data\appdata\image line and data\programdata\fl cloud plugins . registry besides hkcu\software\image line , the launc";}i:9;a:15:{s:4:"slug";s:23:"github-desktop-portable";s:5:"title";s:23:"GitHub Desktop Portable";s:4:"date";s:16:"2026-10-21 09:59";s:7:"updated";s:16:"2026-10-21 10:12";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:60:"/~daemondevin/portableapps/uploads/2026/10/github-4724ea.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:40:"GitHub Desktop Portable v3.6.7 released!";s:5:"words";i:1239;s:7:"minutes";i:6;s:5:"plain";s:4000:"github desktop portable v3.6.7 released < more github desktop portable github desktop portable is a portable build of github desktop https://desktop.github.com/ , github's open source app for working with git and github repositories. it runs the build that's native to the computer x64 or arm64 and keeps itself up to date. it's built with the portableapps compiler https://github.com/daemondevin/pac man pac man : every change it makes to windows is recorded first and undone when github desktop closes, or on the next launch if something went wrong. download downloads are in the releases section https://github.com/daemondevin/githubdesktopportable/releases . the package is in portableapps.com https://portableapps.com/ format, so it installs into the portableapps.com platform or any folder you like. features the full github desktop, with its bundled git. native on every pc: x64 and arm64 builds. on windows on arm the launcher downloads and runs the arm64 build instead of running x64 under emulation. see builds builds updates itself: checks github's official downloads at start and updates the builds the package has. a failed or interrupted update keeps the version you had. see updates updates your data travels with it: settings, the repository list, and the repositories you clone into the default folder are kept in data . see data data leaves the pc's git alone: your git name and email live in data\.gitconfig , not in the pc's .gitconfig . leaves nothing behind: the x github client , x github desktop auth and github windows links github desktop registers for itself only exist while it runs. an installed github desktop's links are put back exactly as they were. no administrator rights: everything is done for the current user only. system requirements windows 10 or later, 64 bit x64 or arm64 . github desktop has no 32 bit build. portableapps.com platform https://portableapps.com/download optional . an internet connection for updates and for working with github. data on a local drive a usb drive is fine; a network share isn't . see data data . configuration githubdesktopportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\githubdesktopportable.ini over it. ini githubdesktopportable additionalparameters= runlocally=false updatecheck=true architecture=auto key values default what it does updatecheck true , false true check for a new github desktop at start and offer to update. architecture auto , x64 , arm64 auto which build to run. auto picks the native one. additionalparameters text empty extra command line switches passed to github desktop. runlocally true , false false copy github desktop to the temp folder and run it from there. builds folder build runs on app\githubdesktop x64 x64 windows, and windows 11 on arm under emulation app\githubdesktoparm64 arm6 4 arm64 windows the package ships the x64 build. the first time it starts on arm64 windows with updatecheck=true , it offers to download the arm64 build; until then the x64 build runs under emulation. if the build the launcher wants is missing, it falls back to the other one instead of failing to start. to force a build, set architecture=x64 or arm64 . the arm64 build can only be forced on arm64 windows. updates with updatecheck=true , the launcher asks github for the latest github desktop each time it starts, the same download links the github desktop website https://desktop.github.com/ uses. when there's a newer version for a build the package has, it asks before doing anything. an update is all or nothing: 1. every installer is downloaded, with a progress bar. if a download fails, nothing changes. 2. github desktop is unpacked straight out of each installer, next to the current build. the installer is never run, so nothing gets installed on the pc. if anything can't be unpacked, or isn't the version github announced, nothing changes. 3. the new builds are swapped in. each swap is recorded firs";}i:10;a:15:{s:4:"slug";s:20:"komodo-edit-portable";s:5:"title";s:20:"Komodo Edit Portable";s:4:"date";s:16:"2026-10-21 12:28";s:7:"updated";s:16:"2026-10-22 21:02";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:64:"/~daemondevin/portableapps/uploads/2026/10/komodoedit-838d59.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:38:"Komodo Edit Portable v12.0.1 released!";s:5:"words";i:561;s:7:"minutes";i:3;s:5:"plain";s:3781:"komodo edit portable v12.0.1 released < more komodo edit portable a portable launcher for komodo edit ko , activestate's free multi language code editor, built with the portableapps compiler pacman pac man . everything komodo changes on the pc is recorded first and undone when komodo closes, or on the next launch if something went wrong. activestate has stopped developing komodo; version 12 is the last release, and its source is on github https://github.com/komodo/komodoedit . ko : https://www.activestate.com/products/komodo edit/ pacman : https://github.com/daemondevin/pac man download https://drive.proton.me/urls/djcgqnekac byv4dxxeaelh system requirements windows 7 or later. no administrator rights. portableapps.com platform https://portableapps.com/download optional . configuration komodoeditportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\komodoeditportable.ini over it. ini komodoeditportable additionalparameters= runlocally=false key default what it does additionalparameters empty extra command line switches passed to komodo. runlocally false copy komodo to the temp folder and run it from there, for read only media. changes made in that session aren't saved back. launching the package again while komodo runs passes the files to the running komodo. data komodo keeps its settings, toolbox, projects list and mozilla profile in one folder per version. the launcher points komodo at data\activestate\komodoedit with komodo's own komodo userdatadir setting, so the folder for version 12 is data\activestate\komodoedit\12.0 . nothing is copied, linked or moved, and an installed komodo edit keeps its own settings. new projects go to data\workspace unless you change the project folder in komodo's preferences. when the package moves another drive letter or folder , the paths komodo remembered inside the package are updated in its preferences and mozilla's add on list. mozilla's startup cache is cleared after each session, since it holds those paths too; komodo rebuilds it on the next start. what's cleaned up komodo and the mozilla platform it's built on make a few folders outside its settings folder: %appdata%\activestate\komodo edit crash reports %localappdata%\activestate\komodo edit the update folder %localappdata%\activestate\komodoedit %appdata%\mozilla any of these that didn't exist before komodo started is removed when it closes, or on the next launch if komodo didn't close properly. folders that already existed from an installed komodo are left alone. %appdata%\mozilla is also where firefox and thunderbird keep their profiles, so it's only removed when komodo made it and no mozilla program has started using it since. if something goes wrong if komodo edit portable didn't close properly a crash, a power cut, a usb drive pulled out , the next launch tells you and undoes everything the last session changed before it starts again. when reporting a problem, please include an export of the hkey current user\software\pac man\journal registry key and the contents of %localappdata%\pac man\journal . building from source the launcher is built with the portableapps compiler pacman . its configuration lives in app\appinfo : file contents app\appinfo\appinfo.ini package details, version and file types app\appinfo\launcher\komodoeditportable.ini the launcher configuration: the data folder, the folders to clean up and the path updates app\appinfo\launcher\custom.nsh cleaning up the folders komodo makes outside data credits komodo edit is developed by activestate software inc. portableapps.com platform https://portableapps.com/download by portableapps.com https://portableapps.com/ . portableapps compiler pacman developed by daemon.devin. ";}i:11;a:15:{s:4:"slug";s:19:"komodo-ide-portable";s:5:"title";s:19:"Komodo IDE Portable";s:4:"date";s:16:"2026-10-22 21:02";s:7:"updated";s:16:"2026-10-22 21:09";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:63:"/~daemondevin/portableapps/uploads/2026/10/komodoide-f473e6.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:43:"Komodo IDE Portable v12.0.1-91869 released!";s:5:"words";i:557;s:7:"minutes";i:3;s:5:"plain";s:3738:"komodo ide portable v12.0.1 91869 released < more a portable launcher for komodo ide ko , activestate's multi language ide, built with the portableapps compiler pacman pac man . everything komodo changes on the pc is recorded first and undone when komodo closes, or on the next launch if something went wrong. activestate has stopped developing komodo; version 12 is the last release, and its source is on github https://github.com/komodo/komodoedit . ko : https://www.activestate.com/products/komodo ide/ pacman : https://github.com/daemondevin/pac man system requirements windows 7 or later. no administrator rights. portableapps.com platform https://portableapps.com/download optional . download https://drive.proton.me/urls/nev7ae65h4 0r4wne0i6fhx configuration komodoideportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\komodoideportable.ini over it. ini komodoideportable additionalparameters= runlocally=false key default what it does additionalparameters empty extra command line switches passed to komodo. runlocally false copy komodo to the temp folder and run it from there, for read only media. changes made in that session aren't saved back. launching the package again while komodo runs passes the files to the running komodo. data komodo keeps its settings, toolbox, projects list and mozilla profile in one folder per version. the launcher points komodo at data\activestate\komodoide with komodo's own komodo userdatadir setting, so the folder for version 12 is data\activestate\komodoide\12.0 . nothing is copied, linked or moved, and an installed komodo ide keeps its own settings. new projects go to data\workspace unless you change the project folder in komodo's preferences. when the package moves another drive letter or folder , the paths komodo remembered inside the package are updated in its preferences and mozilla's add on list. mozilla's startup cache is cleared after each session, since it holds those paths too; komodo rebuilds it on the next start. what's cleaned up komodo and the mozilla platform it's built on make a few folders outside its settings folder: %appdata%\activestate\komodo ide crash reports %localappdata%\activestate\komodo ide the update folder %localappdata%\activestate\komodoide %appdata%\mozilla any of these that didn't exist before komodo started is removed when it closes, or on the next launch if komodo didn't close properly. folders that already existed from an installed komodo are left alone. %appdata%\mozilla is also where firefox and thunderbird keep their profiles, so it's only removed when komodo made it and no mozilla program has started using it since. if something goes wrong if komodo ide portable didn't close properly a crash, a power cut, a usb drive pulled out , the next launch tells you and undoes everything the last session changed before it starts again. when reporting a problem, please include an export of the hkey current user\software\pac man\journal registry key and the contents of %localappdata%\pac man\journal . building from source the launcher is built with the portableapps compiler pacman . its configuration lives in app\appinfo : file contents app\appinfo\appinfo.ini package details, version and file types app\appinfo\launcher\komodoideportable.ini the launcher configuration: the data folder, the folders to clean up and the path updates app\appinfo\launcher\custom.nsh cleaning up the folders komodo makes outside data credits komodo ide is developed by activestate software inc. portableapps.com platform https://portableapps.com/download by portableapps.com https://portableapps.com/ . portableapps compiler pacman developed by daemon.devin. ";}i:12;a:15:{s:4:"slug";s:24:"mozilla-firefox-portable";s:5:"title";s:24:"Mozilla Firefox Portable";s:4:"date";s:16:"2026-10-26 01:23";s:7:"updated";s:16:"2026-10-26 01:30";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:8:"Internet";}s:11:"description";s:0:"";s:5:"image";s:61:"/~daemondevin/portableapps/uploads/2026/10/firefox-304d90.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"Mozilla Firefox Portable released!";s:5:"words";i:1509;s:7:"minutes";i:7;s:5:"plain";s:4000:"mozilla firefox portable released < more a portable launcher for firefox https://www.mozilla.org/firefox/ , built with the portableapps compiler pacman pac man . it keeps your profile in the package, installs firefox from mozilla on the first launch and keeps it up to date itself. every change it makes to windows is recorded first and undone when firefox closes, or on the next launch if something went wrong. firefox and the firefox logos are trademarks of the mozilla foundation. this package isn't made or endorsed by mozilla; it runs mozilla's own, unmodified firefox builds. pacman : https://github.com/daemondevin/pac man system requirements windows 10 or later what current firefox needs . an internet connection for the first launch and for updates. portableapps.com platform https://portableapps.com/download optional . downloads direct link https://github.com/daemondevin/portableapps/releases/download/1.0/firefoxportable x.x.x.paf.exe mirror https://drive.proton.me/urls/ytf51yhxr4 jtiaiddayqfs first launch the package doesn't include firefox. the first launch offers to download it: 1. it asks mozilla which version is current product details.mozilla.org . 2. it downloads the full windows installer from archive.mozilla.org : the 64 bit edition on 64 bit windows, the 32 bit one otherwise. 3. it checks the download against the sha 512 checksum mozilla publishes for that exact file. a download that doesn't match is never used. 4. it unpacks the installer with its own /extractdir option, which writes the program files to a folder and stops, without installing anything, and puts them in app\firefox64 or app\firefox . then firefox starts. if you say no, or the download fails, nothing is left behind and the launcher stops. updates firefox's built in updater is turned off: it needs the mozilla maintenance service or administrator rights for some updates, and writes its state to %programdata% . the launcher does the updating instead, the same way as the first install: before firefox starts, at most once every updateinterval days, it asks mozilla for the latest version on your channel. if there's a newer one, it asks whether to update now updatecheck=ask , or just does it updatecheck=auto . say no and firefox starts as it is; you're asked again after the interval. the new firefox is downloaded and checked as above, then swapped in. the old folder is kept until the new one is in place, and the swap is journaled: if the launcher is stopped halfway, the next launch puts the old firefox back. your additions to the firefox folder are carried over: the distribution folder your own policies, bundled add ons , preference files in defaults\pref and autoconfig files .cfg . if anything fails no connection, a checksum that doesn't match , it says why and starts the firefox you have. both editions are updated when the package has both. if you only use one, delete the other folder to halve the download. to stop firefox's own updater, the launcher puts a policies.json in each firefox folder's distribution folder it also turns off the default browser check and the default browser agent . because of that policy, firefox's settings page says your browser is being managed by your organization . if you put your own policies.json there, the launcher leaves it alone; include "disableappupdate": true in it. configuration firefoxportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\firefoxportable.ini over it. ini firefoxportable additionalparameters= updatecheck=ask updatechannel=release updateinterval=1 locale= key default what it does updatecheck ask ask asks before updating, auto updates without asking, off never checks. updatechannel release release or esr extended support release https://www.mozilla.org/firefox/enterprise/ . updateinterval 1 days between update checks. 0 checks on every launch. locale empty firefox's language as mozilla names it: en us , de , fr , pt br ,";}i:13;a:15:{s:4:"slug";s:19:"o-o-defrag-portable";s:5:"title";s:19:"O&O Defrag Portable";s:4:"date";s:16:"2026-10-22 21:50";s:7:"updated";s:16:"2026-10-23 19:15";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:9:"Utilities";}s:11:"description";s:0:"";s:5:"image";s:62:"/~daemondevin/portableapps/uploads/2026/10/oodefrag-5e566d.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:46:"O&O Defrag Portable v30.0 Build 1056 released!";s:5:"words";i:667;s:7:"minutes";i:4;s:5:"plain";s:4000:"o&o defrag portable v30.0 build 1056 released < more a portable launcher for oo defrag professional https://www.oo software.com/en/oodefrag , built with the portableapps compiler https://github.com/daemondevin/pac man pac man . every change it makes to windows is recorded first and undone when o&o defrag closes, or on the next launch if something went wrong. o&o defrag is commercial software. the package doesn't include or handle a license: enter your own license in o&o defrag. system requirements windows 10 or 11, 64 bit. o&o defrag professional has no 32 bit version, and can't be used on windows server. administrator rights: o&o defrag does its work through a windows service. the .net 8 desktop runtime x64 . if it's missing, the launcher offers to install it from app\prerequisites . that install stays on the computer, since other programs may come to rely on it. data on a local drive a usb drive is fine; a network share isn't . portableapps.com platform https://portableapps.com/download optional . downloads direct link https://github.com/daemondevin/portableapps/releases/download/1.0/o odefragportable 30.0 build 1056.paf.exe configuration o&odefragportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\o&odefragportable.ini over it. ini o&odefragportable additionalparameters= disablesplashscreen=false symlinks=true key default what it does symlinks true link o&o defrag's data folder into data while it runs. with false , it uses the folder on the computer. additionalparameters empty extra command line switches passed to o&o defrag. disablesplashscreen false don't show the launcher's splash screen. what happens while it runs change undone by the oodefragagent service, which does the actual defragmenting, is created pointing at the package and started. an installed o&o defrag's agent is pointed at the package instead. deleting the service, or putting the installed agent back as it was the drive map control oodpeo.ocx is registered. an installed o&o defrag's registration is backed up first. unregistering it and restoring the backup hklm\software\o&o\o&o defrag settings, jobs and your licence is loaded from data\settings\o&odefrag.reg saving it back to data, then restoring what was there before %localappdata%\oo software\oo defrag is linked to data\oo defrag with an ntfs junction removing the junction and putting back anything that was there close an installed o&o defrag, including its tray icon, before starting o&o defrag portable. the launcher waits for o&o defrag's tray icon and update check to close before it removes the service. important junctions can only point to a local drive. running from a network share isn't supported. if something goes wrong if o&o defrag portable didn't close properly a crash, a power cut, a usb drive pulled out , the next launch tells you and undoes everything the last session changed. start it again afterwards. settings changed in the session that crashed aren't saved. when reporting a problem, please include an export of the hkey current user\software\pac man\journal registry key and the contents of %localappdata%\pac man\journal . building from source the launcher is built with the portableapps compiler https://github.com/daemondevin/pac man . its configuration lives in app\appinfo : file contents app\appinfo\appinfo.ini package details and version app\appinfo\launcher\o&odefragportable.ini the launcher configuration: the service, the drive map control, the data link and the .net check app\appinfo\launcher\custom.nsh the portable registry settings app\\prerequisites must hold windowsdesktop runtime 8.0.21 win x64.exe the .net 8 desktop runtime, which includes the base runtime . update the name in the launcher configuration if you ship a newer one. credits o\&o defrag is developed by o\&o software gmbh https://www.oo software.com/ . portableapps.com platform https://portableapps.com/download by portableapps.com ht";}i:14;a:15:{s:4:"slug";s:22:"o-o-regeditor-portable";s:5:"title";s:22:"O&O RegEditor Portable";s:4:"date";s:16:"2026-10-25 21:57";s:7:"updated";s:16:"2026-10-25 22:03";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:9:"Utilities";}s:11:"description";s:0:"";s:5:"image";s:65:"/~daemondevin/portableapps/uploads/2026/10/ooregeditor-6288b7.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:43:"O&O RegEditor Portable v16.1.6660 released!";s:5:"words";i:968;s:7:"minutes";i:5;s:5:"plain";s:4000:"o&o regeditor portable v16.1.6660 released < more a portable launcher for oo regeditor https://www.oo software.com/en/ooregeditor , o&o software's free registry editor: full text search with a results list, favorites, an address bar that takes pasted key paths, and copying and moving of whole keys. it's built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when o&o regeditor closes, or on the next launch if something went wrong. o&o regeditor isn't included: o&o's license only allows it to be passed on unmodified and on its own, and counts packaging it in an installer or wrapper as a modification. you add it youself. pacman : https://github.com/daemondevin/pac man system requirements windows vista or later, 32 bit or 64 bit o&o regeditor 12 . administrator rights. o&o regeditor is built to always run as an administrator, so the launcher asks for them uac every time. portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/o oregeditorportable 16.1.6660.paf.exe mirror https://drive.proton.me/urls/qq9wryn0pr ebmtgm9di7zh adding o&o regeditor 1. download o&o regeditor from oo software.com https://www.oo software.com/en/ooregeditor . 2. extract or copy its program files into this package's app\ooregeditor folder: ooregedt.exe , ooregedt32.exe , and the en and de folders. 3. start o&oregeditorportable.exe . until the program is there, the launcher says which folder to copy and where, offers to open the app folder, and stops. on 64 bit windows it starts ooregedt.exe , the 64 bit edition, which sees the whole registry without wow64 redirection; on 32 bit windows it starts ooregedt32.exe . configuration o&oregeditorportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\o&oregeditorportable.ini over it. ini o&oregeditorportable additionalparameters= language=auto key default what it does language auto en or de sets the language. auto follows the portableapps.com platform's language when started from the platform german for german, english for everything else , and otherwise leaves the choice to o&o regeditor, which goes by the system locale. additionalparameters empty extra command line switches passed to o&o regeditor. o&o regeditor has no language setting of its own: it uses the language whose folder is there. to set one, the launcher renames the other folder de becomes de.off for the session and puts it back when o&o regeditor closes. data o&o regeditor keeps every setting in ooregedt.ini next to the program, shared by both editions: the window and toolbar layout, favorites, the address bar history and the last key opened. it's kept in data\ooregedt.ini and moved into place while o&o regeditor runs. if o&o regeditor was started without the launcher, its ooregedt.ini is left in app\ooregeditor . the next launch takes it into data , or, if data already has one, keeps it as data\ooregedt.found.ini , so neither is lost. what o&o regeditor changes, and how it's undone o&o regeditor changes put back when it closes always open .reg files with o&o regeditor : the default value of .reg in hklm\software\classes or hkcu\software\classes if you have your own .reg entry there put back exactly as it was, normally regfile the ooregedit.document file type it registers for that, in the same places removed, or put back as it was the de or en folder set aside for the language see above put back explorer can't open a .reg file with a program on a drive that isn't there, which is why the association only lasts while o&o regeditor runs. to open .reg files with it from the portableapps.com platform, use the platform's own file type associations. everything you change in the registry with o&o regeditor is, of course, not undone: that's what a registry editor is for. export a key before changing it. updates o&o re";}i:15;a:15:{s:4:"slug";s:8:"portable";s:5:"title";s:13:"PortableApps?";s:4:"date";s:16:"2026-10-02 09:05";s:7:"updated";s:16:"2026-10-21 09:25";s:6:"status";s:9:"published";s:4:"type";s:4:"page";s:4:"tags";a:0:{}s:11:"description";s:128:"Explains what a portable application is, it's pros and cons, what PortableApps.com is, it's competitors, and why PAC-MAN exists.";s:5:"image";s:66:"/~daemondevin/portableapps/uploads/2026/10/portableapps-af922c.jpg";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:203:"A portable application is a program that runs from its own folder without being installed and keeps everything it needs, including its settings, inside that folder. You can copy the folder to a USB dr…";s:5:"words";i:1979;s:7:"minutes";i:9;s:5:"plain";s:4000:"a portable application is a program that runs from its own folder without being installed and keeps everything it needs, including its settings, inside that folder. you can copy the folder to a usb drive, an external ssd, a cloud synced directory, or another pc, and it runs the same way with the same configuration. there are two kinds: 1. natively portable apps are written to keep their config next to the executable and avoid the registry, so they just work from any folder. 2. portablized apps are normal apps that expect to be installed and write to the registry and %appdata% . a launcher such as pal or pac man makes them portable by staging their settings onto the host when the app starts, redirecting paths, and moving everything back into the app's data folder and cleaning up when it closes. benefits no installation or admin rights needed. useful on locked down work, school, or client machines. your setup goes with you. settings, extensions, history, and plugins are the same on every machine. host machines stay clean. no leftover registry keys, appdata folders, or uninstall entries. easy backup and versioning. an app is a folder. you can copy it, archive it, or roll back by restoring an older copy. multiple versions side by side. you can run a stable and a beta version, or an old version for compatibility, without conflicts. safe testing. you can try software without committing your system to it. disaster recovery. a drive full of diagnostic and repair tools works on a machine that won't install anything. simple deployment. for your own tools, distribution is just a zip or a paf.exe installer. downsides technical limits not everything can be made portable. services, kernel drivers, shell extensions, com servers, and anything that needs admin rights to register either can't be made portable or need special handling and admin rights on the host anyway, which defeats much of the point. this is the hardest part of portablizing. weak system integration. file associations, context menu entries, default app status, and "open with" mostly don't exist unless the launcher temporarily registers them. cleanup depends on the exit. if the app crashes, the host loses power, or the drive is pulled, staged registry keys and files can be left on the host and the portable data folder may not be updated. this is the main reason crash resilience matters. path rewriting can break. apps that store absolute paths in config files, databases, or binary blobs can fail when the drive letter changes, unless the launcher knows about every place those paths are stored. conflicts with installed copies. running a portable app while the same app is installed locally can cause profile clashes or single instance locks. performance and hardware slow media. cheap usb sticks have poor random read and write speeds, so large apps such as office suites, ides, and browsers with big profiles can feel slow. flash wear. apps that write caches heavily wear down low end flash drives over time. startup overhead. launchers that copy settings in and out add time when the app starts and closes, which is noticeable with large profiles. security and policy antivirus false positives. unsigned nsis launchers that modify the registry and move files look suspicious to heuristic scanners, and defender for endpoint in particular flags them. portableapps had to ship a defender specific fix as recently as platform 30.1.3. lost or stolen drives. your browser profile, saved sessions, and credentials are on a small, easily lost device unless you encrypt it. untrusted hosts. running your apps on someone else's pc exposes your data to whatever that machine has on it, such as keyloggers or malware. corporate blocking. many organizations block executables from removable drives or user writable paths through applocker or wdac, which stops portable apps completely. not completely traceless. windows itself records some activity outside the app's control, including prefetch, recent files lists, j";}i:16;a:15:{s:4:"slug";s:21:"portableapps-compiler";s:5:"title";s:21:"PortableApps Compiler";s:4:"date";s:16:"2026-10-23 14:18";s:7:"updated";s:16:"2026-10-23 14:44";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:7:"PAC-MAN";}s:11:"description";s:0:"";s:5:"image";s:61:"/~daemondevin/portableapps/uploads/2026/10/pac-man-9a4a22.jpg";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:36:"PortableApps Compiler v3.0 released!";s:5:"words";i:707;s:7:"minutes";i:4;s:5:"plain";s:4000:"portableapps compiler v3.0 released < more portableapps compiler portableapps compiler & management portableapps compiler or pac man for short is an enhanced, compatibility aware launcher framework inspired by the portableapps.com launcher pal . it is designed to support complex, modern and legacy windows applications that pal intentionally does not target. pac man's framework is built on top of pal and still produces packages that follow the portableapps.com format https://portableapps.com/manuals/portableapps.comlauncher/ref/paf/index.html portableapps com format specification . pac man does not replace pal. it augments pal by adding: structured lifecycle segments crash recovery guarantees explicit rollback journaling windows 10/11 compliant integration patterns pac man is designed to behave like a transactional runtime environment , not an installer. it exists to solve a different class of problems than pal. download https://github.com/daemondevin/pac man/releases/tag/v3.0 design principles 1. no permanent system mutation 2. every mutation must be reversible 3. recovery must not depend on successful startup 4. user scope first, system scope only when required 5. deterministic execution order 6. fail closed, not open the one deliberate exception to the first two is installing a shared runtime visual c++ or .net system wide: it can't safely be removed again, because other programs may start using it. the runtime segment only does that when the user agrees in a prompt that says it is permanent, and prefers a portable copy whenever one is available. functional comparison feature pal pac man crash recovery limited journal based file associations not supported user scoped url protocols not supported supported windows services not supported temporary firewall rules not supported reversible scheduled tasks not supported session bound com registration minimal fully tracked fonts limited fully reversible hosts file not supported transactional windows 11 compliance partial explicit the pac man column describes the target behavior. the implementation status implementation status table shows how far each row has got. crash recovery model crash recovery in pac man is: deterministic , not heuristic journal driven , not best effort idempotent , safe to re run if pac man detects that a previous session ended unexpectedly, it recovers first , before any new changes are made. the check runs right after the instance mutex checks, so only the primary instance can recover: if another launcher for the same app is alive, its journal is not stale and is left alone. a segment cleans up after itself with the same rollback call that crash recovery uses, so the normal shutdown path and the recovery path are one and the same code. the unload step also rolls back anything a segment left behind, as a safety net. when launch :waitforprogram=false the launcher exits while the app is still running, so its changes have to outlive the launcher. in that case the session is marked detached and the next launch rolls it back quietly. intended use cases pac man is suitable for portable developer tools, security tooling, controlled enterprise environments and forensic or sandbox workflows. it is not intended for silent system takeover, persistent background services or circumventing os security policies. documentation check out the wiki section for various related articles related to creating portableapps. the wiki serves who need a quick reminder on certain functions and macros for use within the custom.nsh file. as an added bonus, all not yet but most of the source code i've used here is outlined and better explained/documented there as well. for instance, a short guide on registering dlls and all the macros i used to create the registerdll.nsh segment can be found in the wiki. you can also find an exhaustive tutorial on dealing with windows services; plus it explains what each macro is and does within the services.nsh segment and how to use them in action. visit ";}i:17;a:15:{s:4:"slug";s:17:"ripx-daw-portable";s:5:"title";s:17:"RipX DAW Portable";s:4:"date";s:16:"2026-10-25 20:42";s:7:"updated";s:16:"2026-10-25 21:56";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:15:"Music and Video";}s:11:"description";s:0:"";s:5:"image";s:58:"/~daemondevin/portableapps/uploads/2026/10/ripx-93bf78.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"RipX DAW Portable v7.0.2 released!";s:5:"words";i:882;s:7:"minutes";i:5;s:5:"plain";s:4000:"ripx daw portable v7.0.2 released < more a portable launcher for ripx daw https://hitnmix.com/ , hit'n'mix's stem separation and audio editing workstation, built with the portableapps compiler pacman pac man . every change it makes to windows is recorded first and undone when ripx closes, or on the next launch if something went wrong. the package doesn't include or handle ripx's licensing: use it with a copy of ripx daw you're licensed to run. pacman : https://github.com/daemondevin/pac man system requirements windows 10 or later, 64 bit. ripx daw has no 32 bit version. administrator rights for the launcher. ripx itself runs with your normal rights see drag and drop drag and drop . data on a local drive a usb drive is fine; a network share isn't . see data data . portableapps.com platform https://portableapps.com/download optional . downloads direct link https://github.com/daemondevin/portableapps/releases/download/1.0/flstudioportable 25.1 english.paf.exe mirror https://drive.proton.me/urls/9bx2pcw1p8 tw7jk8f73r3i drag and drop windows doesn't let explorer, or any other program running with normal rights, drag files into a program that runs as administrator. so a launcher that runs ripx elevated also breaks dragging audio files into it. the launcher still needs administrator rights for the machine wide registry key ripx reads see registry registry . but once it has set that up, it starts ripx the way explorer would: with the rights of the signed in user, using explorer's own credentials. dragging audio into ripx from explorer, the desktop and other programs then works as it does with an installed ripx. a second launch while ripx runs opening a rip from the portableapps.com platform, for example isn't elevated at all, so there's no uac prompt. it hands its files to the running ripx. if the launcher was elevated with a different account's password a standard user typing an administrator's password , ripx has to run as that administrator, and dragging from your own explorer can't work. signing in with an account that is an administrator avoids that. configuration ripxdawportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\ripxdawportable.ini over it. ini ripxdawportable additionalparameters= disablesplashscreen=false symlinks=true key default what it does symlinks true link ripx's folders into data while it runs. with false , ripx uses the folders on the computer and nothing in them travels with the package. additionalparameters empty extra command line switches passed to ripx. disablesplashscreen false don't show the launcher's splash screen. data while ripx runs, these are linked into data with ntfs junctions, so nothing is copied back and forth. that matters here: a single rip is often several hundred megabytes. ripx uses kept in documents\ripx rips, stems, loops, sound palettes, riplists, ripscripts data\ripx %appdata%\hit'n'mix shared instrument data data\hit'n'mix if an installed ripx already has one of these folders, it's moved aside for the session and put back when ripx daw portable closes. ripx's preferences, hkcu\software\hitnmix\hitnmix\kit , are kept in data\settings\ripx.reg . they're loaded when ripx starts and saved when it closes; an installed ripx's preferences are put back afterward. close an installed ripx before starting ripx daw portable; the launcher won't start while one is open. important junctions can only point to a local drive. running from a network share isn't supported. registry ripx reads where its resources are, and the user details its installer leaves, from hklm\software\hitnmix . without them it treats itself as a broken installation. for the session, the launcher writes what ripx's installer would, pointing at the package: hitnmix\applicationpath : the package's ripx.exe hitnmix\kit\datapath : resourcepath and hitnmixsharedpath , the package's app\ripxdaw folder hitnmix\kit\user info : the installer's defau";}i:18;a:15:{s:4:"slug";s:15:"vscode-portable";s:5:"title";s:15:"VSCode Portable";s:4:"date";s:16:"2026-10-19 09:26";s:7:"updated";s:16:"2026-10-21 09:49";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:60:"/~daemondevin/portableapps/uploads/2026/10/vscode-ba98fa.jpg";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"VSCode Portable v1.142.0 released!";s:5:"words";i:1135;s:7:"minutes";i:6;s:5:"plain";s:4000:"vscode portable v1.142.0 released < more visual studio code portable vs code portable is a portable version of the popular visual studio code https://code.visualstudio.com/ application. support to recompile this paf you must use my portableapps compiler https://github.com/daemondevin/pac man . download all downloads available in the releases section https://github.com/daemondevin/vscodeportable/releases/latest . this portable application was packaged using a modified version of the portableapps.com http//portableapps.com/ launcher. features runs the full visual studio code desktop app. completely portable runs off a usb, cloud drive dropbox, icloud drive, onedrive, etc or hard drive. no need for any external software simply download extract and run packaged in portableapps.com format for easy integration. user configuration file for advanced portable settings see configuration configuration below allows for some developmental environments to be recognized by visual studio code across various devices see environments environments below open with entries and an open with code portable context menu while it runs, removed again on exit see associations associations below installs bundled vsix extensions, each one once. see vsix installations vsix installs below self sustaining; no need to update this package as it should update itself, showing the download's progress. an update that fails or is interrupted puts the previous version back. crash safe: everything the launcher changes on the computer is journaled and undone on exit, or on the next launch if it was interrupted. system requirements microsoft windows 10 or later. portableapps.com platform http://portableapps.com/download optional configuration an optional user configuration file called vscodeportable.ini is available in the vs code portable root directory i.e. vscodeportable\vscodeportable.ini . if this file somehow becomes corrupted or you just need to go back to a default state, there's a default user configuration file located in the source folder located at .\other\source\vscodeportable.ini copy this file to the root directory next to the launcher file vscodeportable.exe to reset these options. refer to the example example section for a brief explanation for each user configuration option. example ini vscodeportable additionalparameters= runlocally=false banner=true fileassociations=true updatecheck=true installvsix=false = environment settings ; uncomment the configurations below to use them ;git=%pal:commonfiles%\git ;python=%pal:commonfiles%\python ;nodejs=%pal:commonfiles%\node.js = advanced settings ; uncomment the configurations below to use them ;githomepath=true ;pythonuserpath=true ;nodeprefixpath=true = banner= ; enable or disable the initialization banner. = updatecheck= ; enable or disable automatic portable updating. = installvsix= ; enable or disable the installation of vsix files found in ; .\app\defaultdata\code\extensions. each file is offered once. = fileassociations= ; turn the open with entries and the open with code portable context menu ; on or off true false . everything is removed again when vs code closes. ; for more information refer to the readme.txt file located at: ; .\other\source\readme.txt = additionalparameters= ; pass additional command line switches. = runlocally= ; application is copied to & executed from $temp directory. = git= ; path to the git directory = githomepath= ; change git home path to "data\git\home" = python= ; path to the python directory = pythonuserpath= ; change python user path to "data\python" = nodejs= ; path to the nodejs directory = nodeprefixpath= ; change node.js npm prefix path to "data\node.js\npm" environments vs code portable has support for certain development environments i.e. git , node.js , etc . preconfigured environments to set up your development environments, follow the steps below. 1. using your preferred text editor, open the optional user configuration file located in the base directory i.e. v";}i:19;a:15:{s:4:"slug";s:18:"webuilder-portable";s:5:"title";s:18:"WeBuilder Portable";s:4:"date";s:16:"2026-10-22 21:10";s:7:"updated";s:16:"2026-10-23 19:19";s:6:"status";s:9:"published";s:4:"type";s:4:"post";s:4:"tags";a:1:{i:0;s:11:"Development";}s:11:"description";s:0:"";s:5:"image";s:63:"/~daemondevin/portableapps/uploads/2026/10/webuilder-c95005.png";s:6:"format";s:8:"standard";s:5:"media";a:0:{}s:7:"excerpt";s:34:"WeBuilder Portable v18.4 released!";s:5:"words";i:452;s:7:"minutes";i:3;s:5:"plain";s:3068:"webuilder portable v18.4 released < more a portable launcher for webuilder https://www.webuilderapp.com/ , the all in one code editor by karlis blumentals, built with the portableapps compiler https://github.com/daemondevin/pac man pac man . webuilder is commercial software. the package doesn't include or handle a licence: register webuilder with your own licence from inside webuilder. system requirements windows 10 or later. no administrator rights. webuilder runs with your normal rights, so dragging files into it from explorer works. data on a local drive a usb drive is fine; a network share isn't . portableapps.com platform https://portableapps.com/download optional . download direct link https://github.com/daemondevin/portableapps/releases/download/1.0/webuilderportable 18.4 english.paf.exe configuration webuilderportable.ini , next to the launcher, holds the user settings. if it gets damaged, or you want to go back to the defaults, copy other\source\webuilderportable.ini over it. ini webuilderportable additionalparameters= disablesplashscreen=false firefox= chrome= opera= difftool= key default what it does firefox , chrome , opera empty browsers webuilder previews pages in, for example %pal:portableappsdir%\firefoxportable\firefoxportable.exe . difftool empty the file compare tool, with %file1 and %file2 where the two files go. additionalparameters empty extra command line switches passed to webuilder. disablesplashscreen false don't show the launcher's splash screen. the tool settings are written to webuilder's settings each time it starts, with %pal:...% variables expanded, so they follow the drive the package is on. leave one empty to keep what's set in webuilder itself. data webuilder runs in portable mode when app\webuilder\settings exists, and keeps all its settings there. while it runs, that folder is an ntfs junction to data\config , so nothing is copied back and forth; the junction is removed when webuilder closes, or on the next launch if something went wrong. earlier packages moved the settings folder in and out of data\config . if one of them left app\webuilder\settings behind after a crash, the first launch moves it into data\config and keeps the previous data\config as data\config.old . important junctions can only point to a local drive. running from a network share isn't supported. building from source the launcher is built with the portableapps compiler https://github.com/daemondevin/pac man . its configuration lives in app\appinfo : file contents app\appinfo\appinfo.ini package details and version app\appinfo\launcher\webuilderportable.ini the launcher configuration: the settings link and the section the tool settings go to app\appinfo\launcher\custom.nsh the tool settings and taking over earlier packages' settings credits webuilder is developed by karlis blumentals https://www.webuilderapp.com/ . portableapps.com platform https://portableapps.com/download by portableapps.com https://portableapps.com/ . portableapps compiler https://github.com/daemondevin/pac man developed by daemon.devin. ";}}}