Benjamin Höglinger-Stelzer

Got notice from a user that it is back in the currently most recent build 🤣  Maybe Microsoft shouldn't have fired the entire QA department... Always nice to see...

I'd love if for a change Microsoft would swiftly fix **core components they casually break all the time** though 🤣

Isn't that exactly what one wants for a productive machine? Stuff randomly breaking? 🤣 I'll stay on 10 for as long as possible, public Beta products aren't my thing 😉

There's news on this topic, apparently Windows 11 will start to mandate Microsoft signed UMDF drivers as well, so future releases will be made "Windows 11-ready" accordingly.

I can try but device naming is unfortunately not as straight forward as it seems. *Sometimes* ™️ Windows is not happy updating this value. We can experiment with how reliable...

Did some experimentation; this unfortunately doesn't work reliably and will therefore only lead to more confusion. At a random pattern Windows will just fall back the display name to `DS3...

Hi @DJm00n As the project evolved we collected more and more feature requests and it became obvious that the approach "one property per setting", or a "key-value-pair" approach would soon...

> Then [Dmf_File](https://github.com/microsoft/DMF/blob/master/Dmf/Modules.Library/Dmf_File.md) could be your friend. Brilliant! Haven't seen this one yet. > File watcher is a great idea! Maybe you can extend DMF and write a module with...

I understand your use case but this request contradicts the current core design of the driver, I keep the request open but bear in mind this is no task of...

So let's collect desired features for a rewrite then 😉