Dang you Windows 10 update!!

[Dafunktyfunk]

Hi Everyone,

So my HS3 server is on a Windows 10 box and I NEED to stop it updating as it seems to be happening whenever it wants -taking down my HS3...

How have you been able to solve for this and just turning it off?

[jon00]

It depend on which version of Windows 10 you have because the Pro version allows WU behavior through its policy editor.

There are many articles on the Internet about this including setting the PC to use metered connections. For one, make sure you set WU to show you when your PC requires a restart. Shameless plug but you should really install this to notify you about Windows updates.

[Monk]

After unwanted updates & rebooting, I found that lack of access to the Internet works 100%, but hard to maintain the functionality we enjoy. As Jon mentioned - the Internet is littered with various tricks / settings. Further, correct about policies that only work depending on your version. The only method I now trust requires Pro - you can deny access to WU via a couple of policy changes. Can't find at the moment - will post later.
Edit -


Just for good measure


This is isn't for everyone. I personally do not use W10 for homeseer.
In my world, the computer must not reboot unexpectedly.

[Guest]

On my WIndows 10 Pro version, I use the advanced Update option to "pause" updates for the maximum 35 days (to set it, you set the resume date to the maximum date available).

I then make a note to myself for 30 days. When that day arrives, and when its convenient, I will shut down Homeseer, press the "Resume Update" button, let the updating finish, and reboot the server if the update did not. I also take this time to do things like backup the Homeseer directory.

I then go back to the advanced Update Options, do the Pause for 35 days thing again, and then restart Homeseer. This way my system is relatively up to date, but the updating is done on my schedule, rather than Microsoft's.

[Charles_cz]

There is no issue until some input is required after update and reboot. It just happened to me a few days ago. Homeseer would not start until I confirmed a couple of things. The best option I have found is to configure Local Group Policy > Administrative Templates > Windows Components > Windows Update > Configure Windows Updates

Enable, option 3 - Auto download and notify for install.

You can update on your terms without worrying about unwanted restarts and other stuff that comes with updates.

Windows PRO is needed for Local group policy editing.

I hope that helps. Charles

[Dafunktyfunk]

Thanks everyone!!!

The below is what happened to me to. I had to chose "Skip" and some other stuff.

I ended up blocking the updater ports for that one machine at my router. Now that will fill fail getting updates but bill still let incoming HSTouch requests to comine in.

I don't have a PRO lic and wont get one just for this. Thanks for the information.

There is no issue until some input is required after update and reboot. It just happened to me a few days ago. Homeseer would not start until I confirmed a couple of things. The best option I have found is to configure Local Group Policy > Administrative Templates > Windows Components > Windows Update > Configure Windows Updates

Enable, option 3 - Auto download and notify for install.

You can update on your terms without worrying about unwanted restarts and other stuff that comes with updates.

Windows PRO is needed for Local group policy editing.

I hope that helps. Charles

[Pete]

Here having issues relating to automagic updates on my HP tablet. The WIndows 10 Touch screen drivers do not work and its been like that since the beginning of Windows 10.

Homeseer 3 will not run correctly on WinEPEmbedded due to some dot NET requirements. Works fine on Windows 7 Embedded or Windows 8.1 Embedded.

I am still using Windows XPe for my tabletop touchscreens running Homeseer Touch. They work perfect with HSTouch / Speaker / SAPI.

Better too to migrate over to "old" Windows 2016 Server. No eye candy in Windows 2016 server; just the meat of the OS (well liked embedded).

Here running HS3 on Ubuntu 64 bit (very stable and never debends) and added Oracle Virtual boxes for running Windows only stuff like SAPI.

[Alex_W]

I use Linux for pretty much everything but I inherited a Window 10 machine that I use to run one DOS program that is used to access a call screening device. I was able to prevent updates by modifying the Hosts file. The file is located in C:\Windows\System32\drivers\etc. You will need to open the file as administrator in a text editor, make the file writable, and add the following lines:

127.0.0.1 *.download.windowsupdate.com

127.0.0.1 *.microsoft.com

127.0.0.1 *.update.microsoft.com

127.0.0.1 *.windowsupdate.com

127.0.0.1 *.windowsupdate.microsoft.com

127.0.0.1 download.microsoft.com

127.0.0.1 download.windowsupdate.com

127.0.0.1 ntservicepack.microsoft.com

127.0.0.1 test.stats.update.microsoft.com

127.0.0.1 windowsupdate.microsoft.com

127.0.0.1 wustat.windows.com

Keep in mind that this will redirect everything from these domains, so you may want to keep a copy of the original file that you can switch to if need be.

It worked for me. YMMV.

By the way, this is also an effective way to eliminate advertising and other annoyances.

[mterry63]

I doubt seriously that wildcards will work in a windows host file. Google seems to agree with me but I haven't tested.

[Pete]

Windows 10 does it's own thing with it's servers and every update wipes out any of your changes 100% of the time. Noticed this in the early days of Windows 10 when trying to make it lighter. Thinking a few years ago it was hitting some 250 plus Microsoft servers on the Internet for updates or Windows 10 peers on your home network. It is worst today as they keep adding the games and xbox stuff and news and weather stuff et al which you cannot remove the regular way.

You can just block them on the firewall but that becomes a PITA.

Not even sure it uses the host file for this stuff. I recall the tweaks being all registry edits at the time automated by a tweaker script.

Lately too there is always some new vulnerability annouced prior to the update so you are SOL whether you up date or not.

[Alex_W]

I doubt seriously that wildcards will work in a windows host file. Google seems to agree with me but I haven't tested.

You and Pete may be right. It seemed to work the last time I was online with the machine, but that was over a month ago. I typically don't connect the Window box to the network at all because I have no reason to do so. It just connects to the call screening box via USB. I'll try to find the original post that listed the domains and you Windows guys can play with it.

[Alex_W]

Here is the original article:

https://www.reddit.com/r/Windows10/c...sync_requests/

It refers to this Windows documentation:

https://answers.microsoft.com/en-us/...74d1526?auth=1

It looks as though Microsoft may be on to this:

https://www.bleepingcomputer.com/new...ged-as-a-risk/

I also found this:

https://www.site2unblock.com/win-updates-disabler/

Of course the one sure way to eliminate all issues with windows is this:

https://www.linux.org/pages/download/

Then you can make your computer do what you want it to do.

[logbuilder]

I use the metered connection hack. It works well on two different Win 10 servers each running HS3. For some reason others will say this doesn't work. Here is something to noodle on. I captured this screen just before I manually updated to the latest version. I also do not let HS3 automatically update. 254 days of uptime is pretty good. I wonder how long it would have run. This server also runs Blue Iris and Plex. Amazingly solid.

[Bill Brower]

Follow the instructions here to implement a host file that will overall help protect your PC:
http://winhelp2002.mvps.org/hosts.htm
But wildcards appear not to work in the HOSTS file.
Another solution may be here:
https://superuser.com/questions/1355...ows-hosts-file

[Alex_W]

I use the metered connection hack. It works well on two different Win 10 servers each running HS3. For some reason others will say this doesn't work. Here is something to noodle on. I captured this screen just before I manually updated to the latest version. I also do not let HS3 automatically update. 254 days of uptime is pretty good. I wonder how long it would have run. This server also runs Blue Iris and Plex. Amazingly solid.

Yes.

http://winhelp2002.mvps.org/hosts.htm

This is what I have used for years. Great stuff. I don't do Windows so I can't speak to its effectiveness in blocking updates. But it is fantastic for blocking crap.