How to Fix Fmod.dll Error Code

What is Error Code 37?

Error Code 37 is a Device Manager Error Code that you may come across when you are unable to use an installed hardware device on your PC. It will pop up on your screen with the following display:

“Windows cannot initialize the device driver for this hardware. (Code 37)”

If you receive the above message, it means that your operating system was unable to acknowledge the drivers for a particular peripheral device.

Solution

Error Causes

Error Code 37 mainly occurs due to device driver corruption. However, there are other factors that can trigger this error code, some of which are the following:

• Missing device drivers
• Out-of-date device drivers
• Presence of malware or spyware in the system
• The particular device is not compatible with your PC

Device driver corruption or other data corruption is not uncommon and part of everyday PC use.

From an installation gone wrong to an unexpected shutdown, commonly generated data errors are considered the main culprit behind error codes.

Further Information and Manual Repair

Just like most PC error codes, Error Code 37 isn’t that difficult to get rid of. There are many DIY methods you can try to have your PC running smoothly in no time. Here are a few methods to resolve this issue:

Method 1: Restart your PC

It is possible that the display of the error code is merely due to a temporary issue with your peripheral device and not anything serious.

Therefore, the quickest and easiest method to solve the error code 37 is to simply restart your PC.

Method 2: Scan for Viruses

If restarting does not do the trick, a quick scan for viruses and removing them is another simple method you can follow to fix your PC.

Since the error code is due to corruption of data, viruses such as malware or spyware create error in your PC’s registry and eliminating them can help restore some of the corrupt data, which also speeds up your PC.

Method 3: Undo recent changes

A possible explanation for the error code may be the recent changes in your Device Manager or due to the peripheral device installation. You can thus undo the changes by either:

• Remove or change settings of the installed peripheral device
• Roll back the version of the driver to the one before the update.
• Use System Restore to reverse the changes made in the Device Manager

Method 4: Manually uninstall and reinstall the drivers

If the above stated methods do not help in speeding up your PC and is still giving you an error code, you may want to manually uninstall and reinstall the corrupt or missing drivers. Here are the following steps:

• Double-check if the installed external device is properly connected and working smoothly
• Open Device Manager and double click on the device that is causing problems
• When it opens, click on the ‘Driver’ tab and click ‘Update Driver’

Method 5: Use DriverFIX

However, updating the missing or corrupt drivers can be time consuming and may also require having a hardware documentation ready that contains specific details about the driver that you should download.

To avoid this time-consuming process, you can use DriverFIX software.

DriverFIX will help you to download the required driver without you having to waste your precious time and effort looking it up in a user manual. This latest software technology is embedded with its own database that tracks the missing or corrupt driver according to your PC’s motherboard version and specific details.

It is user-friendly, which means that it will relieve you from the frustration of such PC error codes appearing from time to time and enable your PC to work efficiently in no time.

Click here to download DriverFIX to resolve Device Manager error code 37 today!

Code 0x80070070 – 0x50011 – What is it?

If you’ve recently tried installing Windows 10, you might have encountered error code 0x80070070 – 0x50011 or its alternatives (error code 0x80070070 – 0x50012 and 0x80070070 – 0x60000). Whatever formats this error code presents itself in, it's usually accompanied by a barrage of other errors, as underscored on Microsoft’s official site. If you’ve encountered this error code, it simply means that your computer system might not have the required or required space to install the upgrade.

Likely, if you’ve experienced error code 0x80070070 – 0x50011, it’ll likely appear in the formats highlighted below:

• 0x80070070 – 0x50011
• 0x80070070 – 0x50012
• 0x80070070 – 0x60000

Solution

Error Causes

At present, this Windows 10 upgrade error is triggered or caused by various factors:

• Lack of computer resources or space
• Virus/malware infestation
• A clogged registry

Further Information and Manual Repair

Whilst new, not much information has been propagated regarding this error. However, there are some manual / practical steps you can take to have your Windows 10 upgrade up and running. Since the primary aspect of solving this problem is to make space on your computer system, here are some ways in which you can do so manually.

Method 1: Get more space

• Check the current space on your computer  

Before making attempts to create space on your computer, it’s vital that you check to decipher how much free space you have available.

• Make use of Disk Clean-up 

Since there’s a free service available on your computer to create space, why not use it and save time? If the Disk Cleanup tool is employed regularly, this will free up hard drive space and optimize your computer to work better.

• Remove unwanted desktop apps 

There are several apps lying around on your computer that you simply don’t use, uninstall those and make space to elude error code 0x80070070 – 0x50011 or its alternatives (Code 0x80070070 – 0x50012, Code 0x80070070 – 0x60000)

• Remove or archive files  

If you have lots of photos, media, documents (files), videos, etc, that you don’t use or will only need in the future, try cloud storage. You’ll still have those files within your possession but just not in a physical location. However, they’re still accessible. Another suggestion: If you use programs such as One Drive or Google Drive for desktop, limit your use to only the online application.

• Add more storage

If you’re not able to implement the above steps to clear some space to accommodate your Windows 10 upgrade due to error code 0x80070070 – 0x50011, acquire more storage. This can be expanded by incorporating storage devices such as USB flash drives, CDs, cloud storage, and SD Cards.

Method 2: Scan your computer for virus/malware

If you regularly download stuff, especially software on the Internet from ‘not so secured’ sites, you might have picked up something. You might have downloaded malware or virus (along with other legit programs).

To resolve this issue, it’s advised and very important that you download a powerful antivirus and perform a complete scan of your computer system. After you’ve detected and removed the suspected malware/virus, you’ll then be able to eliminate error code 0x80070070 – 0x50011 and resume with your Windows 10 upgrade.

Method 3: Clean up your computer’s registry

If you do not clean your computer’s registry often, it could become congested or clogged by .XML files, junk files, and cookies. To resolve this problem, clean your registry by using a powerful and user-friendly tool to clean up the problem.

Click here to download Restoro.

Each you connect time external devices like scanners, printers, and the likes to a Windows 10 computer, the device either pushes the drivers through the USB or any other port, or you are expected to install the drivers through external media. In both cases, the driver will be loaded into the system, allowing you to use the device. However, it doesn’t always go smoothly as you could encounter some errors like the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory ( Code 38 )”. If you encounter such an error in the Device Manager, then this means that a previous version of the device driver is still in memory and that each time the device is used, that previous version is loaded into memory and then unloaded which triggers the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory (Code 38)” error. This kind of error occurs if the operating system loads the unwanted driver or if it fails to unload the driver. It could be that there is an obsolete version of the driver that’s still installed in the system or it could also be that you need to update your USB drivers as they could be outdated or the problem could also be due to some third party program that is interfering with the installation. Whatever the cause is, here are some suggestions you can check out to resolve the problem.

Option 1 – Uninstall previously installed drivers and reinstall their latest working version from the manufacturer’s website

The first thing you can do is to uninstall the drivers that are currently installed on your computer and then reinstall their latest working versions from their official sites. This kind of error is commonly encountered while loading drivers for scanners and printers. This is due to the fact that their drivers and software come along with a package which is usually in external media like CD or DVD. So when you install the software package, there’s a possibility that a newer version has been launched by its manufacturer. When that happens, you have to uninstall the previously installed driver package and then download the drivers from the manufacturer’s website and install them.

Option 2 – Run the Hardware and Devices Troubleshooter

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• 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 “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 4 – Restart your computer in a Clean Boot State

If the first three given options didn’t work and you still see the error when you connect external devices, you can try putting your computer in a Clean Boot State and then try connecting them again.

• Log onto your PC as an administrator.
• 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 try to connect the external devices and check if the error is now gone.

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.

Microsoft store is ready and prepared for Windows 11 official release on October 5^th and it is coming with some surprises. It has officially confirmed that many open source and free applications will be in it like Opera, VLC, discord, Libre office, etc. It seems that Microsoft wants to place its store as one place to go for all of your software needs. Another great surprise is the coming of Epic games store implementation. It was officially confirmed but not explained in detail, will we have Epic store opened in Windows store or we will only get installer as a package we will see but this is some great news. As for how it states now, it seems that the Windows store aims to eliminate searching the web for applications and bring them all into one environment with reviews and ratings so you know which one to install and use. It also features a great search engine to find proper applications for your needs. The new store will come to Windows 10 as well but after all Windows 11 has been mostly released and adopted. So expect it via update in two or three months' time. It would be great if some larger companies decide to join MS stores like Autodesk, Adobe, the Foundry, etc so you can install everything you need from it but one can only hope.

If you are running the Windows Update service but decided to stop it but you encountered an error message instead that says, “The Windows Update service could not be stopped”, read on as this post will help you fix the problem. This kind of error appears when you use the Command Prompt to stop the Windows Update service, especially if you are using cmd without admin privileges. A lot of users reported that they were not able to disable the automatic Windows Update in Windows 10 using Command Prompt. The command used to stop the Windows Update service is the “net stop wuauserv” command. However, when some users executed this command, they got the error message. So if you are one of these users that can’t stop the Windows Update Service via Command Prompt, you can try to fix that using PID as well as checking the Service dependencies. For more details, follow the given options below.

Option 1 – Try to stop the Windows Update service via PID

In case you don’t know, each running service or process has its own unique ID or PID and you can find it in the Task Manager. You can use it to stop the Windows Update service. How? Refer to these steps:

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Services tab and look for the service named “wuauserv” and get its PID.
• After that, type “cmd” in the Windows Start search and right-click on Command Prompt from the search results and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, execute this command: taskkill /f /pid <PID>

Note: You need to replace “<PID>” with the PID of the “wuauserv” service. For instance, the PID is 6676, then this is how the command should be “taskkill /f /pid 6676”.

• After you execute the command, you will this message on your screen, “SUCCESS: The process with PID 6676 has been terminated” which indicates that you have stopped the Windows Update service successfully.

Option 2 – Try to check the Service 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 dependant 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.

Sysdata.xml Error Code - What is it?

To develop a good understanding of the Sysdata.xml error code, it is first important to learn what is sysdata.xml file and its function. Sysdata.xml is a type of XML file. The .XML file extension is an Extensible Markup Language file. XML-based formats have now become the default for many office productivity tools including Microsoft Office and LibreOffice. Furthermore, it has also come into common use for the interchange of data over the internet. Sysdata.xml error code usually pops up when .XML based applications are unable to run and crash while loading. This is a type of BSoD (Blue Screen of Death) error code. Common symptoms include:

• System freeze
• The screen turns blue
• Sudden system shut down

Solution

Error Causes

The Sysdata.xml error code is triggered due to multiple reasons such as:

• Faulty hardware
• Malware or viral infection
• Registry issues

No matter what the reason may be, it is advisable to fix this error code right away without any delays. This is a fatal error and can result in a system crash and loss of data. And recovering valuable lost data is the hardest.

Further Information and Manual Repair

Here are some of the effective and easy do it yourself methods to resolve this error on your system:

Method 1: Fix Faulty Hardware

Hardware issues may arise due to many reasons like manufacturing issues or voltage fluctuations. Electrical storms can cause power surges which may affect the hardware causing it to fail. The best way to resolve this is to download the latest drivers for the problematic devices or alter the device configuration in the BIOS setup program.

• To reconfigure the BIOS simply restart your PC and before Windows starts, press Del Key to access your BIOS.
• Now find the factory reset option.
• Select the option and press the button to load your factory defaults.
• After that save changes and confirm your selection.
• Reboot your PC to activate the changes.

Method 2: Scan for Viruses

Sometimes viruses and malware can disguise themselves in the .XML files which can cause them to get corrupted. To resolve the issue, it is advisable to download a powerful antivirus and scan your entire PC for viruses. Remove the detected viruses to resolve the Sysdata.xml error on your system.

Method 3: Repair the Registry

If the registry is not cleaned frequently, it loads with unnecessary and obsolete files like the junk files and cookies. These files clutter and damage the registry and eventually corrupt it and the important files like .XML files stored in it. To resolve the issue it is recommended to download Restoro. It is a user-friendly and powerful PC Fixer embedded with a registry cleaner. It scans your entire PC for registry-related errors and removes them immediately. It cleans the cluttered registry and restores the damaged files thereby repairing the issue right away. Click here to download Restoro.

Mozilla Firefox has introduced a new feature known as Restart with Windows which allows the browser to automatically start when your Windows 10 computer boots. This means that if you leave the Firefox browser opened while shutting down your computer, Firefox will re-open automatically along with the tabs that were opened right before you shut down your computer. Although some users may find this feature convenient, there are others who do not approve at all as it could be a nuisance. So if you’re one of the latter, then read on as this post will show you how you can disable the Restart with Windows feature in the Firefox browser on your Windows 10 computer. Refer to the instructions laid out below to get started.

• Step 1: Open Mozilla Firefox and if it’s opened already, just open a new tab and then type the following text in the address bar:

about:config

• Step 2: After typing the text given above, hit Enter and if a prompt with a warning message pops up, simply click on the “I accept the risk!” button to proceed.
• Step 3: Next, type “Restart” in the search filter which should display the following preference in the window:

“toolkit.winRegisterApplicationRestart”

• Step 4: After that, check for the preference value and then see if it’s set to true or not. If it is set to true, then it means that the Restart with Windows feature is enabled so obviously, to disable it, you need to set its value to false.
• Step 5: Now restart your computer without closing Firefox. After restarting your computer, you should no longer see Firefox starting automatically.

The Restart with Windows feature by default is disabled for most users. On the other hand, Mozilla will have this feature enabled as the default configuration in the coming weeks so it’s best that you now know what to do when that time comes since the newer versions of Mozilla Firefox are already being shipped with the Restart with Windows feature. However, if this post did not help you, then you might want to check if the feature has been added to the Startup folder, and from there, you can disable this startup program using the Task Manager > Startup tab.

A lot of controversies and mixed emotions have come from statements about Windows 11 minimum system requirements, especially ones linked to TPM. Naturally, each time some software company giant announces how things are must have there are people who go out and prove them wrong. This time Raspberry Pi community was one which demonstrated that not only Raspberry Pi does not have a TPM module, it can run the full desktop version of Windows 11

Raspberry Pi 4 and things you need for Windows 11 installation

In order to actually install Windows 11 on your Pi, there are certain things that you will need. Check out the below list and prepare everything.

• Raspberry Pi 4 4GB or 8GB
• A 32GB or larger SSD via a USB 3 caddy. Best for performance or 16GB or larger microSD card
• USB boot enabled, see below.
• A micro SD card with the latest Raspberry Pi OS
• Windows 10 PC
• USB to Ethernet or WiFi dongle
• Bluetooth dongle (if you want Bluetooth)
• Keyboard, mouse, HDMI, and power for your Raspberry Pi

Configuring Pi to boot from SSD

In order to boot from SSD be sure that firmware and bootloader are up to date on the latest version and upgrade if needed. Be aware that this firmware update can only be performed using the official Raspberry Pi OS. Also if you are eager and want to use a standard microSSD card instead of an SSD to run Windows 11 feel free to skip this entire section.

1. Boot from microSSD with the latest Raspberry Pi OS on it.
2. Update firmware and OS using the terminal by typing sudo apt update sudo apt full-upgrade sudo rpi-update
3. Reboot your Pi
4. Install the latest version of bootloader again using the terminal with the command sudo rpi-eeprom-update -d – a
5. Reboot Pi
6. Launch raspi-config on your Pi via terminal with sudo raspi-config
7. Select option 3 (Boot options – Configure options for start-up) from boot options
8. Select Boot ROM version and press ENTER
9. Select latest and then OK
10. Select NO when prompted to reset boot ROM to defaults on the latest version boot ROM selected screen. Press OK
11. Select Boot order and press ENTER
12. Select USB Boot and click on OK and remove microSD card from Pi
13. Select Finish and click on NO when prompted to reboot

Creating Windows 11 installation image for Pi 4

In order to install Windows 11 on our Pi, we must create an installation image, follow the steps below explaining the process.

1. Go to https://uupdump.net/
2. Search for Windows 11 Arm
3. Select the latest build for arm64
4. Select Language on which you would like installer and Windows
5. Pick Windows edition you would like
6. Set download method to Download and convert to ISO and click on Create download package
7. Extract downloaded content into win11 folder and go into it
8. Double click on uup_download_windows.cmd
9. On the security warning screen click on More info and then on Run anyway
10. Wait for the process to finish completely
11. Once the process is finished, press 0 to close the prompt

Installing image on microSSD or SSD

If previous steps of instruction were follower precisely you now have an ISO image that can be installed onto microSSD or SSD

1. Connect SSD or insert microSSD card into your PC
2. Go to https://www.worproject.ml/downloads
3. Download Windows on Raspberry imager and extract it into the win11 folder
4. Open Imager and allow it to make changes to your computer, set your language, and click on next
5. Select storage drive where you would like to install Windows
6. Set device type and click on next
7. Select our Windows 11 ISO image we created and click on next
8. On the drivers screen select Use the latest driver package available on the server
9. On UEFI firmware select screen choose Use the latest firmware available on the server
10. On configuration screen click on next
11. Check your setting on the installation overview and if everything is ok click on install
12. Wait for the whole process to be finished
13. Once the process is completed, close Windows on Raspberry imager, take out SSD or microSSD card from PC and connect it on your Pi along with Pi peripherals.

Setting Windows 11 on Pi

In order to actually use Windows 11 on our Raspberry Pi we now have to set up the Windows 11 install using the standard post-installation setup sequence.

1. Power up Pi and press ESC when prompted
2. Go to Device manager and press ENTER
3. Select Raspberry Pi Configuration
4. Select Advanced configuration
5. Set Limit RAM to 3GB to a disabled state, press F10 to save, and ESC to exit.
6. Select Display configuration
7. Set the resolution to desired option and press ENTER, F10 to save, and ESC to exit
8. Go to CPU configuration
9. Check if the CPU clock is set to default, if not set it
10. Press ESC to go back all the way to the main menu
11. Select Continue to exit BIOS and boot your Raspberry Pi with Windows 11 on it

And there you have it, fully working Windows 11 OS on Raspberry Pi despite what Microsoft says Note that due to lack of some drivers performance can be less than optimal, for example, full HD videos will not work since there are no compatible graphic drivers for Pi and some other stuff like Wi-Fi will also cause some issues but overall Windows 11 is working pretty well.

If you suddenly receive an error saying, “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” when browsing the web, then this means that the DNS lookup has failed. This kind of error is one of the most commons ones you can encounter while using the Chrome browser. And since it’s a pretty common error, the solutions for this one are pretty easy as well.

Option 1 – Disable both the Antivirus and Firewall temporarily

There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects. Thus, you need to disable these programs temporarily as it might be the reason why you’re getting the “Error 105 (net:: ERR NAME NOT RESOLVED): Unable to resolve the server’s DNS address” error in Chrome.

Option 2 – Check the Network Cables and restart the router then reconnect

Of course, the next thing you have to do is to check if the network cables connected to your computer or router are properly connected. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 3 – Try running the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 4 – Try removing the Proxy

Removing the Proxy might also help you in fixing the ERR_NAME_NOT_RESOLVED error in Chrome. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 5 – Disable Prefetch in Chrome

In case you don’t know, Google makes use of a prediction service that helps users in completing searches and typing URLs in the address bar. This prediction service uses the already resolve IP address to connect to the website you’ve already visited. Thus, it would be better if you disable it in cases like this one.

• Open Chrome’s Settings.
• Next, go to Privacy and Security then look for “Prefetch”.
• After finding Prefetch, toggle off the “Use a prediction service to help complete searches and URLs typed in the address bar” setting and then restart Chrome.

Option 6 – Flush the DNS, reset Winsock and then reset TCP/IP

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 7 – Try using the Google Public DNS

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

Option 8 – Reset Chrome

Resetting Chrome can also help you fix the error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.