Thank you for submitting this bug report! It makes a big difference to the VIPM Community and the VIPM Team. Please fill out as much or as little information below as makes sense to you -- we know your time is important and appreciate you sharing it with us. All of the information you provide (especially your VIPM Version, OS, and Steps to Reproduce) will greatly help us fix your bug.
Note: Don't feel you need to delete any of the placeholder text. The VIPM team will clean things up after you submit the issue.
Kind regards,
~ The VIPM Community Team
Short Description of the Bug (in one or two sentences)
Please provide a clear and concise description of the bug.
VIPM 2024.1.2637 is unable to load WF3132_cDAQ driver by WireFlow onto a Windows 11 Machine. The driver documentation says that is compatible with LabVIEW>=13.0 but fails to install on LabVIEW 2024 Q1 on a Windows 11 machine.
Version Information
VIPM Version and Build:
You can get this information on the Help >> About window or Splash Screen
VIPM 2024.1.2637
Operating System Version:
For example: Windows 10, Windows 11, Ubuntu 22.04.1, MacOS 10.14.6 (Mojave)
Windows 11 Pro for Workstations
10.0.22631 Build 22631
LabVIEW Version:
For example LV2019, LV2021 SP1, LV2022 Q3
LabVIEW 2024 Q1
LabVIEW Bitness:
32-bit or 64-bit LabVIEW?
64
Virtualization or Processor Version Information
Are you running in a Virtual Machine?
Do you have a Mac with an Apple M1 or M2 (ARM) Processor?
HP Z4 G4 Workstation
x64-based PC
Intel Xeon W-2225 CPU @ 4.10Ghz
Steps To Reproduce
What are the steps to reproduce the behavior? (you can replace the text below with your exact steps)
For example:
Go to '...' [screen/page/etc]
Click on '....' [button/menu-item/etc.]
Scroll down to '....' [section/list]
Expected behavior
What did you expected to happen (if the bug didn't exist)?
Successful installation of WF3132_cDAQ driver by WireFlow onto the machine
Actual Behavior
What to you observe that happened (instead of what you expected)?
VIPM gives an error that the driver is not compatible with this version of Windows.
Screenshots
If applicable, please add screenshots to help explain your problem.
A Note to You (With Appreciation from Our Team)
Short Description of the Bug (in one or two sentences)
Version Information
VIPM Version and Build:
Operating System Version:
LabVIEW Version:
LabVIEW Bitness:
Virtualization or Processor Version Information
Steps To Reproduce
Expected behavior
Actual Behavior
Screenshots
Anything else you'd like us to know?