Windows 10: Windows Process Activation Process (WAS) errors after 1803 update

I have resolved this issue, but post it here as it may help others, especially as there are sooooo many issues after the 1803 upgrade.

After the 1803 update the system became very slow.

In the Windows system event log several errors due to the failing WAS service. The effect of this was to slow everything down. In the services info the WAS service is set to manual and stopped. If you try to turn it on it fails with files not found etc.

I noted that elsewhere in the forum someone had a similar situation after the 1709 update. He fixed his problem by going into the "turn windows features on/off" function and found that is his case there was a link to the FTP service. Although I didn't have the FTP service option I did note that the 3 options under the WAS service the .net option was not ticked. I ticked it in hope rather than belief, and rebooted (from cold just in case). To my surprise it booted very quickly and the WAS errors have gone!!!

Hope it helps

:)

 

Boot Process

Hi,

Please suggest me a link that can explain the boot process step by step of ...

• Windows 7,
• Windows 8.1,
• Windows 10,
• Windows Server 2008 R2 and
• Windows Server 2012 R2

With Regards

InTech

 

Process Monitor 1.2 Released

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more. Its uniquely powerful features will make Process Monitor a core utility in your system troubleshooting and malware hunting toolkit.Process Monitor runs on Windows 2000 SP4 with Update Rollup 1, Windows XP SP2, Windows Server 2003 SP1, and Windows Vista as well as x64 versions of Windows XP, Windows Server 2003 SP1 and Windows Vista.

Source: ProcessMonitor

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.