Skip to content
HearingTracker
Log in

Noah wireless not connecting at all

16 replies422 viewsLast reply

Link to this topic
Reply
Edited

I have been using my Noah wireless for several years. All of a sudden today I could not connect to Noah wireless. Any help would be appreciated. Plugged unplugged. Restarted computer. Green lights come on then go off. I cannot update software because it is not recognized. Hope I don’t have to buy a new one.

image

4 people in this conversation3 min readJump to latest

Yeah how strange, nothing else has changed on your PC? Well I’d first try another USB port and then next change the cable, next try the old restart (not a reboot but a complete shut down) then start PC, open target software and then plug the Noahlink wireless in.

You don’t need the Noahlink wireless working to update the software.

In reply to @tenkan

Just got a new usb - usb-c connecting port. Restarted and made sure computer was updated. Opened phonak. Went to connect hearing aid. Noahlink blinked on green for about 3 seconds and then again, “Connection lost” . I have been using this computer and this Noahlink for maybe 2 years. It does say if problem persists, reinstall the driver, not sure how that is done.

In reply to @tenkan

image

I have Windows 11. Like I said I have been using this set up for a couple of years. I clicked the link and I get this. Again Noahlink flashes green, but i seems it is not recognized. It won’t let me type in the box. I closed and tried several times. I clicked on search several times. I unplugged and plugged back in several times. So frustrating. Any other ideas? Do they just go bad and I am going to have to look into buying another one?

What’s that screenshot, that’s the Noahlink upgrader? Why are you there (you don’t get to type anything in there anyway, it’s automatically populated)

@Lydia_M said:

It does say if problem persists, reinstall the driver, not sure how that is done.

That’s what the link is for that I sent you.

So getting the Noahlink to flash that one time is normal which says it’s getting power, go to device manager and plug Noahlink in and see if it shows up there, but no Noahlink wireless is a very reliable and robust device/design, this is more likely something else.

Is it possible to use another PC, install Target and check if Noahlink wireless works there?

So I downloaded the link you sent. After clicking “yes” to do you want to allow this app to make changes to your computer. The screenshot is what appears. Inside the box is blank so I guess it is not being recognized all of a sudden.

Just tried on an older computer. Same thing “NO connection to “Noahlink Wireless” . Guess I am going to be looking for a deal for a new noahlink :frowning:

Wow yeah that’s so strange, just stopped working like that! I suppose both PC are win11, but this is why you “sometimes”, have to reinstall the driver’s for win11. The only others that have had issues similar to yours is when they have tried to do the firmware update to Noahlink wireless and something went wrong.

What does device manager say when you plug Noahlink in?

Click on the driver and see what that reports.

You probably have tried already but did you change the cable.

Thanks for help, I’ve used the 3 different usb ports on computer. Didn’t buy a new cable cause the lights come on why I switch ports and my computer dings when I plug it into port. I sent a pic of what device manager says. I’ve also uninstalled and reinstalled several times.

  1. Replace the USB cable. If you have a printer, you can use the USB cable that comes with it.
  2. Disable the Memory Integrity feature in Windows 11. Following the latest monthly update, this feature appears to disable certain drivers.

Thank you tried but that didn’t work.

When I unplug Noah and then plug it back in the green lights blink on and off then I get a warning that says the device malfunctioned and it doesn’t recognize it

Yeah not a good sign, what else can you do.. replacement is on the way! I think only one other person on the forum had a failed one, this from a firmware update gone wrong.

Related discussions