Problem at boot involving usrbridg.exe

GabbleRatcht · 22-09-2005, 14:37

A mate of mine a while back had a problem occur after trying to install a USB Bluetooth dongle.

During boot he would get 'usrbridg.exe experienced a problem and has been shut down'. It stopped his modem working amongst other things.

I tried to install a program that requires a USB hardware key the other day and now get the same thing at each boot up.

The dongle didn't work but everyone else in the traing group I was in who installed the software had no problems. We were all on XP, some home, some Pro. I tried several dongles.

I have discovered that this is a service related to the IR port. I've found a solution to it for Win2000, but not for XP.

Can anyone help?

Stopped it happening by disabling the service but this is just a bodge.

And why wouldn't the dongle work on my system? XP saw it as new hardware and identified it correctly. It just couldn't install it.

GabbleRatcht · 05-04-2006, 15:35

Just thought I'd bump this up as I got no replies and it's really annoying me and I want to use the IR port.

Maybe someone has joined in the six months since I posted it that can help

Ta again

GR

steev · 05-04-2006, 16:19

I think more people may've had this problem in the last 6 months or so. Not sure how relevant this will be (or if it's the Win 2000 fix you mentioned), but computing.net has a fix (for 2000) which sounds like it should be what you're looking for. The add hardware bit is slightly differently worded in XP, but hopefully you should be able to find your way round it, & if not someone here may be of more help.

computing.net fix

Good luck

GabbleRatcht · 05-04-2006, 22:47

Thanx Steev

that was the link I was looking at.

Tried what it says but it doesn't work.

It refers to the USRBRIDG.exe being related to an IR device made by 'Extended Systems' but my IR device is by SMC.

I tried loading the drivers for the extended device, but just came up as 'not working' in device manager.

So, if this piece of software is, maybe, not applicable to my hardware, why is it installed?

And how do I stop it loading at startup? Not just disabaling the service.

Tried sysedit but it says it's 16 bit and can't run on XP.

SO WHY IS IT STILL THERE ON THE DISK HOGGING SPACE! As little as it is.

Sorry for shouting, but Windows is now just patch, on patch, on patch.

Surely with Bills money, they could just write a NEW OS from the base upwards.

Suppose I could try sysedit in DOS, but like most of us, not that competant!