09-24-2026 10:34 AM
Hello all,
"Patch 2" for the 2026 Q3 version of the Real-Time module is seemingly broken, as installing it results in compactRIO targets being in this state:
If you were unfortunate enough to install this update, you can downgrade to the previous version, which works fine, using this command (must be run as admin and from "C:\Program Files\National Instruments\NI Package Manager\"):
.\nipkg.exe install "ni-labview-2026-rt-module-en=26.1.0.49365-0+f213" --allow-downgrade --accept-eulas
09-24-2026 10:59 AM
Have you also performed a firmware update?
Just recently found out that there are also firmware updates available (Latest for our controller is 2026Q3) which are maintained independently of the Real-Time images themselves, but which sometimes are dependent on certain versions of drivers. We tried to install the 2026 Q3 firmware update on a 2025 Q3 RT-Linux but were told that certain drivers were too old.
I was told they are independent... apparently not quite.
09-24-2026 11:09 AM
Yes, the compactRIO-9040 that I directly work with is on 2026 Q3 and has firmware 26.5.
This is kind of irrelevant though, as the target that I show in the picture above is a "permutation of chassis and c-series cards", not a real target on my network.
Installing "Patch 2" of the 2026 Q3 Real-Time module simply breaks one's ability to code for compactRIOs or their FPGAs.
I have also confirmed this with the classic "uninstall everything and install everything fresh"; the real-time module is still broken.
09-25-2026 09:55 AM
Thank you for bringing this to our attention. We have reproduced the issue (tracked as Bug 4080129) and are working to resolve it at critical priority. We apologize for the inconvenience this has caused.
09-25-2026 02:34 PM
Update: While we work on providing a proper resolution, here is a workaround that involves updating the Windows Registry. It should allow you to perform typical RT workflows with Patch 2.
Warning: Inappropriate changes to the Windows Registry can disable your operating system. To safeguard against such an event, you should backup your existing registry by choosing File » Export... after launching the Registry Editor and before making any changes.