<![CDATA[[Implemented] Differentiate between 32-Bit and 64-Bit]]>The software-update tool that I am currently using shows the text "(64 Bit)" to indicate that an application is installed in the 64-Bit version.

This information is interesting to know, so it should also be displayed behind the application name.

I am not sure if there could be different versions available of the same application in 32-Bit and 64-Bit.
If yes, then it is important that you separate between 32-Bit and 64-Bit.

]]>https://vulndetect.org/topic/31/implemented-differentiate-between-32-bit-and-64-bitRSS for NodeWed, 22 Apr 2026 07:50:30 GMTThu, 17 May 2018 08:03:28 GMT60<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 30 Dec 2021 21:12:01 GMT]]>@tom IMHO it would make sense to show the "(64-Bit)" behind the name of the application, so users see the differences between two identical apps at once (without having to expand the entries).

By the way: if you set an entry to [Implemented], then you also have to update the Overview of Feature and Functionality Requests.
So just leave a comment, that it is implemented, and I will do the rest.

]]>https://vulndetect.org/post/5253https://vulndetect.org/post/5253Thu, 30 Dec 2021 21:12:01 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 30 Dec 2021 14:38:34 GMT]]>We made a general change some weeks ago, so VulnDetect will report the architecture for most apps.

]]>https://vulndetect.org/post/5244https://vulndetect.org/post/5244Thu, 30 Dec 2021 14:38:34 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Tue, 28 Dec 2021 20:13:48 GMT]]>An other example, why the text (64 Bit) is so important:

68902d36-b526-4074-83ec-a83908499a47-image.png

]]>https://vulndetect.org/post/5207https://vulndetect.org/post/5207Tue, 28 Dec 2021 20:13:48 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 20 Dec 2018 23:08:53 GMT]]>Technically VulnDetect is already detecting if an app is 32-Bit or 64-Bit (at least for most apps).
But it is not yet displyed.

]]>https://vulndetect.org/post/2231https://vulndetect.org/post/2231Thu, 20 Dec 2018 23:08:53 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 25 Oct 2018 17:38:43 GMT]]>When will this be implemented?
Would love to see if some apps are 32 or 64 bit.
Cheers

]]>https://vulndetect.org/post/1639https://vulndetect.org/post/1639Thu, 25 Oct 2018 17:38:43 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Sat, 19 May 2018 10:36:24 GMT]]>In the Windows 10 x64 task manager I see the text (32 Bit) behind some processes.
So Microsoft wants to point out older non-64-Bit applications. ;-)

]]>https://vulndetect.org/post/145https://vulndetect.org/post/145Sat, 19 May 2018 10:36:24 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 17 May 2018 16:22:56 GMT]]>@tom said in Differentiate between 32-Bit and 64-Bit:

but it seems most likely, that we will report individually, since most programs require separate updates for 32 and 64-bit versions

I agree

]]>https://vulndetect.org/post/109https://vulndetect.org/post/109Thu, 17 May 2018 16:22:56 GMT<![CDATA[Reply to [Implemented] Differentiate between 32-Bit and 64-Bit on Thu, 17 May 2018 16:13:22 GMT]]>The agent already has support for this. How we display this, is decided in each rule. Thus, we may treat this independently for each program, but it seems most likely, that we will report individually, since most programs require separate updates for 32 and 64-bit versions.
It is something that we will pay attention to and if you see errors in the results, then it should be reported individually for each program.

]]>https://vulndetect.org/post/106https://vulndetect.org/post/106Thu, 17 May 2018 16:13:22 GMT