Cumulative Update KB4517389 Windows 10 v1903 build 18362.418 - Oct. 8 Win Update

did this mess with anyone's bluetooth settings/capabilities? I was just going to finish dark cloud game's final boss, and after I applied this update, my bluetooth vanished

maybe if I reinstall the bluetooth software

- - - Updated - - -

yeah, nope, whatever microsoft did, it completely bungled the HFIL out of bluetooth. No dism scan/sfc scan/chkdsk scan n' fix worked, a refresh install with a fresh 1903 windows 10 iso from the MediaCreationTool didnt work, nor reinstalling the bluetooth software from intel didnt work. More deets in here

microsoft, c'mon man, im trying to play my games with my ps4 controller, can you just not screw anything up for one single update, please?

My BT is fine.

was this BT issue recognized by MS?

BrokenDaily said:

can you just not screw anything up for one single update, please?

I would like to ask the same thing from MS. After updating my production machine for the umpteenth time to 1903, I found out that:
-Remote desktop is not working anymore
-Control Panel when I try to open it, it just quickly opens and closes
-Microsoft Edge in only my Admin Account won't launch at all —No workarounds found on the web seems to be able to fix this freaking issue. Only God knows how many of them I have tried.

The only way my production machine can work to its full potential is on 1809 before KB4516077. Probably, the only way to stop having so much downtime is to stay on 1809 until the end of support and prevent any CUs or FUs from installing except for Windows (Microsoft)Defender updates. The funny thing is that everything seems to be working fine on my other older second machine with 1903. I would like to understand what gives. (Smoke coming out of my ears, to put it mildly!!!)

- - - Updated - - -

IronZorg89 said:

I would like to ask the same thing from MS. After updating my production machine for the umpteenth time to 1903, I found out that:
-Remote desktop is not working anymore
-Control Panel when I try to open it, it just quickly opens and closes
-Microsoft Edge in only my Admin Account won't launch at all —No workarounds found on the web seems to be able to fix this freaking issue. Only God knows how many of them I have tried.

The only way my production machine can work to its full potential is on 1809 before KB4516077. Probably, the only way to stop having so much downtime is to stay on 1809 until the end of support and prevent any CUs or FUs from installing except for Windows (Microsoft)Defender updates. The funny thing is that everything seems to be working fine on my other older second machine with 1903. I would like to understand what gives. (Smoke coming out of my ears, to put it mildly!!!)

I found the solution for Control Panel not working thanks to this thread in tenforums:
Control panel closes automatically after windows 10 1511 update

In Device Manager, under Sound, Video and Game Controllers, I updated "High definition Audio device" (there were two of them-I don't know why-see callout number 1 ) using a Drivers Backup made on Sept 29, 2019 (See red square in screenshot and call out number 2 below). After that, IDT High Definition Audio codec showed up (callout number 3). That was the one probably missing and stymied my CP from working normally. Now everything is OK.



With regard to Microsoft Edge, I gave up about trying to fix it and defaulted my browser to Microsoft Edge Beta which, in the foreseeable future, is going to be new stable browser for MS anyhow. From that experience, I can conclude that MS doesn't respect the settings in GP editor (where I had blocked the installation of new drivers) whenever a FU is released.

For the RDP issue, I know how to take care of that. I have also paused Windows Updates in Update & Security settings.

alright, so even though the chkdsk scan found nothing wrong, I set it to do a /r /f operation yesterday, booted my computer up, ran it until it finished at the time of this post, and to my joy, it fixed it, sorta

I checked device manager and saw I had an unknown device, so checking its hardware IDs show that it matches the IDs of my bluetooth hardware, so I reinstalled the software/drivers, and all is fixed; removing the"Unknown USB Device (Device Descriptor Request Failed)" entry has finally worked and said entry no longer shows