Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    The reboot is almost definitely due to problems in the driver. It could just be incompatibilities, but I would guess it's probably more than that. Compatibility mode does not change how the software is allowed to interact with the hardware, so it will not affect drivers in a way that makes them suddenly work. Your options are probably to either find an alternate driver that offers some functionality, or create a Windows 7 Virtual Machine, if the hardware can be accessed in a VM. Commented yesterday
  • Windows 7 device drivers are not compatible with Windows 10. Time to learn Linux or use a Windows 7 VM. Commented yesterday
  • Thanks for the replies. I already thought as last solution to run a virtual box with a light Linux Debian based distro with TVHeadend as a server to stream the TV channels to the Host Win 10, in case the Linux driver works within the box, but this will consume a lot of RAM, I guess. No solution for a compatible driver for Win 10 then? no driver hacking or mod or anything possible? Commented yesterday
  • Do you have the source code for the Windows driver? Even with the source code available (a) It might not be simple to identify and fix the issue (b) Not sure if Windows still allows loading unsigned drivers. Commented yesterday
  • Nope, no code available anywhere I presume. Regarding the virtual box, would it be possible to send the streaming directly to the Host instead of via LAN? Also, what virtual machine would be better and lighter? VM or VirtualBox? Commented yesterday