You change the account of the administration server service via the klsrvswch tool. Note that this is the only way to change the account, manual modification (for example, via services.msc) is not supported.
Then, the you run the Install required updates and fix vulnerabilities task.
As a result, the task is cancelled and updates are not installed.
Diagnostics
The following error can be found in$klserver-1093.log:
20.11.2023 10:26:16.683 00000ADC.000028C0 L1 KLSTD:ErrorERROR_ACCESS_DENIED(attempt 186 from 300) for the file 'C:\ProgramData\KasperskyLab\adminkit\1093\.working\FTServer\#WSUS#'
When checking permissions of the file C:\ProgramData\KasperskyLab\adminkit\1093\.working\FTServer\#WSUS#, it lacks the new service account assigned to thekladminserverservice:
In this example, the Administration Server accountis the old service account used to start the KSC service.
Workaround
Add the new KSC Service account or theKLAdminsgroup to the access control list of the #WSUS# file and grant it full access:
Featured Replies
Please sign in to comment
You will be able to leave a comment after signing in
Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials.
Problem
You change the account of the administration server service via the klsrvswch tool. Note that this is the only way to change the account, manual modification (for example, via services.msc) is not supported.
Then, the you run the Install required updates and fix vulnerabilities task.
As a result, the task is cancelled and updates are not installed.
Diagnostics
The following error can be found in $klserver-1093.log:
20.11.2023 10:26:16.683 00000ADC.000028C0 L1 KLSTD: Error ERROR_ACCESS_DENIED (attempt 186 from 300) for the file 'C:\ProgramData\KasperskyLab\adminkit\1093\.working\FTServer\#WSUS#'
When checking permissions of the file C:\ProgramData\KasperskyLab\adminkit\1093\.working\FTServer\#WSUS#, it lacks the new service account assigned to the kladminserver service:
In this example, the Administration Server account is the old service account used to start the KSC service.
Workaround
Add the new KSC Service account or the KLAdmins group to the access control list of the #WSUS# file and grant it full access: