Latest server update (2023.12.28.0146) will not run on Windows 7

Heartfelt thanks to you three for continuing to do amazing work and being incredibly approachable and supportive.

Thank you for working on a solution and for the explanation on what happened. Just to clarify, this is a temporary solution and we should assume to continue to get future updates that we are still required to upgrade our older OS?

I would like to suggest that as part of your licensing check call, you send the OS information so that you can be aware of what users are running out there.

I will start working on my server upgrade. Its a multi-day project that I have not been looking forward to. For my purposes, my "antique" server was still perfectly adequate. In my case, being on WHS, MS did not give a good upgrade path for the product.

From the DVR server product page (from where you download the installer):

Channels DVR Server is officially supported on Windows 10 and up.

1 Like

For those of you running into the Windows 7/Home Server 2011 issue, please try to update to the latest pre-release. We've been able to get a new build that works on Windows 7.

1 Like

Thank you folks. I noticed the OS check was implemented and tested this morning. I noticed a discrepancy and noted it here:

Thank you as usual for outstanding support.

As everyone here knows, this Dev team is outstanding!!
Thanks

3 Likes

Steam seems to have come to the same conclusion.

Steam Support :: Windows 7 and Windows 8 Support (steampowered.com)

In regards to Home Server 2011, I did a check for pre-release and it successfully moved me to 2024.01.04.1920. Thank you.

For me, this is now a test server as I completed the week long migration to a completely new Windows 11 PC. The channels migration itself was relatively painless (Thank you!). My week long effort was mostly about the my storage array (fully backing up, reorganizing, preparation), but also included building the new PC, installing OS and apps, etc. I have been completed many successful server migrations at work. Its just a lot of hours to make sure everything gets there and works. Its amazing how many places data gets stashed in the windows systems.

There seems to be a industry wide movement recently to deliberately cutoff the old OS versions. I think its sad when an application "could" still work on those platforms. Think of the environmental waste this constant churn is creating.

I'm sure someone will pipe up and comment about how much time can be saved by eliminating testing these old versions. But lets be realistic, is every version of windows 10 tested? I tried to find an actual count, the list I found was ridiculously long.

Anyhow, thanks again for the improved update process. Many of us have spouses that are very unhappy when their dvr disappears.

I'll pipe up, but not about time saved from testing software on EOLed OSes. The reason that new and updated software is not tested on old unsupported operating systems is because they are old and unsupported. They are security hazards, no longer updated, and cannot reliably support running new software.

If you wish to continue to run older and unsupported software, you are more than welcome to do so. In fact, I do run old versions of software that are no longer supported, and do so on OSes that are old and no longer supported. But I don't expect current software to run on those systems, and I don't expect the old software to implement new features.

(You don't complain to the automakers that you can't play your 8 tracks in that new Audi you've been eying, do you? You don't expect your 64-1/2 Mustang to work with your satellite radio subscription without doing some upgrades, right?)

I think there are a few things that have been happening:

  1. Operating System vendors are deciding the longest amount of time they want to invest in backporting security fixes to older Operating Systems (and things that are actually new features that look like security fixes, like newer cryptography, certificates, etc)
  2. Some Operating System vendors (like Apple) have been decided to stop supporting old hardware with newer Operating Systems and thus prevent them from being upgraded
  3. Software vendors of software that is in any way connected to the internet not seeing the value in supporting Operating Systems that are factually insecure and have actually been abandoned by the Operating System vendor

The one that I think sucks the most is that #2 item. It really is the thing that is contributing to e-waste, etc.

But the other ones? In cases where the hardware is able to run the newer Operating Systems, why should the whole industry be burning lots of resources for fixing and supporting old systems that potentially are exposing everyone to security risks when there are alternatives?

The thing that is a bummer about all of this, is that the things that we have had to do to support old versions of macOS and Windows that are EOL'd by Go have ended up being very small numbers of lines of changes. But, there have been some recent changes, for instance, that made Go on Windows have 1 more bit of randomness in the newer API than the older one (which is a big deal in randomness).

1 Like