Anti-Virus Comparative File Detection Test 2013

http://www.av-comparatives.org/wp-content/uploads/2013/03/avc_fdt_201303_en.pdf

Anti-Virus Comparative - File Detection Test - March 2013 www.av-comparatives.org 

AV Comparatives e.V. is a registered Austrian Non-Profit-Organization

The Malware sets have been frozen the 22nd February 2013 and consisted of 136610 sample variants.The products were updated on the 28th February 2013 and tested under Microsoft Windows 7 64-Bit. 

 

1 We additionally tested also Windows Defender included in Windows 8 (we observed the same results as

achieved by Security Essentials under Windows 7).

2 We added Symantec Norton in this test, even if they did not apply for being included into our test-series, as the results have been highly demanded by our readers and the press.

3 Information about used additional third-party engines/signatures inside the products:

BullGuard, Emsisoft, eScan and F-Secure are based on the Bitdefender engine. 

The tested version of GDATA (2013) was based on the Avast and Bitdefender engines. 

G DATA 2014 is based on the Bitdefender engine; the results in this report of G DATA 2013 are not applicable to G DATA 2014

Funny big head characters

http://10steps.sg/tutorials/photoshop/creating-funny-big-head-characters-in-photoshop/

EaseUS Partition Recovery

http://www.easeus.com/partition-recovery/

Why to choose EaseUS Partition Recovery?

EaseUS Partition Recovery, a free and easy-to-use partition recovery software to recover deleted or lost partition, takes up one of the best partition recovery software for you to keep owing to the following features:

• Free for both home and commercial users.
• Use it with ease: a wizard interface walks you through all the partition recovery process.
• Recover deleted or lost partition quickly and easily.
• Offer several optional scan areas helps locate the lost partition quickly.
• Support FAT, NTFS, Ext2/Ext3 file system.
• Support IDE / ATA / SATA / SCSI drives.
• Bootable disk based on WinPE
• Support Windows 2000, XP, 2003, Vista, 2008, 7

Partition Loss Scenarios

• Inadvertently deleted partitions (using fdisk or other programs)
• Accidently lost partitions (for example due to virus attack)
• ALLTHEPROFIL9SW-3YE3M-LSMR8-PCDHB-L7FDLALLTHEPROF

Partition Recovery Tutorial

• How to recover lost partitions with EaseUS Partition Recovery?
• How to recover deleted or lost NTFS partition?
• How to recover deleted or lost FAT partition?
• How to recover deleted or lost EXT2/EXT3 partition?

Winload.exe is missing or corrupt

http://technet.microsoft.com/en-us/library/cc709667%28v=ws.10%29.aspx
Winload.exe is missing or corrupt - Recover DVD does not boot - Problem SOLVED!
How to use BCDEDIT in case of emergency:

After a power failure the Master Boot Record (MBR) got destroyed on my harddisk.
My entire harddisk appeared to be an unpartitioned area.
All partitions were gone!
***** Shock! *****
***** Panic! *****
As software developer I have a multi-boot system with several operating systems and a huge data partition.
I was not willing to install all this anew.
1.)
So I searched for a tool that may recover the MBR.
And I found "EaseUs Partition Recovery".
http://www.softpedia.com/get/System/Back-Up-and-Recovery/EASEUS-Partition-Recovery.shtml
I put the corrupted disk into another computer.
This program scanned my disk and found all partitions within one minute.
It allowed me to enable the partitions and I saw that all data was still there.
And the best of all: This program did that great work for free!
2.)
After reinstalling the Boot Manager I noticed that the Windows XP partitions were still running fine while Windows Vista did not boot any more with a blackscreen:
#################################################

Windows failed to start. A recent hardware or software change might be the cause.
File: \Windows\System32\winload.exe
Status: 0xc000000e
Info: The selected entry could not be loaded because the application is missing or corrupt.
################################################

This error message is (as I'am sure now) a complete nonsense.
As usual in Microsoft products the error messages are wrong or at least misleading.
The file Winload.exe is neither missing nor corrupt!
People report in serveral blogs to get the same error after resizing the Windows partition with any third party tools that are not certified for Vista like old versions of Partition Magic, Acronis or Linux tools.
3.)
I read that many people in this case successfully booted with the Windows Vista DVD and went to the "Repair" option to repair Windows Vista.
But in my case this did not work.
This stupid DVD did not boot.
In the middle of the boot process it was hanging without any error message.
No chance at all.
It's from Microsoft, so we cannot expect too much.
Other people used
Bootrec /RebuildBCD
or
Bootrec /FixBoot
or
BcdEdit /xyz...
from the rescue console in the Vista boot DVD.
In my case: No hope because Microsoft does not offer any usefull Recover Console.
Searching for hours in blogs I found 99% bullshit. No solutions or misleading nonsense.
Only people reporting the same problem who at the end installed their Windows anew.
Many people don't understand what a restore point is.
It is COMPLETELY useless to have any restore point for this kind of problem.
One of the few interesting comments, that I found was this:
_________________
First,
most rescue disk and other programs will not boot correctly if you have more than 2 active partitions on the harddrive, have more than 4 partitions including and extended partition with several partitions in it.
Second,
Vista uses a different bootloader and thus creates a 'custom' mbr, which if modified by any standard mbr tool will cause vista not to boot. Also because of this some other CD's will not boot if they check the mbr.
Third,
as of yet there are no tools that will allow you to resize or check the NTFS drive of a vista machine. If any program other than vista checks or makes any changes (including XP rescue console) to the drive such as chkdsk this may hang vista.
Fourth,
many computers now include a recover partition most of the time this should be hidden, but sometimes may become active and cause problems booting.
So these things make it more difficult to work with. I would recommend you check out the articles on dual boot with vista, as these help you understand where your system is probably hanging at.
__________________
4.)
After googling for hours I could not find any solution.
So I investigated on my own.
Like a cracker using SysInternals Process Monitor I invesigated about what BcdEdit is doing on the harddisk.
**** And I found a solution which I will describe here: ****
I hope to receive some dollars from Microsoft giving support for their badly programmed products.
Microsoft pays 8,5 Billions dollars to buy Skype but they don't pay one dollar to give support to the millions that suffer from a blackscreen.
Why are there no Microsoft employees responding in social.technet.microsoft.com ?

The internet is full of people reporting this Winload.exe problem and no solution except the Windows Install DVD that does not work (at least in my case).
#################################
Here comes the solution that I found on my own:
5.)
Put the harddisk with the corrupt Vista into another computer that is running Windows (in my case Windows XP).
6.)
Mount the defective Vista partition on a drive (in my case F:\)
7.)
On the Vista partition the file F:\Boot\BCD is the one that needs to be repaired.
You can make a backup of this file now, but why should you backup a corrupt file ?
This file has no extension, the name is simply "BCD".
This file is a database that stores the information how to boot Windows and replaces the former Boot.ini.
This file is hidden. If you don't see it use a real file manager like TotalComander because Windows Exporer really sucks.
8.)
Open a command prompt (Cmd.exe)
9.)
Enter
F:\Windows\System32\bcdedit /store F:\Boot\BCD /enum
NOTE:
The parameter /store will access F:\Boot\BCD, otherwise it would access C:\Boot\BCD which does not exist on Windows XP!
What I saw was this:
Windows Boot Manager
--------------------
identifier {bootmgr}
device unknown
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {1f20452f-f2af-11db-9299-adf714858873}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device unknown
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice unknown
systemroot \Windows
resumeobject {1f20452f-f2af-11db-9299-adf714858873}
nx OptIn
This is the content of a corrupt BCD file.
I have no idea what destroyed this file in my case.
But you see that there are three lines with "unknown".
This is the cause why Vista does not boot anymore.
The Windload.exe is NOT corrupt or missing.
The corrupt file is the BCD file, but the programmers at Microsoft are not able to show helpfull error messages.
10.)
Now enter the following 3 commands:
F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {bootmgr} device boot
The operation completed successfully.
F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {default} device boot
The operation completed successfully.
F:\Windows\System32\bcdedit /store F:\Boot\BCD /set {default} osdevice boot
The operation completed successfully.
11.)
To check the result enter again:
F:\Windows\System32\bcdedit /store F:\Boot\BCD /enum
Now it should look like this:
Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {1f20452f-f2af-11db-9299-adf714858873}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device boot
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice boot
systemroot \Windows
resumeobject {1f20452f-f2af-11db-9299-adf714858873}
nx OptIn
You see that instead of "unknown" there is a "boot" now three times.
12.)
Now BcdEdit has fixed the BCD file and you are ready.
Yeahh!
13.)
This procedure should be added to the MSDN for all those who cannot boot with the misdesigned Boot DVD.
I don't know if this procedure also works for Windows 7.
But I think so, try it, it should work!
14.)
If you don't have a backup of your partitions I URGENTLY recommend that you install "Partition Backup" from Paragon Software.
http://www.paragon-software.com/home/br-free/index.html
It is extremely easy to use and can create an image of entire partitions that you must OBVIOUSLY store on ANOTHER harddisk (e.g. an external USB disk or burn them on a Blue Ray).
It also makes a backup of the Master Boot Record.
"Partition Backup" is better than alternatives like CloneZilla, which is very awkward to use and only has a simple text user interface.
And in comparison with the competition from Acronis it is for free!
With the backups of your partitions and the Paragon Rescue DVD you will never again have to care about any Windows that does not boot.
You simply play back the image.
P.S.
If you are interested in more technical details about BCD and the Vista boot process, read this excellent article:
http://www.multibooters.co.uk/bootmgr.html
Elmü

ElmueSoft

ntldr is missing error

http://pcsupport.about.com/od/findbyerrormessage/a/ntldrmissingxp.htm

1. Restart the PC. The NTLDR error could be a fluke.
   
2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.
   Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
   
3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.
   
   Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
   
4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick:
   Enter Windows XP Recovery Console.
   When you reach the command prompt (detailed in Step 6 in the link above), type the following two commands, pressing Enter after each one:
copy d:\i386\ntldr c:\

   copy d:\i386\ntdetect.com c:\
   

   In the command listed above, d represents the drive letter assigned to the optical drive that your Windows XP CD is currently in. While this is most often d, your system could assign a different letter. Also, c:\ represents the root folder of the partition that Windows XP is currently installed on. Again, this is most often the case but your system could be different.
   If you're prompted to overwrite either of the two files, press Y.
   Take out the Windows XP CD, type exit and then press Enter to restart your PC.
   Assuming that missing or corrupt versions of the NTLDR and/or Ntdetect.com files were your only issues, Windows XP should now start normally.
   
5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation:
   Enter Windows XP Recovery Console. The Recovery Console is an advanced diagnostic mode of Windows XP with special tools that will allow you to restore the boot.ini file.
   When you reach the command line (detailed in Step 6 in the link above), type the following command and then press Enter.
   bootcfg /rebuild
   The bootcfg utility will scan your hard drives for any Windows XP installations and then display the results. Follow the remaining steps to add your Windows XP installation to the boot.ini file.
   The first prompt asks Add installation to boot list? (Yes/No/All).
   Type Y in response to this question and press Enter.
   The next prompt asks you to Enter Load Identifier:.
   This is the name of the operating system. For example, type Windows XP Professional or Windows XP Home Edition and press Enter.
   The final prompt asks you to Enter OS Load options:.
   Type /Fastdetect here and press Enter.
   Take out the Windows XP CD, type exit and then press Enter to restart your PC.
   Assuming that a missing or corrupt boot.ini file was your only issue, Windows XP should now start normally.
   http://www.wikihow.com/Fix-Boot.Ini
   http://www.fermu.com/es/252
   
6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.
   
7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
   
8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.
   
   Try replacing the IDE cable cable if you suspect it might be faulty.
   
9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
   
10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
    
11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
    
    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
    
12. Replace the hard drive and then perform a new installation of Windows XP. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

NTLDR Errors Apply To

This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.
Windows 8, Windows 7, and Windows Vista utilize BOOTMGR, not NTLDR.

Still Having NTLDR Issues?

See Get More Help for information about contacting me on social networks or via email, posting on tech support forums, and more. Be sure to let me know what steps, if any, you've already taken to fix the "NTLDR is missing" issue.

Other Errors That Appear During the Boot Process

• "Missing or Corrupt Hal.dll"

stop error 0xC000000E after resuming of hibernation

Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:
1. Insert your windows installation disc and restart your computer.
2. Choose your langugae settings, and then click next
3. Click "repair your computer."
Info: The boot selection failed because a required device is inaccessible
http://www.sevenforums.com/general-discussion/100857-boot-selection-failed-because-required-device-inaccessible.html
Computer after hibernation or stand by status becomes that error.
================
http://www.petri.co.il/forums/showthread.php?t=42099
you can try download EasyBCD (OR run probably bcdedit command from recovery dvd_win7_disk)
This program will boot your machine.
Then look at your item which boot Win!
My item had a record with *unknown* device or similar *Deleted partition* drive.
I suppose correctly there must be something like C:\.
So instead of delete that item I prefer added next and selected right drive for it.
It can be one of C:\,D:\,E:\,... with your Windows directory (where you have installed it).
More interesting is that it didnt have to be equal letter as it appears after boot in different computer, different hdd order...
-------------------------
Solution for 0xc000000e problem!!!
1. First Load Windows RE from Windows 7 or Server 2008 R2
2. Open Diskpart and make problematic partition Active
3. Open bcdedit and you should get something like this:
Windows Boot Loader
-------------------
identifier {default}
device unknown <===0xc000000e problem!
path \Windows\system32\winload.exe
description Windows Server 2008 R2
locale en-US
inherit {bootloadersettings}
recoverysequence {e0025536-b36d-11de-aadd-ddc0b5870e2c}
recoveryenabled Yes
osdevice unknown <===0xc000000e problem!
systemroot \Windows
resumeobject {e0025534-b36d-11de-aadd-ddc0b5870e2c}
nx OptOut
hypervisorlaunchtype Auto
4. Enter these commands:
bcdedit /set {Your-OS-Identifier} device partition=X:
bcdedit /set {Your-OS-Identifier} osdevice partition=X:
bcdedit Where X: - drive letter with your problematic OS in Windows RE. You can find it by opening notepad and pressing save
5. Reboot
This problem I always getting after clone smaller drive to bigger with Acronis 2010.

--------------------------
Another way to fix it
Set up a new Windows 7 on a extra disc, copy out the BOOT directory from the SYSTEM DRIVE which actually has no DRIVE LETTER .
Then slave the Original HARDDRIVE which has the Error to another computer and Overwrite all the files in \Boot of the 200MB partition which is actually hidden by the OS and also has NO DRIVELETTER.
Use the diskmanager of Windows 7 from the new install to add a driveletter to the 200MB parition on the drive with the ERROR. The new install you dont need to activate or anything like that because we just use it as a toolt to repair the Original Install.
When finish don't forget to remove the Driveletter.
Return the Repaired HARDDRIVE/OS to it's Computer housing and then start the Computer using the Windows 7 Original DVD.
Input location and language and on the next part select REPAIR COMPUTER.
IT may take a few minutes (on my system it took about 1.5 minutes) and then it will tell you that it has a option to repair the OS
GO for it and click on Repair & restart and everything is as it has been.
BTW it isn't actually ACRONIS which causes the problems, it's more likely when a USB scanner or Extern Harddrive hasen't been removed correctly. I use about ten computers running win7 and even with Acronis which actually will not run on Win7 without applying a littel Tweak, it never has happen that it crashes on any Machine.
Before it has happen I used a SCANNER and I removed it without to disconnect the proper way. Ater this I got that error.
--------------------------
solution: (i can t explain why at the moment but it does fix my immediate problem!)
. go to CMOS, change the SATA Emulation opt from AHCI to IDE mode
. reboot PC
problem fixed!
--------------------------
Tutorial to to edit BCD code with bcdedit (which manage to solve my similar problem)
this is the picture of my bcdedit before repair
w.flickr.com/photos/58829069@N07/5876679214
***actually all partition=D show unknown
and this is after repair
w.flickr.com/photos/58829069@N07/5876118801
what i did was
1. bcdedit /set {bootmgr} device partition=E:
2. bcdedit /set {default} device partition=E:
3. bcdedit /set {default} osdevice partition=E:
*you may have to change {default} to {current} depending on what your computer show at identifier
*you may have to change E: to your respective partition by regedit>import browse My Computer. Notice your primary partition which usually C: but in recovery environment is difference, mine is E:.
By the way i got this problem after I
1. delete Ubuntu volume in windows.
2. bootrec/fixboot and bootrec/fixmbr in the Windows Recovery(already installed)
So, I install back Ubuntu and Grub. Hope problem solved but fail.
I tried to install EASY BCDEDIT but got cancelled.
--------------------------
Another solution
1.Insert the installation disc.
2. Restart your computer.
3.Click the Start button , click the arrow next to the Lock button , and then click Restart.
If prompted, press any key to start Windows from the installation disc.
NoteIf your computer is not configured to start from a CD or DVD, check the information that came with your computer. You may need to change your computer's BIOS settings.
4. Choose your language settings, and then click Next.
5. Click Repair your computer.
6. Select the operating system you want to repair, and then click Next.
7. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repair
================
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/0xc000000e-boot-error/ef08ab00-e130-4301-bc80-79d5b414a81f
================
www.sevenforums.com/bsod-help-support/91753-disk-error-press-any-key-restart-no-system-partition.html
Perhaps the HD ist malfunctioning... check power supply,  SATA cable connection, change to cable with snap-in contacts.
Check your HD
Disk Check
Check with a hard drive diagnostic tools.
Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.
You may need to replace your HD.
Clean Install Windows 7
http://www.tacktech.com/display.cfm?ttid=287
Diagnostic software and utilities from the manufacturer of your hard drive(s).
Hitachi [IBM]
Seagate [ Samsung,  Maxtor [Quantum],  Conner ]
Toshiba [Fujitsu]
Western Digital
----------------------

January 2003 - IBM and Hitachi's storage divisions merged to establish Hitachi Global Storage Technologies (Hitachi GST).
Drive Fitness Test
This download creates a self-booting DOS diskette to run the DFT utility. The Drive Fitness Test (DFT) provides a quick, reliable method to test SCSI and IDE hard disk drives, including Serial-ATA IDE drives. The Drive Fitness Test analyze function performs read tests without overwriting customer data. (However, Drive Fitness Test is bundled with some restoration utilities that will overwrite data.)
Note: Currently, the Drive Fitness Test does not support Microdrives, Travelstar 8E, Travelstar 10E, or Travelstar C4K Series hard drives.
- Download Drive Fitness Test Windows Diskette Creator v4.16 b00 (10.07.2009) (Direct Link)
- Download Drive Fitness Test v4.16 b00 (10.07.2009) - Diskette Image (Direct Link)
- Download Drive Fitness Test v4.16 b00 (10.07.2009) - CD Image (Direct Link)
- View Additional Information
OGT Diagnostic Tool v9.0 (11.25.2004)
The OGT diagnostic tool is a failure analysis tool for Ultrastar 10K300, Ultrastar 15K73, and DK32XX products.
Consumers and end users should use this tool instead of DFT for Ultrastar 10K300, Ultrastar 15K73, and DK32XX drives only.
Performs diagnostic testing and failure analysis.
Windows version only.
The OGT will perform necessary tests to the drives and can perform failure analysis automatically.
- Download OGT Diagnostic Tool (Direct Link)
- View Additional Information

------------------------------
Maxtor PowerMax v4.23 (07.27.2006)
The PowerMax utility is designed to perform diagnostic read/write verifications on Maxtor and Quantum hard drives. These tests will determine hard drive integrity. The PowerMax utility is effective on all ATA (IDE) hard drives with a capacity greater than or equal to 500 MB. Maxtor recommends the use of this utility for troubleshooting potential hard drive problems.
- Download PowerMax (English | TACKtech Mirror Direct Link | 1.03 MB)
- Download PowerMax (Brazilian Portuguese | Direct Link | 1.03 MB)
- Download PowerMax (Spanish | Direct Link | 1.03 MB)
- View Additional Information
Maxtor PowerMax 4.23 Bootable CD .ISO image file (08.02.2006)
The POWERMAX utility is designed to perform diagnostic read/write verifications on Maxtor/Quantum hard drives. These tests will determine hard drive integrity. The POWERMAX utility is effective on all ATA (IDE) hard drives with a capacity greater than or equal to 500 MB. Maxtor recommends the use of this utility for troubleshooting potential hard drive problems.
- Download PowerMax (English | TACKtech Mirror Direct Link | 1.78 MB)
- View Additional Information
Maxtor MaxBlast 5.0 (04.23.2007)
Maxtor MaxBlast makes it easy to work with your new Maxtor disc drives. MaxBlast lets you quickly install your new disc drive, with wizards that guide you through the processes of creating and formatting partitions on your disc drive.
MaxBlast also lets you transfer your data to your new Maxtor disc drive in minutes. The software migrates everything – your operating systems, applications, documents and personal setting – to your new disc drives just as you had them. After you migrate, you can keep using your PC just like before. You can then keep your old drive as a backup or use MaxBlast to store your image backups.
- Download Maxtor MaxBlast (Direct Link)
- View Additional Information
Maxtor/Quantum SCSIMax v1.21 (05.14.2003)
SCSIMax is a diagnostic utility for all Maxtor/Quantum® SCSI hard disk drives supporting Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T). This test will determine hard drive integrity in a short period of time, with a high degree of confidence. If the program completes without error, the problem remains elsewhere in your system. Check SCSI cables, termination and operating system. Maxtor recommends you use this utility for troubleshooting potential hard drive problems. These problems include, but are not limited to: potential hard drive surface media problems (e.g., bad clusters or sectors, partitioning/formatting problems, etc.) and drive recognition problems (e.g. hard drive that is not recognized by the operating system). SCSIMax uses the SCSI controller's ASPI driver to route Int13 commands to the hard drive. The utility is not data destructive, but Maxtor recommends that you complete a full backup of your hard drive before running this utility. Note: Incompatible with Apple® systems, and SCSI Ultra320 controllers. This utility does not run from the Windows desktop.
Note: Incompatible with Apple® systems, and SCSI Ultra320 controllers. This utility does not run from the Windows desktop.
- Download SCSIMax (Direct Link | 70KB)
- View Additional Information
-------------------------------
Samsung Drive Manager 1.0.147 (10.28.2011)
Samsung Drive Manager is a bundled software for Samsung external drives. It comprises:
Samsung AutoBackup
Samsung SecretZone
Samsung Secure Manager - a secure external hard drive management solution
Samsung external drive management tools Note: Samsung Secure Manager cannot be used if your hard drive does not support the security function.
- Download Drive Manager (Direct Link)
- View Additional Information
Samsung Disk Manager 10.42 (12.30.2003)
Some old BIOSs have a capacity barrier and does not recognize the high capacity HDD. In that case, the Disk Manager will solve the capacity barrier.
- Download Disk Manager for FDD (Direct Link)
- Download Disk Manager for CD-ROM (Direct Link)
- View Additional Information
ES-Tool (The Drive Diagnostic Utility) v2.12a (03.12.2009)
ES Tool (The Drive Diagnostic Utility) is made with the aim of testing a Samsung hard disk drive while it is installed inside a PC, regardless of the status of user's operating system. In fact of the drives returned to Samsung, a large percentage are NTF("No Trouble Found") after testing. So it is strongly recommended to test the drive if it is truly defective by a few fundamental troubleshooting of ES Tool first, to avoid user's unnecessary effort and inconvenience of replacing a good drive.
- Download ES-Tool for FDD (Direct Link)
- Download ES-Tool Bootable CD ISO (Direct Link)
- View Additional Information
--------------------------------
Western Digital Corporation Western Digital
--------------------------------
Fujitsu
--------------------------------
Samsung
Samsung Drive Manager 1.0.147 (10.28.2011)
Samsung Drive Manager is a bundled software for Samsung external drives. It comprises:
Samsung AutoBackup
Samsung SecretZone
Samsung Secure Manager - a secure external hard drive management solution
Samsung external drive management tools Note: Samsung Secure Manager cannot be used if your hard drive does not support the security function.
- Download Drive Manager (Direct Link)
- View Additional Information
Samsung Disk Manager 10.42 (12.30.2003)
Some old BIOSs have a capacity barrier and does not recognize the high capacity HDD. In that case, the Disk Manager will solve the capacity barrier.
- Download Disk Manager for FDD (Direct Link)
- Download Disk Manager for CD-ROM (Direct Link)
- View Additional Information
ES-Tool (The Drive Diagnostic Utility) v2.12a (03.12.2009)
ES Tool (The Drive Diagnostic Utility) is made with the aim of testing a Samsung hard disk drive while it is installed inside a PC, regardless of the status of user's operating system. In fact of the drives returned to Samsung, a large percentage are NTF("No Trouble Found") after testing. So it is strongly recommended to test the drive if it is truly defective by a few fundamental troubleshooting of ES Tool first, to avoid user's unnecessary effort and inconvenience of replacing a good drive.
- Download ES-Tool for FDD (Direct Link)
- Download ES-Tool Bootable CD ISO (Direct Link)
- View Additional Information
HUTIL (Diagnostic Utility for New Drives) v2.10 (10.08.2007)
Hutil (The Drive Diagnostic Utility) is made with the aim of testing a Samsung hard disk drive while it is installed inside a PC, regardless of the status of user’s operating system. In fact of the drives returned to Samsung, a large percentage are NTF(“No Trouble Found”) after testing. So it is strongly recommended to test the drive if it is truly defective by a few fundamental troubleshooting of Hutil first, to avoid user’s unnecessary effort and inconvenience of replacing a good drive.
- Download HUTIL for FDD (Direct Link)
- Download HUTIL Bootable CD ISO (Direct Link)
- View Additional Information
============================== 
Thanks, Shawn!!
How to Repair Windows 7 System Files with System File Checker 

A) To Run the SFC /SCANNOW Command at Boot

1. For how, see METHOD TWO at this link: SFC /SCANNOW : Run in Command Prompt at Boot

B) To Run the SFC /SCANNOW Command in Windows 7

1. Open an "elevated command prompt" (right click -> Run as administrator), and do step 2 or 3 below for what type of scan you would like to run.
2. To Scan and Repair System Files
NOTE: Scans the integrity of all protected system files and repairs the system files if needed. Please see red WARNING box at the top of this tutorial.

A) In the elevated command prompt, type sfc /scannow and press Enter. (see screenshot below)
NOTE: This may take a little bit to finish.

B) Go to step 4.

3. To Only Verify if the System Files are Corrupted
NOTE: Scans and only verifies the integrity of all proteced system files only. This command will not change your system files as in the red WARNING box at the top of this tutorial.

A) In the elevated command prompt, type sfc /verifyonly and press Enter.

4. When the scan is complete, hopefully you will see all is ok like the screenshot below.

   Note

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
• If not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix.

5. When done, close the elevated command prompt.

C) How to See and Read Only the "SFC" Scan Results from the CBS.LOG
NOTE: When SFC runs, it logs it's actions into the C:\Windows\Logs\CBS\CBS.log. The steps in this option will show you how to see only the specific SFC entries with the [SR] tags in this CBS.log. This can be helpful to show you what files SFC could not fix automatically if you wanted to try and manually replace them.

1. Open an "elevated command prompt" (right click -> Run as administrator).
2. In the elevated command prompt, copy and paste the command below, and press Enter. (See screenshot below)
NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it.

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

3. Close the elevated command prompt.
4. Open the sfcdetails.txt file on your desktop to see the SFC scan details in the CBS.LOG.
5. You can safely delete the sfcdetails.txt file afterwards if you like.

   Tip

If you need to replace a corrupted system file that SFC cannot fix, then this will show you how to by extracting a new copy directly from your Windows 7 installation DVD.
Extract Files from Windows 7 Installation DVD

chkdsk switches

To Run Chkdsk from Command Prompt
NOTE: The chkdsk command can be used on a FAT32 or NTFS formatted disk.1. Open a elevated command prompt or a command prompt at startup.

2. In the command prompt, type in the following command below followed by one or more switches that you would like to use below with a space between each switch and press Enter.
NOTE: For example, the most common command to run chkdsk on your C: drive is: 
 chkdsk C: /F

chkdsk [drive letter]: [switches with space inbetween]
Switches that you can use in the command:

• /F - Fixes errors on the disk. The disk must be locked. If chkdsk cannot lock the drive, a message appears that asks you if you want to check the drive the next time you restart the computer. For example, on the C: drive.
• /V - Displays the name of each file in every directory as the disk is checked.
• /R - Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.
• /L:[size in KB] - Can only be used with a NTFS disk. Changes the chkdsk log file size to the number size in KB you type. If you omit the size parameter, typing /L by itself will display the current chkdsk log file size. For example, to have the default 65536 KB log file for the C: drive, you would type: chkdsk C: /F /L:65536
• /X - Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.
• /I - Can only be used with a NTFS disk. Performs a less vigorous check of index entries, which reduces the amount of time required to run chkdsk.
• /C - Can only be used with a NTFS disk. Does not check cycles within the folder structure, which reduces the amount of time required to run chkdsk.
• /B - Can only be used with a NTFS disk. Clears the list of bad clusters on the volume and rescans all allocated and free clusters for errors. /b includes the functionality of /r. Use this parameter after imaging a volume to a new hard disk drive.

Alwil software

es.kioskea.net/forum/ quitar-residuos-de-alwil-software
A veces no es posible desinstalar avast! en la forma estándar - con el / Agregar o quitar programas en el panel de control. En este caso, puede utilizar nuestro aswClear utilidad de desinstalación.
¿Cómo desinstalar el software utilizando aswClear.exe:
1. AswClear.exe de descarga en el escritorio
2. Iniciar Windows en modo seguro
3. Abrir (ejecutar) la utilidad de desinstalación
4. Si ha instalado avast! en una carpeta distinta de la predeterminada, navegar por ella. (Nota: ¡Cuidado! El contenido de cualquier carpeta que elija será eliminado!)
5. Haga clic en Eliminar
Descargar utilidad de eliminacion avast en
http://files.avast.com/files/eng/aswclear.exe
==========
http://espanol.answers.yahoo.com/question/index?
ALWIL SOFTWARE es la empresa creadora del antivirus AVAST!, como ESET es la creadora del NOD32...
Desinstalar el antivirus, luego INICIO - EJECUTAR
 del /f /a /q C:\Archivos de Programa\Alwil Software /d /s
Si no te funciona, quitale la "/d" o la "/s" al final, una de las dos te va a funcionar.
==============
http://www.forospyware.com/t363722-2.html
inicio-ejecutar:
cmd
net stop aswFsBlk
sc delete aswFsBlk
net stop epfwtdir
Sc delete epfwtdir
------------
solo te quedaría desinstalar CF de la siguiente manera:

• Ir a Inicio - Ejecutar
• Escribir lo siguiente: ComboFix /Uninstall como muestra la imagen debajo:
  
  
  • 
• Esto activara el desinstalador de ComboFix abriendo su pantalla principal y luego de unos segundos veras ("ComboFix is uninstalled")

safesaver

that is the shitware:

http://safe-saver.com/how-it-works.html

How to uninstall
If you installed the Chrome Extension (CRX):
Step 1:
Open Chrome, click on the Settings icon, and navigate to Tools -> Extensions.
Step 2:
Select the Safe-Saver plugin from the list of extensions, and click Uninstall.
** That's it, Safe-Saver plug-in is now uninstalled!
If you installed the Firefox Addon (XPI):
Step 1:
Open Firefox, and navigate to Tools -> Add-ons.
Step 2:
Select the Safe-Saver plugin from the list of add-ons, and click Uninstall.
** That's it, Safe-Saver plug-in is now uninstalled!

If you installed the plugin for other browsers:
Step 1:
Click Start, and navigate to: Control Panel.
Step 2:
Select "Add/Remove Programs" from the Control Panel. For Windows Vista/7 users, this will be called "Programs/Features".
Step 3:
Select the Safe-Saver plugin from the list of software, and click Uninstall/Remove.
** That's it, Safe-Saver plug-in is now uninstalled
=========================
http://greatis.com/blog/how-to-remove-malware/safesaver-sprotector-dll.htm

be careful ...i`m not aware of this removal application...
=========================

http://home.mcafee.com/virusinfo/virusprofile.aspx?key=3294242
This software is not a virus or a Trojan. It is detected as a "potentially unwanted program" (PUP). PUPs are any piece of software that a reasonably security- or privacy-minded computer user may want to be informed of and, in some cases, remove. PUPs are often made by a legitimate corporate entity for some beneficial purpose, but they alter the security state of the computer on which they are installed, or the privacy posture of the user of the system, such that most users will want to be aware of them.
Symptoms
This symptoms of this detection are the files, registry, and network communication referenced in the characteristics section.
Method This is not a virus or Trojan. PUPs do not "infect" systems. They may be installed by a user individually or possibly as a part of a software package (in a bundle, for example). 

======================

Characteristics

This software is not a virus or a Trojan. It is detected as a "potentially unwanted program" (PUP). PUPs are any piece of software that a reasonably security- or privacy-minded computer user may want to be informed of and, in some cases, remove. PUPs are often made by a legitimate corporate entity for some beneficial purpose, but they alter the security state of the computer on which they are installed, or the privacy posture of the user of the system, such that most users will want to be aware of them.

File Properties	Property Values
McAfee Detection	Downloader-FLN!9EF09911AABB
Length	261460 bytes
MD5	9ef09911aabbdf2ec2d4ed3200ae2bae
SHA1	022ee13539d2a0663635adc959f0f6fe7bdd2480

Other Common Detection Aliases

Company Names	Detection Names
avira	ADWARE/Adware.Gen7
Kaspersky	not-a-virus:AdWare.Win32.MegaSearch.am
Eset	Win32/Adware.MultiPlug.H application
vba32	BScope.Adware.MegaSearch

======================

All Users:

Please use the following instructions for all supported versions of Windows to remove threats and other potential risks:

1.Disable System Restore .

2.Update to current engine and DAT files for detection and removal.

3.Run a complete system scan.

Modifications made to the system Registry and/or INI files for the purposes of hooking system startup, will be successfully removed if cleaning with the recommended engine and DAT combination (or higher).

1. Please go to the Microsoft Recovery Console and restore a clean MBR.

On windows XP:

Insert the Windows XP CD into the CD-ROM drive and restart the computer.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Select the Windows installation that is compromised and provide the administrator password
Issue 'fixmbr' command to restore the Master Boot Record
Follow onscreen instructions
Reset and remove the CD from CD-ROM drive.

On Windows Vista and 7:

Insert the Windows CD into the CD-ROM drive and restart the computer.
Click on "Repair Your Computer"
When the System Recovery Options dialog comes up, choose the Command Prompt.
Issue 'bootrec /fixmbr' command to restore the Master Boot Record
Follow onscreen instructions
Reset and remove the CD from CD-ROM drive.

ssafe saveu

http://www.threatexpert.com/report.aspx
http://home.mcafee.com/virusinfo/virusprofile.aspx?
McAfee Labs&trade recognizes that this program may have legitimate uses in contexts where an authorized administrator has knowingly installed this application. If you agreed to a license agreement for this or another bundled application, you may have legal obligations with regard to removing this software, or to using the host application without this software. Please contact the software vendor for further information.
See http://vil.nai.com/vil/DATReadme.aspx for a list of program detections added to the DATs.
See http://vil.nai.com/vil/pups/configuration.aspx for information about how to enable, disable, and exclude the detection of legitimately installed programs.
This software is not a virus or a Trojan. It is detected as a "potentially unwanted program" (PUP). PUPs are any piece of software that a reasonably security- or privacy-minded computer user may want to be informed of and, in some cases, remove. PUPs are often made by a legitimate corporate entity for some beneficial purpose, but they alter the security state of the computer on which they are installed, or the privacy posture of the user of the system, such that most users will want to be aware of them.
Symptoms
This symptoms of this detection are the files, registry, and network communication referenced in the characteristics section.
Method
This is not a virus or Trojan. PUPs do not "infect" systems. They may be installed by a user individually or possibly as a part of a software package (in a bundle, for example).

======================

This software is not a virus or a Trojan. It is detected as a "potentially unwanted program" (PUP). PUPs are any piece of software that a reasonably security- or privacy-minded computer user may want to be informed of and, in some cases, remove. PUPs are often made by a legitimate corporate entity for some beneficial purpose, but they alter the security state of the computer on which they are installed, or the privacy posture of the user of the system, such that most users will want to be aware of them.

File Properties	Property Values
McAfee Detection	Downloader-FLN!4EBDF3B16CA4
Length	261476 bytes
MD5	4ebdf3b16ca43d2154cf3717a249d77d
SHA1	58aef5aa6fec0c2d7264ffc8639c56109b77e424

Other Common Detection Aliases

Company Names	Detection Names
avira	ADWARE/Adware.Gen7
Kaspersky	not-a-virus:AdWare.Win32.MegaSearch.am
Dr.Web	Adware.Plugin.31
Eset	Win32/Adware.MultiPlug.H application
vba32	BScope.Adware.MegaSearch

======================

All Users:

Please use the following instructions for all supported versions of Windows to remove threats and other potential risks:

1.Disable System Restore .

2.Update to current engine and DAT files for detection and removal.

3.Run a complete system scan.

Modifications made to the system Registry and/or INI files for the purposes of hooking system startup, will be successfully removed if cleaning with the recommended engine and DAT combination (or higher).

1. Please go to the Microsoft Recovery Console and restore a clean MBR.

On windows XP:

Insert the Windows XP CD into the CD-ROM drive and restart the computer.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Select the Windows installation that is compromised and provide the administrator password
Issue 'fixmbr' command to restore the Master Boot Record
Follow onscreen instructions
Reset and remove the CD from CD-ROM drive.

On Windows Vista and 7:

Insert the Windows CD into the CD-ROM drive and restart the computer.
Click on "Repair Your Computer"
When the System Recovery Options dialog comes up, choose the Command Prompt.
Issue 'bootrec /fixmbr' command to restore the Master Boot Record
Follow onscreen instructions
Reset and remove the CD from CD-ROM drive.

Back to Top

---

Hitman Pro: anti-spyware SW

http://www.techspot.com/downloads/1278-hitman-pro.html

HOSTS Anti-PUPs/Adware

This summary is not available. Please click here to view the post.

How To Boot Your Android Phone or Tablet Into Safe Mode

Welcome to Android: A Beginner’s Guide

http://www.howtogeek.com/130327/how-to-boot-your-android-phone-or-tablet-into-safe-mode/

On your Windows PC, you can boot into safe mode to load Windows without any third-party software. You can do the same on Android with Android’s safe mode. In safe mode, Android won’t load any third-party applications.
This allows you to troubleshoot your device – if you’re experiencing crashes, freezes, or battery life issues, you can boot into safe mode and see if the issues still happen there. From safe mode, you can uninstall misbehaving third-party apps.

Booting Into Safe Mode

To reboot into safe mode on Android 4.1 or later, long-press the power button until the power options menu appears.

Long-press the Power Off option and you’ll be asked if you want to reboot your Android device into safe mode. Tap the OK button.

On older versions of Android, long-press the power button and then tap Power Off to turn off your device. Turn on the phone or tablet by long-pressing the power button again. Release the power button and, when you see a logo appear during boot-up, hold down both the Volume Up and Volume Down buttons. Continue holding the two buttons until the device boots up with a Safe mode indicator at the bottom-left corner of its screen.

Troubleshooting in Safe Mode

While in safe mode, the words “Safe Mode” will appear at the bottom of your screen.

In safe mode, you’ll only have access to the apps that came with your device. Apps you’ve installed will be disabled and any widgets you’ve added to your home screens won’t be present. Try using your device normally after booting into safe mode. If your issue – freezing, rebooting, crashes, battery life issues, or bad performance – is solved in Safe Mode, the problem is with a third-party app you’ve installed.
While apps are disabled, you can uninstall them normally. Open the Settings screen, tap Apps, locate the app you want to install, tap it, and tap the Uninstall button. if you’ve installed any apps recently, you should probably try uninstalling those apps first.

After uninstalling the apps, you can try installing them one at a time to identify which app is causing you problems.
If you’re experiencing major problems with your device, you may want to skip all the troubleshooting and restore your device to its factory default settings. You’ll lose all the data on your device – so make sure you have everything backed up – and you’ll have to reinstall any apps you’ve installed. To do this, open the Settings screen, tap Backup & reset, tap Factory data reset, and follow the instructions on your screen.

---

To exit safe mode, restart your device normally. (Long-press the power button, select Power Off, and then long-press the power button again to turn it back on.) Your Android phone or tablet will boot and load third-party software as normal.