WinUtil-for-Channels: A Community Windows Installer for Channels DVR and Related Projects (focusing on those not Docker-based) Plus OliveTin EZ-Start

Playground
,
#1

The idea with this project is to provide a straightforward way to install community projects related to Channels DVR, along with various other "foundational" pieces required to support those projects in a Windows environment.

I'm calling it WinUtil-for-Channels, and it can be launched with a single command in a PowerShell window -- with no installation required. This project is a fork of the popular christitustech/winutil, specifically tailored for Channels users:

irm https://raw.githubusercontent.com/bnhf/cdvr-winutil/main/winutil.ps1 | iex

That will, in turn, launch two Windows. One will be your PowerShell console, where you can see what's actually happening with a given installation, and the other is the application's GUI:

Screenshot 2026-08-14 100834
Screenshot 2026-08-14 1008341440×753 99.5 KB

Each of the apps shown can be installed, uninstalled or upgraded using this interface. In addition to right-click options for each of those, there are also small dropdown buttons that will take you to the app's online home, to the app's local WebUI, or to an application's GUI.

This is intended to be a Windows dashboard for any and all of the pieces you might want (or need) to install Channels DVR and any of the community projects designed to work with it. Each of the buttons will install the "native" or non-Docker version of a given project.

The exception is OliveTin EZ-Start, which through its own dashboard will give you access to a variety of Docker-based projects via Project One-Click. The OliveTin EZ-Start installation requires only a single variable -- which is the password you'd like to use for Portainer (which is a WebUI for Docker):

Screenshot 2026-08-14 130013
Screenshot 2026-08-14 1300131920×1080 204 KB

If you're a Windows user, this is your one-stop-shop for installing and maintaining everything related to Channels DVR. Combine this with OliveTin EZ-Start, and every known Windows-native or Docker-based CDVR extension is at your fingertips.

The source code can be found here, if you'd like to review it:

If you have any suggestions for other packages/projects to include -- let me know!

6 Likes
#2

Thanks for including Clicker. Here are icons in various formats and sizes if you'd like: Clicker/assets at main · mackid1993/Clicker · GitHub

2 Likes
#3

Maybe the non-docker version of Frndly TV?

Not sure if there is a big enough demand for it.

I haven't used it in quite a long time.

#4

Are these intended to install the projects on the host Windows PC? Or, can this interface be used to install projects on another device?

#5

On the Windows PC you're running WinUtil-for-Channels, but since it's a "no installation" script itself, you can run it wherever and whenever you want -- on any Windows system. Plus, you'll always be running the latest version right from GitHub.

#6

That's a good thought. I'll probably add it.

#7

one thing that would be helpful is either a link directly to this window, or a script that turns flow control off when installing cdvr
Screenshot 2026-08-14 190352
Microsoft doesn't make it easy (for normal people) to get to these settings anymore

also since I just did this myself, I thought I'd share the target for a desktop shortcut.

powershell.exe -Command "irm https://raw.githubusercontent.com/bnhf/cdvr-winutil/main/winutil.ps1 | iex"
#8

I'm not running arm, install failed.

[2026-08-14 21:54:16.595] [INFO] [Package] Querying latest release for mackid1993/Clicker
[2026-08-14 21:54:17.191] [INFO] [Package] Downloading Clicker-Setup-1.3.1-arm64.exe for Clicker
#9

Let me grab my MacBook and see what broke.

#10

@Shaggylive I just successfully downloaded directly from GitHub and installed on my MacBook Pro running Windows under Parallels. The ARM64 version installed, no issues. So that means no Prism emulation, it's just straight Windows on ARM. Can you download from GitHub and let me know if it works? Because it could be a bug with this tool.

#11 
Clicker-Setup-1.3.1-arm64.exe
sha256:316f58fb37020abf587fc6fe07ffb3067262133e707b36cd298e2ac0ddefba5b
18.5 MB
4 hours ago

Error; This program does not support the version of windows your computer is running.


Clicker-Setup-1.3.1.exe
sha256:5d1d89073988d83cc79618bd4ffcb450ff2ce5720d7853d7b3e3eb51117f6456
21.4 MB
4 hours ago

installs and works as expected.

#12

What kind of computer do you have?
Are you running a Snapdragon chip?

If not, then this is querying the ARM64 architecture for everyone rather than querying the architecture and then downloading the right release.

This is so not @bnhf's fault as I just added ARM64 support like yesterday because someone desperately asked for it, and I thought I'd be nice and do it, even though it was kind of a huge pain. :joy:

Someone asked for picture in picture support, and I said no. And then I realized, hmm, that might be nice. And I spent an entire day getting it working. LOL.

Just so bnhf knows, everything is built through CI on GitHub. So the naming is just completely consistent. I don't intend on changing the naming scheme. I even have the macOS build notarizing on GitHub, which is freaking awesome.

#13

Looks like this is an issue with WinUtil-for-Channels. I don't believe there was an ARM version of Clicker when I was testing. I'll see what's going on with this tomorrow.

1 Like
#14

It's 100% my bad. Someone asked for it and I added it, and I didn't know you were working on this, but I appreciate you including my tool in your tool!

#15 
Device name	IdeaPadSlim5-16IRU9
Processor	Intel(R) Core(TM) 7 150U (1.80 GHz)
Installed RAM	16.0 GB (15.7 GB usable)
Device ID	B0CC5420-5E9B-474F-9209-4CF54E80EE64
Product ID	00330-81627-04704-AA370
System type	64-bit operating system, x64-based processor
Pen and touch	Touch support with 10 touch points


Edition	Windows 11 Pro
Version	25H2
Installed on	‎12/‎27/‎2024
OS build	26200.8875
Serial number	INVALID
Experience	Windows Feature Experience Pack 1000.26100.334.0

lol, I know, instead of busting chops, i kept my post simple..

I really like how you implemented it like PIP, I was expecting vlc style 'Always on Top"

2 Likes
#16

I really like how you implemented it like PIP, I was expecting vlc style 'Always on Top"

Thank you for that. I appreciate the compliment. It keeps me going because honestly, building apps like this is sometimes thankless. Much better than someone complaining that Dolby Vision doesn't work. :joy: I actually wrote a really snarky response and then cleaned it up after the fact. Like, how can you expect me to support Dolby Vision when Samsung doesn't even support Dolby Vision?

#17

Also, thank you, fellow Lenovo person. Although I'm more of a ThinkPad type contrary to my username, I like my track point. I do have the MacBook for development because it's really good for that. And it's also really fast.

#18

wrote many a college paper on the freeway after work on my way to class with an 11" p2 thinkpad. it fit so nicely against the steering wheel, and track point didn't bounce. :racing_car:
nowdays i'm addicted to fingerprint reader.

#19

There are several issues with what you've put in place with SLM. I believe by trying to build your own package installer instead of using the existing .bat file directly, you've most likely created a function and maintenance gap for yourself. But if you like the work, I'm not going to stop you! For instance:

  • Missing the option to set the port, which could be a big issue given the default is 5000.
  • Also doesn't set the port in the environment variables.
  • Due to this, the Windows Firewall rule seems too open for my taste as it is opening all ports instead of just the selected one.
  • The name of the folder is StreamLinkManager instead of StreamingLibraryManager.
  • No control over where the installation happens.
  • The build sequence does not start SLM to run in the background, but is putting it as a foreground window. It should execute the Task Scheduler item since that is already set to run in the background, or do what the .bat does.
  • No ability to select the Prerelease version.

I did test the upgrade, and was pleased that it protected the program files, so no problems there (did all the steps and safety requirements I'd expect).

Uninstall did not remove the Windows Firewall rules.

#20

You're quite right. There were issues I was trying to address with the batch file, but the result was not what I was after. I'm working on an update now that will use the batch file with just a couple of on-the-fly fixes -- but it'll be your batch file otherwise.

1 Like