NPVR4 and MPC-HC problem

[sub]

But explain why NTPVR5 on LTSB2016 does not work until i upgrade the framework

I don't have a big team of people testing on different versions of Windows. This is a very small project. I test on my version of Windows, which is the currently version, fully patched.

[sub]

What output do you get if you run the following from a command prompt?

DeviceHostWindows.exe -discover

[The Solutor]

What output do you get if you run the following from a command prompt?

DeviceHostWindows.exe -discover

Code:

Eccezione non gestita: System.IO.FileLoadException: Impossibile caricare il file o l'assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' o una delle relative dipendenze. La definizione di manifesto dell'assembly specificato non corrisponde al riferimento all'assembly. (Eccezione da HRESULT: 0x80131040)
  in DeviceHostWindows.Program.Run(String[] args)
  in DeviceHostWindows.Program.Main(String[] args)

P.S. a few words in technical Italian shouldn't be a problem, but if you need a translation I'm here 

P.S2 I didn't even remember that but the desktop app crashes as well

[The Solutor]

I think it is only fair for sub to limit support the current and updated desktop Windows environment.  How many users purchase Enterprise volume licenses that LTSB requires? 

Technical curiosity isn't your best quality isn't it ? 

Jokes aside.

#1 .net updates aren't mandatory, you can have a Server 2016 machine which is fully updated but still on 4.6.1

#2 is plenty of power user that prefer to spend 60$ or so for a stable and debloated windows rather than spend 0$ and have an ever changing machine, which is a privacy nightmare.

#3 is plenty people that use at home the Server 2016 essentials as file server/backup machine and also as HTPC, that have no problem to spend 250/400$

[sub]

#1 .net updates aren't mandatory, you can have a Server 2016 machine which is fully updated but still on 4.6.1

#2 is plenty of power user that prefer to spend 60$ or so for a stable and debloated windows rather than spend 0$ and have an ever changing machine, which is a privacy nightmare.

#3 is plenty people that use at home the Server 2016 essentials as file server/backup machine and also as HTPC, that have no problem to spend 250/400$

Regardless, it's a small project, which gives away the software for free, and can only so much. For the most part we do a pretty good job, and a whole lot of people managing to use it without issue. There is always going to be some setups that are odd versions of OS or supporting software which it may have problems with.

I definitely don't test against any versions of Window Server

[sub]

What output do you get if you run the following from a command prompt?

DeviceHostWindows.exe -discover

Code:

Eccezione non gestita: System.IO.FileLoadException: Impossibile caricare il file o l'assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' o una delle relative dipendenze. La definizione di manifesto dell'assembly specificato non corrisponde al riferimento all'assembly. (Eccezione da HRESULT: 0x80131040)
  in DeviceHostWindows.Program.Run(String[] args)
  in DeviceHostWindows.Program.Main(String[] args)

P.S. a few words in technical Italian shouldn't be a problem, but if you need a translation I'm here 

P.S2 I didn't even remember that but the desktop app crashes as well

It looks like it's complaining it can't find netstandard 2.0, which is installed with .NET Runtime 4.6.1. Maybe try installing that if you haven't already.

[The Solutor]

But explain why NTPVR5 on LTSB2016 does not work until i upgrade the framework

I don't have a big team of people testing on different versions of Windows. This is a very small project. I test on my version of Windows, which is the currently version, fully patched.

I'm just providing educated guesses and infos you may have missed.

I think are valuable infos exactly because of the small team, but then is up to you to decide if they are helpful or not and if they are wellcome or not.

Surely I'm not here to waste your time.

[The Solutor]

What output do you get if you run the following from a command prompt?

DeviceHostWindows.exe -discover

Code:

Eccezione non gestita: System.IO.FileLoadException: Impossibile caricare il file o l'assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' o una delle relative dipendenze. La definizione di manifesto dell'assembly specificato non corrisponde al riferimento all'assembly. (Eccezione da HRESULT: 0x80131040)
  in DeviceHostWindows.Program.Run(String[] args)
  in DeviceHostWindows.Program.Main(String[] args)

P.S. a few words in technical Italian shouldn't be a problem, but if you need a translation I'm here 

P.S2 I didn't even remember that but the desktop app crashes as well

It looks like it's complaining it can't find netstandard 2.0, which is installed with .NET Runtime 4.6.1. Maybe try installing that if you haven't already.

4.6.1 is installed.

I see that now there is a 4.6.2 update I'll try that and I'll report back ASAP

[The Solutor]

Technical curiosity isn't your best quality isn't it ? 

I expect that I have installed NextPVR and various NextPVR clients on far more platforms out of curiosity then anyone else on this forum.

Then you should understand my curiosity I expressed on first post (which isn't just a curiosity as I clearly explained)

Unsupported hacking of BDA driver onto Win Server

Look.. is better if you argue of a matter you know well, and that is clearly not the case.

BDA and streaming components are included in any Windows Home Server 2011 flavors AND in any Windows Storage Server 2008R2 essentials as well

BDA and streaming components are included in Server 2012 essentials and Server 2012R2 Essentials

BDA and streaming components are included in Server 2016, 2019 and 2022

Perhaps i can't see where the problem is supposed to be in installing the BDA components on servers from the stone age era which lacked them

 and installing WMC past Win 7 is not my cup of tea though, it never was better then NextPVR. 

Thanks god we live both in democratic countries  and we can express more or less biased opinions w/o being jailed.

BTW WMC was officially available until win 8.1 and aside there isn't any client program who beat it in usability and smoothness, WMC was and still IS the only SW based option to watch the TV for cable card users in the US.

So can we stop with the OT?

[The Solutor]

@sub

Sorry for the delay, but I decided to use a fresh installation to be as sure as possible that anything else is interfering

In short this is a virgin installation of the RTM version 10240.16384.

The only things installed are the 4.6.2 .NET framework, NTPVR5, and the vc installer you linked.

I didn't even bother to install the tuner's driver