Logo

Chrome won’t open or launch on Windows

If you’re suddenly unable to launch or open Google Chrome or unable to load web pages, then it’s most likely that the files in Chrome have been corrupted or some plugin is taking up a lot of resources which is why you encounter an error message saying, “Google Chrome has stopped working”. And when you try to check the Task Manager, you’ll see that Chrome is really taking up lots of resources, however, when you check the Taskbar, strangely, you will see nothing. If you are currently facing this issue in Chrome on your Windows 10 PC, follow the given options below.

Option 1 – Kill Google Chrome’s process in the Task Manager

If you aren’t able to open Chrome, then maybe its process is running in the background and you don’t see the browser windows. If that’s the case, you may have to force quit the browser and then try to open it again.

  • First, right-click on the Taskbar then select the Task Manager. And if the Task Manager is not responding, you can just use the Alt + Ctrl + Del keys and then select the Task Manager.
  • After opening the Task Manager, under Processes, look for Google Chrome’s process which would most likely be named “chrome.exe”.
  • Right-click on Google Chrome’s process and then select the End task option.
  • Now try to open Google Chrome again.

Option 2 – Try checking if your antivirus program is blocking Google Chrome

There are instances when due to false-positive, a security or antivirus program might block Chrome which is why it failed to open properly. Thus, you can just disable the security program temporarily and then check if you can now open Chrome or not.

Option 3 – Delete the User Profile in Chrome

You can also try deleting the User Profile folder in Chrome. To do so, follow these steps:

  • Tap the Win + R keys to open the Run dialog box.
  • Then copy and paste “%USERPROFILE%AppDataLocalGoogleChromeUser Data” and hit Enter.
  • From there, look for a folder named “Default folder” and then copy the folder to another drive as a backup.
  • After creating a copy of the folder, delete the Default folder.
  • Next, open Google Chrome again and go to Settings > Advanced > Reset.

Option 4 – Disable the Extensions in Chrome

There are instances when issues on a browser are triggered or caused by some problematic extension. To find out which one of your extensions is causing the problem, disable them all first and then enable them back one by one.

  • Click on the three-dotted icon for the menu located at the top-right corner of your screen.
  • Then click on the More tools option and go to Extensions.
  • From there, you will see a list of all the installed extensions in Chrome.
  • Disable all these extensions and restart the browser.
  • Now enable them back one by one to figure out which one of them is the culprit. You could also remove extensions that you no longer use.

Option 5 – Run the Chrome Cleanup tool

You might also want to try running the Malware Scanner & Cleanup tool in Chrome. This is a built-in tool that can help you get rid of any unwanted pop-ups, banners, ads, unusual startup pages, toolbars, and malware. Thus, it can help you to resolve the issue in Chrome.

Option 6 – Try to reinstall Chrome

If running the Malware Scanner & Cleanup tool in Chrome didn’t work out for you, you can try reinstalling it. To do so, follow these steps:

  • Open the Settings app and go to System > Apps & features.
  • From there, look for Chrome and uninstall it from your PC.
  • Then go to the official website of Google Chrome and download its latest version and install it.

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

Step By Step Guide to Fixing Regsvr32.exe Error On Windows

What is Regsvr32.exe Error?

Regsvr32 (Microsoft Register Server) is a command-line utility in Microsoft Windows Operating System. This is used for registering and unregistering OLE controls such as ActiveX controls and DLLs in the Windows Registry. This is executed as Regsvr32.exe.  The filename extension .exe is the abbreviation for executable.   It is installed in the %systemroot%System32 folder in Windows XP and new Windows versions. The Regsvr32.exe is an error that occurs when you attempt to run Regsvr32.exe to register a 32 bit DLL (Dynamic Link Library) on a 64-bit version of Windows. The error message is displayed as the following:
  • Filename.dll is not an executable file and no registration helper is registered for this file type.
  • Unrecognized flag: /invalid_flag
  • No DLL name specified
  • Dll_Name is not an executable file and no registration helper is registered for this file type.
  • The module "%1" failed to load.

Solution

Restoro box imageError Causes

There are multiple causes for the Regsvr32.exe error code. These include:
  • Invalid entry (command) path
  • Active X control errors
  • Missing or Damaged .dll files
  • Viral infection (Trojans) (.exe can easily get infected by viruses)
  • Registry issues
If you come across the Regsvr32.exe error code, it is advisable to repair it immediately before the damage sets in. Since this may occur due to viral infection, it can pose privacy and data security risks to your PC.

Further Information and Manual Repair

Here are solutions that you can implement to resolve the Regsvr32.exe error code on your system:
  1. If an invalid entry point is the cause of the error, then simply open an elevated command prompt. If the 32-bit DLL is in the %systemroot%System32 folder, then move it to the %systemroot%SysWoW64 folder. After that run the following command: %systemroot%SysWoW64regsvr32 <full path of the DLL>. This will help resolve the Regsvr32.exe error.
  2. If the cause of the error is a viral infection, then you will need to run a powerful antivirus to detect and remove viruses from your system to resolve the Regsvr32.exe error on your system.
  3. Nonetheless, if the causes for Regsvr32.exe are either Active X controls or registry corruption, then you will need to scan your computer with different tools to resolve each issue separately.
This can be time-consuming and too many program installations at one time can also slow down your system’s performance. This means you’ll also have to compromise on your PC’s speed.

Repair Regsvr32.exe Error With Restoro

To avoid all this hassle yet repair the Regsvr32.exe error, download Restoro. This is a multi-functional and innovative PC repair tool deployed with multiple utilities in one program including features like a registry cleaner and an Active X controls error fixer. It also functions as a system optimizer. It is a one-stop solution for all your PC-related errors including the Regsvr32.dll error. It is safe, efficient, and user-friendly. It is compatible with all Windows versions. When the RAM overloads it leads to damaged dlls and registry corruption. The registry cleaner utility repairs the damaged dll files and the corrupt registry. It wipes out all the unnecessary files cluttering the RAM including the junk files, invalid registry entries, and temporary files. Restoro also has an Active X controls scanning utility. This utility can be of great use if the Regsvr32.exe error is triggered by Active X control-related issues. Click here to download Restoro and resolve Regsvr32.exe on your computer right away.
Read More
Fix Steam stuck on Allocating disk space
If you have been stuck on allocating disk space on steam you know how annoying this error could be. Here you are, with your new game eager to play it and relax a little and all of the sudden steam gets stuck on allocating disc space. Luckily this error is fixable, follow provided guide to fix the error and continue with installing the game.
  1. Restart computer

    An old age solution of turning it off and turning it back on but in this case, it works 90% of the time.
  2. Run Steam as administrator

    Allocating disk space when done by a third-party application can be a task that requires privileges higher than the normal user. Find the steam executable file in the installation folder, right-click on it and run it as an administrator
  3. Clear Steam cache

    Launch Steam in admin mode. Once in the client, click on Steam at the top left corner of the screen. From the drop-down box, click on Settings. Once in the Settings, navigate to the Downloads tab. Click the Clear Download Cache option. Click OK on the prompt to confirm your action. Wait for the process to complete. When done, save changes and exit the client.
  4. Change download server

    Launch Steam client in admin mode. Once in the client, click on Steam at the top left corner of the screen. From the drop-down box, click on Settings. Once in the Settings, navigate to the Downloads tab. Click the drop-down menu under the Download Region. Choose a different server to download from. Exit the Steam client.
  5. Refresh installation files

    • Kill a Steam process in Task Manager.
    • Navigate to your Steam folder
    • Inside the Steam folder, select everything except the steamapps folder and the Steam.exe executable file.
    • Tap the Delete key on your keyboard.
  6. Turn off firewall

    Firewall can prevent steam and cut access to system operations, disable firewall to fix this issue.
  7. Stop overclocking

    If you have overclocked your PC, you can simply reverse the change. The steps you will need to take depends on the overclocking software. Launch the software and look for the option to stop the overclocking. Once done, restart your computer, rerun the game installation.
Read More
How to Fix R6025 Pure Virtual Function Call
R6025 pure virtual function call’ is a runtime error that occurs suddenly on the screen and disrupts the program being run prior to it. This error display indicates that the program has been corrupted. R6025 runtime error usually occurs with the Visual C++ framework.

Solution

Restoro box imageError Causes

This error occurs when the C++ program crashes which is usually because of the malfunctioning or missing of the device driver or incomplete device driver files. It happens because your application indirectly calls a pure virtual member function in a context where a call to the function is invalid. Most of the time, the compiler detects it and reports it as an error when building the application. R6025 error is usually detected at run time.

Further Information and Manual Repair

To fix the R6025 pure virtual function call error, you need to find the call to the pure virtual function. After you find the call, you need to rewrite the code so that it is not called again. There are 2 ways to do this:

Alternative 1

One way to fix the R6025 pure virtual function call is to replace the function with an implementation that calls the Windows API function DebugBreak. The DebugBreak causes a hard-coded breakpoint. Once the code stops running at this breakpoint, it is easy for you to view the call stack. By viewing the call stack you can identify the place where the function was actually called.

Alternative 2

Another quick way to find a call to a pure virtual function to fix the R6025 error is to set a breakpoint on the _purecall function that is usually found in PureVirt.c. By breaking this function you can trace the problem occurring and rewrite the call to ensure the error does not occur and the program you are trying to develop on the Visual C++ framework is easily developed. If R6025 Error is related to Windows Registry Problem Then here’s how you can fix the problem: To fix the runtime error R6025, run registry cleaner software to scan and fix all errors.  This alternative is suitable if the R6025 error is related to the Windows registry problem and where the error has occurred due to corrupted or malicious registry entries. You can download the registry cleaner repair tool for free. Run it to scan errors and then click the fix error button to repair the problem immediately.
Read More
Fix Error Accessing the Registry in Windows
If you encounter an error saying, “error accessing the registry” when you try to merge a registry key on your Windows 10 computer, you’re not alone as some users also experienced the same problem. According to these users, they encounter the error after they’ve re-installed their Windows version and tried to open a .reg file. Based on the reports, this error could occur if the registry file does not have administrative privileges. Meaning to say, the program does not have the necessary permission to merge the .reg file. This is common with fresh installs as well as reinstalls. Moreover, this kind of issue could also occur due to system file corruption. Whichever the case may be, here are some troubleshooting tips you can check out to resolve the error.

Option 1 – Try to import the .reg file with admin privileges

As pointed out, the error may be due to a lack of admin privileges. It could be that the Registry Editor does not have admin privileges to merge the registry file. This is common with new Windows installations especially since the Registry Editor hasn’t been opened before. So you need to import the .reg file again and this time, with admin privileges.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “Regedit” in the field and tap the Ctrl + Shift + Enter keys to open the Registry Editor with admin privileges.
  • A User Account Control or UAC prompt will appear where you have to click Yes to proceed.
  • After opening the Registry Editor, go to File > Import using the ribbon bar at the top.
  • Next, use the import menu to go to the location of the file you were trying to merge. Once you’ve found it, click Open to merge it with your current registry. This should fix the problem. If not, refer to the next options below.

Option 2 – Try performing a System Restore

Running System Restore can also help you fix the error when accessing the Registry. 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.
  • Once the next startup is complete, you have to merge or import the file again and see if the error is now fixed or not.

Option 3 – Try to perform repair install by creating a Windows 10 installation media

  • Click this link and then click the Download Tool Now button.
  • Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
  • Now select the ISO file option in step 5.
  • After that, you should now have an ISO file.
  • Next, go to the location where you’ve downloaded the ISO file.
  • Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
  • Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try running the System File Checker Scan

As mentioned, the error when accessing the Registry might be caused by file corruption. And that’s where the SFC scan comes in. The SFC or System File Checker scan could detect and automatically repair damaged system files. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given 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.
  • Now restart your computer.
Read More
Fixing the Port in use, please wait
Recently, a number of Windows 10 users reported an issue wherein they try to print from their PCs but were unable to and got an error message instead that states, “Port in use, please wait”. However, no matter how long they waited, nothing changed and they were still unable to print from their computers. On the other hand, when some of the users attempted to print wirelessly from their mobile devices, the printing continues which indicates that there is some issue between the computer and the printer. So if you are one of the users who are currently facing this problem, then this post should help. To fix this issue with your Printer, here are some possible fixes you can try that might work.

Option 1 – Run the Printer Troubleshooter

The first thing you can do to fix the “Port in use, please wait” error is to run the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msdt.exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
  • Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Try updating the Printer drivers

You might also want to try updating your printer drivers. All you have to do is locate the USB Composite Device. For complete details, follow the steps below.
  • First, click the Start button and type “device manager”.
  • Then click on the “Device Manager” from the search results to open it.
  • From there, look for the USB Composite Device option and right-click on it, and select the Update Driver from the options.
  • Restart your PC and then click the “Search automatically for updated driver software” option.
Note: You also have the option to download the latest version of your Printer from the manufacturer’s website.

Option 3 – Try selecting the correct port for your Printer

If the first two options given above didn’t work, then maybe it’s time to select a correct port for your printer since the wrong port has been selected which is why you’re getting the “Port in use, please wait” error.
  • Open “Devices and Printers” from the Start search.
  • Next, look for your printer from the list of devices and right-click on it, and then select Printer Properties.
  • Now go to the Ports tab under the newly opened Properties window and make sure that the port type matches the connection on the list of ports currently in use.
Note: If your printer is using a USB connection then the port should have a USB or DOT 4 in its description but if your printer is using a network connection then it should have the following description:
  • WSD
  • Network
  • IP
And if you notice that there are several listings for the same type of port, you have to change the selection to a different one and then click the OK button to save the changes made.
Read More
Windows 10 is stuck on Checking for updates
Over the years, the Windows 10 updates have smoothened but that does not mean that it no longer encounter some issues. One of these issues is when it gets stuck. As you know, Windows automatically checking for updates regularly or when you click the “Check for updates” button. However, if the Windows 10 update is taking forever and seems to be stuck, then you’ve come to the right place as this post will guide you on what you can do to resolve the problem. This kind of scenario in Windows Updates can be quite confusing especially since there is no response or any indication of what is really happening since you don’t know if the update is still downloading or if it’s already getting installed. To resolve this problem, there are several options you can check out. You can try to exit settings and restart your computer. You could also try to restart the services related to Windows Update or clear both the Software Distribution and Catroot2 folders, as well as run a System File Checker scan. For more details follow each one of the given steps below.

Option 1 – Restart your computer

The most basic thing you can do to fix the problem is to restart your computer. It usually works in fixing common issues like the Windows Update getting stuck at the “Checking for updates” screen. However, if it didn’t work, proceed to the next given options below.

Option 2 – Reset Windows Update components

If the first two options did not work then you might want to reset the Windows Update components manually. Follow the steps below to reset them.
  • 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:WindowsSoftwareDistribution SoftwareDistribution.old
    • ren C:WindowsSystem32catroot2 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 – Try checking Services Dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependent service will also be affected. This could be the reason why the Windows Update service could not start.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “services.msc” in the field and hit Enter to open Windows Services.
  • From the list of Services, look for the following services:
    • Remote Procedure Call (RPC) Service
    • DCOM Server Process Launcher
    • RPC Endpoint Mapper
  • After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
  • If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

Option 4 – Check the Background Intelligent Service and the Cryptographic Service

  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “services.msc” in the field and hit Enter or click OK to open Services.
  • From the list of Services, look for the following services and make sure that their Startup type is as follows:
    • Background Intelligent Transfer Service – Manual
    • Cryptographic Service ­– Automatic
  • After that, check if the Service status of the listed services above is set to Running. If they’re not, click on the Start button to start these services and then check if you can now enable the Windows Update service or not.

Option 5 – Try running the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why your screen is stuck at “Checking for updates”. To run the SFC command, follow the steps given 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.
Read More
Fix Windows Update Error 0x800F081F – 0x20003
If you are trying to upgrade your computer but encounter the Windows Update Error 0x800F081F – 0x20003 instead, then read on as this post will guide you in fixing this Windows Update error. This kind of error is commonly encountered when upgrading your copy of Windows 10 and is caused by errors with various developer-related settings that are being enabled in the system. When you encounter Windows Update Error 0x800F081F – 0x20003, you will see either of these error messages:
“We couldn’t install Windows 10. The installation failed in the SAFE_OS phase with an error during INSTALL_UPDATES operation: Error 0x800F081F”  “The installation failed in the Safe_OS phase with an error during apply_image operation: Error: 0x800f081f – 0x20003”
To fix this kind of Windows Update error, you need not use external programs but you can try to disable the Developer Mode, run the Windows Update troubleshooter or restart all the Windows Update-related services and components. For more details, refer to the options provided below.

Option 1 – Try to disable Developer Mode

You might have to disable Developer Mode to fix the Windows Update Error 0x800F081F – 0x20003. How? Refer to these steps:
  • Tap the Win + I keys on your keyboard to open the Settings app.
  • Next, go to Update & Security > For Developers.
  • From there, select the toggle for Sideload apps or Microsoft Store apps located on the right-side panel.
  • If you get any prompt, just click on Yes.
  • After that, navigate to Apps > Apps & features and then click on Optional features on the right-side panel.
  • Then scroll down to locate the Windows Developer Mode entry and select it and click on Uninstall.
  • Once you’re done uninstalling the Windows Developer Mode component, close the Settings app and restart your computer to apply the changes made.

Option 2 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x800F081F – 0x20003. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try restarting various Windows Update-related services and components

  • Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
  • After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
    • net stop wuauserv
    • net stop bits
    • net stop appidsvc
    • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
    • ren %systemroot%system32catroot2 catroot2.bak
  • Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
    • net start wuauserv
    • net start bits
    • net start appidsvc
    • net start cryptsvc
  • After that, restart your computer and try to run the setup again, and see if the error is now fixed.
Read More
Repairing or rebuilding the WMI Repository
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.
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
One or more Network Protocols are missing
Windows 10 users a set of rules or standards called Network Protocols in communicating over the internet. These protocols are the ones that made sure that the data is correctly sent between computers. However, if any of the Network Protocol is missing in your Windows 10 computer, then you will most likely encounter a problem like not being able to browse the internet, or share files. For this, you can try to run the Incoming Connections troubleshooter: As you were not able to connect to your internet connection using your PC, you can try to run the Incoming Connections troubleshooter as it might resolve the problem. Refer to the following steps to run this troubleshooter:
  • Tap the Win + I keys to open Settings.
  • After opening Settings, go to Update and Security.
  • Next, navigate to the Troubleshoot pane and select the Incoming Connections section and click the Run Troubleshooter button to get started.
  • Wait until the troubleshooter is finished doing its job and then try connecting to your network again.
If after running the Incoming Connections troubleshooter you receive an error message instead that says, “Network Protocol is missing”, then here are some suggestions you need to check out to fix it. Take note that you must have admin privileges before you start troubleshooting the problem.

Option 1 – Try to update or rollback or uninstall the Network drivers

You might also want to update, roll back, or disable your Network drivers to fix the “This operation failed as no adapter is in the state permissible for this operation” error.
  • Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
  • Then right-click on each one of the Network drivers and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
  • After that, restart your PC and see if it helped in fixing the netio.sys Blue Screen error.

Option 2 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:
  • Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
  • After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.
  1. netsh winsock reset – type in this command to reset Winsock
  2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
  3. ipconfig /flushdns – type in this command to flush the DNS cache
  • Next, restart your PC and check if the problem’s fixed.

Option 3 – Diagnose the Network Adapter

To diagnose the Network Adapter, go to Control Panel > All Control Panel Items > Network Connections, and from there, look for the network adapter that could be causing the error. Note that if you are using a Wi-Fi connection, then it’s probably your Wi-Fi adapter, otherwise it has something to do with your Ethernet adapter. Just right-click on the problematic network adapter and select diagnose to troubleshoot.

Option 4 – Try to perform Network Reset

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:
  • Tap the Win + I keys to open Settings.
  • From there, go to the Network and Internet section.
  • Next, scroll down and look for “Network Reset” under the status pane.
  • After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Option 5 – Try importing Winsock settings from another computer

If resetting Winsock or the Network didn’t fix the problem, then you can try to import settings from a computer that’s in good condition. You need to have access to the registry to get this done and then export and import a couple of settings. Refer to these steps to get started:
  • Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
  • After that, go to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
  • Next, look for two registry keys named “Winsock” and “Winsock2” and then right-click on each one of them and select the Export option.
  • Now copy the registry keys to a USB drive and then copy the keys on the PC in excellent condition.
  • Then double click on each one of them and it will install the WINSOCK keys.
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