I get a bad return code on "Stop CryptSvc" task

Hi Shawn,



I am running a simple (2 lines) script called "Stop CryptSvc" saved in C:\ that starts on event 1074 and sometimes (1 out of 30) I get a bad return code, the task runs 2 sec too late (after apps delayed the task) or the task runs OK but the CryptSvc service was not stopped. Not sure if this is an acceptable performance? I wonder if I rearrange the action tab items



and place the full path in "add argument" and just CryptSvc.bat in Program/script?
I already added c:\ in "Start in"

Any suggestions?
Frank

Brink said:

Hello Frank,

What is the code in the CryptSvc.bat file?

Maybe we can include it directly in the task instead of running a .bat.

Sorry, forgot to show the script.
Like I wrote it runs OK 97% of the time but have to check code and timing after each boot as I feel I cannot rely on it
Thanks
Frank

Brink said:

Normally, this service wouldn't need to be stopped at shut down since shut down will power off the computer.

Is it causing an issue at shut down?

It is about a 2 year old issue "VSS error 13" on this forum, only some systems (like W10 1909 x64 Home) are affected and stopping Crypt.SVC at shut down will fix it. Tried all the other methods on this forum and others.
Frank

Brink said:

If it's causing a hung shut down, you could also test turning on AutoEndTasks and lowering the HungAppTimeout value.

Turn On AutoEndTasks at Restart, Shut down, or Sign out of Windows 10

Change HungAppTimeout Value in Windows 10

Hi Shawn
Reading your tutorial on that and will try it out if my apps "degradations" exceed 1 minute, both shutdown (max 20 sec., avg. 12 sec.) and full boot (0x0) are less than a minute so that's not the problem. Do you see anything in my task that can be improved (make the start and execution of the script 100%)?
Frank

Brink said:

I'm not sure what else can be improved on the script.

Is there an event I can use in my task that runs 2-5 seconds before Explorer shuts down (1074), do you know?