Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TouchOdeath

  • Rank
  1. Immunet should update itself automatically in the background without needing user input. Users in general don't care about the health of their PCs or the 'security' of their PCs. Their jobs are not the PCs, PCs are only apart of their job. Most users see the 'you should update immunet' warning, or other software, and just ignore it. Why do they ignore it? Because it take time to update stuff and they don't care if its updated because it isn't broken. Immunet should update in the background and not show the user anything. The only time you would need to show the user anything is if in the update you added some crap like 'oh... btw we updated your immunet and in this update we are going to collect some new information from you in this update is that ok?'. Other than that I can't see any other reason to prompt the user. This change would have prevented the 'no disk space' plague, because I know immunet had a newer version before this bug triggered.
  2. I tested Keyscrambler 3.10 with a keylogger. Keyscrambler didn't work in that instance. I know ritchie has suggested this, which to me, means alot. I appreciate your suggestions ritchie!
  3. Hey EugeneC, I just emailed you another instance on a different computer. I copied quite a few log files, however not all of them. In the screenshots I sent, notice how big the vertical scroll bar is. Also, take note of the start and end date of the logs. I appreciate both of you Ritchie and EugeneC. On this computer, when I logged onto it, sfc.exe was pegged at 50% cpu.
  4. Email sent... So heres the deal Ritchie. The log files on these computers were taking up any remaining space the disk had. I had to free up 'some' space in order to run your tool. However, I couldn't let your tool finish because I didn't have enough disk space to let your tool do its thing, so I closed the window early. Unfortunately doing that made a corrupt .7z file, which I'm just now realizing. So... good luck on retrieving the log files..... :/. If I would have known that closing the window early would have resulted in a corrupt .7z, I would have made my own .7z. So big apologies for not testing the .7z at the time. Heres an example of what the disk would look like: 1tb HD: 100gb = real data 900gb = log files 0bytes = free space In the example above, you could only free up space from only the 100gb section. 7z does compress the 900gb to be a smaller size of course, but not enough. So basically its impossible for your tool to finish. Unless of course you were to change the desktop environmental variable to a seperate harddrive temporarily. Another bit of information: When I logged onto each computer, sfc.exe would be pegged at 25% cpu usage. Since I didn't have physical access to these computers, my biggest concern was restoring these PCs to working order while I had the chance, so that was my main priority. Also, for whatever reason, everytime I tried to uninstall Immunet, I got an NSIS error, or some error that wouldn't allow me to uninstall. So I had to copy the original install file to the PC and perform an install so I could uninstall. Thats around 16mb of data. If you were to delete all the temp files off the PC, and say sfc.exe filled said space back up so you had 0 bytes again, you would either A: find something else worthless to delete or B: delete real data. B of course wasn't an acceptable option for me.
  5. See this post: http://support.immunet.com/index.php?/topic/3100-immunet-taking-100-disk-space/ Let me know if that helps.
  6. Dear ritchie58, I came across two different PCs that had the exact same problem, and they occured on the exact same day (today). Whether that was coincidence or not, not sure. Problem: ======= 100% disk space on Drive C:\ (windows install drive). It would say 0 bytes free. Cause: ====== C:\Program Files\Immunet\clamav\clamav.log-20151023_204525 there were several files with a similiar name as this above. Each file was 102kb in size, and there were several of them. These files were taking up ALL of the remainder disk space on clients PC. Solution: ======= Close sfc.exe to prevent anymore logs being written to disk to prevent any further space from being taken up. Uninstall immunet, because it won't let you delete the log files. If you encounter an error uninstalling, on one of the two computers I did. If in that event, you need to remove the registry key "Immunet 3" which will be in one of these locations: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Immunet Protect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Immunet Protect HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Immunet Protect Then re-run the original installer, and make sure you install in the same directory. After Install, you should beable to uninstall. I hope this helps someone. ritchie58, I appreciate all your help on these forums and your deep insights.
  7. I sent that email upon creating this thread using the same subject line using this guide: http://forum.immunet.com/index.php?/topic/909-how-to-post-an-effective-bug-report/ I'll await the email! Thanks again ritchie! Edit: Just now seeing this, my appologies. I guess I can try to figure out which domain that its trying to access and make sure that I can ping them..
  8. ritchie, I tried your first paragraph, and just to make sure that I did, I went ahead and reinstalled again. and same result, same error in log file (I actually tried this more than once). I see what your talking about on the scheduled task, however I can't figure out the magic numbers to create a Scheduled Task of my own. If I could create my own Scheduled Task, that would solve the problem. Either way thank you for your response. Edit: I noticed on the bottom left of the immunet gui it said 'Installed antivirus' 'Microsoft Security Essentials'. When I first initially got on the clients computer, he had mentioned he tried to manually uninstall Microsoft security essentials... when I got on there I removed security essentials through add/remove and installed immunet. So I installed Security essentials so I could uninstall it again (so it would recreate the correct entries so I could properly remove). After that I ran Microsofts 'Fix it' to make sure its removed https://support.microsoft.com/en-us/kb/2435760. Uninstalled immunet, rebooted installed immunet, same result. Also I see you mentioned about how the internet needs to be uninterrupted through the install process, I remote onto his computer, while I don't have any facts to support my claim, I am 99% sure that his internet didn't hiccup during the process.
  9. I was trying to "Add New Scheduled Scan", I entered every 'day', 7:00 PM, Full Scan. I hit 'create', and the Scheduled Scan info screen came up, leaving things as default, I hit 'OK' at that instance it errors saying 'An unknown error has occured.' sfc.log gives me a detailed error which is in the subject line. Immunet version: OS: win7 x64 ServicePack 1 Language english There are no other virus scanning software installed, or internet security bull. The computer I was on I was instructed not to clean it or tweak it. So whatever viruses/malware/worthless programs that were there, are there. I also never performed a full scan. In summary Local.xml didn't get changed. On another note, im suprised to see such amazing piece of software produce a bug. But then again you are running on a windows operating system .
  • Create New...