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; therefore, you may be unable to pair or discover the NOAHlink in NOAHlink Properties.

If you have the option, decline the Windows Spring update for now.

If the update has already been installed, and the Noahlink is required, the only fix at present is to roll back the Windows update. 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 appears to be available for 10 days. After that, the C:\Windows.old folder that is the preupgrade copy is deleted by Windows.

HIMSA is investigating this problem and an update or solution for NOAHlink will be delivered as soon as possible.

**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.