CSR Bluetooth driver stopped working after last Win7 update  

Has anyone a solution to this? This driver has worked fine since late august and after the latest security update on Win7 it has stopped working correctly. It can see the server and reports back it COM nr, but when opening we're back at the same problem as in summer 2017 - timeout even after waiting maximum allowed time in the COMPort.Open statement in VB2010.
Where can I find the old driver? I use the BT820 from Laird that uses a CSR chipset with internal BT driver.
So there is nothing I can download from CSR.
Or, is there any solutin to this?
CSR is as usual unresponsive.
rgds

Hi, thanks for reply. If this were true then WHY was the safety critical update issued from Microsoft? Doing a system restore would also remove all other program changes that I've made to my own developed SW? What is the idea of doing work if the first update forces me to remove all my work? Perhaps my computer should only be used for doing global purchases and viewing the internet?
Well, I hope someone comes up with anything more practical that could SOLVE this problem. I take it from numerous previous articles on the subject that the problem is in the PnP layer in Windows.
However, in the old XP SP3, it all works fine, since this has NOT been updated.... LOL!
And all this is because ot the numerous CIA exploits we have around and that MS takes one at a time, which will take decades to counteract. Yet another reason for a "new" Windows.....

Hi mate, thing is I've tried the uninstall before on Win7, it is a complete disaster. After that
attempt I had to install Win7 from scratch to make it work properly. So, not again.
Case is that if you do any update of any kind after a system checkpoint, all is lost, it can't
go back without making a mess of things. It is NOT benevolent.

What I see is needed is how to fix that recurring problem with the PnP layer that seems to be
the culprit.

That fact exactly this problem existed in mid aug this year, then came an update and all worked fine.
Then another update and the problem is back again. In Win7.
In WinXP that is kept away from all updates, it works fine.

Hi, I'vd been in the computer/electronics development business since 1970.
The driver is developed & owned by Microsoft and is of the latest version, yes.
The chip & FW is by CSR (CSR8510).
I' surprised you ask those questions since I told that it all worked perfectly during the autumn
until the latest update from MS.
Since the dongle is not of my make and the driver stack is by MS, then where do I do wrong?

Hi, well uninstalling the update - last time I tried this I ended up having to install Win7 to a fresh disk
since the entire system crashed because of some error in the uninstall.

There are Bluetooth modules around that has a range of abt 1km line-of-sight. But as we all know by now CIA has infected everythig there is, so the MS "concern" is reall out of place.