Navigation:  7.19 > 7.19.0728

Released on March 5, 2020

Bug Fix: Autocomplete bug fixed

Following recent changes, when the first letter was typed in a list (in the minutes or the WBS), the complete word was no longer suggested. That worked only after 2 letters inputted.

Bug Fix: ‘Cannot Get Identifier’ message should now be very rare

QDV uses an internal process to uniquely identify a computer. This is used for licensing purposes, to identify the user when using a license server and to provide statistics to the administrators of the license servers.

However, this unique identifier (the 12 hex char key like E055AF45E34B) sometimes disappeared or was changed because now Windows Update can provide major releases of Windows 10 which are still called Windows 10 (Microsoft announced that he will never deliver Windows 11, 12…) so all future versions will also be called Windows 10! Unfortunately, when Microsoft issues such a major version inside Windows 10 it also changes the unique identifiers as he did when moving in the past from Windows 7 to Windows 8 for example. This affected our QDV identifiers and could require a new installation of QDV and a new license code request.

Now QDV bases the QDV identifier on keys which are no longer based on Windows but of course, it keeps the old identifiers so that your license code can work as usual and you can still use old versions of QDV. The new identifier is created when QDV is installed from its Setup program or when installed using Click-Once.

Notice that if you use Click-Once without administrative permissions on a computer where QDV has been previously installed using the Setup, the unique identifier is already built and will be used, no change. But, if you use QDV installed via Click-Once without administrative permissions and later you decide to install QDV with the Setup program (which requires such permissions), your unique identifiers will change and you will need to request a new license code. The rule is as follows: identifiers created by users having administrative permissions always have priority over identifiers created by users having no administrative permissions.