Some machines fail software updater Code 514

Scholar

Some machines fail software updater Code 514

Hi, 

 

Checked our companys psb and saw few machines (including my own) not being scanned for software updates. 

Employees are in and machines online but last known working time has been July 5. 

 

Affecting small set of machines running Windows 10 (1809, 1903). Some identical machines work fine with same version. 

PSB 19.5, update agent version 4.05.1065.0. 

Same on working and non-working devices.

Manual check gives Failed to scan for missing updates, Error code 514. 

In log it reports:

2019-08-06 10:58:56.939 [3100.3ae0] I: Updating the database.
2019-08-06 11:00:58.317 [3100.3ae0] I: Updating the database. Done.
2019-08-06 11:00:58.317 [3100.3ae0] I: Scanning local system for updates.
2019-08-06 11:00:58.404 [3100.3ae0] I: Scanning local system for updates.Finished with status 'Scanner error; Failed to initialize a scanner.'
2019-08-06 11:00:58.405 [3100.3ae0] I: Updating the database.
2019-08-06 11:05:03.222 [3100.3ae0] I: Updating the database. Done.
2019-08-06 11:05:03.222 [3100.3ae0] I: Scanning local system for updates.
2019-08-06 11:05:03.358 [3100.3ae0] I: Scanning local system for updates.Finished with status 'Scanner error; Failed to initialize a scanner.'

 

Can only say it started during my vacation, last known working time in these machines are from 5.7. around 9:00. 

My log from working time below. 

2019-07-04 14:51:20.476 [1754.2534] I: Deploying updates.
2019-07-04 14:51:20.561 [1754.2534] I: Deploying updates. Done.
2019-07-05 07:02:03.687 [3560.3324] I: Updating the database.
2019-07-05 07:02:35.154 [3560.3324] I: Updating the database. Done.
2019-07-05 07:02:35.154 [3560.3324] I: Scanning local system for updates.
2019-07-05 07:02:52.051 [3560.3324] I: Scanning local system for updates. Done.
2019-07-05 07:02:52.051 [3560.3324] I: Deploying updates.
2019-07-05 07:02:52.090 [3560.3324] I: Deploying updates. Done.
2019-07-05 08:46:06.159 [31ec.2ddc] I: Updating the database.
2019-07-05 08:46:07.270 [31ec.2ddc] I: Updating the database. Done.
2019-07-05 08:46:07.270 [31ec.2ddc] I: Scanning local system for updates.
2019-07-05 08:46:22.588 [31ec.2ddc] I: Scanning local system for updates. Done.
2019-07-05 08:46:22.588 [31ec.2ddc] I: Deploying updates.
2019-07-05 08:46:22.630 [31ec.2ddc] I: Deploying updates. Done.
2019-08-05 06:45:05.861 [2468.3940] I: Updating the database.
2019-08-05 06:46:18.944 [2468.3940] I: Updating the database. Done.
2019-08-05 06:46:18.944 [2468.3940] I: Scanning local system for updates.
2019-08-05 06:46:19.461 [2468.3940] I: Scanning local system for updates.Finished with status 'Scanner error; Failed to initialize a scanner.'

 

Any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions
Scholar

Re: Some machines fail software updater Code 514

I got help from F-Secure on topic and got it resolved. 

Something had been corrupt in these machines due to issue in Server-end.

 

Resolution: 

1. In affected machine, go to %ProgramData%\F-Secure

2. Rename swup2 folder

3. Restart machine / restart all security features.

3 REPLIES 3
Superuser

Re: Some machines fail software updater Code 514

Hello,

 

I wonder if the symptoms could be related to this development:

 

https://community.f-secure.com/t5/Business-Suite/Upgrades-to-Software-Updater/ta-p/118347

 

Mandatory upgrades to Software Updater engines bring many improvements

 

(It should not affect F-Secure PSB, though since it is Cloud-based and updates-hotfixes oneself automagically.)

 

Best regards: Tamas Feher, Hungary.

 

Scholar

Re: Some machines fail software updater Code 514

I got help from F-Secure on topic and got it resolved. 

Something had been corrupt in these machines due to issue in Server-end.

 

Resolution: 

1. In affected machine, go to %ProgramData%\F-Secure

2. Rename swup2 folder

3. Restart machine / restart all security features.

F-Secure

Re: Some machines fail software updater Code 514

You could also enable "Pilot" in your profile and you would get latest Computer Protection 19.6 which fixes this issue automatically.

It will be soon published to everyone to solve this issue