The problem is that it is difficult to move on to design flaws in the product with such an obvious bug causing problems.
Not sure I can see where you're coming from Dave Gayler, surely before adding further detail to the map content (and that includes revisions due to road changes and additions), its worth making sure existing hardware that worked with previous versions of
Windows such as my fTech Bluetooth GPS Receiver (which complies with the above Bluetooth and GPS standards), should at least work under Windows 10 natively. This means those responsible for the integration of Microsoft Maps into Windows 10 need to do some
bug fixing.
Its all well and good complaining about roads missing from your map data but I've had that problem with other (far more established) GPS mapping providers. At least you are getting some roads showing in the first place!
If you want to know more about how Windows 10 has 'broken' support for many existing GPS hardware receivers (including those that connect through 'non-proprietary' Bluetooth). ask yourself why are there products such as GPSDirect to try and fix the issue.
Surely the fact that people are going to the trouble of developing software to get around this common issue should indicate Microsoft has dropped the ball.