Logo

How to Resolve Error Code 0x80070422 on Windows 10

Error Code 0x80070422

Error code 0x80070422 is a Windows-based error code occurring in various versions of Windows including Windows 7, Windows 8 and Windows 8.1, and Windows 10. It usually occurs when users attempt to update Windows. A message box will appear stating that the error code has occurred.  Users will notice the following common symptoms:

  • Inability to complete Windows updates
  • Error message occurring during use of Windows Update service

The error code, if left unresolved, can cause serious problems for PC users as they will be unable to access the latest updates to the Windows operating system. Such a situation can expose their system to vulnerabilities. Thus, fixing Windows 10 error code is of utmost importance.

Solution

Restoro box imageError Causes

Among the many reasons Error code 0x80070422  is encountered includes:

  • Corrupted or missing registry and DLL files
  • Badly or poorly installed software. The software could also be infected by a virus or Trojan
  • Outdated or poorly installed drivers

Further Information and Manual Repair

Fixing Windows-based error codes can be a simple process. However, in some cases, it requires specialized skills. In the case of Windows 10 error code 0x80070422 consider the two (2) main solutions available through manual repair. You may also need to consider help from a certified Windows repair technician or the use of an automated tool if you are not confident you have the skills to perform the solutions below.

Method 1: Check if Windows Update is Running Properly

One of the main reasons for error code 0x80070422 is a Windows Update service that is not running on the right settings. To verify if an issue with your Windows Update service is the source of the problem applies the following steps:

  1. Type “Windows Update” in the search bar near the Windows home button.
  2. Select “Windows Update settings” when this option appears. (You may also click the home button, then “Settings” followed by “Update and Security”.)
  3. Select “Advanced Options”
  4. (You will be given an option to choose how updates are installed.) Select Automatic.
  5. Save settings and restart the computer.

Once these settings are in place Windows will be able to download updates automatically. This enables your machine to run more smoothly. However, if after applying the steps above, Windows 10 error code 0x80070422 is not resolved, you may proceed to solution two (2).

Method 2: Disable Internet Protocol Version 6 (IPv6)

IPv6 is the latest or most current version of Internet Protocol (IP). This provides your machine with an IP address, a crucial aspect of all communications related to the Internet. By disabling this IP some users have been able to successfully resolve Windows 10 error code 0x80070422.

Like many tasks involving Windows, there are more than one ways in which you can attempt to disable IPv6. These require different types of skills and must be approached with care, as mistakes can lead to serious issues with your machine. Methods include using Command Prompt, Registry Editor, or Control Panel.

If your experience with Windows 10 is quite limited and you are not certain of your skills choose the simplest approach as listed below.

  1. Select Control Panel.
  2. Choose “Network and Internet”, then “Network and Sharing Center”.
  3. Right-click your Internet Connection. The name of your connection will be listed underneath the heading – “View your basic network connection and set up connections”.
  4. Select “Properties” then uncheck Internet Protocol version 6 (IPv6)
  5. Save settings by clicking OK.
  6. Restart the computer and check if the 0x80070422 error code has been corrected.

Method 3: Using An Automated Tool

If the issue persists despite following the solutions above, the best step to take is to use an automated tool. This may not be your preferred course of action, especially since it can be difficult to ascertain the safety of certain tools found online. For this reason, choose a reputable source offering automated tools which are designed to specifically fix Windows 10 error code including error code 0x80070422.

Download and install a powerful automated tool to access the best Windows 10 error code solutions. The process is simple and includes clear instructions which enable even average Windows users to completely resolve complicated errors on their machine.

How to Stop Future Error Codes from Occurring

Though it is hard to predict when an error code will occur, each Windows 10 user can take precautionary steps to prevent other errors from occurring. This includes the following:

  • Ensure you download software from reputable sources to avoid viruses and other forms of malware.
  • Clean your registry often. The registry stores settings across all applications. Regular cleaning will your machine function more efficiently as it reduces the likelihood of issues such as crashes or system errors.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Disable non MS store apps in Windows 11
Disable non MS store apps in Windows 11 post pictureYou can prevent starting of app installations files if they have not come from the MS store inside Windows 11. This can make your PC more secure because all apps in the store will have to be digitally signed and overall it can provide you with more control over what will be installed. Follow the guide below to find out how can you easily turn this feature ON.
  1. Press ⊞ WINDOWS + I to open Windows settings
  2. Select Apps and then choose Apps & Features
  3. Click on Choose where to get apps to bring a drop-down menu
  4. Select The Microsoft Store only (Recommended)
  5. Close settings
Settings will apply changes immediately and you continue using Windows right away. With these settings turned ON if you want to install a downloaded application or run the installer you will not be able to, and message The app you’re trying to install isn’t a Microsoft-verified app will show on your screen. You can always reverse this setting by choosing Anywhere in settings instead of Microsoft store only.
Read More
Delete large System Error Reporting files
In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

  • Go to Settings.
  • From there, go to System > Storage > Free Up Space and then click on it to launch it.
  • Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
  • Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

  • Tap the Win + E keys to open File Explorer.
  • Next, enable the Hidden Files view from the menu.
  • Then go to C:/ProgramData/MicrosoftWindowsWER.
  • From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
  • Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.
Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:
  • Right-click on the folder and then select Properties.
  • Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
  • After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
  • Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
  • Now edit the permission to Full Control for “Everyone”.
  • Click OK to save the changes made and then exit.
On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.
Read More
4 Methods of Fixing Error Code 48

Error Code 48 – What is it?

Error Code 48 is a device driver error code that users can encounter on any Windows 2000 operating system and later versions.

It occurs when the connected peripheral device cannot be run as the Windows operating system’s driver required to install the programs for peripheral devices has either been corrupted or is incompatible with the system.

It prompts the user with the following message on the screen:

The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

Solution

driverfix boxError Causes

Like most other Windows error codes, error code 48 is triggered by the following factors.

  • Corrupted system registry files
  • Presence of viruses in the device
  • The device driver is out-of-date
If this error code is not rectified, it could give birth to other driver device errors such as error code 52.

Further Information and Manual Repair

Method 1 – Run a complete scan for malware and spyware

Identifying and removing the viruses in the system registry and in the connected devices is the easiest method to fix the corrupted registry files.

Viruses such as spyware and malware infect the registry entries and eat up the files that lead to incomplete or missing data. This creates problems for installing external devices as the driver required to install them is not complete.

Method 2 – Use System Restore

You can also use system restore to eliminate the problem. Here is how you can use it:

  • Log in using an Administrator account
  • Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
  • Click ‘Restore my computer to an earlier time’ and click ‘Next’
  • Select the last Windows to restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
  • Click ‘Next’ on the confirmation window to proceed
  • Restart your PC after restoration is complete

By restoring the system via the last saved system checkpoint, you can obtain undamaged Windows system registry files that can help resolve the error code.

Method 3 – Manually uninstall and reinstall the device driver

Since Error Code 48 is due to a missing or an out-of-date device driver, uninstalling and then reinstalling the device driver can help solve the error.

You can do this by firstly logging in as Administrator and opening Device Manager. Select the device that is causing the problem and double click it; make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual. Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer. DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 48. It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 48 quickly and effectively!
Read More
Personalize Windows 11 Start menu
Windows 11 is released and its adoption goes slower than Microsoft would like but nevertheless, it is slowly getting adopted, especially among new computers. Windows 11 has brought us a new modern look of OS but if you would like to personalize it a little more you can. Follow the guide on various things that you can change inside Windows 11.

windows 11 desktop iconsPersonalize list of recently added apps, opened items, folders

The recommended section that shows recently added apps and recently open items can be turned off and hidden now to be shown. In order to do this follow these steps:
  1. Open Windows Settings by pressing WINDOWS + I
  2. Click on personalization in the sidebar
  3. Click on START and go through the options
  4. Turn OFF switch beside recently accessed files
  5. Additionally, you can also change which folders appear on the Start menu.

Remove apps or change app order on the Start Menu

To remove application not to be shown in the Start menu at all follow this simple guide:
  1. Right-click on app
  2. Choose unpin
  3. To place the application on Start click on All Apps, right-click on the app and choose Pin to Start
  4. To drag and rearrange apps, simply click on them and drag them to the new place.

Change the Start Menu location

When Windows 11 was first released Start Menu could only be located in the middle of the screen but thanks to plenty of backlash from users now it is possible to move it on a more traditional left side.
  1. Press WINDOWS + I to open the settings app
  2. Click on Personalization
  3. Look for taskbar behaviors
  4. Inside taskbar behaviors look for Taskbar alignment
  5. Change alignment to left

Change the Start Menu color

In order to change the color of the Start Menu follow the next steps:
  1. Open Settings app
  2. Go to personalization settings
  3. Go to Colors
  4. Switch to custom
  5. Under accent color pick a color you like or make your custom one.
Read More
Fix Error 0xe0434f4d

What is Error 0xe0434f4d?

Error 0xe0434f4d displays when a remote computer runs an instance of the SQL Server 2005 but it fails to initialize. When the plan is started, this error displays in a status window on the SQL Server. Also, when the Update-OffilineAddressBook cmdlet is started in Microsoft Exchange Server, this error can occur.

Solution

Restoro box imageError Causes

Error 0xe0434f4d can occur for possibly two main reasons. The first one is when the System Attendant Service is not properly running, and the second when you don’t have the permission to run the update. Other causes are when the .NET Framework 2.0 security does not allow sqlplanlaunch access to run from a shared network. Another cause is when the Offline Address Book (OAB) is not found in the Configuration Domain Controller server that the server of OAB generation uses.

Further Information and Manual Repair

In case you didn’t know, the Offline Address Book generation server is a mailbox server, and in order to resolve error 0xe0434f4d, you will have to replicate the OAB object to the Configuration Domain Controller server. In order to do so, follow steps:
  • Go to start and click on All Programs, then go and click on Microsoft Exchange Server 2010. Click on Exchange Management Console
  • In Exchange Management Console, go to Server Configuration and click on Mailbox
  • In the details, go to mailbox server that generates Offline Address Book and right-click it, then go to Properties
  • In the Properties, click on System Setting and locate the domain controller name in the box that reads Domain controller servers being used by Exchange
Make sure the OAB object is reproduced in the Configuration Domain Controller Server. Follow these steps to do that:
  • Go to Start and click on Run. Type Adsiedit.msc in Open box and press Enter. Right-click on ADSI Edit and click on Connect to
  • Locate a list reading Select a well-known naming context, and from there select Default naming context. In a Select or type a domain or server window, type FQDN (fully qualified domain name) of the Configuration Domain Controller server which was determined in step 1, and click OK
  • Expand Configuration [dc.domain.com], expand CN=Configuration, DC=domain, DC=com, expand CN=Services, expand CN=First Organization, and expand CN=Address Lists Container
  • Click on CN=Offline Address Lists and make sure the OAB object is listed on the details pane
When the OAB generation server receives this, then it will connect to the Configuration Domain Controller server and will locate the OAB object. If the OAB generation server is unable to find the OAB object, then the error will return on the cmdlet. On SQL Server, you should change the .NET permissions to allow sqlplanlaunch application access to run from shared administration. For that, follow these steps:
  • On ArchiveIQ Server, open System from the Control Panel and note down the computer name
  • On SQL Server, log in as administrator and open the command prompt
  • On the command prompt type, ‘C:windowsmicrosoft.netframeworkv2.0.50727caspol.ece –m –ag l – url file:\[Archive IQServer Computer Name]AlQRemote$*FullTrust and Press Enter. Type yes and press Enter again to confirm the permission changes.
Read More
How to Resolve Internal Error 2753

Internal Error 2753 - What is it?

Internal error 2753 is associated with Windows Installer failure. The Windows Installer is basically an in-built software program in Windows 7 and 8. It installs all programs on the system smoothly, saves the program in the computer program files and in the Windows Registry. Though this can be carried manually Windows Installer makes the installation process much easier. However, internal error 2753 can cause a great deal of distress and frustration during program installation. This error prevents you from installing your desired program successfully.

Solution

Restoro box imageError Causes

The 2 known causes for Internal Error 2753 are:
  • Viral infection
  • Windows Installer not properly registered

Further Information and Manual Repair

To resolve internal error 2753 on your system, try the methods discussed below. These methods are easy and require no technical expertise. Let’s get started:

Method 1 - Remove All Malicious Programs

Malicious programs like viruses, malware, adware, Trojan and spyware can corrupt programs on your PC like Windows Installer. If this is the underlying cause of error code 2753, then simply download a powerful antivirus on your system. Run it to scan for all such malicious programs and remove them. Once your PC is clean, try installing your desired program. This will hopefully resolve the issue. If the error still pops up then try method 2.

Method 2 - Register Windows Installer Properly

To do this, go to the start menu and then open Run and type ‘cmd’ in the box, and press OK. This will open the DOS command window. In the command prompt type "regsvr32 vbscript.dll" and then press Enter to proceed. After that, you will see a message that will read as "DllRegisterServer in vbscript.dll succeeded." This means Window Installer files have been successfully registered on your PC.  Now you can try installing your desired program again. If the installation begins and completes successfully, then the error is resolved.

Method 3 - Undo Recent Changes

If nothing works, then use the Windows System Restore Utility tool to undo recent changes. This will bring back your PC in the former state before you experienced the error 2753 on your PC. To access System Restore Utility, press Start and type System Restore in the search box. Now follow the steps in the Wizard to choose a restore point. Once you select the point, reboot your system to activate changes.
Read More
10 Worst Computer Viruses in history
Computers viruses, worms, ransomware, etc. are kinds of malicious software that no user should take lightly. On several occasions, we have touched upon security steps that each user should take in order to protect its identity and data. Sadly sometimes even when all precautions are taken some malware can still slip through and wreak havoc. Today we are looking at some of the worst or the best, depending on your view that has indeed wreaked plenty of havoc.

viruses10 worst computer viruses in history

In the list of the 10 most famous computer viruses below, we show the costs, dates, reach, and other key facts. First a note about terms: we use the words “virus” and “worm” interchangeably because most readers search for them that way. But there’s a subtle difference that we explain after the list.

1. Mydoom – $38 billion

The worst computer virus outbreak in history, Mydoom caused estimated damage of $38 billion in 2004, but its inflation-adjusted cost is actually $52.2 billion. Also known as Novarg, this malware is technically a “worm,” spread by mass emailing. At one point, the Mydoom virus was responsible for 25% of all emails sent. Mydoom scraped addresses from infected machines, then sent copies of itself to those addresses. It also roped those infected machines into a web of computers called a botnet that performed distributed denial of service (DDoS) attacks. These attacks were intended to shut down a target website or server. Mydoom is still around today, generating 1% of all phishing emails. That’s no small feat considering the 3.4 billion phishing emails sent each day. By that figure, Mydoom has taken on a life of its own, infecting enough poorly-protected machines to send 1.2 billion copies of itself per year, 16 years after its creation. Though a $250,000 reward was offered, the developer of this dangerous computer worm was never caught. Wondering what makes the world’s most secure computers so safe? See the Tech@Work guide: Upgrade to the World's Most Secure and Manageable PC

2. Sobig – $30 billion

The 2003 Sobig computer virus is actually another worm. It is second only to the Mydoom virus in its scope. The $30 billion figure is a worldwide total, including Canada, the U.K., the U.S., mainland Europe, and Asia. Several versions of the worm were released in quick succession, named Sobig.A through Sobig.F, with Sobig.F being the most damaging. This cybercriminal program masqueraded as legitimate computer software attached to emails. It disrupted ticketing at Air Canada and interfered with countless other businesses. Despite its widespread damage, the creator of the successful bug was never caught.

3. Klez – $19.8 billion

Klez is a close third on the list of the worst computer viruses ever created. With nearly $20 billion in estimated damages, it infected about 7.2% of all computers in 2001, or 7 million PCs. The Klez worm sent fake emails, spoofed recognized senders and, among other things, attempted to deactivate other viruses. As with other viruses and worms, Klez was released in several variants. It infected files, copied itself, and spread throughout each victim’s network. It hung around for years, with each version more destructive than the last. Windows has come a long way since most of the computer viruses on this list hit the web. Thankfully, built-in protection with Microsoft Defender is always on the watch.

4. ILOVEYOU – $15 billion

The year 2000’s ILOVEYOU virus worked by sending a bogus “love letter” that looked like a harmless text file. Like Mydoom, this attacker sent copies of itself to every email address in the infected machine’s contact list. Shortly after its May 4 release, it had spread to more than 10 million PCs. The virus was created by a college student in the Philippines named Onel de Guzman. Lacking funds, he wrote the virus to steal passwords so he could log into online services he wanted to use for free. He reportedly had no idea how far his creation would spread. This virus is also known as Loveletter. Need to up your remote work security game before there’s another entry on the list of most deadly computer viruses? See our guide: How to Work Remotely and Securely

5. WannaCry – $4 billion

The 2017 WannaCry computer virus is ransomware, a virus that takes over your computer (or cloud files) and holds them hostage. The WannaCry ransomware ripped through computers in 150 countries, causing massive productivity losses as businesses, hospitals, and government organizations that didn’t pay were forced to rebuild systems from scratch. The malware raged like wildfire through 200,000 computers worldwide. It stopped when a 22-year-old security researcher in the U.K. found a way to turn it off. Computers with out-of-date operating systems were hit especially hard. That’s why security experts always recommend updating your systems frequently.

Ransomware strikes again

In September 2020, one of the potentially largest computer virus attacks in medical history hit Universal Health Services. The U.S. hospital chain, which has more than 400 locations, was reportedly struck by damaging ransomware. The attack forced the cancellation of surgeries and made healthcare workers switch to paper records.

6. Zeus – $3 billion

The Zeus computer virus is an online theft tool that hit the web in 2007. A whitepaper by Unisys three years later estimated that it was behind 44% of all banking malware attacks. By then, it had breached 88% of all Fortune 500 companies, 2,500 organizations total, and 76,000 computers in 196 countries. The Zeus botnet was a group of programs that worked together to take over machines for a remote “bot master.” It originated in Eastern Europe and was used to transfer money to secret bank accounts. More than 100 members of the crime ring behind the virus, mostly in the U.S., were arrested in 2010. It’s not as prominent today, but some of the virus’ source code lives on in newer botnet viruses and worms. Zeus caused documented damage of $100 million. But the real cost in terms of lost productivity, removal, and undocumented theft is undoubtedly much higher. A $3 billion estimate, adjusted for inflation, puts this virus at a cost of $3.7 billion in today’s dollars.

7. Code Red – $2.4 billion

First observed in 2001, the Code Red computer virus was yet another worm that penetrated 975,000 hosts. It displayed the words “Hacked by Chinese!” across infected web pages, and it ran entirely in each machine’s memory. In most cases it left no trace in hard drives or other storage. Financial costs are pegged at $2.4 billion. The virus attacked websites of infected computers and delivered a distributed denial of service (DDoS) attack on the U.S. White House’s website, www.whitehouse.gov. In fact, the White House had to change its IP address to defend against Cod Red. Can your printer get a virus? See our cool infographic: The State of Printer Security

8. Slammer – $1.2 billion

The SQL Slammer worm cost an estimated $750 million across 200,000 computer users in 2003. This computer virus randomly selected IP addresses, exploiting vulnerabilities and sending itself on to other machines. It used these victim machines to launch a DDoS attack on several internet hosts, significantly slowing internet traffic. The Slammer worm hit banks in the U.S. and Canada especially hard, taking ATMs offline in many locations. Customers of Toronto’s Imperial Bank of Commerce found themselves unable to access funds. The attack reared its ugly head again in 2016, launching from IP addresses in Ukraine, China, and Mexico.

9. CryptoLocker – $665 million

Thankfully, ransomware attacks like the 2013 CryptoLocker virus have dipped since their 2017 peak. This malware attacked upwards of 250,000 machines by encrypting their files. It displayed a red ransom note informing users that “your important files encryption produced on this computer.” A payment window accompanied the note. The virus’ creators used a worm called the Gameover Zeus botnet to make and send copies of the CryptoLocker virus. According to a report by security firm Sophos, the average ransomware attack costs a business $133,000. If we estimate that CryptoLocker hit 5,000 companies, that would put its total cost at $665 million. Where will cybersecurity go next? See our guide: The Future of Cybersecurity

10. Sasser – $500 million

The Sasser worm was written by a 17-year-old German computer science student named Sven Jaschan. He was arrested at the age of 18 in 2004 after a $250,000 bounty was posted for the computer virus’ creator. A friend of Jaschan’s tipped authorities that the youth had penned not only the Sasser worm but also the damaging Netsky.AC attack. Jaschan was given a suspended sentence after it was found he was a minor when he wrote the malware. The Sasser worm crashed millions of PCs, and though some reports put damages at $18 billion, the relatively low infection rate suggests a more likely cost of $500 million. Other notable viruses The top 10 worst computer viruses above are just the ugly tip of a gargantuan digital iceberg. With a million new malware programs popping up every 3 years, we may miss the forest for a few outstanding trees. Here are just a few more viruses that have wreaked havoc over the years: Mimail: This worm tried to harvest data from infected machines to launch a string of DDoS attacks, but was relatively easy to remove. Yaha: Yet another worm with several variants, thought to be the result of a cyber-war between Pakistan and India. Swen: Written in C++, the Swen computer worm disguised itself to look like a 2003 OS update. Its financial cost has been pegged at $10.4 billion, but not reliably. Storm Worm: This worm showed up in 2007 and attacked millions of computers with an email about approaching bad weather. Tanatos/Bugbear: A 2002 keylogger virus that targeted financial institutions and spread to 150 countries. Sircam: A computer worm from 2001 that used counterfeit emails with the subject line, “I send you this file in order to have your advice.” Explorezip: This worm used fake emails to spread to every machine on thousands of local networks. Melissa: The most dangerous computer virus in 1999, Melissa sent copies of itself that looked like NSFW pics. The U.S. FBI estimated cleanup and repair costs at $80 million. Flashback: A Mac-only virus, Flashback infected over 600,000 Macs in 2012 and even infected Apple’s home base in Cupertino, Calif. In 2020, there’s now more malware on Macs than on PCs. Conficker: This 2009 virus still infects many legacy systems and could do significant damage if it ever activates. Stuxnet: This worm is reported to have destroyed Iranian nuclear centrifuges by sending damaging instructions.
Read More
DISM Error 14098, component store corrupted
As you know, one of the useful and efficient utilities in Windows 10 is the DISM tool. It can be used with the Command Prompt command line which allows users to carry out various tasks. However, there are instances when the DISM tool could encounter some errors when you try to execute a command. One of these errors is the one that states, “The component store has been corrupted”. This kind of DISM error is due to an error in the image file. When you encounter the DISM Error 14098 when running the DISM tool, you will see the following content in the command line:
“C:>Dism /Online /Cleanup-Image /RestoreHealth /Source:c:testmountwindows /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 [==========================100.0% Error: 14098 The component store has been corrupted. The DISM log file can be found at C:WINDOWSLogsDISMdism.log C:>”
There are several fixes you can check out to fix the DISM Error 14098, “The component store has been corrupted”. You can try to run the Restore Health command or reset the Windows Update components, or whitelist the dism.exe in your antivirus program, as well as try to uninstall any recently installed updates. Follow the options provided below for more details.

Option 1 – Run the Restore Health command in a Clean Boot State

  • First, you need to put your computer in a Clean Boot State.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • Now open Command Prompt with admin privileges.
  • Then type and enter this command to execute it: Dism /Online /Cleanup-Image /RestoreHealth
  • Wait until the process is completed and restart your computer.
Note: If the Restore Health command fails, you can use the “/StartComponentCleanup parameter” by executing this command: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 2 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:
  • Open Command Prompt with admin privileges.
  • After that, type each one of the following commands and hit Enter after you key in one after the other.
    • net stop wuauserv
    • net stop cryptsvc
    • net stop bits
    • net stop msiserver
Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.
  • After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
    • ren C:/Windows/SoftwareDistribution/SoftwareDistribution.old
    • ren C:/Windows/System32/catroot2/Catroot2.old
  • Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
    • net start wuauserv
    • net start cryptsvc
    • net start bits
    • net start msiserver
  • Close Command Prompt and reboot your PC.

Option 3 – Whitelist the “dism.exe” in your antivirus program

The DISM error 14098 might also be caused by your antivirus program which could be interfering it from running. To fix this, you have to whitelist dism.exe. How? Refer to these steps:
  • Open the Windows Defender Security Center from the system tray area.
  • Next, click the “Virus & threat protection” option and then open the “Virus and threat protection settings”.
  • After that, scroll down until you find the “Exclusions” and click on the “Add or remove exclusions” option.
  • Then click the plus button and select the type of exclusion you want to add and from the drop-down list, select Folder.
  • Next, navigate to this path and select the WinSxS folder: C:/Windows/WinSxS
  • When a User Account Control or UAC prompt, just click on Yes to proceed.

Option 4 – Try to uninstall recently installed updates

There are times when some Windows Updates affect some mechanism internally when you update your Windows 10 computer. As a result, it causes issues with other components of the operating system which could be the reason why you’re getting the DISM error 14098.
  • Go to Settings and select Update and Security > Windows Update.
  • From there, click on the “View update history” option and then click on the “Uninstall Updates” option.
  • This will open a new window that contains the list of installed Windows Updates.
  • Now right click on the Windows Update you wish to uninstall and click Uninstall.
Read More
How to Fix fltmgr.sys in Windows 10
The fltmgr.sys file or the Filter Manager is the one that’s responsible in making sure that all the file stored in a computer’s hard drive stays on their respective locations and is located in C:/Windows/System32/drivers. Now when you encounter a Blue Screen of Death or BSOD error saying, “Your PC ran into a problem that it couldn’t handle, and now it needs to restart. SYSTEM_SERVICE_EXCEPTION”. This kind of Stop error is due to an error with the driver that’s responsible for enabling the communication between the hardware and the computer. It indicates that this driver allows direct access to the internal hardware from the CPU itself. What’s worse about the SYSTEM_SERVICE_EXCEPTION BSOD error is that there are times when you won’t be able to log in to your computer even after it reboots. However, you need not worry as this post will guide you into fixing this BSOD error. All you have to do is follow the given options below carefully and that before you proceed make sure that you create a System Restore point just in case something goes wrong.

Option 1 – Run the Windows Update

Obviously, since the fltmgr.sys file is a system file from Microsoft, you can try running the Windows Update and see if it fixes the problem or not.

Option 2 – Run the System File Checker

The System File Checker, also known as the SFC scan, is a built-in utility in Windows that can be found in the C:/Windows/System32 folder. This tool allows you to scan and restore any corrupted system files in Windows that might be causing the SYSTEM_SERVICE_EXCEPTION BSOD error. To use this tool, follow the steps below.
  • 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 and then check if it has fixed the error or not.

Option 3 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that 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.

Option 4 – Check your hardware for any physical issues

There are times when faulty hardware can result in serious problems in the system such as the SYSTEM_SERVICE_EXCEPTION Blue Screen error. Thus, it is highly recommended that you check the internal components of your CPU to find out if there are any problems. And if there is any physical damage, you need to bring that to a technician to get it fixed or have it replaced.

Option 5 – Run the CHKDSK utility

You can also run the Chkdsk utility to resolve the BSOD error. The Chkdsk utility is the one that repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
  • chkdsk C: /r /x
  • chkdsk C: /f
Read More
The boot configuration data store can not open
The Boot Configuration Data or BCD files have the instructions required by the Windows operating system in order to properly boot the computer. So if you experience any trouble when you boot your computer, then it is possible that it is due to some misconfiguration or even corrupted Boot Configuration Data files. And if you also encounter an error saying,
“The boot configuration data store could not be opened”
while you try to carry out any command on the bcedit.exe, then you’ve come to the right place as this post will guide you on how you can fix this error in Windows 10. This kind of error could pop up if the system is not able to locate the specified file. It is also possible that the requested system device can’t be found or that the boot configuration data store could not be opened. In addition, when you open the System Configuration or MSConfig, you might notice that there is no Boot data, and according to the reports, is that when you try to dual boot the computer, the installer will replace the default bootloader.

Explanation

In case you don’t know, Windows’ earlier versions were stored in the “Boot.ini” file. You can find the entry in the EFI firmware boot manager of the EFI-based operating system which is located at EFIMicrosoftBootBootmgfw.efi. Whatever the cause of the error is, there are several suggestions you can check out to resolve the problem. You can try to set an entry option value in BCD or enable the Advanced options menu, as well as rebuild the BCD. Before you proceed with the troubleshooting options provided below, make sure that you boot your computer into the Advanced Recovery Mode first since that’s where you can find Command Prompt under the Advanced Options. In addition, you also have to suspend or disable BitLocker and Secure Boot on your PC.

Option 1 – Try to set an entry option value in BCD

  • Once you’re in the Advanced Options, select Command Prompt.
  • Next, execute this command to set an entry point: bcdedit /set {current} Description "TheNameYouWant"
  • After the command has been executed, it will enable the system to trust a version of Windows that is not trusted by default. This should fix the problem, if not, follow the next given options below.

Option 2 – Try to specify the BCD file

  • In the elevated Command Prompt, execute this command: bcdedit /store c:BootBCD
  • Once done, the command will give you a list of options and then execute this next command: bcdedit /store c:BootBCD /set bootmenupolicy legacy
  • After that, restart your computer and select your Windows and then tap the F8 key right away.
Note: When you select the legacy option, the Advanced Options menu will be available during the computer boot up and then you can select into which operating system you can boot your computer into.

Option 3 – Try to rebuild the BCD files

The first thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.
  • You can start by booting into the installation environment for Windows 10 from an installation media.
  • After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
  • From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
    • bootrec /FixMbr
    • bootrec /FixBoot
    • bootrec /ScanOS
    • bootrec /RebuildBcd
  • Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status