Reply to thread

Message

<blockquote data-quote="infinite.loop" data-source="post: 186153" data-attributes="member: 10723">it seems that there are leftovers from the WinTvUsbCi in your system. that causes the issue. (windows registry / dll's)you coul try to use the windows restore point feature to get to the point befor the installation.the problem to support the WinTvUsbCi is not technical. we have been adviced to remove the support (right after we avvounce it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite4" alt=":mad:" title="Mad&nbsp; &nbsp; :mad:" loading="lazy" data-shortname=":mad:" /> ), because the sdk we got was send to us &quot;by accident&quot; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite4" alt=":mad:" title="Mad&nbsp; &nbsp; :mad:" loading="lazy" data-shortname=":mad:" />no news from hauppauge since that time (~2months ago) :sorry:</blockquote>

[QUOTE="infinite.loop, post: 186153, member: 10723"] it seems that there are leftovers from the WinTvUsbCi in your system. that causes the issue. (windows registry / dll's) you coul try to use the windows restore point feature to get to the point befor the installation. the problem to support the WinTvUsbCi is not technical. we have been adviced to remove the support (right after we avvounce it :wtf: ), because the sdk we got was send to us "by accident" :bitch: no news from hauppauge since that time (~2months ago) :sorry: [/QUOTE]

Verification