NOAHlink and the Microsoft Spring Update 1803 for Windows 10

The Microsoft Spring Update 1803 for Windows 10 was released on April 30, 2018. This Microsoft update breaks the Bluetooth communication between the computer and NOAHlink. After applying this Windows update, NOAHlink users report that they are unable to discover the NOAHlink in NOAHlink Properties.

IMPORTANT: HIMSA’s advice in the short term is to delay or defer the Windows Spring update for now if you still have the option. This article provides options based on your version of Windows 10.

If the update has already been installed and the NOAHlink is required, the only way to fix the problem is to either move the NOAHlink to an unaffected PC, or to roll back the Windows update within 10 days. You will find the option to rollback at Settings, Update and Security, Recovery. Select ‘Go back to the previous version of Windows 10’.

*The ability to roll back the update is only available for 10 days. After that, the C:\Windows.old folder that is the preupgrade copy is deleted by Windows.

**The Microsoft Spring update does not cause a problem for Noahlink Wireless. As with most Microsoft updates, you may need to reset the Noahlink Wireless by unplugging and replugging the USB cable, but beyond that it will function as expected.


Update, May 11: Our investigations indicate that this is an issue with the Microsoft update. HIMSA has therefore opened a support issue with Microsoft and are awaiting their response. 

Update, May 14:  HIMSA continues to work with Microsoft for a resolution to the 1803 update issue for Bluetooth. In the meantime, be aware that Microsoft has options to prevent Windows 10 from installing the April 2018 Update, version 1803. For Windows 10 Pro or Enterprise, you can defer or pause the 1803 update for a time. The option is located at Settings, Update and Security, Windows Update, Advanced options.

For Windows 10 Home, you can change the properties of the Wi-Fi connection to limit updates from downloading.

Details and options can be researched in this article:


Update, May 25:  HIMSA has made good progress with Microsoft.  Technical experts at HIMSA and Microsoft have been able to precisely determine the root cause of the issue.  HIMSA is now waiting for insiders build of Windows to verify that a solution is functioning as desired.  HIMSA has not been promised a date at this point but we will keep this high priority issue in focus and will continue to update this page with new information when it becomes available.

For the meantime the steps to avoid the issue listed above are still the best available.


Update, June 8:  Unfortunately, we do not have the update that we have been working hard towards.  HIMSA is very aware that this issue is a big problem for NOAHlink users.  We have continued to press Microsoft to commit to releasing a fix as this is by far the best option for a timely resolution.

If you have a few spare minutes please help us by voting this issue directly to Microsoft.  We have provided some simple directions to follow.

Q: Why has HIMSA not provided a direct fix to this issue?

A: HIMSA has initiated a development project and expects to start a testing process with hearing instrument manufacturers in the near future.  Unfortunately, the workaround requires a change to the Noahlink firmware.  As Noahlink is an electrical medical device it is required to go through rigorous quality and approval processes before it may be used with a patient.  At this time, we are aware that this approval and testing process will take 2-3 months.

HIMSA will continue to apply pressure on Microsoft to address the issue as a resolution in Windows will not require extensive testing.  In the meantime, your best course of action is to follow the previously provided advice above.