Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
In past have found things that can't be deleted have ownership set to some process, with legit stuff it's usually trustedinstaller. If log in as admin should be able to change that through file properties. Forget details but just fanny about, it's there somewhere.
Try booting from CD base Linux distro (e.g. Pated Magic); <hold-nose-mode>mount MS partition</hold-nose-mode> and have a play; I quite like the look of this command:
rm -rf
surely thats rm -rf /
Either way only if that dll is the root cause of the problem deleting it will solve the problem. If the real file is elsewhere it will simply reappear under another name.
Sadly the only way to really be sure of solving a trojan attack is to wipe the system and start again. Backup every file you need and proper to spend ages installing everything.
If your helldesk are not too useless they will probably have a base image that contains most of the programs you need.
Try booting from CD base Linux distro (e.g. Pated Magic); <hold-nose-mode>mount MS partition</hold-nose-mode> and have a play; I quite like the look of this command:
I'd also recommend trying something other than AVG to check your system is clean after managing to delete the dodgy dll. It could be that the real nasty on your system just keeps recreating the dll.
For free tools I ditched AVG some time ago in favour of Microsoft's Security Essentials. It seems to catch most problems before they have chance to get a hold of the system, when doing real time protection. Its library also usually gets updated several times per week as Windows Update is always pestering me to do an update for it.
Putting the drive as a slave in another PC may work, if the file is being locked during boot up.
I remember having to sort something like this out some years ago. I think the solution I found was to use a utility that does a 'move on boot' so the file is not locked and can be deleted after startup.
Leave a comment: