Linker prevented from writing file starting with version 17.3.3011

Hello R Curry,
We regret to hear about the inconvenience caused, could you please share us a screenshot of the interface from where you are facing issues, so that we can check and help you. Please click on the link to show how to create a screenshot : http://avgread.me/1aZxsAV
Also, please tell us the version of AVG you are using in your computer. Thank you.

Hi Akash,

I added the executable to Exceptions->File Path and Exceptions->CyberCapture.  The Cybercapture addition may have caused the intermittent problem to happen less often.  It definitely does not resolve the issue.

Hello R Curry,
We regret to hear about the inconvenience caused, could you please share us a screenshot of the interface from where you are facing issues, so that we can check and help you. Please click on the link to show how to create a screenshot : http://avgread.me/1aZxsAV
Also, please tell us the version of AVG you are using in your computer. Thank you.

I am having an issue since the latest upgrade (17.3.3011)

AVG Free, Resident Shield component (when 'ON') prevents the linker from completing.
Linker is 386Link.exe: 386|LINK: 8.03 – Copyright (C) 1986-98 Phar Lap Software, Inc.

The error returned is Fatal error LINK.1060: Cannot create linker output file – Permission denied
The command (that fails):
 386link @\s\DMC3.dos @AL2\DMC3\DMC3 -exe c:\T.EXE -LIB DACLIB32\DACLIB32.LIB

Directing 'T.EXE' to somewhere other than C:\ works and it also works just fine if I turn off Resident Shield.

I have already provided that information above.


Here you go Viveksaravanan Neelagantan.

The same thing I already posted but now as a picture

Hello R,
We are sorry but we haven't received the screenshot of the error message yet. Please try to follow the instructions provided in previous post and reply back with screenshot.
Thank you.

My error is showing up in a command-line prompt (we’re old-school and build with ‘make’).  I can take a picture of it, but as it is all characters I’ll just post that inline.
 
r:\t>del t.exe
Delete R:\t\T.EXE (Y/N/R)? Y
     1 file deleted         466,944 bytes freed
 
r:\t>386link @\s\DMC3.dos @AL2\DMC3\DMC3 -exe T.EXE -LIB DACLIB32\DACLIB32.LIB
386|LINK: 8.03 – Copyright (C) 1986-98 Phar Lap Software, Inc.
 
r:\t>del t.exe
Delete R:\t\T.EXE (Y/N/R)? Y
     1 file deleted         466,944 bytes freed
 
r:\t>386link @\s\DMC3.dos @AL2\DMC3\DMC3 -exe T.EXE -LIB DACLIB32\DACLIB32.LIB
386|LINK: 8.03 – Copyright (C) 1986-98 Phar Lap Software, Inc.
Fatal error LINK.1060: Cannot create linker output file – Permission denied

                       "T.EXE".
 
This morning, I noticed that it is not guaranteed to fail every time; there is some random aspect to it.  When invoked from a build script the failure seems very consistent.
 
I have checked for information in event viewer, but I see nothing there coincident with failure in the linker.
 
I stated in the original error description that I was having a problem writing to C:\ and that much is true.  A better description is that I cannot write to any location on C: reliably when the Resident Shield module is active.  I only have the one local disk, and I have been assuming this would be a problem on any local disk.

Hi Akash,

I added the executable to Exceptions->File Path and Exceptions->CyberCapture.  The Cybercapture addition may have caused the intermittent problem to happen less often.  It definitely does not resolve the issue.

R, For your info, just in case that you are unaware, you can post the screenshot here in your topic. Click on 'Answer' & then click on the 'Image' [mountain symbol] & follow the instructions. 
AVG Guru

I forgot to say: yes it is an application.  Adding to exceptions did not help.