Preventing Reboots in Windows 10 for Long-Term Tests

[RTSLVU]

---

@Eric1977 wrote:

I thought Windows 10 gave you the option to download the updates but not load them or to notify the user that there were updates pending. This would require the PC to have human interaction for updates. Is that not the case anymore?

---

I think you can only "delay" them for like 30 days before they will auto-install. 

[Eric1977]

That stinks. I guess the only solutions are to disable Windows Updates or to not allow internet access on that machine.

[wiebe@CARYA]

---

@Eric1977 wrote:

That stinks. I guess the only solutions are to disable Windows Updates or to not allow internet access on that machine.

---

Or convincing whoever is responsible that a real solution (cRIO or Win IoT) isn't that expensive compared to 1..n wasted test runs.

What would be really bad is to first waste time on tweaking Windows (AKA rowing against the stream) and then having to invest because it didn't work.

I stopped trying to tweak Windows years ago, long before it got this bad. 

Either way, good luck. We are interested in the results. 👍

[JohnJoyceFlusso]

I'll look into other ways if we end up having to do another system for another product; hadn't encountered WinIoT before (ex WinCE?). At that point there would become a major re-architecting exercise as the whole thing has grown organically to one with 24 USB-serial adapters, which appear to be fighting each other for the USB bus at times.

It's one of those situations where a few hours figuring what to tweak in Win10 could do the job at the cost of a few of hours of my time; if it doesn't then it's quite a lot of hours and potentially hardware cost, plus the general 'leap into the unknown' factor. Hence being prepared to spend a few hours trying to make the current setup work - basically it's a calculated gamble.

I'll try to remember to post an update in a few weeks when it works (or not, as the case may be).

Thanks for the various pointers, in particular the one to how to fix "Reboot-AC" and friends.

[RTSLVU]

---

wiebe@CARYA wrote:

---

---

Or convincing whoever is responsible that a real solution (cRIO or Win IoT) isn't that expensive compared to 1..n wasted test runs.

👍

---

I don't believe Windows IoT is really an option here as IoT is basically Windows CE and LabVIEW was never supported on that.

Windows 10 IoT Core can run UWP and . NET applications, C++ application will run but are limited in the features that can be supported.

[wiebe@CARYA]

---

@JohnJoyceFlusso wrote:

 hadn't encountered WinIoT before (ex WinCE?).

---

It serves the same purpose, but the concept is completely different. Win IoT is the successor of Windows Embedded, IIRC.

WinCE was simply source code, and could be compiled to any target. Given enough time, because that probably wasn't easy.

Win IoT is basically like normal Windows, but you have more control over what is installed (and more importantly what not). So you can actually turn Candy Crush Saga off 😎. So migrating to it doesn't need to be that bad.

It is however only allowed to be used on 'single purpose computers', so you can't use it for your desktop (single purpose is probably defined somewhere).

You pay licenses depending CPU type and nr of cores, IIRC. Which is just weird.

[wiebe@CARYA]

---

@RTSLVU wrote:

---

wiebe@CARYA wrote:

---

---

Or convincing whoever is responsible that a real solution (cRIO or Win IoT) isn't that expensive compared to 1..n wasted test runs.

👍

---

I don't believe Windows IoT is really an option here as IoT is basically Windows CE and LabVIEW was never supported on that.

Windows 10 IoT Core can run UWP and . NET applications, C++ application will run but are limited in the features that can be supported.

---

No, we've used Win IoT to run LabVIEW applications. It can be configured as normal Windows, without modules that you don't want.

I'll check, as I recall there are flavors of Win IoT, for instance for ARM devices and for Intel.

[crossrulz]

---

@JohnJoyceFlusso wrote:

At that point there would become a major re-architecting exercise as the whole thing has grown organically to one with 24 USB-serial adapters, which appear to be fighting each other for the USB bus at times.

---

You might want to invest in something like this: 16-Port USB-to-Serial Adapter Hub 

[rolfk]

---

@RTSLVU wrote:.
I don't believe Windows IoT is really an option here as IoT is basically Windows CE and LabVIEW was never supported on that.

 It depends. Windows IoT is not just Windows IoT. There are various (last time I checked at least 3) variants. Only the Enterprise variant runs on standard Intel hardware and supports running Win32 apps like Windows 10 does. It is the Windows 10 version of Windows 7 Embedded, The others are limited to running UWP and .Net apps and usually require the Windows App Store in order to install additional software.

[Hooovahh]

We typically have multi-month testing going on here, and an embedded cDAQ is the way to go.  We have a private network between it and a Windows PC for data collection and reporting, and that Windows PC has a second network port for the facility.  These PCs reboot all the time for various IT related reasons and the test just runs 100% on the remote controller.  LabVIEW makes it quite easy to deploy to embedded Linux device, as long as you stay in the NI eco system.

Oh I do love those USB serializers.  We use the 12 port Startech ones, but there seems to be a 14 port limit on Linux RT.