4.2 series 64bit crashing every time

[knighthartt]

Please provide the following information

qBittorrent version and Operating System

4.2.1 64bit Windows10 Pro 1903

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

After updating to 4.2.0 (64bit), qBittorrent crashes without fail 5 to 10 minutes after opening. No crash dialog, the window or tray icon just disappears. No change in behavior after updating to 4.2.1. Torrents that were downloading at the time of the crash reset to 0%, after a restart. Torrents that completed before the crash stay completed.

What is the expected behavior

No crashing

Steps to reproduce

Unclear (update to 4.2 series?)

Extra info(if any)

[xavier2k6]

Is there anything in the event viewer?

[knighthartt]

Where do I access that? Are we talking an event viewer in Windows or something in the program itself?

[xavier2k6]

Press windows key + R key to bring up Run dialog box. In the Run dialog box, type eventvwr (<-that's not a typo!) Event Viewer will open! Left hand side, click on Windows Logs & then Application. On right hand side look through for level: error/source: windows error reporting that may be related to qbittorrent.

You can also click on Find, type: qbittorrent

If this only happened in the last 24hrs, should be quick enough to find anything....

[FranciscoPombal]

@knighthartt

Since you mention an upgrade, I would suggest preforming a clean install of qbittorrent and seeing if the problem still reproduces.

This means:

1. Uninstall.
2. Backup the BT_backup folder in %AppData% (this is what contains the data about your added torrents)
3. Delete all qbittorrent config files in %AppData%
4. Install the latest version, leave all settings as default
5. Add some test torrents, see if the problem persists.
6. If there is no problem, incrementally change each setting to your preferred setup, making sure to restart qBittorrent between settings changes. If at any point the problem reappears, we now know it must be from some setting or some settings combination.
7. If there still is no problem, close qBittorrent, restore your BT_backup folder and see if the shutdown problem still happens. If the problem appears at this stage, we now know the issue must be with a specific torrent/tracker.
8. Post your findings here.

[knighthartt]

There are Application Error logs for each crash in the Event Viewer. Here's the latest:

Faulting application name: qbittorrent.exe、バージョン: 4.2.1.0、タイム スタンプ: 0x5df96484 Faulting module name: unknown、バージョン: 0.0.0.0、タイム スタンプ: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0xf0 Faulting application start time: 0x01d5d60d8017ba3c Faulting application path: D:\Program Files\qBittorrent\qbittorrent.exe Faulting module path: unknown Report Id: 77f59b27-b4b2-4313-9848-3852f2b738ce Faulting package full name: Faulting package-relative application ID:

[xavier2k6]

@FranciscoPombal how would you like to proceed? Do you still want @knighthartt to follow your steps?? Or should an attempt be made to attach debugger for stack trace?

11662 I have currently open with c0000005 access violation exceptions that are hinting both at Qt & libtorrent (currently 9 other issues open in relation to c0000005)

[knighthartt]

Some more:

障害が発生しているアプリケーション名: qbittorrent.exe、バージョン: 4.2.1.0、タイム スタンプ: 0x5df96484 障害が発生しているモジュール名: unknown、バージョン: 0.0.0.0、タイム スタンプ: 0x00000000 例外コード: 0xc0000005 障害オフセット: 0x0000000000000000 障害が発生しているプロセス ID: 0x1d30 障害が発生しているアプリケーションの開始時刻: 0x01d5d4072b7b344c 障害が発生しているアプリケーション パス: D:\Program Files\qBittorrent\qbittorrent.exe 障害が発生しているモジュール パス: unknown レポート ID: ea179f97-88f8-4755-b3b5-3ef234cb60fc 障害が発生しているパッケージの完全な名前: 障害が発生しているパッケージに関連するアプリケーション ID:

---

障害が発生しているアプリケーション名: qbittorrent.exe、バージョン: 4.2.1.0、タイム スタンプ: 0x5df96484 障害が発生しているモジュール名: unknown、バージョン: 0.0.0.0、タイム スタンプ: 0x00000000 例外コード: 0xc0000005 障害オフセット: 0x0000000000000000 障害が発生しているプロセス ID: 0x257c 障害が発生しているアプリケーションの開始時刻: 0x01d5d40674d1c05b 障害が発生しているアプリケーション パス: D:\Program Files\qBittorrent\qbittorrent.exe 障害が発生しているモジュール パス: unknown レポート ID: 68d8e02b-cc95-405e-b1c5-2bc9776e3c40 障害が発生しているパッケージの完全な名前: 障害が発生しているパッケージに関連するアプリケーション ID:

---

障害が発生しているアプリケーション名: qbittorrent.exe、バージョン: 4.2.0.0、タイム スタンプ: 0x5de6af08 障害が発生しているモジュール名: unknown、バージョン: 0.0.0.0、タイム スタンプ: 0x00000000 例外コード: 0xc0000005 障害オフセット: 0x0000000000000000 障害が発生しているプロセス ID: 0x3b2c 障害が発生しているアプリケーションの開始時刻: 0x01d5aa5865fcf4d5 障害が発生しているアプリケーション パス: D:\Program Files\qBittorrent\qbittorrent.exe 障害が発生しているモジュール パス: unknown レポート ID: c7bdccc2-d94e-4b94-aba0-1860261a426a 障害が発生しているパッケージの完全な名前: 障害が発生しているパッケージに関連するアプリケーション ID:

[FranciscoPombal]

@xavier2k6 yes, I think those steps should be followed. I cannot reproduce such crashes. @knighthartt It would be helpful if those could be in English.

[xavier2k6]

@FranciscoPombal I have a debugger attached basically 24/7 - when qbittorrent runs it's automatically attached & have got those exceptions from just running as normal, aka no interactions....adding torrents/pausing etc.....resume the torrents i want downloading & walk away.....

Know there's an issue when qbittorrent isn't showing aka crashed & auto catches stacktrace etc.

I don't think there's any reproducible method per-say...... I'm waiting for arvidn to get back to me on the last stacktrace anyway.....

[knighthartt]

@FranciscoPombal Sorry, it was a bit lazy of me to not throw it in Google translate first. I'll add in the actual timestamp to them too, I don't know why it shows up in hex(?) here.

---2020/01/26 0:17:14 Faulting application name: qbittorrent.exe, version: 4.2.1.0, time stamp: 0x5df96484 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0x1d30 Start time of the failing application: 0x01d5d4072b7b344c Faulting application path: D: \ Program Files \ qBittorrent \ qbittorrent.exe Faulting module path: unknown Report ID: ea179f97-88f8-4755-b3b5-3ef234cb60fc Full name of the failing package: The application ID associated with the failing package:

---2020/01/26 0:12:08 Faulting application name: qbittorrent.exe, version: 4.2.1.0, time stamp: 0x5df96484 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0x257c Start time of the failing application: 0x01d5d40674d1c05b Faulting application path: D: \ Program Files \ qBittorrent \ qbittorrent.exe Faulting module path: unknown Report ID: 68d8e02b-cc95-405e-b1c5-2bc9776e3c40 Full name of the failing package: The application ID associated with the failing package:

---2019/12/03 23:12:52 Faulting application name: qbittorrent.exe, version: 4.2.0.0, time stamp: 0x5de6af08 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process id: 0x3b2c Start time of the failing application: 0x01d5aa5865fcf4d5 Faulting Application Path: D: \ Program Files \ qBittorrent \ qbittorrent.exe Faulting module path: unknown Report ID: c7bdccc2-d94e-4b94-aba0-1860261a426a Full name of the failing package: The application ID associated with the failing package:

[knighthartt]

Is there any way to save a snapshot of my configured settings before uninstalling, like a text file export? Also, would uninstalling be any more likely to lose my torrent data than just downgrading to an earlier version?

[knighthartt]

I attempted the uninstall and fresh reinstall. No change. There was also a new bug, any non-magnet torrent I added would result in an "Invalid torrent" error message chain, with each error box showing one word or phrase of the torrent title. This bug appeared shortly before the uninstall (I made no changes in settings, qB or Windows) and stayed on the new install.

I'm going to try downgrading to 4.1.9 now.

[knighthartt]

Same problems with 4.1.9.1. The bug I mentioned is an I/O error. The torrents are saving normally to AppData\Local\Temp, save for the error, and need to be opened manually from the saved torrent file.

This is looking like a Windows problem more and more, but I'll try 32bit qB just in case. There's no problem loading torrents between 64 and 32bit versions right?

[knighthartt]

4.2.1 32bit is working perfectly, I just need to load my torrents now.

[Dhruvjdave]

Qbitttorrent crashes even if it is idle for more than 1 hour.It crashes if we dont touch it for more than 1 Hour Using 64bit

[Dhruvjdave]

Uninstalled 64bit and installed 32bit and now it does not crash anymore.So problem is with 64bit installers.

[FranciscoPombal]

@FranciscoPombal I have a debugger attached basically 24/7 - when qbittorrent runs it's automatically attached & have got those exceptions from just running as normal, aka no interactions....adding torrents/pausing etc.....resume the torrents i want downloading & walk away.....

Know there's an issue when qbittorrent isn't showing aka crashed & auto catches stacktrace etc.

I don't think there's any reproducible method per-say...... I'm waiting for arvidn to get back to me on the last stacktrace anyway.....

Most stacktraces you posted seem to point to qt issues though (or qbittorrent's usage of qt). It is nice that you have it setup like that, but if you can, you should also try to set it up so that it generates a core dump and not just the stack trace. That way, the cause of the crash can be examined in more detail inside a debugger.

[FranciscoPombal]

Since the issue seems to be related to 64 bit only, I think it is important to find out the root cause of this. 32 bit won't be around for much longer.

@xavier2k6 This guide should be enough https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps But I don't know anything about the format of the information it produces. For instance, is it usable on gdb, or is there anyway of converting to something that gdb can use (so that users on other platforms like linux can also examine the dumps without much hassle)? Maybe someone with more experience in debugging on windows can help out. @glassez thoughts?

[xavier2k6]

@FranciscoPombal i actually have dumps from 3 access violations.....2 full & 1 mini.......but they are very large 6gb+ & 15gb+ as i have full page heaps enabled to as per arvidn's request in other thread. I have analysis reports for them too just like the report i provided in the mem leak issue in mhtml format....can save as html if needed or maybe save as pdf......

[FranciscoPombal]

@xavier2k6 I am only interested in an image of the process's memory at the time of termination. It should be a few hundred megabytes in size at most, unless you added a gigantic amount of torrents or have the disk cache set to something silly like 512 MiB+.

From what I understand these are called "minidumps" in Windows land, and they can be loaded into, and debugged with, both visual studio and a tool called WinDbg. Also there are some third-party tools that can be used to do this.

I found some stuff that you may want to check out:

• https://github.com/jrfonseca/drmingw
• https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_minidump
• Apparently it is indeed possible to convert minidumps to core files (this would be useful for me): https://www.chromium.org/chromium-os/packages/crash-reporting/debugging-a-minidump#TOC-Use-gdb-to-show-a-backtrace
• official microsoft docs: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-postmortem-debugging and https://docs.microsoft.com/en-us/windows/win32/debug/configuring-automatic-debugging (check the sidebar for other subsections that might be of interest to you)

[xavier2k6]

will come back to you on it...(probably in my own issue/thread.)

[Dhruvjdave]

In 64bit I have set outstanding memory when checking to 64mb from 16mb.After that it has not crashed.Please try that.

[knighthartt]

I tried setting memory when checking up to 64mb, it doesn't help. Still crashing at just before 5 minutes without fail.

[BattouSaeen]

Hello, I have also been having these crashes, but in a longer interval and also more random. On average it takes an hour or more for it to crash but there have been times where it's happened earlier as well. My version is also x64 4.2.1.

In Event Viewer, the Exception code is: 0xc0000409

My settings have been exactly the same since 3.3.6 for years. I have almost never experienced any crashes.

What I was doing since upgrading to 4.1.9 and then 4.2.1 is seeing if I could make use of themes. I downloaded and applied one. Then wanted to see if I could modify it, I installed the latest Qt environment, opened up the relevant files. Could not find what I was looking for, then returned to stock, default theme. I may be biased in my memory for this, but the crashes have been coming up either since I installed the theme originally or 4.2.1 or Qt.

It feels as if just downloading a theme or installing Qt has messed things up.

I saw a mention of Disk cache size here - mine is 2048 and has been since 3.3.6.

I was also using x64 of 3.3.6.

[xavier2k6]

@BattouSaeen Can you create a new issue with the title Exception 0xC0000409 - 4.2.1 & put in as much info as possible under the new issue template. Will help you to create a dump file, maybe a stacktrace if possible to help diagnose where the problem is.

[BattouSaeen]

@xavier2k6 Thanks, done: https://github.com/qbittorrent/qBittorrent/issues/12064#issue-569779761

[knighthartt]

@BattouSaeen "Outstanding memory when checking torrents" is a component of the overall disk cache memory right? Or is it not included?

[BattouSaeen]

@knighthartt It seems to be a separate setting but I have never touched it. Mine is set to 16 MiB by default. I found these explanations on github and they may be useful:

Outstanding memory when checking torrents — the amount of memory to use when checking torrents. Higher numbers give faster rechecks but use more memory. Disk cache — amount of data that will remain in RAM before being written to disk. If set to 0, no data will be kept in RAM and instead it will be immediately written to disk (you might see performance impact.)

For me so far, I have reduced my memory overclock from 3200 to the rating from the manufacturer of 3000 and I have also reduced the disk cache from 2048 to 1024. It should be noted that 2048 had no issues on earlier versions of qB. So it was either the overclock or the disk cache or both of them together messing something up. SO FAR I haven't experienced a crash, been about 4-5 days now.

[Dhruvjdave]

I have set disk cache to auto and outstanding memory to 64mb.After that no crashes.

[xavier2k6]

@knighthartt your qBittorrent installation isn't in the normal "application path" ie "C Drive" - it's on "D Drive" Do you have correct read/write permissions set?

@FranciscoPombal Perhaps this could also be a reason for not being able to reproduce problem if normal "application path" is being adhered to under testing....

[knighthartt]

@xavier2k6 Yes I install most programs to D drive, where should I check the permissions?

[xavier2k6]

@knighthartt Please download & install Debug Diagnostic Tool v2 Update 3

Download & extract these predefined rules qBittorrent DebugDiag Rules_11.03.2020_Full PageHeap Enabled.zip to your desktop or where you would like to.

Run DebugDiag 2 Collection from your start menu. On the bottom right of the main window, you will find an Import button. Click the Import button & point it to where you extracted the rules above. The debugger rules should show active & as soon as there's a crash - it will capture a "stacktrace"

This will hopefully help point us in the right direction to where there's a problem in the program.

Your memory usage will probably increase more so than normal due to having a debugger attached.

[knighthartt]

xavier2k6, I'll try to get around to reinstalling 64bit again and attaching the debugger--I'm pretty sure it can't run alongside 32bit.

What are the default directory permissions I should look for? I can check D: itself, and my DL folders real quick.

[xavier2k6]

@knighthartt the 64bit debugger should be able to pick up qBittorrent 32bit as well as the rules are for all instances of qBittorrent......it may be best to re-install the 64-bit of qBittorrent as that seems to be where the issue was in the first place anyway.

[gitthehubs]

Same problem here since a day or 4. After an hour or 3 qbittorrent.exe crashes, without any error on the desktop, but leaving an event in the windows log.

Faulting application name: qbittorrent.exe, version: 4.2.2.0, time stamp: 0x5e7a27fa Faulting module name: qbittorrent.exe, version: 4.2.2.0, time stamp: 0x5e7a27fa Exception code: 0xc0000005 Fault offset: 0x0005c32b Faulting process id: 0x233c Faulting application start time: 0x01d604f5f02bb96c Faulting application path: X:\\qBittorrentPortable\App\qBittorrent\qbittorrent.exe Faulting module path: X:\\qBittorrentPortable\App\qBittorrent\qbittorrent.exe Report Id: 12eb2fe6-7d17-4e54-8a56-4e86dbfd3ca7 Faulting package full name: Faulting package-relative application ID:

First I thought it might have to do that I changed some memory settings in the advanced qbittorrent settings, but I changed them back to default but qbittorrent.exe still crashes after an hour or 3.

[xavier2k6]

@gitthehubs

Please download & install Debug Diagnostic Tool v2 Update 3

Download & extract these predefined rules qBittorrent DebugDiag Rules_26.03.2020_Full PageHeap Enabled.zip to your desktop or where you would like to.

Run DebugDiag 2 Collection from your start menu. On the bottom right of the main window, you will find an Import button. Click the Import button & point it to where you extracted the rules above. The debugger rules should show active & as soon as there's a crash - it will capture a "stacktrace"

This will hopefully help point us in the right direction to where there's a problem in the program.

Your memory usage will probably increase more so than normal & the program itself may become unresponsive for a period of time due to having a debugger attached.

As soon as a stacktrace is created, it will be ok to close/detach the debugger from qBittorrent

[gitthehubs]

@xavier2k6 In the windows event viewer, the security logs, I noticed always the same events during the crash of qbittorrent.exe , I will summarize them:

1. Event ID 4624, Logon. -> The logon of the computer account.
2. Event ID 4672, Special Logon -> The logon of the SYSTEM account.

3. Event ID 6417, System Integrity. The FIPS mode crypto selftests succeeded.

   Process ID: 0x294 Process Name: C:\Windows\System32\svchost.exe

4. Event ID 6417, System Integrity The FIPS mode crypto selftests succeeded.

   Process ID: 0x2568 Process Name: C:\Windows\SysWOW64\WerFault.exe

5. Event ID 6417, System Integrity The FIPS mode crypto selftests succeeded.

   Process ID: 0x14f0 Process Name: C:\Windows\SysWOW64\WerFault.exe

So I decided to disable the use of FIPS, you can do that with the group policy editor: Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options: System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing -> disabled.

For now this day qbittorrent.exe is running for 4 hours without any crash, where it before crashed after an hour or 3. Maybe the FIPS integrity check wanted to do an integrity check on the qbittorrent.exe executable and crashed for some reason. FIPS integrity checks are done on the background on all executables, I see those checks in the security log on windows executables and other programa's I have installed and running.

Maybe other people ( @knighthartt ) with this problem can check their windows security logs on the time qbittorrent.exe is crashing and generated the 'Application Error' log in the windows application log and check if they have the same security logs as I have. Or maybe the devs can replicate this error with enabling FIPS in the Windows security policy.

System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/system-cryptography-use-fips-compliant-algorithms-for-encryption-hashing-and-signing Security Options https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/security-options

I will see for the next few days if this solved the problem and keep you updated!

[gitthehubs]

I did have a crash with qbittorrent, so it has nothing to do with windows systems integrity checks.

But I have now updated to qbittorrent 4.2.3 and haven't had a crash till now.

[FranciscoPombal]

@gitthehubs this is disabled by default on Windows though, so it's probably not the same cause as others.. Still I wonder if this case could be fixed by enabling FIPS support in qBittorrent's OpenSSL build? Would that be related? I'm not user if it's enabled or not.

[thunderresistant]

same thing, this shit keeps crushing OP, have you managed to fix it?

[xavier2k6]

same thing, this shit keeps crushing OP, have you managed to fix it?

@thunderresistant Is it the same error code/crash? Can you post your OS/qBittorrent version etc.

[xavier2k6]

@gitthehubs can you carry out my instructions that I posted here: https://github.com/qbittorrent/qBittorrent/issues/11942#issuecomment-605497402

[thunderresistant]

same thing, this shit keeps crushing OP, have you managed to fix it?

@thunderresistant Is it the same error code/crash? Can you post your OS/qBittorrent version etc.

Hey thanks for your response.. I installed 4.2.3 32bit version after complete wipe of the previous 64bit. I'm on Windows 10 Pro, qBittorrent 4.2.3. So far, working roughly 10 hours without issues. Will report back after some time, cheers mate

[gitthehubs]

@xavier2k6 I ran a complete debugdiag analysis with all checkboxes checked, the result is in the .zip file. Strangely, at the end of the analisys it is saying: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. Stack Trace: System.Security.Cryptography.SHA1Managed..ctor() ..

But I also had a crash with fips disabled... I hope this helps you in the right direction.

Full_debug_analysis.zip

[xavier2k6]

@gitthehubs thanks for that, can you also post the debug diag logs.

The report shows that although you were having the same crash previously as reported in this issue for "Exception 0xC0000005" in an earlier version of qBittorrent, but now you are having an "Exception 0xC0000409" which you can post about & follow over in #12064.

Can you also post some more details about your OS/RAM/qBittorrent version etc please.

[gitthehubs]

@xavier2k6 ow oops... sure...forgot to add that logfile. :)

OS: Windows 10 Pro x64, version 1909 build 18363.720 (with all latest updates, but think I will get the 2020-04 update tomorrow/this week) RAM: 8 GB qbittorrent 4.2.3 (portable from portableapps, so the 32 bit version, there is no 64 bit version yet) (previous crash was with qbittorrent 4.2.2)

Because the debugger is catching the crash it did not make an event in the event viewer, but from yesterday, when the debugger was off, I have the following event: Faulting application name: qbittorrent.exe, version: 4.2.3.0, time stamp: 0x5e85f7a4 Faulting module name: qbittorrent.exe, version: 4.2.3.0, time stamp: 0x5e85f7a4 Exception code: 0xc0000005 Fault offset: 0x0005d509 Faulting process id: 0x490 Faulting application start time: 0x01d6116e096ffe7d Faulting application path: Z:\\qBittorrentPortable\App\qBittorrent\qbittorrent.exe Faulting module path: Z:\\qBittorrentPortable\App\qBittorrent\qbittorrent.exe Report Id: e49f3b80-967a-4ac8-94e8-8b2f3e277669 Faulting package full name: Faulting package-relative application ID:

Here it still shows exception 0xc0000005.

qbittorrentPID1128Date04_14_2020__Time_10_41_32AM891Log.txt

[xavier2k6]

@gitthehubs why is the stack trace showing (omitted) do you know & it's a very very short log, can you post the log in full please. the stack trace is very important info as it points in general to where the underlying problem could be.

(Oh, I see now some were omitted because they were over limit, but that doesn't explain why the other two are completely blank.)

Can you post any other previous logs from debug diag as well so I can look through them.

The fact that you are using a portable version from portableapps & using different drives/partitions could also be a factor in the 0xc0000005 issue.

[gitthehubs]

@xavier2k6 I have no idea why the stack trace showing (omitted)... you are the expert, I only provide the logs and crash analysis. :D The log is very short because the crash happened very quickly, the pc booted at 10:36 and at 10:45 qbittorrent.exe crashed.. just a few minuted after it started, so this log is all I have and I provided the full log already.

I cleaned the log directory yesterday, I had some problems with the debug analysis tool, which was due to internet restrictions, after a change in the firewall it ran without errors. So this is the only log I have for now. If needed and wanted I will run the debugger again for more crash dumps so I can provide more logs and analyses. But you have to wait for the next crash :D .

[xavier2k6]

I have no idea why the stack trace showing (omitted)... you are the expert, I only provide the logs and crash analysis. :D

(Oh, I see now some were omitted because they were over limit, but that doesn't explain why the other two are completely blank.)

I had edited my post previously.

@gitthehubs ok, will need more info - so please attach debugger again.

NOTE:

You can run qBittorrent in portable mode now without using the one from portableapps

[gitthehubs]

@xavier2k6 Ok, I will attach de debugger again, but I think it will be tomorrow again before I have a new crash. For some reason I had two days with crashes very quickly after the pc started, as mentioned above. The rest of the day it ran without a crash.

I downloaded the original qbittorrent x64 installer, but I don't really see a portable option. I followed the installer till the directory choice, but after that I only had the installation button to install the program.