Troubleshooting an run-time problem I noticed that while my development environment which I keep updated using NI Update Service was LabVIEW 2015 SP1f1 - the run-time engine available on ni.com was at fix 5 (LabVIEW SP1 f5). A manual search revealed an f5 patch available for the development environment too, but it is not listed by NI Update Service...(nor have I seen any other since patch f1). Not under critical updates, nor under Upgrades and service packs.
As soon as LabVIEW 2016 was out NI Update showed *that* as an update path (a path I will not use as I will always keep the previous versions untouched, and rather install 2016 in addition to it or on a different machine (should be an option to do that instead of updating by the way)), but still not any of patches.
How come? Is the patch not considered critical, nor an update - so it ends up in no category in the Update Service?
When you install NI software, you are given the option to ‘Allow National Instruments to search for important updates’, can you remember if this box was checked?
Please use the link below to manually install the LabVIEW 2016 SP1 (32-bit) f5 Patch:
Sure, I know that. Do you get the f5 patch as an option?
The NI Updater is set to do an automatic search on every restart, and we also manually run it every now and then. However the f5 patch has never been discovered. I found out by accident that there was a patch and installed it then without the NI Updater.
Same problem. Running version 18.104.22.168 of Update Service. No patches after f1 showed up for 2015SP1.
Win7 SP1 64bit machine with 32bit versiona of LabVIEW 2013SP1, 2014SP1 and 2015SP1 dev systms installed.
If I recall correctly, some patches are for combinations of software and/or specifically. It could be that the updates decided that patch was not necessary.
I also didn't see 2015 f5 or 2016 f1 in NI Update Service, which for me is at version 22.214.171.124. I also don't see either of these patches here: http://www.ni.com/white-paper/13503/en/
Maybe they're not considered important enough?
It could be a bug in the updater, it could be caused by some unique combination of factors that affect the updater, or the updater might be (too) selective as you say arteitle.
Only someone from NI can answer that.
In my opinion the updater should list every applicable update, and let the users decide if they want to apply them or not. I noticed 2016 f1 only because a post mentioned that it was required for some sample code to work (new type of channel wire), so it is clearly nice to have...