WaasMedic Agent Exe stopping me from working

The problem with being a "Windows lover" is that it blinds people to the facts and keeps them in defense mode constantly looking for something else to blame for Windows' problems. There are already other threads concerning WaasMedic. In one a "Microsoft Agent" wrote "By design, WaasMedic is only going to work if it finds a problem with Windows Update". That is not correct. It runs by schedule every seven days. On one system this morning that hadn't been booted since the last scheduled run on Sunday the 18th WaasMedic ran for 7 minutes at or near 100% disk activity. So what is it "fixing" every week and if it's fixing something then M$ is breaking something every week. It showed no network activity so it's not downloading anything but simply grinding away at our drives reducing their lifespans.                                                                                                                 

In that same thread the Microsoft Agent wrote "We got to involve Paul in the original thread WaasMedic Agent Exe stopping me from working - Microsoft Community, and he'd like to start collecting high CPU or high disk usage cases of the WaasMedic agent through Feedback Hub entry, and Feedback URLs on that thread.

We will continue to focus only in that thread to better support this issue".

So where is "Paul" ? Where is the interaction from M$ Agents in this thread if they are "focusing" on it ? They are simply ignoring the issue since apparanlty M$ has no clue why WaasMedic needs to grind away at our harddrive at least once a week and accorinding to some reports every day.

1. Updates installed when issue, Windows checks at least 2ce a day for any new issued updates.

Have you checked your manufacture's website? Windows Update will update driver(s) after it has been published for 1 month.

2. System maintenance/trouble shoot runs automatically as a regular MS task. Did have errors sometimes with updates but these disappeared over 3 months ago.
3. AV OK, Window Defender installed - no 'unusual software' nothing new installed for 2 years.

Ok, you're good to go. But you're using AV anti-virus, right? I just asked.

4. A system should very, very rarely use 100% disc so the fact it does is cause to worry as this infers a problem.

I'm missing here: instead of waiting, why don't we check why and which is using disk by using Resouces Monitor?

If you found some system file is writing, and/or app(s) or services(s) has stopped, let us know your Event Viewer. And while you're uploading it, don't forget to delete some personal information.

5. No need for a new thread as this thread is in connection with WaasMedic using 100% disc on frequent occasions - I have only had the issue once - normally WaasMedic running takes 50% usage including all other processes, as this happens at boot, a large amount of disc is required to load system files, app start--ups etc. (in my case minimal number)

I do have a Dell computer but I assume all contributors to this thread have various other makes.

Oh, I'm using ASUS now. And I mean: "with detailed information from Windows Error Reporter" is report it.

That's it. Have a good day from Windows lover!

Maybe you're right....but my 'advice' is not only for built-in Windows OS, but it's for including VM!

If you want to look deeper into what some of the "internals" do as regards WaasMedic, the blog below provides some useful insights to those technically minded.

This is an analysis of the UPFC.EXE that seems to be what starts off the WaaSMedicSVC.

https://www.acepace.net/2019-03-29-upfc/  

As most who are suffering the system hogging and high disk activity, are saying (quite rightly) that a "system checking and remediation" service like this should NOT be taking over the machine in this way. I think Microsoft still need more information on this, to be able to come up with a proper fix, so if you have any "screenshots" or a Feedback hub trace you can supply when it is happening, then do that if you can. Ideally, this stuff should be running at a lower priority (affinity) than it does, and it should reduce its "run count" per session.

In case some installed app or program is causing this "spike" in remediation, it might be worth getting the "Diagnostic Data Viewer" from the MS Store, and running it, first using the "Problem Reports" section to get an overview of app hangs/errors, to see if they are coincident with the long run times or hogging by WaasMedic, then look at the "Diagnostic Data" section. In the Search box at the top, put in Waas, and you should see the Microsoft.Windows.WaaSMedic.SummaryEvent set.

You could upload a typical one to Feedback Hub, to help them diagnose what might be going on. You only need to click on the "Provide Event Feedback" at the top of the viewer, and it starts the Feedback Hub, and fills in some stuff for you.