Windows Update effected my recording equipment

Even though your drivers might be up to date, I suggest that you install the drivers [for the devices you mentioned and your sound card(s)] again in case they have been corrupted.

Best of luck,
Denis

Hi, in all probability you are experiencing driver-related latency - you can check this by running LatencyMon (free). This does not fully diagnose the problem - this is not straightforward.

The usual resolution is to use an appropriate older version of the relevant driver.

Note that 20H2 has had particular issues with Conexant sound. (yours is not stated)

You've not stated your current build as you were prompted by this site, nor have you stated what the update (or upgrade) was.

If you had a feature update (build upgrade) the easiest way to resolve this will be to 'Go back to the previous build' which you can do within 10 days of upgrading.

If it was a particular update or driver update, you can uninstall and hide (block) that or roll back the driver update.

takadakeyo said:

Current build as in my laptop parts?

No, this meant the Windows 10 Build. It is reported in the response to the command

Code:

WinVer

which can be used in a cmd window or Powershell window. See below.

Denis

---

Welcome to TenForums.
It's really worth making time to browse through the Tutorial index - there's a shortcut to it at the top of every page.

- At the foot of the Tutorial index is a shortcut to download it as a spreadsheet.
- I download a new copy each month so I can benefit from Excel's filtering capabilities when I search for topics of interest.
- Tutorials are also listed by category at www.tenforums.com/tutorials

You have not completed your system specs. www.tenforums.com/profile.php?do=extra This can be very useful for respondents [depending on what problems you're investigating].
- At least, for the time being, fill in the model number and OS lines.
- If you click on the bottom-left of any of my posts, the "My computer" entry, then you'll see that I do just about the same myself.

- You can worry about the other details later.

---

By the way, you will often be asked for the Version or Build number of Windows 10.
- Right-click on the Start button
- Select Run
- In it, enter winver and a dialog box appears
- In your specs OS line, enter everything in the line beginning Version and anything else you want such as Home Edition [the Edition is stated in the paragraph underneath the Version line, mine is Home].
- Here's my winver dialog from a few weeks ago

- Version [mine is 20H2] refers to the latest half-yearly update "Feature update"
- Build number is in two parts - the 19042 also refers to the latest half-yearly update "Feature update" whereas the .868 shows the latest monthly "Cumulative update" I have installed.

I update my specs [OS line only] every month by updating the Version & Build numbers I've entered in that line. They show up in the block on the left of each one of my posts two lines above the Union Jack.
Windows 10 Home x64 Version 20H2 Build 19042.868
Naturally, it is entirely up to you but having all that info right there stops people having to ask me about it when I request assistance here which avoids delaying any useful guidance people might want to post.

Hi, let's try to make this a little simpler for you.

a. Search for, download, install and run LatencyMon (free) for, say 20-30 mins. (Click the little trangle).
b. Post a screenshot (picture) of its window

It will look something like this:


c. Build number: the forum displayed a prompt like this when you created your post (so we don't have to keep asking..)


d. Please post a screenshot (or screenshots) of your Update History including drivers at the bottom. Something like this:

- note drivers are at the bottom.

We can then see what you got when. Thanks.

Thanks, so you're on 20H2, but we don't know when you received that- compare mine where the feature update to 20H2 is at the top (quite recent too). Do you know when that happened? - Would have taken an hour perhaps.. with at least one restart...

If you look here: (search Settings for 'Go back') is the button greyed out as shown here?


You've received far more driver updates than I can remember seeing for a long time.

Considering the driver reported by LatencyMon, a search for
wdf01000.sys latency
produces quite a few results which you can study: e.g.

https://answers.microsoft.com/en-us/...d-9d6607f91ad9

https://www.kvraudio.com/forum/viewtopic.php?t=505093

You will find many struggling to identify the root cause. This is non-trivial.

The tool that can help- but which is technically demanding- there is really only 1 person on this forum who's familiar with it (zinou) is the WPA - Windows Performance Analyser/Recorder from MS.

You can search tenforums for
LatencyMon WPA
latency Windows Performance Analyser
etc
and find examples of its use and screenshots.

I can offer no quick and easy fix, I'm afraid.

There are the following approaches:
a. Experimental (=trial and error)
- rolling back updated drivers targetting the data this started
- disabling drivers you don't need in order to boot Windows e.g. graphics, internet etc and then seeing if LatencyMon reports issues - i.e. elimination

b. Roll back to or restore a previous build - this can remove the issue but mean you have to stay on that build (which is quite easy to do).
- you can only roll back if you are within 10 days of upgrading (up to 60 if you extended that- tutorial)
- restore- i.e. you had been using disk imaging and can restore a previously created image of that older build
(the routine and regular use of disk imaging is endlessly recommended here - a.e. Macrium Reflect (free)).
- Install a fresh copy of an older build - i.e. clean install.

c. Analytical - painstaking use of the Windows Performance Analyser.

There are some guides on the internet including some information on LatencyMon's site.