Closed GoogleCodeExporter closed 9 years ago
For the current build of busdog to work on an x64 build of windows you need to
enable test signing (http://msdn.microsoft.com/en-us/library/dd419910.aspx).
Other then that to uninstall busdog you should be able to do one of the
following:
- run the busdog gui and select "uninstall" from the setup tab
- uninstall the busdog driver from the "add/remove programs" applet in the control panel
- use system restore
Original comment by djpnew...@gmail.com
on 11 Nov 2010 at 3:56
Rebooting in Safe Mode doesn't help. With all USB broken, the only option is to
reboot, F8, and select 'Last known good configuration' (USB should work upon
reboot). This just happened to me a few minutes ago.
Original comment by jim.fre...@gmail.com
on 12 Nov 2010 at 10:02
>Rebooting in Safe Mode doesn't help. With all USB broken, the only option is
to reboot, F8, and select 'Last known good configuration' (USB should work upon
reboot). This just happened to me a few minutes ago.
Is this on x64 and did you enable test-signing?
Original comment by djpnew...@gmail.com
on 13 Nov 2010 at 5:34
Same problem here.
v0.2.1, Windows 7 64 bits
Test signing enabled.
Used system restore and 'scan for hardware changes' to get mouse and other USB
devices working again. Bluetooth still broken.
Original comment by Robert.S...@gmail.com
on 12 Oct 2011 at 3:30
Same problem.
Uninstall from GUI worked.
Beware this program!!
Original comment by roger.mc...@gmail.com
on 19 Jan 2012 at 5:04
Ok, I restored the system now everything is working fine again, but... how can
I make busdog work?
Original comment by pmferre...@gmail.com
on 18 Oct 2012 at 4:31
>Ok, I restored the system now everything is working fine again, but... how can
I make busdog work?
Is your system 64 bit? If so the driver needs to be signed. If someone donates
the money (for a thwate cert) I will sign the releases with certificates so
they work on 64 bit windows
Original comment by djpnew...@gmail.com
on 30 Oct 2012 at 4:19
> Rebooting in Safe Mode doesn't help. With all USB broken, the only option is
to reboot, F8, and select 'Last known good configuration' (USB should work upon
reboot). This just happened to me a few minutes ago.
Coworker encountered same problem, even Safe Mode didn't help. Thanks to your
advice, we were able to recover.
Configuration :
v0.2.1 @ Win7 64bit
It happened right after installation, so it doesn't matter, if test-signing was
enabled.
Original comment by fli...@gmail.com
on 5 Apr 2013 at 10:03
Guy's put a dam warning on this thing i just wasted 35 mins getting my pc going
again -_- easy fix but comon now atleast tell people this could possibly happen
if your on windows 7 -_-
...
Original comment by spanjer1...@hotmail.com
on 6 Aug 2013 at 12:21
My whole USB sub-system is also broken, even after reboot. Any solution for a
PC without PS/2 adapters? Without mouse and keyboard it is impossible to
recover the system... :-(
Original comment by laura.sa...@gmail.com
on 2 Mar 2014 at 6:41
reboot, F8, and select 'Last known good configuration'
Original comment by djpnew...@gmail.com
on 2 Mar 2014 at 7:41
I can reboot, but without keyboard I am not able to press F8...
Original comment by laura.sa...@gmail.com
on 2 Mar 2014 at 8:52
You press F8 before Windows has booted, see:
http://windows.microsoft.com/en-us/windows/using-last-known-good-configuration#1
TC=windows-7
Original comment by djpnew...@gmail.com
on 2 Mar 2014 at 8:56
Thanks! After changing my wireless keyboard with a wired one, I was able to
press F8 and recover the System (Windows 8).
Original comment by laura.sa...@gmail.com
on 2 Mar 2014 at 9:33
I found some hints on fixing the registry if busdog corrupts the drivers
settings such that non of the USB devices work again (ie Device Controller
error code 39).
http://www.tricksguide.com/solve-device-manager-error-code-39-on-usb-controller.
html
Original comment by mark.lak...@gmail.com
on 31 Mar 2014 at 3:07
signed installer for 64 bit windows now available
my whole usb stopped working. I recover some devices by removing value "busdog" from key "LowerFilters" on registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{36fc9e60-c465-11cf-8056-444553540000}
Original issue reported on code.google.com by
pmena...@gmail.com
on 10 Nov 2010 at 10:45