LabWindows/CVI for Windows 2020 f1

[carlox]

Just for completeness, my GetCVIRTEVersion() function (revamped today, full project attached) compiled and run in LabWindows 2020 f3 returns 20.0.3.49152.
On a f2 2020 runtime it gives 20.0.2.49152.
I leave the obvious conclusions as an exercise for the reader.

[RobertoBozzolo]

Just to add some more data to the readers, I have a non-patched CVI 2020 installation where the properties window both for the IDE and the RTE give "20.0.0.49152"

And I tested it with my function, which returns - again both for the IDE and the RTE- "20.0.0f0" when querying both ProductVersion and FileVersion.

[Wolfgang]

The list of known issues has been updated with the fixes of patch 3. Obviously CVI2020f3 now officially supports Windows 11 and also fixes three known bugs, see here.

[JKneale]

Another way of determining if a patch was loaded is to do a windows file explorer search for DLLs, then sort by date.  Look for files that were added shortly after that date, such as C:\Program Files (x86)\National Instruments\CVI2017\bin\msvc64\cviiw.dll updated 8/9/2018.

The look in the .cab files associated with that patch for similar files of the same size and date.  ADEF1.cab has cviiw64.dll.CVI1701.ADEF1 with the same date and size.  If that file is present with that date on the target PC, then I'm assuming that it has the F1 patch loaded