Click here to go to the forum index Click here for the home page
 
Author Message

<  Computer connections  ~  Win10 anniversary update - driver signing enforcement

Page 2 of 4
Goto page Previous  1, 2, 3, 4  Next
Stu's TV
Posted: Tue Jun 27, 2017 6:11 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Thanks Bizman and again TopTapper

I had a search on the forum but couldn't really find anything! Maybe my search skills need improving!

So in frustration (and before I saw your reply TopTapper, your caveats did make me chuckle), I used to the Devices and Printers Window to Unistall the WinUSB driver, ran z4t again, the toppy did not appear in the Devices currently Connected, so I cycled the power on my Toppy, in appeared in the Devices Connected, hit the install button and got this in the debug log

ini file 'zadig.ini' not found - default parameters will be used
0 devices found.
libwdi:info [detect_version] Windows 7
Driver Installation: FAILED (No such device)
0 devices found.
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_8087&PID_07DA&REV_7869
libwdi:debug [wdi_create_list] BTHUSB USB device (0): USB\VID_8087&PID_07DA\6&8386542&0&3
libwdi:debug [wdi_create_list] got hardware ID: USB\ROOT_HUB30&VID8086&PID1E31&REV0004
libwdi:debug [wdi_create_list] USBHUB3 USB device (6): USB\ROOT_HUB30\4&1B6EEE9&0&0
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_174F&PID_148D&REV_0827&MI_00
libwdi:debug [wdi_create_list] rtsuvc USB device (7): USB\VID_174F&PID_148D&MI_00\7&267E667C&0&0000
1 device found.
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_8087&PID_07DA&REV_7869
libwdi:debug [wdi_create_list] BTHUSB USB device (0): USB\VID_8087&PID_07DA\6&8386542&0&3
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_11DB&PID_1000&REV_0100
libwdi:debug [wdi_create_list] WinUSB USB device (4): USB\VID_11DB&PID_1000\6&8386542&0&2
libwdi:debug [wdi_create_list] Device description: 'Topfield (libusb-winusb)'
libwdi:debug [wdi_create_list] got hardware ID: USB\ROOT_HUB30&VID8086&PID1E31&REV0004
libwdi:debug [wdi_create_list] USBHUB3 USB device (7): USB\ROOT_HUB30\4&1B6EEE9&0&0
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_174F&PID_148D&REV_0827&MI_00
libwdi:debug [wdi_create_list] rtsuvc USB device (Cool: USB\VID_174F&PID_148D&MI_00\7&267E667C&0&0000
Using inf name: Topfield_(libusb-winusb).inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created C:\usb_driver\Topfield_(libusb-winusb).inf
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:debug [installer process] got parameter Topfield_(libusb-winusb).inf
libwdi:debug [process_message] got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_11DB&PID_1000\6&8386542&0&2'
libwdi:debug [process_message] got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_11DB&PID_1000&REV_0100'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-2659952142-704720065-1091483357-1001'
libwdi:debug [installer process] using syslog 'C:\WINDOWS\inf\setupapi.dev.log'
libwdi:debug [installer process] sylog reader thread started
libwdi:debug [process_message] switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_11DB&PID_1000&REV_0100 - please wait...
libwdi:debug [syslog] ERROR: Unable to convert log entry to UTF-8
libwdi:debug [syslog] >>> [Device Install (UpdateDriverForPlugAndPlayDevices) - USB\VID_11DB&PID_1000&REV_0100]
libwdi:debug [syslog] >>> Section start 2017/06/27 17:53:33.371
libwdi:debug [syslog] cmd: C:\usb_driver\installer_x64.exe Topfield_(libusb-winusb).inf
libwdi:debug [syslog] ndv: INF path: C:\usb_driver\Topfield_(libusb-winusb).inf
libwdi:debug [syslog] ndv: Install flags: 0x00000001
libwdi:debug [process_message] switching timeout back to finite
libwdi:debug [installer process] more recent driver was found (force option required)
libwdi:debug [process_message] installer process completed
Driver Installation: FAILED (Resource already exists)


on further inspection (via Devices and Printers Window) the WinUSB driver has been installed again!!!!!!

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Stu's TV
Posted: Tue Jun 27, 2017 6:44 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Just tried it again. Uninstalled WinUSB, did a cold re-start on the toppy (disconnected from the PC, ran z4t, plugged in the USB lead, it appeared on the list. I then looked at the Toppy via the Devices and Printers window (before hitting the 'Install Driver' button in z4t), and the WinUSB had already been installed!!

At a bit of a loss now.......

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Geoff Bacon
Posted: Tue Jun 27, 2017 9:33 pm Reply with quote
Frequent contributor Joined: 12 Jan 2007 Posts: 3941
But does it work or are you just looking at the reports ?

Geoff

_________________
TopManager program
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; StopExit v1.01; EPG2MEI v0.96; QuickJump 1.72; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MHEG On/Off A3; MyInfo B5.6; WSSkiller V2.12d; CrashTrace v0.4; fsSave 1.1; PruneEPG 1.0;
Sig generated by MyInfo on 17/1/16
View user's profile Send private message Visit poster's website
Stu's TV
Posted: Tue Jun 27, 2017 9:50 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Hi Geoff

No still cannot communicate with it! When I try and connect with TopManager I get this:

Connecting to Toppy1...
Attempting to open USB connection using tfWinUSB.dll ...
Attempting to open USB connection using XP.dll ...
Attempting to open USB connection using Vista.dll ...
Failed to establish connection to Toppy using any of the USB drivers
<<< Connection failed
TopManager has not detected any programs that would prevent use e.g. Altair
<<< Check Toppy is switched on and cable is connected


Last edited by Stu's TV on Wed Jun 28, 2017 1:45 am; edited 1 time in total

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Stu's TV
Posted: Wed Jun 28, 2017 1:17 am Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Post deleted - barking up the wrong alley!

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Geoff Bacon
Posted: Wed Jun 28, 2017 9:11 am Reply with quote
Frequent contributor Joined: 12 Jan 2007 Posts: 3941
No real idea - still on XP here.

Try
1) disconnect toppy
2) removing WinUSB again
3) reboot to safe mode with driver signing disabled (you know how to do this better than me)
4) check whether WinUSB has been reinstalled (some other kit may be using it)
5) check whether or not the pc knows anything about the toppy (it may still be in the registry and/or in the device manager structures)

I seem to remember someone using a program to uninstall the driver before running z4t but I can't locate the post

Are you using Kaspersky - this previously caused problems.

Geoff

_________________
TopManager program
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; StopExit v1.01; EPG2MEI v0.96; QuickJump 1.72; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MHEG On/Off A3; MyInfo B5.6; WSSkiller V2.12d; CrashTrace v0.4; fsSave 1.1; PruneEPG 1.0;
Sig generated by MyInfo on 17/1/16
View user's profile Send private message Visit poster's website
Stu's TV
Posted: Wed Jun 28, 2017 5:07 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Hi Geoff

Thanks for that.

I can only see the driver for the Toppy when the Toppy is connected to the USB. Then, once I have removed the driver the Toppy becomes invisible! Nothing happens when hit the 'Properties' button in the 'Topfield (libusb-winsub) Properties' Window, the toppy is no longer visible in the Devices and Printers Window and it is not on the list in Zadig for Windows. As soon as I unplug and reconnect the Toppy Windows loads the (default? WinUSB.SYS) driver and I'm back to where I started......

It doesn't look to me like anything else uses the WinUSB.SYS Driver, as far as I can see. There is a check box when Uninstalling the WinUSB.SYS Driver from the Toppy - Delete the driver software for this device. I've tried both options, same result!

I still can't see the Toppy in Device Manager, with or without the 'default' driver (which I still think is very odd) only in Devices and Printers. But I can see many references to it in the Registry (but, I'm getting well out of depth in the Registry!)

No, not using Kaspersky.

So, in summary (as far as I can tell): as soon as I connect the Toppy, Windows assigns the WinUSB.SYS driver.
z4t fails to/cannot load the correct driver
If I try and replace the driver manually Windows won't let me, telling me that it thinks the best driver is already installed.

I can't boot my PC in Safe Mode and with driver signing disabled, only one or the other.........

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Geoff Bacon
Posted: Wed Jun 28, 2017 6:41 pm Reply with quote
Frequent contributor Joined: 12 Jan 2007 Posts: 3941
Your initial post implies that the toppy used to work about a year ago.

Is there any chance you can rollback the driver to that time? (possibly harder because you have tried to load it several times recently).

Another post implies that you can delete the .inf for the driver and this will cause windows to prompt before installing a driver i.e. you could then run z4t when it prompts to load a driver. Suggest search file system for "*WinUSB*,inf" and rename any located files to .inf_temp (this will prevent them being recognised and allows them to be easily reinstated should you need to).

Another alternative is that you remove the .inf file using a tool like PnpUtil (I've never used it)

Note: Might be a good idea to disconnect from the web when you attempt to change the driver - that way you know it can't automatically download anything without you knowing about it.

Geoff

_________________
TopManager program
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; StopExit v1.01; EPG2MEI v0.96; QuickJump 1.72; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MHEG On/Off A3; MyInfo B5.6; WSSkiller V2.12d; CrashTrace v0.4; fsSave 1.1; PruneEPG 1.0;
Sig generated by MyInfo on 17/1/16
View user's profile Send private message Visit poster's website
YorkshireJumbo
Posted: Thu Jun 29, 2017 8:24 am Reply with quote
Frequent contributor Joined: 16 Sep 2005 Posts: 677
Stu's TV wrote:
So, in summary (as far as I can tell): as soon as I connect the Toppy, Windows assigns the WinUSB.SYS driver.
I thought you were supposed to run z4t before connecting the Toppy, as Windows always assigns the wrong driver...

_________________
YJ - You may have speed, but I have momentum
Black Panther since Sep '05, Caps replaced July '10, WD5000AVJB added April '12
F/W: MS6 Recommended F/W 12/9/2009 -Sy+U+Uu
TAPs: MS 6.6 Suite, UK OZ Surfer
View user's profile Send private message
Bizman
Posted: Thu Jun 29, 2017 2:10 pm Reply with quote
Frequent contributor Joined: 06 Apr 2010 Posts: 1700
@Stu's TV: Have you read the topic at http://forum.toppy.org.uk/forum/viewtopic.php?t=20995 for more information?

_________________
TF5810, F/W: 5.15.09T 4/9/2009 -FmTe+EzHsVb
TAPs: EIT Sub (Game) v0.6; SecCache (UK) v0.4; MHEG On/Off A3; MPDisplayLITE V1.2; MyInfo B5.6; PruneEPG 1.0; EPG2MEI v0.96; QuickJump 1.72; Extend v1.7; (fsSave 1.1);
Sig generated by MyInfo on 3/8/17

Other TAPs : FsCheck, Channel Organiser. PSU Caps 7/2/2011 Tx: Mendip. TV: Samsung (32"), NSLU2, STB: Labgear FV300. PC Acer Aspire One with Win7 Starter
View user's profile Send private message
Stu's TV
Posted: Thu Jun 29, 2017 3:41 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Hi Guys

Bizman yes, seen that thread, it was the one I started last time I had connection problems.

YorkshireJumbo yes, I thought I had done this. However, after reading your post I thought I'd give it another go. So, I:
1. Uninstalled the WinUSB.SYS driver (again!) and disconnected the USB lead.
2. started z4t ('Topfield devices currently connected' was blank).
3. I also opened Device Manager and selected View ->Devices by connection (I haven't spotted this option before!)
4. connected the toppy USB cable, the toppy appeared in Zadig for Topfield, I could also see it in Device Manager so I looked at the Properties and no driver had been assigned. Wooppeeee, I thought, no WinUSB.SYS!
5. Tried Install Driver in Zadig (z4t) - Driver installation Failed.
6. Tried to manually install the drivers, as suggested in one of TopTapper's previous posts. 'Windows encountered a problem installing the driver software for your device - Windows found driver software for your device but encountered an error while attempting to install it.

I'll paste the Debug log from z4t, but the line that leaps out to me is:
libwdi:debug [installer process] the driver is not compatible with this version of Windows

Here's the full log:
Using inf name: Topfield_(libusb-winusb).inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created C:\usb_driver\Topfield_(libusb-winusb).inf
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:debug [installer process] got parameter Topfield_(libusb-winusb).inf
libwdi:debug [process_message] got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_11DB&PID_1000\1000'
libwdi:debug [process_message] got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_11DB&PID_1000&REV_0101'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-2659952142-704720065-1091483357-1001'
libwdi:debug [installer process] using syslog 'C:\WINDOWS\inf\setupapi.dev.log'
libwdi:debug [installer process] sylog reader thread started
libwdi:debug [process_message] switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_11DB&PID_1000&REV_0101 - please wait...
libwdi:debug [syslog] ll (UpdateDriverForPlugAndPlayDevices) - USB\VID_11DB&PID_1000&REV_0101]
libwdi:debug [syslog] >>> Section start 2017/06/29 15:26:58.914
libwdi:debug [syslog] cmd: C:\usb_driver\installer_x64.exe Topfield_(libusb-winusb).inf
libwdi:debug [syslog] ndv: INF path: C:\usb_driver\Topfield_(libusb-winusb).inf
libwdi:debug [syslog] ndv: Install flags: 0x00000001
libwdi:debug [syslog] ndv: {Update Device Driver - USB\VID_11DB&PID_1000\1000}
libwdi:debug [syslog] ndv: Search options: 0x00000080
libwdi:debug [syslog] ndv: Searching single INF 'C:\usb_driver\Topfield_(libusb-winusb).inf'
libwdi:debug [syslog] dvi: {Build Driver List} 15:26:59.014
libwdi:debug [syslog] dvi: Searching for hardware ID(s):
libwdi:debug [syslog] dvi: usb\vid_11db&pid_1000&rev_0101
libwdi:debug [syslog] dvi: usb\vid_11db&pid_1000
libwdi:debug [syslog] dvi: Searching for compatible ID(s):
libwdi:debug [syslog] dvi: usb\class_ff&subclass_00&prot_00
libwdi:debug [syslog] dvi: usb\class_ff&subclass_00
libwdi:debug [syslog] dvi: usb\class_ff
libwdi:debug [syslog] dvi: Created Driver Node:
libwdi:debug [syslog] dvi: HardwareID - USB\VID_11DB&PID_1000
libwdi:debug [syslog] dvi: InfName - c:\usb_driver\topfield_(libusb-winusb).inf
libwdi:debug [syslog] dvi: DevDesc - Topfield (libusb-winusb)
libwdi:debug [syslog] dvi: Section - USB_Install
libwdi:debug [syslog] dvi: Rank - 0x80ff0001
libwdi:debug [syslog] dvi: Signer Score - Not digitally signed
libwdi:debug [syslog] dvi: DrvDate - 02/06/2011
libwdi:debug [syslog] dvi: Version - 6.1.7600.16385
libwdi:debug [syslog] dvi: {Build Driver List - exit(0x00000000)} 15:26:59.516
libwdi:debug [syslog] dvi: {DIF_SELECTBESTCOMPATDRV} 15:26:59.518
libwdi:debug [syslog] dvi: Default installer: Enter 15:26:59.520
libwdi:debug [syslog] dvi: {Select Best Driver}
libwdi:debug [syslog] dvi: Class GUID of device changed to: {78a1c341-4539-11d3-b88d-00c04fad5171}.
libwdi:debug [syslog] dvi: Selected:
libwdi:debug [syslog] dvi: Description - [Topfield (libusb-winusb)]
libwdi:debug [syslog] dvi: InfFile - [c:\usb_driver\topfield_(libusb-winusb).inf]
libwdi:debug [syslog] dvi: Section - [USB_Install]
libwdi:debug [syslog] dvi: {Select Best Driver - exit(0x00000000)}
libwdi:debug [syslog] dvi: Default installer: Exit
libwdi:debug [syslog] dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 15:26:59.623
libwdi:debug [syslog] ndv: Forcing driver install:
libwdi:debug [syslog] ndv: Inf Name - topfield_(libusb-winusb).inf
libwdi:debug [syslog] ndv: Driver Date - 02/06/2011
libwdi:debug [syslog] ndv: Driver Version - 6.1.7600.16385
libwdi:debug [syslog] sto: {Setup Import Driver Package: c:\usb_driver\topfield_(libusb-winusb).inf} 15:26:59.714
libwdi:debug [syslog] sto: Driver package already imported as 'oem2.inf'.
libwdi:debug [syslog] sto: {Setup Import Driver Package - exit (0x00000000)} 15:26:59.765
libwdi:debug [syslog] dvi: Searching for hardware ID(s):
libwdi:debug [syslog] dvi: usb\vid_11db&pid_1000&rev_0101
libwdi:debug [syslog] dvi: usb\vid_11db&pid_1000
libwdi:debug [syslog] dvi: Searching for compatible ID(s):
libwdi:debug [syslog] dvi: usb\class_ff&subclass_00&prot_00
libwdi:debug [syslog] dvi: usb\class_ff&subclass_00
libwdi:debug [syslog] dvi: usb\class_ff
libwdi:debug [syslog] ndv: {Update Device Driver - exit(e0000203)}
libwdi:debug [syslog] !!! ndv: Failed to install device instance 'USB\VID_11DB&PID_1000\1000'. Error = 0xe0000203
libwdi:debug [syslog] <<< Section end 2017/06/29 15:26:59.964
libwdi:debug [syslog] <<< [Exit status: FAILURE(0xe0000203)]
libwdi:debug [process_message] switching timeout back to finite
libwdi:debug [installer process] the driver is not compatible with this version of Windows
libwdi:debug [process_message] installer process completed
Driver Installation: FAILED (Operation not supported or not implemented)
1 device found.
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_11DB&PID_1000&REV_0101
libwdi:debug [wdi_create_list] Driverless USB device (0): USB\VID_11DB&PID_1000\1000
libwdi:debug [wdi_create_list] could not read device description for 0: [13] The data is invalid.
libwdi:debug [wdi_create_list] Device description: 'Topfield (libusb-winusb)'
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_8087&PID_07DA&REV_7869
libwdi:debug [wdi_create_list] BTHUSB USB device (1): USB\VID_8087&PID_07DA\6&8386542&0&3
libwdi:debug [wdi_create_list] got hardware ID: USB\ROOT_HUB30&VID8086&PID1E31&REV0004
libwdi:debug [wdi_create_list] USBHUB3 USB device (7): USB\ROOT_HUB30\4&1B6EEE9&0&0
libwdi:debug [wdi_create_list] got hardware ID: USB\VID_174F&PID_148D&REV_0827&MI_00
libwdi:debug [wdi_create_list] rtsuvc USB device (Cool: USB\VID_174F&PID_148D&MI_00\7&267E667C&0&0000


Last edited by Stu's TV on Thu Jun 29, 2017 5:33 pm; edited 1 time in total

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Stu's TV
Posted: Thu Jun 29, 2017 5:21 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Geoff Bacon wrote:
Your initial post implies that the toppy used to work about a year ago.

Is there any chance you can rollback the driver to that time? (possibly harder because you have tried to load it several times recently).

Another post implies that you can delete the .inf for the driver and this will cause windows to prompt before installing a driver i.e. you could then run z4t when it prompts to load a driver. Suggest search file system for "*WinUSB*,inf" and rename any located files to .inf_temp (this will prevent them being recognised and allows them to be easily reinstated should you need to).

Another alternative is that you remove the .inf file using a tool like PnpUtil (I've never used it)

Note: Might be a good idea to disconnect from the web when you attempt to change the driver - that way you know it can't automatically download anything without you knowing about it.

Geoff


Hi Geoff, yes last time I had to connect to my PC was a little over a year ago (first time with Windows 10) and I did get it to connect, after some arm-wrestling.. http://forum.toppy.org.uk/forum/viewtopic.php?t=20995

Not sure how to rollback the driver.

I think what I have just done navigates round to need to change the .inf file as I now have the toppy connected without a driver installed?

I'm thinking that a Windows update has clashed with the toppy driver, rendering it incompatible with my now updated version of Windows.......

I really want to get MyStuff loaded back onto the toppy, it's really horrible having to use it with the old 'standard' user interface........

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message
Geoff Bacon
Posted: Thu Jun 29, 2017 5:52 pm Reply with quote
Frequent contributor Joined: 12 Jan 2007 Posts: 3941
A simple google for "windows 10 rollback driver"produces
Quote:
To roll back to a previous version of a driver
Open Device Manager.
Right-click the device for which you want to roll back to the previous version of the driver, and then click Properties.
Click the Drivers tab.
Click Roll Back Driver.
In the Driver Package rollback dialog box, click Yes.


I didn't realize that you had "lost" MyStuff on the toppy disk - did it get corrupted or is it a new disk? If corrupted then I could get the files back for you. I could also install MyStuff at the same time.

Can you borrow a different Windows pc to load the toppy disk?

Theoretically, you could take the disk out of the toppy, connect it to the pc and manually copy the MyStuff files to the required location (not easy but possible).

Geoff

_________________
TopManager program
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; StopExit v1.01; EPG2MEI v0.96; QuickJump 1.72; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MHEG On/Off A3; MyInfo B5.6; WSSkiller V2.12d; CrashTrace v0.4; fsSave 1.1; PruneEPG 1.0;
Sig generated by MyInfo on 17/1/16
View user's profile Send private message Visit poster's website
ccs
Posted: Thu Jun 29, 2017 6:51 pm Reply with quote
Frequent contributor Joined: 30 Oct 2007 Posts: 2379
As you've mentioned .inf files, I'd noticed this a while back......

Quote:
Somehow C:\Windows\Inf\usb.inf and C:\Windows\Inf\usb.PNF were GONE on both machines having the issue. I have no idea how, perhaps a failed Windows update, but copying those files from a machine that was working fixed the issue.

_________________
TF5810, F/W: MS6 Recommended F/W 12/9/2009 -FmXl+CtEzIScVdZ
TAPs: EIT Sub v0.6; EPG2MEI v0.96; MPDisplayLITE V1.2; MyInfo B5.6; SecCache (UK) v0.4; Extend v1.7; MyStuff 6.6;
Sig generated by MyInfo on 20/10/14
ccsx
View user's profile Send private message
Stu's TV
Posted: Thu Jun 29, 2017 6:58 pm Reply with quote
Regular contributor Joined: 18 Apr 2012 Posts: 34
Roll back driver is greyed-out! I think borrowing another PC is probably my best option, I'll have to look into how I can get hold of one......

Many thanks for the offer of file retrieval. I actually managed to re-format the toppy's hard drive, not 100% sure how I managed that! It was very late night after the pub, so I think we can safely put it down to pilot error Embarassed

It would be nice to able to connect to the toppy with my window 10 PC, but I'm thinking that the toppy driver needs to be modified for that to happen, which is way, way beyond my capabilities........

_________________
TF5800, TS On, F/W: MS6 Recommended F/W 12/9/2009 -Sy
TAPs: PcControl B1.4; EPG2MEI v0.96; MyStuff 6.6; Font Manager 1.0d; Extend v1.7; SecCache (UK) v0.4; EIT Sub (Game) v0.6; MyInfo B5.6; MHEG On/Off A3; PruneEPG 1.0;
Sig generated by MyInfo on 9/3/16
View user's profile Send private message

Display posts from previous:  

All times are GMT + 1 Hour
Page 2 of 4
Goto page Previous  1, 2, 3, 4  Next

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum