Cumulative Update KB4512941 Windows 10 v1903 build 18362.325 - Aug. 21 Insider

swarfega said:

hmm no update being offered on WU. Still on .295.

Should probably have a go at MUC (MS Update Catalog) after backing up.

swarfega said:

I'll wait a day then give that a go.

Fair enough!

No thanks, I'm not a beta tester cannon fodder. Will wait for offical CU.

slicendice said:

@IronZorg89

I had similar issues with my wireless mice using the Unifying Receiver yesterday. I've also got MX Master, but also other mice. All behaving the same. Over BT everything worked great though. Never had this issue before and today all is normal again. Very strange behavior.

Very strange behaviour indeed!, What caught my attention though was the fact that there were news about flaws in Logitech Unifying dongles. Even though the following article mentioned there was no fix for the issue right at the time of writing, somehow a recent update was issued and I think I tried to install it. That was when I started to notice some strange behaviour. Couldn't say whether or not that has anything to do with my recent action. But I am not inclined to think so, according to your own experience

Logitech "Unifying" dongles are impacted. According to Mengs, the vulnerabilities impact all Logitech USB dongles that use the company's proprietary "Unifying" 2.4 GHz radio technology to communicate with wireless devices.

On top of the four vulnerabilities he discovered over the course of the last months, Mengs also warned that many ogitech Unifying dongles are still vulnerable to the old MouseJack vulnerabilities disclosed back in 2016.

Logitech wireless USB dongles vulnerable to new hijacking flaws | ZDNet

All in all, for now I am not having any issue with both mice. I have to say though, from the time I was having this issue to present day, lots of changes have been made to my machines with roll-backs, CUs, dism.exe command-lines and so on...

Polo6RGTI said:

I also had the same issue, the "AllowCortana" and "BingSearchEnabled" registry settings needs to be set to 1 to fix the issue.

Code:

Windows Registry Editor Version 5.00


[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search]
"AllowCortana"=dword:00000001
"BingSearchEnabled"=dword:00000001

Attachment 244049
Attachment 244048

Thank you a lot, that worked!

For everyone who installed this update please try and run any program that uses .net. It completely castrates .net. Going back to 295 fixes the issue. This update is crap.