Each time Rufus 4.2 is started, RufXXXX.tmp (language messages, >1M) is created in app directory and not deleted once Rufus is closed.
Also reproducible with original rufus-4.2p.exe file, without PortableApps environment. Definitely a Rufus bug, not a PortableApps one.
So, if Rufus 4.2 is started N times, then N+ megabytes is occupied in Rufus app directory.
Not reproducible with Rufus 4.1 or older.
Update #1. This bug occurs because I use a RAM disk R: (ImDisk ToolKit) and my TEMP and TMP are R:\Temp (no symlinks). In this case Rufus 4.2 creates temporary files in . directory for unknown reason and just forgets to delete them. Looks like the bug is introduced here: https://github.com/pbatard/rufus/compare/beb847511bf75c4120a3a5b23e0785b...
Rufus 4.1 worked correctly. That is, temp. file is created in R:\Temp and deleted before Rufus 4.1 is closed.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It's now supposed to be running with a contained TEMP folder (launcher creates a temporary folder in TEMP, launched app should use it, on exit the launcher deletes it all) as the original trick of setting a working directory to Data\settings and having it store settings and logs there no longer works. It worked in 4.1 but not in 4.2.
Do you have both TEMP and TMP environment variables set for your RAM disk?
Sometimes, the impossible can become possible, if you're awesome!
Previous versions create such temp. files in R:\Temp\RufusPortableTemp directory in PortableApps environment on my OS. But not Rufus 4.2.
Both TEMP and TMP variables in my OS are set to R:\Temp, no symlinks are used.
Already reported: https://github.com/pbatard/rufus/issues/2296
But a reporter uses directory junctions as TEMP/TMP. I'm using neither directory junctions nor symlinks.