top | item 43348819

(no title)

crschnick | 11 months ago

Are you using the LTSC version on your desktop or also for some of your remote systems? I think if it's only for the desktop, I can fix that as that isn't really intended to be limited to the Professional version. Didn't really test it on an LTSC system so far, so I will look into that

discuss

von_lohengramm|11 months ago

On my desktop, but I am trying to access it "remotely" from the same machine. I have a Linux host and an LTSC KVM guest with GPU passthrough so I can cleanly isolate (and more easily reproduce) my Windows environment. Currently, I just use VSCode's Remote SSH to develop in Windows, but it leaves much to be desired.

crschnick|11 months ago

Ah I see. The reason it complains now is that the LTSC systems are called Windows Enterprise LTSC, didn't even know that they fell under the Windows Enterprise category.

You can run XPipe on a local LTSC installation, you just can't connect to one remotely because it thinks that you are connecting to a Windows Enterprise server. I will think about how to solve this the best way, because that wasn't on my radar