Categories

  • Announcements regarding the VulnDetect project

    14 Topics
    123 Posts
    T
    Version 3.4.0.0 is the latest Stable release. It can be downloaded from here: https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.exe https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.msi

  • Post requests for apps that are missing

    351 Topics
    2k Posts
    OLLI_SO
    The portable version of Super Productivity is still not detected. Only the installed version is detected. Please detect also the portable version. The current version is 15.0.3. Here the information extracted from the EXE file: File name and path: C:\PortableApps\PortableApps\_SuperProductivity\superProductivity-x64.exe Product Name: Super Productivity Internal Name: Original Filename: File Description: ToDo list and Time Tracking Company: Johannes Millan Legal Copyright: Copyright © 2025 Johannes Millan Legal Trademarks: Comments: File Version String: 15.0.3 File Version: 15.0.3.0 Product Version String: 15.0.3 Product Version: 15.0.3.0

  • Post requests for apps that you wish to see updated automatically

    23 Topics
    38 Posts
    T
    The release notes are out: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuoussept2025qfe.html#dccontinuoussepttwentytwentyfiveqfe This is the official fix for the printing issue: 4529876: Data loss in printing PDF on Reader and Acrobat The packages for Acrobat/Reader in VulnDetect and PatchPro was released earlier this morning.

  • Announcements regarding the VulnDetect project

    48 Topics
    48 Posts
    A
    With the release of Microsoft SQL Server Management Studio 22, we have introduced an improved solution for patching, deployment, and uninstallation. Users are no longer required to submit an installer manually, and automatic patching is now available. However, this change breaks the existing PatchPro update chains, and they must be manually replaced by deleting the current configurations and publishing new ones. PatchPro Configurations PatchPro provides three configurations for SSMS: Microsoft SQL Server Management Studio (Install:Only) (x64) (EXE) Microsoft SQL Server Management Studio (Upgrade:Only) (x64) (EXE) Uninstall Microsoft SQL Server Management Studio 21 Recommended Migration Process (SSMS 21 → SSMS 22) If your systems are currently running SSMS 21, we recommend the following steps: Publish all three configurations listed above. Assign Uninstall Microsoft SQL Server Management Studio 21 to all systems you plan to upgrade. Assign Microsoft SQL Server Management Studio (Install:Only) to install SSMS 22 onto all systems. After all systems have been upgraded and SSMS 21 has been fully replaced by SSMS 22: You can delete the assignments or the entire configurations. Then assign Microsoft SQL Server Management Studio (Upgrade:Only) (x64) (EXE) to enable future automatic patching. VulnDetect Notes To upgrade from SSMS 21 → SSMS 22, it is necessary to uninstall SSMS 21 first. We now provide uninstall jobs for all SSMS versions. To complete the upgrade: Create an uninstall job for SSMS 21 (or any previous version). Create an install job for SSMS 22. Once the uninstall/install job sequence has completed, your systems will be fully prepared for future automatic patching of SSMS 22.

  • Detection errors and issues should be posted here

    448 Topics
    2k Posts
    OLLI_SO
    Microsoft has added new icons to their Microsoft 365 apps. Details see here: https://microsoft.design/articles/fluid-forms-vibrant-colors/ Here are the new app-icons (extracted from the EXE files): Microsoft Access [image: 1760814196638-microsoft_access_2025_icon.png] Microsoft Excel [image: 1760814215615-microsoft_excel_2015_icon.png] Microsoft OneNote [image: 1760814238547-microsoft_onenote_2025_icon.png] Microsoft Outlook [image: 1760814265083-microsoft_outlook_2025_icon.png] Microsoft PowerPoint [image: 1760814284009-microsoft_powerpoint_2025_icon.png] Microsoft Publishe [image: 1760814303383-microsoft_publisher_2025_icon.png] Microsoft Word [image: 1760814329793-microsoft_word_2025_icon.png]

  • Detection errors and issues should be posted here

    45 Topics
    149 Posts
    G
    @Tom : Nvidia app and its former (unsafe) versions are now reported in one bundle. Unsafe 7zip version which is bundled with this soft is still not reported with Nvidia app bundle but separately.

  • This category will be used to keep track of user contributed suggestions

    143 Topics
    472 Posts
    OLLI_SO
    I am using the CSV export on a daily base, it is really very useful. But sone things should really be improved. Recommended Version For some tools (like “MiTeC Icon Explorer") the recommended version (5.2.0) is older, than the installed version (5.3.0). In the list of applications you do not show a recommended version. In my CSV export I have 15 applications, where the recommended version is different, but only for 3 entries the recommended version is newer. Therefore, the recommended version should not be exported, when it is older or equal to the installed version. Export Tool Collections All tools from "Sysinternals" are bundled as "Sysinternals Suite". The whole suite including all apps is not exported. You should export the package headline ("Sysinternals Suite") and also all included tools. I do not know if it causes trouble when the package headline ("Sysinternals Suite") has an empty column "File". Identical naming for Apps in Tool Collections All tools from Sysinternals begin with the text "Sysinternals" (like "Sysinternals DebugView" or "Sysinternals Process Explorer") what is great, when you sort the exported CSV. Also all tools from MiTeC begin with the text "MiTeC". But only some tools from NirSoft begin with the text "NirSoft" and none of the tools from Nenad Hrg begin with "Nenad Hrg". Export status "Patch" and "Update" In the UAT instance you show the status "Patch" and "Update". This status is not yet exported, but it is really very helpful! Please consider these suggestions for the CSV export.

  • This category will be used to keep track of bugs reported by users

    48 Topics
    284 Posts
    OLLI_SO
    @GregAlexandre OK, then I mark this issue as solved.

  • Feel free to discuss what was good or bad in Secunia PSI and what you expect from VulnDetect

    18 Topics
    70 Posts
    T
    During testing of the Google Chrome 131.0.6778.109 MSI package, we found that it was broken, resulting in Exit Code 1603 after attempting to spawn a UAC prompt as the SYSTEM user. This issue occurs both when upgrading via VulnDetect and Intune. In some cases, it even breaks the existing installation during rollback of the failed update. As a result, we pulled the update before releasing it to customers. Once Google has fixed the Enterprise "ready" MSI installer, we will update the package and make it available after thorough testing. Please "upvote" the following post by Mikhail Gurin if you are affected by this and have a Google account. Hopefully, this will help make Google prioritize the fix: https://support.google.com/chrome/thread/311347547 For reference, we use the following installers: https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise.msi https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise64.msi We also tested the EXE-based installers for offline deployment but found that these are incompatible with MSI-based installations. It should be noted that the MSI works if launched interactively as a regular user who can approve the UAC prompt.