Forum Discussion

jeffrey_katz's avatar
jeffrey_katz
Active Contributor
4 months ago

logmein creating "waapi" folders

the last few months we've found hundreds of folders in C:\Windows\Temp named "waapi-<10 digits>". Each folder contains one file called ".sig" and one or more files named "<24 hex digits>". The folders are created about 15 minutes apart. Adds up to about 20GB per month.

No problem deleting these files as they accumulate, but we want to know where they come from. ProcMon shows they are being created by LogMeIn

Googling finds some similar reports, including this discussion

Folder Waapi-xxxxxx | GoTo Community - 324046

but nothing to explain where the come from or what do about it, other than delete them.

Any ideas?

 

13 Replies

Show More
  • jeffrey_katz's avatar
    jeffrey_katz
    Active Contributor
    4 months ago

    Hi Glenn - 74 folders created 8/21, 53 folders created 8/22 as of 4:43pm. Punctual also - 13, 29 and 43 minutes past the hour every hour. I left the monitor running to check for any activity at the top of the hour, but none seen.

     

     

  • jeffrey_katz's avatar
    jeffrey_katz
    Active Contributor
    4 months ago

    Hi Glenn - we purged them today, but there were about 2000 of them going back to 7/15 (when we last looked and purged). Here's the current status

    very punctual - created around quarter past, half past, and quarter to the hour, but not on the hour. The ones at quarter past and quarter to have two files, the ones at half past have a third file that is substantially larger

     

     

    The large file has a header that reads "SQLite format 3". The smaller file just has a string that corresponds to the name of the folder (in this case "1755721744"). The .sig file is a mix of characters, nothing legible.

     

     

  • GlennD's avatar
    GlennD
    GoTo Manager
    4 months ago

    Hi jeffrey_katz,

     

    They are type of temporary file that is created during a process and they should self delete. The Resolve customer who posted a similar question reported back that the issue resolved itself. I've reached out to the team to find out which process is creating them, how many are you seeing that are older than 24 hours?