LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Windows 11 API call to prevent Windows Update during critical test


@Station8 wrote:

I wonder, with Windows 11, if disconnecting from the internet will actually prevent the automatic reboot. I'll have to experiment. I believe that Windows Update downloads the update packages in the background in the hours prior, and then the actual installation action that includes the reboot may not need an internet connection.

 


In theory this could happened only if you have adjusted "working hours" and then outside of these hours Windows will perform "postponed" upgrade. Just keep computer running for 24 hours, and if PC will not reboot, then will not do that in next 20 hours with very high probability.

We delivering industrial systems and if they should work in 24/7 mode, then local IT department usually perform some adjustments (in GPO, I believe), then systems running without any interruptions days and weeks, and still connected to rhe network (behind firewall). Usually when I performing 24 hours- or over weekend- manufacturing test, then I keep PC connected to the network, because I would like to have status, it is just very convenient.

 

I'll start tomorrow a simple experiment. I have one unused PC with fresh installed Win11 (was definitivily rebooted in the past during updates). I will stop windows update service, turn on metered connection, disable updates in GPO, then keep it running and connected to the internet and check maximal reachable uptime, just for fun.

0 Kudos
Message 11 of 16
(331 Views)

@Andrey_Dmitriev wrote:

I'll start tomorrow a simple experiment. I have one unused PC with fresh installed Win11 (was definitivily rebooted in the past during updates). I will stop windows update service, turn on metered connection, disable updates in GPO, then keep it running and connected to the internet and check maximal reachable uptime, just for fun.


Okay, the Experiment was started today. Three things was changed — Windows Update Service Disabled, GPO modified to prevent updates and restart and Ethernet Connection set to Metered.

Screenshots under Spoiler (in German, sorry about that):

Spoiler

This is all about Windows 11 Enterprise LTSC 24H2 26100.2033 installed three months ago:

Screenshot 2024-10-11 08.39.35.png
Windows Service Disabled:

01 Screenshot 2024-10-11 08.23.22.png

GPO:

Screenshot 2024-10-11 08.27.32.png

This one:

Screenshot 2024-10-11 08.29.50.png

and this one:

Screenshot 2024-10-11 08.32.14.png

I general I see in GPO lot of configuration possibilities, in theory it should be enough to adjust all of them here without additional actions.

Anyway, Metered connection is enabled:

Screenshot 2024-10-11 08.33.18.png
This disabled, and grayed out, because was configured in GPO:

Screenshot 2024-10-11 08.37.42.png

Latest updates was downloaded and installed:

Screenshot 2024-10-11 08.36.57.png
Screenshot 2024-10-11 08.38.47.png

After these manipulations above I checked the Registry Key NoAutoUpdate and this was set to 1 as expected (can be added manually if needed):

Screenshot 2024-10-11 09.30.37.png


Finally restarted:

Screenshot 2024-10-11 09.03.47.png

One small thing - the Windows Update Service was started again, I deactivated this one more time (needs to found setting how to disable it completely), then added scheduled task with call "net stop "Windows Update" with Admin privileges at logon:
Screenshot 2024-10-11 09.12.07.png

PC is connected to Internet:

Screenshot 2024-10-11 09.21.00.png
Current uptime - 12 miniutes

Screenshot 2024-10-11 08.53.00.png

will see how long this PC can run without restart.

Message 12 of 16
(311 Views)

Nice job documenting your steps. I share the concern about updates being pre-downloaded and being scheduled outside working hours, but I remember using the same settings. There might be more services running that might trigger interruptions. For example, I remember a forced update from IE to MS Edge (triggered by a separate background service) restarting the regular update services as well.

0 Kudos
Message 13 of 16
(290 Views)

Perhaps you have already done this, but, if not, it might be worthwhile to contact your local Microsoft rep and ask them how to disable Windows Updates for just like a scenario you have. The Sales Division certainly won't know so ask for a Windows OS Engineer.

0 Kudos
Message 14 of 16
(273 Views)

For anyone who doesn't have access to Group Policy but does have a firewall or router under their control, you can also block the Windows Update sites themselves.

 

Microsoft was nice enough to provide troubleshooting guides on how to be sure that your Windows updates work, such as this one:

https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/wind...

 

If you go about halfway down the page you can see they provide a nice list of sites and protocols.  So if you do require network access but want to stop updates, you can simply deliberately block all those sites instead of allowing them.

 

You should still periodically (monthly?) unblock them to get updates.  Just... not in the middle of a test.

Message 15 of 16
(252 Views)

@Andrey_Dmitriev wrote:

@Andrey_Dmitriev wrote:

I'll start tomorrow a simple experiment. I have one unused PC with fresh installed Win11 (was definitivily rebooted in the past during updates). I will stop windows update service, turn on metered connection, disable updates in GPO, then keep it running and connected to the internet and check maximal reachable uptime, just for fun.


Okay, the Experiment was started today. Three things was changed — Windows Update Service Disabled, GPO modified to prevent updates and restart and Ethernet Connection set to Metered.will see how long this PC can run without restart.


The experiment continues successfully, the PC is still up and running since 11th Oct, stays connected to the Internet all the time and was not restarted (who said the Windows is not stable OS?). Current uptime is over fifty days and counting, so I can confirm that the steps introduced above does the job pretty well:

Screenshot 2024-12-02 09.04.34.png

49,71 days was most critical milestone, because every 4294967295 seconds the 32.bit tick counter resetted to zero (remember old WinNT bug). Anyway, I think from this point the computer can run indefinitely long (as long as the electronic components will allow, someday capacitors will dry and the motherboard or drive will die). Unfortunately can't keep this PC running for years, because we have e-check time to time, this will expire soon for this PC, then it must be down, in additional running long time without critical security updates is also not a good idea. And I guess, the metered connection was most important and fully sufficient to prevent updates, this single option is most easiest way to keep PC running without restart.

Message 16 of 16
(86 Views)