How to Resolve Error Code 0x800704c7 in Windows 8

Apple introduced the Live Photo feature way with iPhone 6S in their iOS9. Live Photo idea was that each time you take a photo, your phone will capture a few seconds of video along with sound and all of that is sent when you share your photo. This of course can sometimes be really bad when some not wanted audio gets recorded in the background.

Since the feature was introduced it has been set as the default option when taking pictures so each time you snap one you just capture a small amount of video and audio along. Good thing is that this feature can be turned off and the even better news is that you can edit your old photos to remove back video and audio.

How to share only photo

You can keep your Live Photos but share only a single still typical photo if you wish. Go to the photos app on your phone and select the photo you wish to share. Press the Share button on the bottom left part of the screen and once the Share menu appears tap on the Live button in the upper left corner of the selected photo. The button should turn grey and become slashed and now you can share only still photo. This is only temporary for this one specific share so next time you want to do this you will have to go through the process again.

How to disable Live Photo

If you are not happy with the previous solution and really do not want to turn off the Live feature each time you want to share a photo or you just simply do not want the feature at all there is way to turn if off for good. Take note that you can temporarily not use this feature just by opening the camera, switching to photo mode, and then tapping on the Live photo button on the toolbar that looks like three circles one inside another. This will temporarily turn the Live Photo feature for this session but next time when you open the camera by default it will be turned on again. This is a good approach if you want the feature but sometimes you just want not to use it.

In order to turn it off completely go to the settings of your phone and go to Camera and then preserve settings. inside the preserve setting turn the switch Live Photo to ON position, now go-to camera and again click on the live photo button to turn it off but this time setting will be saved and next time you open the camera it will not be ON.

Editing old Live Photos

As stated before you can edit your old pictures in order to make them stills. You can edit them to remove audio only but keep the video part, or you can completely remove everything and convert them into typical still images.

In order to only remove audio from your Live Photos go to pictures and select one that you wish to change, click on edit, and inside edit tap on the Live Photo icon (three circles). Next tap on the audio icon located in the top left corner of your screen and it will change into the mute icon. Click on done and you are finished.

To completely remove the Live photo go to Photos, select picture, click on edit and select the live photo button again. This time tap and hold the Live button next to the sound until it turns gray with a strike through it. Click on done and you are finished.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

Error 0x80070003 - What is it?

Error 0x80070003 is a type of Windows file backup and restore error code. This error occurs when you copy files or try to create backup and restore files and folders by using Windows Backup and Restore. This error stops you from using browse for files or folders. It hampers your ability to browse and restore files in the File Restore Wizard on your PC.

Solution

Error Causes

Error 0x80070003 may occur due to numerous reasons such as:

• Registry files are corrupted and damaged
• Missing directories
• Boot sector corrupted
• Outdated drivers
• Faulty software installation
• Malware infection
• Improper maintenance and incomplete installation

Further Information and Manual Repair

Here are some manual and easy do-it-yourself methods that you can try at home and resolve the issue on your own and save hundreds of dollars that you would be otherwise spending to hire a professional for the job.

Method 1 - Use Search Functionality in the File Restore Wizard to restore files

To work out and resolve error 0x80070003 on your system simply use the search functionality in the File Restore Wizard to locate and restore the files. This can be done by going to the start menu and then click on search. Now enter the keywords in the search for box and then click search again. Click to select the files that you want to restore from the list and then click OK. This will help you restore the files and resolve the issue.

Method 2 - Recreate the Missing Directory

If the re-parse point is deleted, then you will have to recreate the missing directory. The deletion of the re-parse point can be identified if the error code is displayed in this format ‘Filename: C:\Myfolder\11111.txt, Error: the system cannot find the path specified (0x80070003)’. To resolve, simply follow the path that is pointed out in the error and create the corresponding folder. Create the folder Myfolder in Drive C. Then try the restore operation again. Now click to clear the Restore the files to their original subfolders check box and then run the File Restore Wizard. This is most likely going to resolve the issue.

Method 3 - Scan for Viruses

Sometimes error 0x80070003 may occur due to malware. This stops you from creating file backup and restore files. If this is the cause then simply download and run an antivirus to remove malware programs on your PC.

Method 4 - Clean and Repair the Corrupted Registry

Error 0x80070003 can be triggered due to registry corruption. If this is the cause then simply download Restoro. This is a user-friendly and powerful multi-functional PC Fixer integrated with a registry cleaner. The registry cleaner scans for all registry-related errors, wipe out all unnecessary and junk files, and also cleans and repairs the damaged registry in seconds. Click here to download Restoro and resolve error 0x80070003 today!

What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• INVALID_PROCESS_ATTACH_ATTEMPT

To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
• Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
• Restart your PC and then check for updates under the Windows Update section.
• After that, it will find the latest available and stable Synaptics driver and then install it.
• Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
• Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.SYS Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

There are several kinds of errors you could encounter when you are running Windows 10 on a virtual machine. The Windows OS knows the difference between booting up in a standalone computer or in a virtual machine. This is why some specific drivers and system capabilities are used while emulating the Windows OS on software and during this phase, there are times when the System Preparation may throw up an error that says, “A fatal error occurred while trying to sysprep the machine”. This kind of error arises due to a race condition wherein the Sysprep command tries to stop the Microsoft Distributed Transaction Coordinator or MSDTC service and the VMware tool tries to start the MSDTC service. You may also see the following messages logged in the Setuperr.log file:

• [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing ‘C:Windowssystem32msdtcprx.dll,SysPrepDtcCleanup’, returned error code -2146434815[gle=0x000000b7]
• [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2146434815[gle=0x000000b7]
• [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80100101[gle=0x000000b7]

To fix the 0x0f0082, 0x0f0070, 0x0f00a8 Sysprep errors, you can check out two potential fixes. First, you have to check the status of the MSDTC service and the second one is to check the settings in the Windows Registry. Note that these fixes are proven to be effective on many users and apply to several versions of Windows, including Windows 10.

Option 1 – Check the status of the MSDTC service via Command Prompt

As mentioned, the error could be caused by the malfunctioning of the MSDTC service or it. Thus, you have to uninstall and reinstall the MSDTC service to resolve the problem and you can do that using Command Prompt. Follow the steps below.

• In the Start Search, type “command prompt” and from the results, right-click on Command Prompt and then select the “Run as administrator” option to open it with admin privileges.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Once you’ve opened Command Prompt, execute this command: msdtc –uninstall
• The command you just entered will uninstall the MSDTC service. After that, you need to execute this second command to reinstall the service: msdtc –install
• Now exit Command Prompt and check if the error is now fixed.

Option 2 – Check the Registry settings

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and click OK or hit Enter to open the Registry Editor.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
• From there, look for a DWORD value that’s named “SkipRearm” and double click on it.
• Then change its value data to “1”.
• Restart your computer to apply successfully apply the changes made and check if it was able to fix the error.

Universal PnP or plug-and-play monitors use a generic PnP Windows driver. Whenever a user plugs a USB device or monitor into a PC the system will automatically identify the device and it will install the proper driver for smooth running. Generic PnP Monitor in Windows 10 means that Windows 10 installed a monitor driver as the PNP did not recognize the device. This generic PnP monitor driver may not work perfectly like the manufacturer’s one. It can lead to issues like unable to set the best monitor resolution and the screen refresh rate. Therefore, it is important to fix this issue. All of that being said let us fix your PnP display driver issue.

1. Reconnect monitor

   Always try this first, just by unplugging the monitor and then plugging it back may resolve the issue, if the monitor was not detected properly the first time, there are very high chances that this method will resolve the issue.

2. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

3. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically install the latest driver for your device, then reboot.

4. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

5. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

What Is 0x80004005 Outlook Error?

0x80004005 Outlook is an error that users commonly encounter while attempting to send or receive emails on Outlook.

The message that appears usually states “This message could not be sent. Try sending the message again or contact your network administrator."

The client operation failed. Error is [OX80004005- 0X0004B9-OXOO501].

Error Causes

This error is usually caused by a problem in the Local Area Network or LAN. What actually happens is that signals with the wireless LAN are lost or a connection problem occurs within the network cable.

As a result, the 0x80004005 Outlook error is triggered while sending or receiving an email. Sometimes the problem goes away on its own. However, if it recurs after a few hours, it shows that some problem exists within the network.

Also, it is important to understand that different factors can affect the quality of wireless connections in a network.

For instance, garage door openers, microwave ovens, and Bluetooth devices can easily become obstacles, disrupting the connection and causing the quality to degrade. Other causes are listed below as follows.

• Missing, corrupt, or damaged registry keys
• Existence of viruses
• Outdated drivers

It is a must to fix this error otherwise potential risks associate with this error such as permanent damage and blue screens.

Further Information and Manual Repair

There are two ways to fix this error and both are listed below as follows.

• One solution is to disable script blocking in Norton Antivirus. Most users encountering this problem have Norton Antivirus installed on their PCs. To correct this problem, simply turn off the ‘Enable Script Blocking’ feature. However, there is a downside associated with this solution. Enabling script blocking will make your network or computer vulnerable to viruses and malware. That’s why it is not advised to implement this solution.
• The alternative solution is to simply disable the new-mail notification feature offered in Outlook. To disable notifications of any new emails, the steps go as follows. Open Outlook and go to the Tools menu. Here you will come across ‘Options’.Click on it and then select the ‘Preferences’ tab. Here you will find the ‘Email Options’. Click on it and then uncheck the checkbox against the option, ‘Display a notification message when new mail arrives’. Click Ok two times.

Both these workarounds will work. Therefore, it is advised that you employ any one of them as per your needs.

If you are trying to access a particular file on your Windows 10 computer either to open, rename or delete it, and you suddenly encounter an error stating, “Could not find this item. This is no longer located in [Path]. Verify the item’s location and try again”, read on for this post will help you out in resolving this issue. If you are able to find and view a file on your computer, you should have clear access to it. And since you are seeing an error message when you try to do something about this file, you are not able to do anything with the file. There are times when this error pops up with the files created by third-party services and that the file’s extension is not defined properly. On the other hand, there are also other obscure causes for this error. To fix it, here are some suggestions you can try.

Option 1 – Delete the file using Command Prompt

If you wish to delete the problematic file and weren’t to, you can use Command Prompt.

• In the Start menu, type in “Command Prompt” to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator”.
• Once you’ve opened Command Prompt, copy and paste the command given below and tap Entre after you do so. You also have to make sure that you key in the correct path where the file is located as well as its name.

rd /s \?X:badfolderpath Note: In the command above, “X” is the placeholder letter so you must input the letter that corresponds to the drive’s letter where the file is located.

• After that, you will see the “Operation completed successfully” message on your screen. If you don’t, check if you’ve really inputted the correct location of the file or its name.

Option 2 – Use a Command Prompt tweak to rename the file

If you don’t want to delete the file and only want to rename it, you can apply some tweaks using the Command Prompt. Make sure to follow the steps carefully.

• In the Start menu, type in “Command Prompt” to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator”.
• After opening Command Prompt, type in “cd” followed by the path where the file is located with this format – “C:\Folder1\Folder2\Folder3”. However, you have to omit the problematic file this time. To put it simply, the last folder in the command must be the folder where the file is located.
• After inputting the command, tap Enter on your keyboard and then use the set of commands given below. Note that each command is a new line so you need to tap Enter after copying each line.
  • DIR /A /X /P
  • RENAME (the current name of the problematic file) (a non-problematic name)
  • EXIT

Note: Make sure that you only input the current name and the new name separated by a space. You must not write the brackets in the command. If everything goes well, you will now be able to operate the file like you used to before.

Option 3 – Use Command Prompt to delete the file without any extension

This option applies to cases where the affected file does not have any viable extension which means that Windows does not really know what to do with it and it only displays the “Could not find this item. This is no longer located in [Path]. Verify the item’s location and try again” error message. It usually occurs with the files created by browser plugins that are mostly from Mozilla Firefox. To delete these kinds of files, here’s what you have to do:

• Follow the first two steps from the previous option above so you can navigate to the location of the file accurately just be careful in inputting the folders.
• Don’t forget to tap Enter right after each command and then use the next command below so you can delete the affected file which has no extension:

del *.*

• After you’re done, open the File Explorer and then check if the file is now deleted or not.

Option 4 – Try using another workaround without using Command Prompt

This option is a lot like a workaround but it definitely gets the job done for you. It’s ideal for you if you do not want to deal with Command Prompt and only want to do everything in a graphical environment. To get started, follow the steps below.

• Look for the affected file or folder on your PC using File Explorer. Once you found it, right-click on it and select the “Add to archive” option from the context menu.
• Once the archiving options window pops up, look for the “Delete files after archiving” option and make sure that you select it then click OK to start archiving the folder or file. After that, you should now notice the file no longer exists.
• After that, delete the archive file as well.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

Computer viruses are malicious applications that have the ability to self replicate and spread over the system and various devices, just like viruses in organisms. We all know that computer viruses are bad and that you should avoid them however you can. So in this spirit, we are taking a deeper dive into what kind of viruses exist and how they function.

1. File-infecting Virus

A virus that attached itself to an executable program. It is also called a parasitic virus which typically infects files with .exe or .com extensions. Some file infectors can overwrite host files and others can damage your hard drive’s formatting.

2. Macro Virus

This type of virus is commonly found in programs such as Microsoft Word or Excel. These viruses are usually stored as part of a document and can spread when the files are transmitted to other computers, often through email attachments.

3. Browser Hijacker

This virus targets and alters your browser setting. It is often called a browser redirect virus because it redirects your browser to other malicious websites that you don’t have any intention of visiting. This virus can pose other threats such as changing the default home page of your browser.

4. Web Scripting Virus

A very sneaky virus that targets popular websites. What this virus does is overwrite code on a website and insert links that can install malicious software on your device. Web scripting viruses can steal your cookies and use the information to post on your behalf on the infected website.

5. Boot Sector Virus

These viruses are once common back when computers are booted from floppy disks. Today, these viruses are found distributed in forms of physical media such as external hard drives or USB. If the computer is infected with a boot sector virus, it automatically loads into the memory enabling control of your computer.

6. Polymorphic Virus

This virus has the capability to evade anti-virus programs since it can change codes every time an infected file is performed.

7. Resident Virus

A resident virus stores itself on your computer’s memory which allows it to infect files on your computer. This virus can interfere with your operating system leading to file and program corruption.

8. Multipartite Virus

A type of virus that is very infectious and can easily spread on your computer system. It can infect multiple parts of a system including memory, files, and boot sector which makes it difficult to contain.