Trend Micro Maximum Security 11.1 filling up disk space

Computer: ASUS VivoMini
OS: Windows 10
Version: Maximum Security 11.1.1045

The disk space on my computer recently started to run out, and when I investigated what caused this I noticed that most of the space was taken by my Maximum Security software. To be specific it was the debug folder in the AMSP folder that was taking up most of the space. When investigating this I found that this appears to be a common problem, and that the suggested fix was to set the DebugLogAMSPServiceStart flag to 0. The problem with this is that my software seems to be setting the flag back to 1 when it starts up again.

What can I do to resolve this issue? Is it safe to delete the content of the debug folder?

AmspConfig.ini

[Debug]
DebugLevel=2
DebugFlag=1
DebugLogFilePath=.\Debug\
DebugLogFilePrefix=Amsp
DebugLogFileMaxSize=52428800
DebugLogFileMaxCount=10
DebugLogAMSPServiceStart=1
DebugLogMode=0

; DebugLevel: Debug level
; 0: Disable -> No log.
; 1: Performance -> Performance testing data.
; 2: Info -> Detail information.
; 3: Warning -> Acceptable error.
; 4: Event (Always output to AMSP_Event.log) -> Critical event.
; 5: Error -> Unexpected input or return error.
; 6: Fatal -> System or unrecoverable error.
; DebugFlag: Debug flag
; 1: File
; 2: Console
; 4: Debug string
; 7: All
; DebugLogFilePath: Debug log file absolute path
; For example, C:\Program Files\Trend Micro\AMSP\Debug.
; DebugLogFilePrefix: Debug log file prefix
; For example, Amsp -> Amsp_*.log.
; DebugLogFileMaxSize: Debug log file size (1-100M)
; DebugLogFileMaxCount: Debug log file max count (1-10)
; DebugLogAMSPServiceStart: Start up AMSP_LogServer.exe with Amsp service

DebugLogFileSeq=1

AmspLogFilter.ini

[LogFilter]
LOG_INFO_TYPE_FRAMEWORK=2
LOG_INFO_TYPE_REGISTRY=2
LOG_INFO_TYPE_CONFIG=2
LOG_INFO_TYPE_NETWORK_CONFIG=2
LOG_INFO_TYPE_PROCESS_SNAPSHOT=2
LOG_INFO_TYPE_SYSTEM_INFORMATION=0
LOG_INFO_TYPE_TREE_INFORMATION=0

; LOG_INFO_TYPE_ENGINE=2
LOG_INFO_TYPE_ENGINE_IAU=1
LOG_INFO_TYPE_ENGINE_SSAPI=2
LOG_INFO_TYPE_ENGINE_DCE=2
LOG_INFO_TYPE_ENGINE_TMUFE_FR=1
LOG_INFO_TYPE_ENGINE_TMUFE_UF=1
LOG_INFO_TYPE_ENGINE_TMUFE_CS=1
LOG_INFO_TYPE_ENGINE_TMUFE_DC=1
LOG_INFO_TYPE_ENGINE_TMFBE=2
LOG_INFO_TYPE_ENGINE_ICRC=2
LOG_INFO_TYPE_ENGINE_TMPROXY=1
LOG_INFO_TYPE_ENGINE_AEGIS=2
LOG_INFO_TYPE_ENGINE_TMSA=1
LOG_INFO_TYPE_ENGINE_TMLCE=2
LOG_INFO_TYPE_ENGINE_TMLES=2
LOG_INFO_TYPE_ENGINE_TMPFW=2
LOG_INFO_TYPE_ENGINE_BP_ADAPTER=1
LOG_INFO_TYPE_ENGINE_WHITELIST=2
LOG_INFO_TYPE_ENGINE_DRE=2
LOG_INFO_TYPE_ENGINE_NCIE=2
LOG_INFO_TYPE_ENGINE_EAGLEEYE_UM=1
LOG_INFO_TYPE_ENGINE_EAGLEEYE_KM=1
LOG_INFO_TYPE_ENGINE_OSPREY_KM=1
LOG_INFO_TYPE_ENGINE_TMUMH=2
LOG_INFO_TYPE_ENGINE_FALCON=2
LOG_INFO_TYPE_ENGINE_TRXHANDLER=2
LOG_INFO_TYPE_SERVICE_STATUS=2
LOG_INFO_TYPE_FOLDER_PATH=2
LOG_INFO_TYPE_FILE_ATTRIBUTE=2
LOG_INFO_TYPE_CONNECTION_STATUS=2
LOG_INFO_TYPE_ENGINE=2
ERROR=2
LOG_INFO_TYPE_SYSTEM_EVENT=2
LOG_INFO_TYPE_DIRTREE_INFORMATION=2

AmspLogList.ini

[LOG_INFO_TYPE_FRAMEWORK]
amsp_filepath=C:\Program Files\Trend Micro\AMSP\debug\
amsp_filename=Amsp_*.log*

[LOG_INFO_TYPE_ENGINE]
iau_folderpath=C:\Program Files\Trend Micro\AMSP\debug\7\
iau_foldername=*
iau_udump_filename=tmudump.txt

ssapi_filepath=C:\Program Files\Trend Micro\AMSP\debug\10001\
ssapi_filename=ssapi.log

dce_filepath=C:\Program Files\Trend Micro\AMSP\debug\10002\
dce_filename=TSCDebug_*.log

tmufe_filepath=C:\Program Files\Trend Micro\AMSP\debug\10005\
tmufe_fr_filename=TMUFE_FR.log
tmufe_uf_filename=TMUFE_UF.log
tmufe_cs_filename=TMUFE_CS.log
tmufe_dc_filename=TMUFE_DC.log

tmfbe_filepath=C:\Program Files\Trend Micro\AMSP\debug\10007\
tmfbe_filename=TMFBE.log

icrc_filepath=C:\Program Files\Trend Micro\AMSP\debug\10008\
icrc_filename=*.log

icrc_dat_filepath=C:\Program Files\Trend Micro\AMSP\debug\10008\
icrc_dat_filename=*.dat

icrc_csv_filepath=C:\Program Files\Trend Micro\AMSP\debug\10008\
icrc_csv_filename=*.csv

tmproxy_filepath=C:\Program Files\Trend Micro\AMSP\debug\20004\
tmproxy_filename=*_NSC_TmProxy.log

tmosprey_filepath=C:\Program Files\Trend Micro\AMSP\debug\20013\
tmosprey_um_filename=*_EE_TmOsprey*.etl
tmosprey_km_filename=*_EE_TmUsa*.etl

eagleeye_filepath=C:\Program Files\Trend Micro\AMSP\debug\20011\
eagleeye_um_filename=*_EE_EagleEye*.etl
eagleeye_km_filename=*_EE_Tmee*.etl

tmproxy_bho_filepath=C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
tmproxy_bho_filename=*_TmPlugIn.log

tmpfw_filepath=C:\Program Files\Trend Micro\AMSP\debug\20003\
tmpfw_filename=*_NSC_Tmpfw.log

aegis_filepath=C:\Program Files\Trend Micro\AMSP\debug\10004\
aegis_pem_filename=Tmpem*.log

sysevt_filepath=C:\Program Files\Trend Micro\AMSP\debug\20001\
tmsysevt_filename=TmSysEvt*.log

tmsa_filepath=C:\Program Files\Trend Micro\AMSP\debug\10011\
tmsa_filename=*.log

tmlce_filepath=C:\Program Files\Trend Micro\AMSP\debug\10009\
tmlce_filename=*.log

tmles_filepath=C:\Program Files\Trend Micro\AMSP\debug\10010\
tmles_filename=*.log*

tmbep_filepath=C:\Program Files\Trend Micro\AMSP\debug\20002\
tmbep_filename=*.log*

tmbep_temp_filepath=C:\WINDOWS\TEMP\
tmbep_temp_filename=tmptmbep.log*

whitelist_filepath=C:\Program Files\Trend Micro\AMSP\debug\10015\
whitelist_filename=tmwlchk*.log

dre_filepath=C:\Program Files\Trend Micro\AMSP\debug\10012\
dre_filename=*.*

tmncie_filepath=C:\Program Files\Trend Micro\AMSP\debug\20009\
tmncie_um_filename=*_tmncieum.etl
tmncie_km_filename=*_tmnciekm.etl

cleanboot_filepath=C:\Program Files\Trend Micro\AMSP\debug\CleanBootLibrary\
cleanboot_filename=*

tmlce_rca_filepath=C:\ProgramData\Trend Micro\AMSP\report\10009\
tmlce_rca_filename=rca*.xml

dcereport_filepath=C:\Program Files\Trend Micro\AMSP\report\
dcereport_filename=*.log

tmumh_filepath=C:\Program Files\Trend Micro\AMSP\debug\20019\
tmumh_filename=TMUMHMGRDebug.log

falcon_filepath=C:\Program Files\Trend Micro\AMSP\debug\10019\
falcon_filename=*.log

trxhandler_filepath=C:\Program Files\Trend Micro\AMSP\debug\10018\
trxhandler_filename=*.log

[LOG_INFO_TYPE_REGISTRY]
registry_filepath=C:\Program Files\Trend Micro\AMSP\debug\
registry_filename=registry.txt

[LOG_INFO_TYPE_CONFIG]
config_filepath=C:\Program Files\Trend Micro\AMSP\debug\
config_filename=*.cfg

[LOG_INFO_TYPE_NETWORK_CONFIG]
ipconfig_filepath=C:\Program Files\Trend Micro\AMSP\debug\
ipconfig_filename=ipconfig.txt

[LOG_INFO_TYPE_PROCESS_SNAPSHOT]
processes_filepath=C:\Program Files\Trend Micro\AMSP\debug\
processes_filename=processlist.txt

[LOG_INFO_TYPE_SYSTEM_INFORMATION]
systeminfo_filepath=C:\Program Files\Trend Micro\AMSP\debug\
systeminfo_filename=systemInfo.txt

[LOG_INFO_TYPE_TREE_INFORMATION]
tree_filepath=C:\Program Files\Trend Micro\AMSP\debug\
tree_filename=amsp_tree.txt

[LOG_INFO_TYPE_DUMP]
dump_filepath=C:\Program Files\Trend Micro\AMSP\dump\
dump_filename=*.dmp

[LOG_INFO_TYPE_COMMON_SCAN_CACHE]
commonscancache_filepath=C:\Program Files\Trend Micro\AMSP\backup\30006\
commonscancache_filename=CommonScanCache.*

[LOG_INFO_TYPE_RTS_CACHE]
rtscache_filepath=C:\Program Files\Trend Micro\AMSP\backup\30004\
rtscache_filename=*.dat

[LOG_INFO_TYPE_UTIL_SYS_INFO_CACHE]
sysinfocache_filepath=C:\Program Files\Trend Micro\AMSP\backup\40002\
sysinfocache_filename=*.dat

[LOG_INFO_TYPE_CONFIGURATION]
configuration_filepath=C:\Program Files\Trend Micro\AMSP\backup\5\
configuration_filename=*.cfg

[LOG_INFO_TYPE_SNAPSHOT]
snapshot_folderpath=C:\Program Files\Trend Micro\AMSP\snapshot\
snapshot_foldername=*

[LOG_INFO_TYPE_DEBUG_LOG_CONFIG]
logconfig_filepath=C:\Program Files\Trend Micro\AMSP\
logconfig_filename=amsp*.ini

tomas.lindohf

90 Points

Posted 2 years ago

2 years ago

TM_Kim, Employee

1,110 Points

Hi tomas.lindohf! :)

How are you today? I hope you are doing very much fine.

Sorry to hear that you're encountering this issue.

Based from your concern, the "debug" folder of the AMSP folder of your Trend Micro program is filling up the disk space of your computer. And, you would like to know if it is safe to delete the files inside of the "debug" folder.

Actually, it is unusual that the "debug" folder is getting filled up with log files. It is safe to remove these log files, but, it would be best if we will reinstall the Trend Micro program since it appears that your Trend Micro program has an issue with its log collection. We will reinstall the program since we would like to provide a long-term solution for your concern.

To successfully reinstall your Trend Micro program, please uninstall first your Trend Micro program using the Diagnostic Toolkit. Please refer to the instructions provided on the link below.

Uninstalling Trend Micro Program using Diagnostic Toolkit

After successfully uninstalling the Trend Micro program, please proceed with the installation of your Trend Micro program. Please refer to the instructions provided on the link below.

Installing Trend Micro Maximum Security

I hope this will solve the issue.

Thank you and have a great day. :)

Trend Micro Home Users Community

(Edited)

1 person likes this

2 years ago

David Nelson

70 Points

I have the exact same issue that Tomas has, that is, AMSP debug log files just chewing up huge amounts of drive space. Perhaps its not as unusual as you say - perhaps Trend Micro could come up with a switch to turn off this runaway debug tool.

As an owner of 6 licenses, I can assure you I will be uninstalling. Whether I reinstall or install something else is up in the air right now. Fix this problem or give me to ability to turn it off. Please.

2 years ago

TM_JustineM

3,774 Points

Hello David Nelson and welcome to the community.

I hope you are doing good today.

Apologies for the late response and for the inconvenience you are experiencing.

Did you try to follow the same steps that my colleague posted on this thread? If not yet please follow the same steps for you to resolve this particular issue with the debug log file. Also there is a way for you to check if the Trend Micro program is collecting logs. You can follow these steps:

On your keyboard, press the Windows + R keys.
Type in "supporttool", then press OK. This will open the Trend Micro Diagnostic Toolkit.
Check if the Finish collecting logs is clickable, if so please click on it to stop the collection of logs.

Please let us know if the issue has been resolved, feel free to post or comment on this community.

Thank you!

Trend Micro Home Users Community

2 years ago

David Nelson

70 Points

To properly follow up, here's the results of my testing. Neither uninstalling/reinstalling worked, nor did letting the supporttool run.

One month later - after the reinstall - I had over 310GB chewed up in the AMSP/Debug folder. So I tried the supporttool option. Before I uninstalled nor now was the log collection in process - in other words, only "Begin Collecting Logs" was available. I tried anyway, to no avail.

However, I found something that might have worked. I found a batch file under C:\Windows\Program Files\Trend Micro\Titanium called "AMSPForceRemove". While it didn't run cleanly, this batch file whacked most of the AMSP folders and almost all of the 310GB in drive space was regained.

Perhaps you should check with the engineers who wrote the batch file. Might want to tidy it up, document it for customer service, and add a button so end users could use it easily.

Thanks.

2 years ago

TM_Pat, Official Rep

11,246 Points

Hello David Nelson!

Thank you for providing these updates. Apologies for whatever inconvenience this has caused you, we understand that you are a busy person.

Going back to your concern, did you remove any AMSP related folders in your computer aside from the Debug folder? If you did, we advise that you reinstall your Trend Micro Security software since it may affect the performance of the software if there are removed files. Please follow the simple steps below for you to reinstall Trend Micro Security on your computer:

Uninstall Trend Micro Security from the Diagnostic Toolkit

Once the Diagnostic Toolkit (supporttool) is open go to (C) Uninstall and then click on "1. Uninstall Software". Once the process is done, please restart your computer to apply the changes made.

Run the Remnant File Remover Tool

Click here to download the tool.

Install Trend Micro Security.

Click here to download the installer.

If you did not remove any other AMSP related folders aside from Debug, please disregard the steps above and let us proceed with the steps below. Note: Please proceed with the steps below even after reinstalling Trend Micro Security.

Check Task Manager if AMSP_LogServer.exe is running and end the process.

Check if Diagnostic Toolkit is still collecting data.

Under debug tab, click on “Finish Collecting Data”. Restart computer and check Trend Micro Diagnostic Toolkit again if it’s still collecting data.

If the issue still persists, navigate to C:\Program Files\Trend Micro\AMSP and replace the following files:

AmspConfig.ini

AmspLogFilter.ini

Please get the replacement files here.

After that, manually delete debug logs. Navigate to C:\Program Files\Trend Micro\AMSP\debug and check the logs with a numeric name, such as 10019, 20011, 20013 with large size.
And then, restart your computer to check if the issue still persists

I hope this helps! We'd love to hear from you soon!

Have a great weekend!

Trend Micro Home Users Community

(Edited)

1 person likes this

11 months ago

dnalexander

72 Points

This is still a problem for me on v12. I've changed the debug settings as other posts have suggested. At one point, the debug logs were working so fast that I had something like 50MB remaining on my drive. Rebooting would save some, and then I would watch as my computer basically self destructed, the logs quickly eating up my disc space.

I had to delete another 80GB of garbage today, which is pretty unacceptable if you ask me. I suspect this "lowkey logging" is also what seems to randomly throttle my computer, despite having very few other programs running. When checking the task manager, Trend Micro seems to briefly appear at the top of the list before suddenly releasing all of it's resources. Not sketchy at all.

(Edited)

11 months ago

TM_Pat, Official Rep

11,246 Points

Hello dnalexander,

Thank you for letting is know about this issue that you encountered and apologies for the inconvenience.

For the issue with Trend Micro Security consuming too much of your disk space, please double check if the Finish Collecting Data button on the Diagnostic Toolkit is already grayed out.

And for the other issue wherein Trend Micro Security consumes too much of your computer's CPU usage, can you verify if Trend Micro Security is the only security software that you installed on your computer? If there is another security software, please remove it immediately.

Last resort is to reinstall the Trend Micro Security software on your computer. please follow the instructions below:

Uninstall Trend Micro Security from the Diagnostic Toolkit

Once the Diagnostic Toolkit (supporttool) is open go to (C) Uninstall and then click on "1. Uninstall Software". Once the process is done, please restart your computer to apply the changes made.

Run the Remnant File Remover Tool

Click here to download the tool.

Install Trend Micro Security.

Click here to download the installer.

Should you have any other concern or question, please let us know.

Regards,
Pat

1 person likes this

11 months ago

dnalexander

72 Points

The "Finish Collecting Data" button is never enabled, it is always grayed out. There is no other security software installed on this machine.

I deleted another 30GB of logs from Trend Micro/AMSP/debug today.

11 months ago

Tom Emmelot, Champion

27,258 Points

Hi dnalexander

did you follow the reinstall Pat was giving you???

Try that and give us your answer after that.

Kind regards,
Tom

1 person likes this

This conversation is no longer open for comments or replies.

Trend Micro Maximum Security 11.1 filling up disk space

Related Categories

PC Security