SWCUEngine.log on C:\ since Windows 10 update 1709

bob3160 · 2017-11-12T16:25:25.000Z

I can confirm that and am reporting it to the developers.

system · 2017-11-18T11:30:31.000Z

Same situation here, latest versin 1709 of Windows 10 Pro x64 (OS Build 16299.64).

SWCUEngine.log file appers on root of partition where Avast is installed (C: in my case), and can’t be opened and also can’t be delete. Avast is holding write lock on file.

bob3160 · 2017-11-18T14:45:26.000Z

zokopa post:3:

Same situation here, latest versin 1709 of Windows 10 Pro x64 (OS Build 16299.64).

SWCUEngine.log file appers on root of partition where Avast is installed (C: in my case), and can’t be opened and also can’t be delete. Avast is holding write lock on file.

Avast self protection is likely protecting the file.

system · 2017-11-21T17:28:44.000Z

I have the same issue but you can copy it and then read the copy.

system · 2017-11-29T17:43:04.000Z

Was the problem resolved?

system · 2017-11-29T22:50:23.000Z

As well as copying the file, I can delete it occasionally but I can’t see any pattern in this. There is really no point in deleting it because it comes back the next day. It’s presence is harmless but irritating! >:(

system · 2017-11-30T14:13:35.000Z

Really, annoying …

bob3160 · 2017-11-30T14:50:11.000Z

I’ve reported this to Avast on the Developers Channel.

http://screencast-o-matic.com/screenshots/u/Lh/1512053375265-25504.png

When I get an answer, you’ll have an answer.

system · 2017-12-01T03:42:24.000Z

Thank you!

bob3160 · 2017-12-01T13:43:44.000Z

yurlow69mail2013 post:10:

Thank you!

Here’s what I’ve been told so far:
“Hi! SWCUEngine.log is written by Software Cleanup Engine which is used for Cleanup and Game Mode.
Error 3004 means that requesting additional information from backend failed.
Why it is located in C:\ is probably related to wrong initialized Engine instance.
We are currently investigating that. I will let you know as soon as I have more information.”
When I know more, so will you.

system · 2017-12-01T19:40:57.000Z

Thanks again!

bob3160 · 2017-12-01T20:49:54.000Z

Problem was resolved with the last VPS update.

http://screencast-o-matic.com/screenshots/u/Lh/1512161355858-10732.png

system · 2017-12-01T21:20:55.000Z

Does not want to be updated …

bob3160 · 2017-12-01T21:24:48.000Z

http://screencast-o-matic.com/screenshots/u/Lh/1512163345440-97731.png

system · 2017-12-01T21:39:58.000Z

It was updated, we will look, what will be farther.

system · 2017-12-02T16:05:35.000Z

SWCUEngine.log is also created in the root of drive C.

bob3160 · 2017-12-02T16:13:25.000Z

yurlow69mail2013 post:17:

SWCUEngine.log is also created in the root of drive C.

Did you delete the log after doing your VPS update ???
I don’t have the log on the root folder any more.

http://screencast-o-matic.com/screenshots/u/Lh/1512231191696-72524.png

system · 2017-12-02T19:08:36.000Z

Removed, but it appeared again.

bob3160 · 2017-12-02T19:50:03.000Z

yurlow69mail2013 post:19:

Removed, but it appeared again.

In the root folder ??? Not here as you can see from the screenshot.

Asyn · 2017-12-02T20:24:46.000Z

bob3160 post:20:

yurlow69mail2013 post:19:

Removed, but it appeared again.

In the root folder ??? Not here as you can see from the screenshot.

Hi Bob, your screenshot is related to another log file.

Announcements