WaasMedic Agent Exe stopping me from working

WaasMedic will show as stopped in services , this is because this is a scheduled task. This will show in scheduled tasks as running from 3:00 am every 7 days on a Sunday. Booting after 3:00 am will then send a trigger to the WaasMedic app to run shortly after boot. If you open actual services, this will listed as Manual, i.e., task scheduler will effectively switch it on to run. Likewise a lot of services, only running when receiving a trigger from Task Scheduler. I also have a second unscheduled weekly run, it appears to run sometimes a day or so soon after a WUD but, I did find once, we also seem to get 'updates' that don't come thru' the actual WUD app but come in thru' the back door. co-incidence perhaps?

I am totally confused now then.

The machine I removed third party AV from has no WaasMedic running.  Actually, looking in the Services Waas Medic is reflected as STOPPED.

I did not stop it.

What the hell is this damned thing?

Anyway, I am out o here.

Thanks to everyone.

6-8 weeks ago, booted on the Sunday morning, attempted to open Task Manager from Task Bar so could catch WaasMedic running. Task Bar not responding, could not open TM, any apps, Start etc. Control/Alt/Delete brought up Task Manager, WaasMedic not running. Put away TM, control/alt/delete again, WM still not running, realised mouse working OK so could interact with TM. Couple of minutes later WM kicked in, another couple minutes later decided to stop. then forced a reboot.. Assumed, rightly or wrongly, WM was not causing issue with Task Bar not being responsive.

WaasMedic than ran on Monday morning's boot which seemed fair enough, doing a catch-up. Since then, this weekly second run has been moving out each week from am boot to pm boot, next week moves on a day, back to am boot. last week had progressed to Wednesday pm boot, so, in theory this week will run Thursday am boot. Must admit, overall, each run might last a minute or so less duration, now might be 6 minutes each run instead of 8 - put this down to me cancelling the run of 6-8 weeks ago. So does a cancel trigger a second boot, cancelling each time triggers another, is this why some people reporting WM running each day.

No that's not it. The WaaS issue occurs on systems that only have Microsoft Defender. A third party AV solution can certainly add to the run time but is not the cause.

Anyway I've noticed on my studio computer that WaaS has been running on Fridays as well as Sundays. It runs for about five and a half minutes each day instead of running for 11 minute plus every Sunday as before. So is Microsoft's solution to break up the run into two days to make it seem like it's running for a shorter time as we all watch it on Sunday? There is NO reason WaaS needs to scan and read the same files twice a week every week.

Paul says that screenshots don't do any good but they would if he actually knew what to look for. I doubt that the Feedback Hub reports I generated today will ever make it to someone at Microsoft that might just might actually know what they are doing.

With Windows 11 right around the corner I imagine 10 will be orphaned and any issues will go unaddressed as the WaaS issue has for six months.

So for anyone with an older computer the solution will be to run Linux since Win 11 requires newer system specs. It's funny how much Win 11 "borrows" from Linux. It's too bad it won't also borrow the concept that an Operating System shouldn't be Spyware and Malware and that an OS should be lean and efficient and not bloated with data mining systems. .