Dave,
We checked the situation with higher level team. The possible reason for the issue we encountered could be related to changes in system Windows, corrupted files or services which inform s"AVG" about drive names or the file system generally.
To further analyse the issue, we would like to get additional logs from the specific computer where AVG is installed. I have sent you an email that has further information about collecting the AVG logs.
I ran a file and folder scan on a laptop drive which was attached to my PC as drive F:, and selected the entire drive.
The following list shows the results. I only selected the F: drive.
My PC is running Windows 10 Pro. The F: drive is Windows 7.
! PHP:Agent-TX[Trj] F:\Documents and Settings\Public\Downloads\XXXXXX Download\ba… Resolve >
! PHP:Agent-TX[Trj] F:\Documents and Settings\Public\Downloads\XXXXXX Download\ba… Resolve >
! PHP:Agent-TX[Trj] F:\Documents and Settings\Public\Downloads\XXXXXX Download\ba… Resolve >
! PHP:Agent-TX[Trj] F:\Documents and Settings\Public\Downloads\XXXXXX Download\ba… Resolve >
! PHP:Agent-TX[Trj] F:\Documents and Settings\Public\Downloads\XXXXXX Download\ba… Resolve >
! MBR:Plite-D[Rtk] F:\hiberfil.sys Resolve >
!AntiEXE F:\pagefile.sys Resolve>
The five PHP:Agent-TX[Trj] detections are all incorrect for two reasons.
Firstly, the files in question are script files containing a small bit of php code within simple recursive encoding. I have taken them to bits and the actual code is totally innocent - just a simplistic attempt to hide some key information from casual viewing of the scripts. I know what they are, I'm not worried.
Secondly, and most importantly, the five files are located on the C: drive, which is a completely separate physical device to the F: drive I was scanning.
The final two files in the list are correctly identified as the hiberfile.sys and pagefile.sys on the F: drive.
Why does the scan return results from a different drive to the one I asked it to scan, and tell me that the files it wasn't supposed to be looking at are on a different drive to the one they are on?
Hi Dave,
We appreciate your efforts in providing us the detailed information.
In order to investigate further, please share us the screenshot of the scan results to know more about the detected file paths.
Dave,
We checked the situation with higher level team. The possible reason for the issue we encountered could be related to changes in system Windows, corrupted files or services which inform s"AVG" about drive names or the file system generally.
To further analyse the issue, we would like to get additional logs from the specific computer where AVG is installed. I have sent you an email that has further information about collecting the AVG logs.
Dave, we will check this with our senior team and get back to you.
Your patience is much appreciated.
Hi Dave,
We appreciate your efforts in providing us the detailed information.
In order to investigate further, please share us the screenshot of the scan results to know more about the detected file paths.
Hi Dave,
We have additional troubleshooting steps given by our senior team. I'm sending out an email to you to get connected to our Remote support. Please follow the instructions in the email and we will proceed further in fixing the issue.