Windows 10: GoogleUpdate.exe and Controlled Folder Access

Hello,We have Controlled Folder Access activated on the computers of our network and GoogleUpdate.exe is always blocked by this feature.The problem is that if I want to exclude GoogleUpdate.exe I need to mention the path to the exe file on the exclusions. But every time GoogleUpdate.exe is created, it is created on a temporary folder that is always different. Wildcards does not seems to work for Controlled Folder Access exclusions.Example 1 :Example 2 :Thanks for your help.Jonathan

:)

 

Controlled Folder Access

Hi.

I've been using Controlled Folder Access recently but I'm having a problem getting one application to change/create files. I use doPDF8 to create PDF files, but when CFA is active, it won't save my work. The notice explaining that something has tried accessing the folder only comes up once. (I assume that if you don't do anything about it, the program trying to access the file is put on the 'black list'.) Turning CFA off and then on again causes the notice to appear once more. However, the notice seems to suggest that it is C:\Windows\splwow64.exe that is trying to access/create the file, but when I put this into the 'allow app control' list, it still doesn't work. The only way I can find to get the PDF file created is to turn off CFA, create the file and then turn it back on again.

Any ideas?

Matt

(Windows 10 ver 1709)

 

Controlled Folder Access is off. Shouldn't this be on?

Suggestion to also read

• this article (ignore ads):
  How to Protect Your Files From Ransomware With Windows Defender’s New “Controlled Folder Access”
• and this thread:
  Controlled Folder Access Feature in Windows 10 Fall Creators Update Questions?
  

 

Controlled Folder Access

1709 is very old. The functioning of Controlled Folder Access has changed little since then but the UI has improve enormously. In 1903 it now tells you exactly what was blocked and allows you to add it to the list of allowed apps with a single click. With 1709 you have to dig deep into the Event log to find out the path and name of the executable you'll need to allow through CFA.

Open Event Viewer, go to Application & Service Logs > Microsoft > Windows > Windows Defender > Operational. Look for Event ID 1123 which will give the full name and path of the executable that was blocked. IDs 1125 and 1127 may also be relevant.

Note that a restart is required before any apps you have added will be allowed through CFA.