WaasMedic Agent Exe stopping me from working

My feedback hub doesn't work. I've tried using it from my CPU and it will not send anything out. I have no idea what is going on with my CPU. Lost my foster son last year and he advised me on my computers. Now with my husband going through his situation, he had a stroke on Christmas Eve, still needs another brain surgery and this CPU is not cooperating with me for me to do the simplest of tasks.

I'm about to have a meltdown. Covid is killing my life. I lost way too many friends and family last year. 12 passed and my husband almost left me. 3 were my foster sons. One a foster brother. Horrible year. I just need this computer to work. Sorry for taking it out of you people. I just need my computer back to normal again.

Interesting, how MS is getting bashed for trying to solve a scenario that earlier would have required re-installing the Windows.

From the high volume of 'same problem' entries, we can identify the pattern.

1. always after starting the machine.
2. always after starting the machine after forcefully closing down while a background update was running.

Understandably MS cannot stop the user from pulling the plug in the middle of whatever, even if it would end up leaving the system in a helluva mess.

What MS could do - rather than starting up into an unusable state - is making it clear that previous shutdown was irregular, and some repair work is necessary before the machine is available again.

An honest inconvenience is better than a hidden attempt to fix things, while making it impossible to work, anyway.

From the multitude of replies it is not possible to know whether

3. 'always in a system with either SSD or external drive' is true or not.

Mine certainly is a SSD based one, and today I encountered this hiccup after yesterday shutting down by a lid slam.

If 3) is true, then MS should be able to recreate and fix the problem without asking us to provide any further diagnostics without compensation.

****** Just read Reply #309 (MarcHoppe). Obviously not just SSD. But even ignoring my 3) , I still think a reasonable MS engineer should be able to do something, either to make the process genuinely background, or to inform the user, if the repairs require 100% control.

1. WaasMedic is in Task Scheduler - default is every Sunday at 3:00 or after so if you boot at 6:00 am it will run. If you boot mid week instead of Sunday it will run because it is overdue.
2. Have seen no postings saying people have turned off power during WUDs updating. MS used to advise of incorrect shutdown such as switching off power, now they don't but it cures itself during the next boot.
3. Happens with SSD or HD - the process of WaasMedic seems to be 'Read Only', advantage of SSD is that any read/write activity is a lot quicker due to the fact it does not read or write to a moving disk - it is Solid State. The fact there never seems to be any Write activity when WaasMedic runs infers to me it is actually not repairing anything. Don't suppose a lid slam would help but if it is updating it should warn you that it is updating. Here again it would sort itself out next boot.

If anybody at MS is using a user issue Windows 10 computer they will have the problem , likewise the million or so voluntary Insiders will have the same problem so MS definitely know the problem. After a lot of various update problems a couple of years ago, MS assured us there would be a lot more testing prior to public release - are they not doing the testing or are they ignoring Insiders feedback that things do not work properly as has happened on more than a couple of occasions since their statement.

"2) always after starting the machine after forcefully closing down while a background update was running". This is incorrect. I've never "forcefully closed down while a background update was running" on any of my five Windows 10 systems. WaaSMedic runs as a scheduled task. You can check in the task scheduler. Here on all five computers it's set to run every Sunday. The problem is that on some systems it runs for long periods of time reading files in the LCU folder and WinSxS folders and then starts reading personal files. Again you can monitor that activity in the Task Manger. However on this system which has an SSD even with the scheduled run of WaaS it only takes a matter of seconds to run and finish. There is a reason for that and it's just a matter of finding out what that reason is. As for Microsoft getting bashed for "helping" what have they done? Nothing, absolutely nothing. They can't even be bothered to read this thread. The one guy who did respond a couple of times is not an M$ engineer. The WaaS long run time issue started earlier this year not only for me but for most others who are posting in this thread. It is NOT user error it is a BUG most likely introduced in an update earlier this year. Look in Windows>Servicing>LCU and you'll find at least one folder called "Package for Rollup Fix". That indicates something is BROKEN and it's up to M$ to fix that issue. So far they have been unwilling to help in any way.