MicrosoftHello Alex,
I hope it's not too inappropriate to ask this directly here.
Is there already a well-known procedure available somewhere that I can reach and follow to be able to report a bug found while trying to run a Sysinternals tool ?
I've already tried to use Search line on top right corner to possibly find an answer inside TechCommunities or even this blog but found nothing, and some time ago I also tried on Q&A but what I found then was not very clear either, so I'm wondering if you're aware of anything more correct.
To be more specific, I'm currently unable to use latest ZoomIt v7.2 that seem to start fine (as Zoom64.exe) and correctly minimized just like v7.1, but if I try to open its Options menu then it immediately Stops working and always closes itself.
P.S. As always my OS, which is not Windows 10, is obviously already automatically sending to Microsoft any collected error reports, so ITMT I'm simply reverting to ZoomIt v7.1.
P.P.S. This is just a small idea, but I also just noticed that inside registry used by ZoomIt v7.1 there's no entry for MicrophoneDeviceId so I'm wondering if instead it might be needed by v7.2, so ITMT, while I'm searching inside registry or elsewhere via Bing to see if I find a similar value that might match same use and purpose, I'll also see if just trying to initialize MicrophoneDeviceId as REG_DWORD to 0, might be of any help anyway.
Quick update: MicrophoneDeviceId doesn't seem to be REG_DWORD, maybe a REG_SZ, but even if after I checked other sources I found which registry subkey is indeed involved for it (to identify my mic device), below HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture\, just trying to specify and use that value still does not changes effect I reported. So chances are that v7.2 is probably trying to access and use other Windows 10 & 11 only more specific APIs, maybe graphical and/or MultiMedia ones, that are unavailable with lower OS versions.
Thanks in advance for your attention.
Rob
