<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FreeFileSync - Bundling Issue]]></title><description><![CDATA[<p dir="auto">I have installed <strong>FreeFileSync</strong> normally (not Portable) and I see the following files:</p>
<p dir="auto"><strong>1.</strong> C:\Program Files\FreeFileSync\FreeFileSync.exe<br />
<strong>2.</strong> C:\Program Files\FreeFileSync\Bin\FreeFileSync_Win32.exe<br />
<strong>3.</strong> C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe</p>
<p dir="auto">File <strong>1.</strong> is  detected by VulnDetect.<br />
It is only 464 KB in size and is only a <strong>Launcher</strong> that starts the correct EXE file (files <strong>2.</strong> or <strong>3.</strong>) depending on your system.<br />
So when I start <strong>FreeFileSync.exe</strong> (launcher) then the <strong>FreeFileSync_x64.exe</strong> is started as child process:</p>
<p dir="auto"><img src="/assets/uploads/files/1552816631014-freefilesync_process_tree.png" alt="FreeFileSync_Process_Tree.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">So here you should show <strong>FreeFileSync</strong> (the launcher) as root application and show <strong>FreeFileSync (32-Bit)</strong> and <strong>FreeFileSync (64-Bit)</strong> as bundled applications.</p>
]]></description><link>https://vulndetect.org/topic/710/freefilesync-bundling-issue</link><generator>RSS for Node</generator><lastBuildDate>Mon, 17 Aug 2026 23:01:57 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/710.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Jun 2019 16:09:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to FreeFileSync - Bundling Issue on Tue, 25 Jun 2019 13:11:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/olli_s" aria-label="Profile: OLLI_S">@<bdi>OLLI_S</bdi></a> Like I said below, then this is not the same case as the other ones you mentioned.</p>
]]></description><link>https://vulndetect.org/post/3082</link><guid isPermaLink="true">https://vulndetect.org/post/3082</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Tue, 25 Jun 2019 13:11:36 GMT</pubDate></item><item><title><![CDATA[Reply to FreeFileSync - Bundling Issue on Fri, 21 Jun 2019 10:32:17 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tom" aria-label="Profile: Tom">@<bdi>Tom</bdi></a> said in <a href="/post/3077">FreeFileSync - Bundling Issue</a>:</p>
<blockquote>
<p dir="auto">Coincidentally, bundling is also useful in the cases where the original vendor supplies multiple main executables (either with different architectures or due to updates) and these happen to be the best choice for detecting the presence of the program.</p>
</blockquote>
<p dir="auto">FreeFileSync provides a 32-Bit and a 64-Bit version.<br />
Same as CCleaner, Speccy and many others (that are already bundled).</p>
]]></description><link>https://vulndetect.org/post/3078</link><guid isPermaLink="true">https://vulndetect.org/post/3078</guid><dc:creator><![CDATA[OLLI_S]]></dc:creator><pubDate>Fri, 21 Jun 2019 10:32:17 GMT</pubDate></item><item><title><![CDATA[Reply to FreeFileSync - Bundling Issue on Thu, 20 Jun 2019 17:45:49 GMT]]></title><description><![CDATA[<p dir="auto">The purpose of bundling is not to include all executables or libraries.</p>
<p dir="auto">In the case of FreeFileSync it is sufficient to detect the "launcher" as it contains sufficient with information and the vendor seems to have a solid policy of supplying useful and updated version information in both the launcher and the architecture specific executables.</p>
<p dir="auto">Bundling is primarily used to "bundle" certain applications (or in some cases libraries) such as 7-Zip, Java, Flash, NodeJS and others, which shouldn't be updated separately, but rather together with the program that bundles these.</p>
<p dir="auto">Coincidentally, bundling is also useful in the cases where the original vendor supplies multiple main executables (either with different architectures or due to updates) and these happen to be the best choice for detecting the presence of the program.</p>
<p dir="auto">We only display bundled programs, because we know that many power users such as you and <a class="plugin-mentions-user plugin-mentions-a" href="/user/anselm" aria-label="Profile: Anselm">@<bdi>Anselm</bdi></a> (I guess) like to know about these and their security state (and so do I :) )</p>
]]></description><link>https://vulndetect.org/post/3077</link><guid isPermaLink="true">https://vulndetect.org/post/3077</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Thu, 20 Jun 2019 17:45:49 GMT</pubDate></item></channel></rss>