Microsoft Fixes Annoying Bluetooth Issue in Windows 10 Version 1809

Microsoft shipped a major Windows 10 update earlier this month after the company’s first attempt didn’t go too well. The update fixed a critical file deletion issue that was shipped with the original version of the update, known as the October 2018 Update, even though Windows Insiders reported the problem when it was in testing.

And that’s not the only bug that slipped through Microsoft’s testing to the public. Windows 10 version 1809, right now, has a bug where Bluetooth playback randomly stops every few minutes. You could be listening to music on your wireless headphones or watching a Netflix show, and all of a sudden you will stop hearing anything even though Windows will tell you the device is connected via Bluetooth.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

The bug first appeared months ago when Microsoft was still somewhat in the early days of the development of Windows 10 October 2018 Update, codenamed Redstone 5. I spotted it back in July of this year, reported it on Twitter and even notified a Windows Insider team member via direct message, and yes, you guessed it: the bug still somehow made it to the public version of 1809, even the re-release.

Microsoft has now fixed the issue in Windows 10, with the fix currently being in testing for Insiders in the Release Preview ring. Better late than never, but it just goes to show how broken the bug reporting system really is on the Insider program. Granted, the bug wasn’t affecting every user and I truly have no idea how many users are affected by it, but I received complaints from some users about the same issue on their device running Windows 10 version 1809.

And yes, the update brings a bunch of other fixes for similar, annoying issues, so here’s the full changelog:

  • Addresses an issue in Microsoft Edge with using the drag-and-drop feature to upload folders from the Windows desktop to a file hosting service website, such as Microsoft OneDrive. In some scenarios, files contained in the folders fail to upload, with possibly no error reported on the web page to the user.
  • Addresses an issue that degrades Internet Explorer performance when you use roaming profiles or you don’t use the Microsoft Compatibility List.
  • Addresses updated time zone information for Fiji.
  • Addresses time zone changes for Moroccan daylight standard time.
  • Addresses time zone changes for Russian daylight standard time.
  • Addresses an issue that causes display settings to stop working when changing a multi-monitor configuration.
  • Addresses an issue that displays a black screen on some servers when waking a display from sleep.
  • Addresses an issue with long delays in taking a photo when using the Camera app in certain lighting conditions.
  • Addresses an issue that prevents live Hulu TV content from playing in Microsoft Edge; instead, a black screen appears.
  • Addresses an issue that stops Bluetooth® headsets from receiving audio input after several minutes of listening.
  • Addresses an issue that causes the Brightness slider preference to be reset to 50% when the device restarts.
  • Addresses an issue with the OEM manufacturing processes when running sysprep /generalize.
  • Addresses an issue with Microsoft Intune that causes devices to be incorrectly marked as not compliant because a firewall incorrectly returns a ‘Poor’ status. As a result, the affected devices will not receive conditional access compliance approval and may be blocked from access to corporate resources such as email.
  • Addresses a performance issue with vSwitch on network interface cards (NIC) that do not support Large Send Offload (LSO) and Checksum Offload (CSO).
  • Updates the Wi-Fi policy for service set identifier (SSID) filtering to avoid filtering out Wi-Fi Direct devices.
  • Addresses an issue that causes rasman.exe to stop responding.
  • Addresses an issue in which regedit.exe fails to add double null terminator to REG_MULTI_SZ values in the Windows registry. The missing terminator may prevent services and applications from reading REG_MULTI_SZ values that regedit.exe adds after installing the operating system.
  • Addresses an issue with RemoteApp visibility that may cause the main window to disappear until the user clicks the screen.
  • Addresses an issue that prevents some users from setting Win32 program defaults for certain app and file type combinations using the Open with… command or Settings > Apps > Default apps.
  • Addresses an issue that may cause mapped drives to fail to reconnect after starting and logging onto a Windows device.

The update for version 1809 will likely make its way to all users in the coming weeks, maybe as the Patch Tuesday next month. And if you are already quite tired of the Bluetooth bug like I was, you should probably just enrol into the Release Preview ring of the Insider program and grab the latest updates right away.

Thanks for the tip, Eplak, and Stanzilla. 

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 23 comments

  • wolters

    Premium Member
    28 November, 2018 - 2:36 pm

    <p>I think I've encountered this bug. I have a Bluetooth Surface Precision Mouse, Bluetooth Surface Keyboard and Invoke Bluetooth Speaker on my work PC. Ever so often, all 3 will freeze but I'll lose the keyboard. Rebooting is the easiest fix but initially, I would try to re-pair the keyboard and it would cause worse problems and the PC wouldn't even shut down properly…would have to fat finger. I even made sure I had the most recent Bluetooth drivers. Happens about once a day. </p><p><img src=""></p><p>I really hope this will be part of the fix…I love this current setup. </p><p><br></p><p><img src="https://i.imgur.com/5Iq9l73.jpg"></p&gt;

    • oaklines

      Premium Member
      28 November, 2018 - 5:07 pm

      <blockquote><em><a href="#374223">In reply to wolters:</a></em></blockquote><p>Yes – I've had the same issue – periodically loose the response of surface bt keyboard – or the surface dial. I use them with a desktop that does not have native bluetooth – but bluetooth was added with a usb dongle. What worked for me – unplug/re-plug the dongle.</p><p><br></p><p>If you have native Bluetooth – maybe try using device manager to disable – enable the Bluetooth adapter. If it works for you – it might save a little time over a reboot.</p><p><br></p><p>But – hopefully the issue is fixed now! ;-]</p>

      • wolters

        Premium Member
        28 November, 2018 - 6:16 pm

        <blockquote><em><a href="#374357">In reply to OakLines:</a></em></blockquote><p>Thank you…I will try this out…I love this setup and don't want to change…if this doesn't fix it, then fingers crossed this will be fixed on the next patch Tuesday… 🙂 </p>

    • robsanders247

      Premium Member
      29 November, 2018 - 2:56 am

      <blockquote><em><a href="#374223">In reply to wolters:</a></em></blockquote><p>I have something similar. Using the modern keyboard with fingerprint ID and the Precision Mouse, every 30 minutes to an hour the mouse will get very laggy. Fortunately turning the mouse off and back on resolves the issue, but still very annoying.</p><p><br></p><p>Almost as annoying as not being able to manage a $150 keyboard in the Keyboard and Mouse Center…</p>

      • wolters

        Premium Member
        29 November, 2018 - 9:31 am

        <blockquote><em><a href="#374590">In reply to robsanders247:</a></em></blockquote><p>Yes, I have the mouse issue too and power cycling works. </p><p><br></p><p>The whole keyboard not responding has been the worst since it requires a reboot. I didn't notice this happening until I paired my Invoke as a Bluetooth speaker and now it happens almost daily. I'd be willing to go back to wired speakers to prevent the daily reboots. I hope this fix will resolve this problem. </p>

  • feek

    Premium Member
    28 November, 2018 - 2:53 pm

    <p>where did you find this changelog?</p>

  • jgraebner

    Premium Member
    28 November, 2018 - 3:57 pm

    <p>I wonder if it is an issue with specific Bluetooth radios. I use Bluetooth headphones a lot and have not had any issues with them at all with my Surface devices (SB2, SP4, and Surface Go), all of which have been on 1809 for a while.</p>

  • jimchamplin

    Premium Member
    28 November, 2018 - 3:58 pm

    <p>One I’ve seen is UAC elevation prompts ignoring the admin user’s PIN and requiring the full password. Randomly. This issue exists only on one machine, and it has survived two clean reinstalls.</p><p><br></p><p>Craphell. What are they doing!?</p>

  • NT6.1

    28 November, 2018 - 4:20 pm

    <p>I feel like this is the end of Windows. Time to start over. Windows 10 isn't working. Give Windows 7 more 3 years of support while you develop the next version of Windows.</p>

    • warren

      28 November, 2018 - 6:17 pm

      <blockquote><em><a href="#374306">In reply to NT6.1:</a></em></blockquote><p><br></p><p>You've forgotten that Windows 7 RTMand its early patches were riddled with bugs, too. Haven't you? …. or maybe you're too young to remember? Maybe you're being ignorant on purpose?</p><p><br></p><p>Whatever your excuse, it doesn't change the fact that "KB977074" and "KB977165" both definitely happened (Google them)…. or that Dell's popular V105, V305 and V505 printers stopped working if you upgraded from XP or Vista…. or that the "calculator" button on keyboards like Microsoft's own Ergonomic Natural 4000 didn't work for the first couple of months. Or KB977544, in which a specifically-crafted SMB message over the network would crash Windows 7. Nice. Those were the days, eh?</p><p><br></p><p>I could go on and on like this… problems with new releases of Windows have been a "feature" of Windows for 25 years.</p>

      • NT6.1

        28 November, 2018 - 6:23 pm

        <blockquote><em><a href="#374379">In reply to warren:</a></em></blockquote><p><br></p><p>So what used to happen every 3 years is happening twice a year…</p>

      • bluvg

        28 November, 2018 - 6:59 pm

        <blockquote><em><a href="#374379">In reply to warren:</a></em></blockquote><p>Let's not forget Windows 2000–which some deem as the best Windows release ever (I have a soft spot for it myself)–had "66,000 bugs" on release.</p>

  • glenn8878

    28 November, 2018 - 4:24 pm

    <p>I tried connecting my iPhone to my PC via Bluetooth. Nothing happens. I can't see my iPhone on my PC. Another bug is the PC breaks the wired (Lightning) connection to my iPhone so I can't import photos. Windows is a mess.</p>

  • Jacob Klein

    28 November, 2018 - 4:25 pm

    <p>The changelog is located here:</p><p>https : // blogs.windows. com/windowsexperience/2018/09/18/announcing-windows-10-insider-preview-build-17763</p>

  • warren

    28 November, 2018 - 6:20 pm

    <p>The Bluetooth bug might've made it to the 1809 release because it wasn't widespread enough to be easily reproducible. I've used multiple Bluetooth headsets &amp; headphones on two different Insider Preview releases of 1809 and never had the described problem. </p>

  • Pbike908

    28 November, 2018 - 7:01 pm

    <p>I think these fixes are awesome! The update hasn't been forced on me yet and by the time it is I imagine it will be a SOLID operating system!</p><p><br></p><p>I get a kick out of all the bashing, much of which is probably warranted.</p><p><br></p><p>However, one can't beat the value of a Windows laptop anymore especially compared to a Mac — many quality 256GB SSD and 8GB models for between $650 to $800!</p><p><br></p><p>Android, IOS, and Chrome OS fall short as far as personal computing devices go, so if one doesn't like Windows 10 put your $$$ where your mouth is and switch to Mac.</p>

    • Tony Barrett

      29 November, 2018 - 6:41 am

      <blockquote><em><a href="#374393">In reply to Pbike908:</a></em></blockquote><p>I guess you think all the bugs and quality control issues are awesome too then. Win10 is already a PoS farce. One day, when many finally realize they don't actually <em>need </em>Windows anymore, things will change. It's just familiarity that keeps people coming back – not loyalty.</p>

  • irfaanwahid

    29 November, 2018 - 1:05 am

    <p>Windows quality before Windows 10 – way better (Hint: No Insiders)</p><p>MacOS quality good quality (Hint: No program like Insiders)</p><p>Windows 10 – Worst Quality – (Hint: Millions of Insiders testing)</p><p><br></p><p>Why Microsoft cannot see this?</p><p><br></p><p>How is Apple releasing MacOS with not big bugs like Windows 10 and their OS isn't getting tested by millions of users?</p>

    • mrlinux11

      29 November, 2018 - 8:49 am

      <blockquote><em><a href="#374554">In reply to irfaanwahid:</a></em></blockquote><p>One of the advantage Apple has is they know exactly what hardware (and drivers) their products have so they have a smaller testing surface. Where as Microsoft has to support millions of different configurations that they have no control over. </p>

    • fbman

      29 November, 2018 - 11:55 pm

      <blockquote><em><a href="#374554">In reply to irfaanwahid:</a></em></blockquote><p>the biggest issue with the insider program, as 99% of them test in a virtual machine, so you never get the wide range of configurations tested.</p><p><br></p><p>That is understandable, as who in right mind would install a beta version on their main daily "production" machine. </p><p><br></p><p>I install my insider builds in a virtual machine. My main "production" pc only has public versions of windows 10. </p>

  • DaddyBrownJr

    29 November, 2018 - 6:14 am

    <p>The 23 users who got 1803 are overjoyed right now. </p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2024 Thurrott LLC