@GregAlexandre This is expected and it is due to the way that Office is updated. It is likely to require a reboot before the vulnerable file is removed and replaced by the one in "Updates"

@OLLI_S The version should be fixed now. Can you verify that it correctly shows 8.1.14. Xinorbis is one of those were it needs to be done manually based on user feedback, that is why it says "Unknown, please report".

@scottsan We will come back with either a new version soon or some suggestions about how to troubleshoot it.
The only workaround so far is by using the ignore option in the registry as discussed in this thread:
https://vulndetect.org/topic/144/work-in-progress-exclude-specific-drives-folders-from-scan

We are currently releasing some breaking changes. So the VulnDetect service is currently unavailable. We will be back in a few minutes.

See the changelog:
https://vulndetect.org/topic/472/release-secteer-vulndetect-personal-corporate-and-backend-2019-01-15

We are upgrading VulnDetect Personal and Vulndetect Corporate this morning. So you are likely to see a bit of downtime while we deploy new servers.

Version 0.10.8.0 was released today.

The updated version will also be made available via auto updating in a few minutes.

Manual upgrades can be done using this link:
https://vulndetect.com/dl/secteerSetup.exe

A new agent has been release today, more details here:
https://vulndetect.org/topic/411/release-secteer-vulndetect-agent-v0-10-7-0

Version 0.10.7.0 was released today.
https://vulndetect.com/dl/secteerSetup.exe

This version fixes a bug related to auto updating of the VulnDetect agent itself.

Users with patching enabled, can "auto update" to version 0.10.7.0, please ping us here on the chat or via email tom at vulndetect dot com if you wish to test auto updating.

Today we published a new UI and backend update with a tech preview of the auto updating / patching for VulnDetct Personal.

This is disabled by default, if you wish to get access and test this, please write to tom at vulndetect dot com or send us a message on the chat (@tom).

Please note that this is functionality from the Corporate edition and that the UI part of it will be completely redone. The underlying technology will remain the same for both Personal and Corporate.

You can find the updated changelog here:
https://vulndetect.org/topic/472/release-secteer-vulndetect-personal-and-backend-20-11-2019

Hi,

We've been a bit silent lately, mostly because we've been extremely busy.

Today we updated the changelogs, so you can get an idea of the recent changes.

What is less clear when reading the changelogs is the upcoming addition to SecTeer VulnDetect:

• Automated updates

We will launch a "tech preview" of the automatic updating capability this week - this will be an "opt-in" feature for a while. Mostly, because we need volunteers to test the quality of the updates, especially the support for localized versions and 32/64bit architecture is important to test.

Please write to "tom [at] vulndetect [dot] com" if you wish to enable auto updating and help testing.

The automated updates in SecTeer VulnDetect is powered by chocolatey, usually referred to as choco. Initially SecTeer will provide homegrown packages from our own repo only. Later we may add support for third party repos, including the official choco repo. We chose to use choco, because this a popular, established and well maintained open source project, that aims to "packify" software management. Today, most software on Windows is managed by a variety of installers and update mechanism, the goal of standardizing this is beautiful and we would like to support those efforts.

In turn choco uses an official Microsoft package standard called NuGet.

/Tom