02-23-2023 09:54 AM
Hello forum
the solution from this post below does not work anymore, the rights on the reboot file are simply restored by Windows.
https://forums.ni.com/t5/LabVIEW/Preventing-Reboots-in-Windows-10-for-Long-Term-Tests/td-p/4164732
Does anyone have a new solution for this problem? Until about last summer it was possible to simply deactivate the Windows Update Service, since then Microsoft seems to have decided to take away the right to do so even for admins. In the meantime even taking away the rights for SYSTEM so far that it should not be able to execute reboot has been removed, the rights are simply restored.
IT will not let me introduce a firewall, is there a solution to prevent Windows from updating so that I can switch it on during weekends? Our production runs 24hours a day and windows will not let me limit the Update hours accordingly.
Thanks, Raphael
02-23-2023 03:18 PM
If you need to run LabVIEW and have it "insulated" from Microsoft, then you need to run it on using a non-MS Operating System. There are (at least) two ways to do this: Run LabVIEW on a Linux box, or run a "mixed" (a.k.a. "Real-Time") configuration with a PC running Windows, capable of being forced to update by the Powers that Be, talking to a LabVIEW Real-Time system running an NI-supported Real-Time OS, such as NI Real-Time Linux.
Bob Schor
02-24-2023 03:37 AM
Hi Bob
thanks for your insight, two interesting approaches.
Last time I checked for another project the virtual way was excluded in the NI license agreement. As of now it seems allowed, unsupported however: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAiJSAW&l=en-CH
The real time OS probably would work for LabView, however I run TestStand and a whole bunch of drivers on Windows that are only available on this platform.
Thanks a lot!
Raphael
02-27-2023 03:54 AM
Block Windows Update adress?
02-27-2023 11:10 AM
Simple solution: Don't give it internet access
There is no reason automated test equipment needs internet access.
Also if it is Windows 10 Professional there are ways to force it to not automatically install updates with Registry settings, Google it.
03-08-2023 03:23 PM - edited 03-08-2023 03:24 PM
We have lots of Windows 10, and a few Windows 11 machines that never reboot without being told to. I just disabled the Reboot Task Scheduler item, under the UpdateOrchestrator. To prevent it from being reenabled I set the file to read only, after disabling it, and then removed permissions on the file so it couldn't be edited. I think I then took away ownership of the file but I can't remember if that was needed. This was described in the superuser post you linked to. Between tests I will perform a Windows update, and allow it to reboot a few times until it is up to date. But when a test is running it keeps it from rebooting mid test.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord