You are right of course , I am back to 1909 which was installed on 14/10/2019 but it seems the roll back to this did not revert fully as I still have the problem.
ea3aqr wrote:
This is W10 v.1909.
I don't remember if V.1909 is also afected by this issue, for sure v.1903 (13362) isn't.
Edit: I may have misspoken Re testing on 1909 shows the following correction
- FireShot Capture 148 - - .png (13.84 KiB) Viewed 8323 times
Although the request is showing as outstanding a helpful person on the voicemeeter forum gave the following info
"It's normal for a timer request to be 'outstanding' - Imagine this scenario:
App 1 requests 1ms timer
App 2 requests 1ms timer
App 1 exits
What will occur is:
Step 1 will result in decreasing the timer period per App 1's request.
Step 2 will result in the timer not being altered as it is already in the desired state. The request is kept.
Step 3 will result in App 1's timer request being removed, thus allowing the timer to return to default state...
However, the request from App 2 is still outstanding, and now it takes effect.
Accordingly, no change is made to the timer.
Without this 'outstanding' request to change the timer config, step 3 would result in App 1's request being cleared, and the timer returning to normal, leaving App 2 with the wrong timer config."