nslookup works but ping fails in Windows

Hello everyone and welcome to another great tutorial from errortools.com I hope everyone is feeling great and that you are prepared to boost the performance of your computer. This time we will speed up Windows startup time and overall performance by eliminating startup programs that we don't need and do not use. Microsoft itself and some application developers tend to have some applications or some services always active and set to be loaded on Windows startup. If you want to change which of these applications are starting up with your Windows and change them, follow this easy guide and you will be speeding up your Windows in no time. First thing is to open a task manager, fastest and most direct way of doing this is with a keyboard combination of CTRL + SHIFT + ESC When Task Manager opens, click on the startup tab on top. Once you click on startup you will get a list of applications that are set to be started when Windows is booted. You can now click on the application and then click on disable on the bottom button, the application status will update in task manager to disabled and it will not be booted anymore when Windows starts. In this same manner, you can enable back some applications if you changed your mind about them. Please note that some applications are using some services and must have them running or they will not work properly. The best practice is to disable applications you are positive you will not use or use rarely so you do not want them to slow down Windows.

If, while using your computer, you encounter the ACPI.sys Blue Screen error, read on as this post will guide you in fixing the problem. The ACPI.sys file is a Windows operating system file that is related to the MSDN 2939. ACPI.sys, the Windows ACPI driver, is an inbox component of the Windows operating system. It is the one that supports the power management as well as the Plug and Play or PnP device enumeration. And so if this file ends up getting corrupted, it is known to cause a Blue Screen error. Another possible cause for the ACPI.sys Blue Screen error includes RAM issues, incompatible firmware, hard disk issues, corrupted drivers or malware infection, and so on. Here are some Blue Screen errors that can be triggered by the ACPI.sys file:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL
• KERNEL DATA INPAGE
• SYSTEM SERVICE EXCEPTION

To fix the Blue Screen error associated with the ACPI.sys file, refer to the instructions provided below.

Option 1 – Try to recreate the ACPI.sys file

If the first option didn’t work, the next thing you can do is to recreate the ACPI.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named ACPI.sys and rename it to ACPI.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the ACPI.sys Blue Screen error is now fixed.

Option 2 – Try to update or rollback the ACPI Driver

The first thing you can try to fix the Storport.sys Blue Screen error is to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Tap the Win + X keys to open the Win X menu and from there, select the Device Manager.
• After opening the Device Manager, look for the ACPI.sys driver and right-click on it, and then select Properties.
• Next, go to the Driver section. Note that the rollback option would only be available if you’ve recently updated the ACPI.sys driver. So if you can’t see it then click on the Update Driver button.
• After that, Windows will automatically check for the problems that could be related to the Blue Screen error.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. On the other hand, if updating the ACPI driver, didn’t work, you can also try to copy the ACPI.sys system driver file from the System32 folder of another computer that’s functioning properly and runs the same Windows OS version. Afterward, place it on your problematic computer and check if it fixes the BSOD error or not.

Option 3 – Run System File Checker or SFC scan

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 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.

 Reboot your PC.

Option 4 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ACPI.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

Option 5 – Run System Restore

• 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.

One of the primary packages that install the Windows Media Player is the Media Feature Pack among other related files that are needed by the associated software products. And one of the essential DLL files in that package is the mfplat.dll file which is needed by various games and streaming services. So if this DLL file goes missing, you will most likely encounter any of the following error messages:

• “mfplat.dll missing”
• “The application failed to start because mfplat.dll was not found.”
• “The program can’t start because mfplat.dll is missing from your computer.”

In other circumstances, the Media Feature Package does not come pre-installed with the main Windows package especially for those who use Windows N, thereby causing the error to pop up. The main cause of this problem is that users who use Windows 10 N do not have the Media Feature pack pre-installed with the installation package. Aside from that, the installation package could go missing after a few Windows Updates or if you have uninstalled it by accident. To resolve this problem, you need to check out each one of the given options below.

Option 1 – Try to enable Media Playback via Command Prompt

If you encounter the mfplat.dll missing error when you attempt to run PLEX or other similar streaming service and you’ve already verified that the Media Feature Pack is indeed installed, you might want to try enabling it using an elevated Command Prompt. There are cases when a particular Windows Update ends up disabling the feature and creates the grounds which results in the mfplat.dll missing error. Thus, you can have to enable the feature via Command Prompt.

• Tap the Win + R keys to open the Run dialog box.
• Then type “cmd” in the field and hit Enter to open an elevated Command Prompt.
• Next, click on Yes if a User Account Control prompt pops up.
• After opening Command Prompt, copy and paste the following command and hit Enter to execute it:

dism /online /enable-feature /featurename:MediaPlayback

• Close Command Prompt and then open the app once again to check if the problem is now fixed.

Option 2 – Try installing the Media Feature Pack for Windows 10 N version

As mentioned, the Windows 10 N version does not come with Windows Media Player. Meaning to say, the Media Feature Pack is also not installed by default or won’t be updated by the Windows Update component. So if you are not quite sure what Windows 10 version you currently have installed, refer to these steps:

• Tap the Windows key + S and then type “about” in the search box.
• From the search results, click on the “About your PC” to open the About tab of the Settings app.
• Afterward, scroll down to the Windows specifications and check your Windows version under Edition.

Note: If you have verified that your PC is using the Windows 10 N version, you need to install the appropriate Media Feature Pack for your computer. How? Refer to the steps below:

• Click this link to download and install the Media Feature Pack from Microsoft’s official website.
• Upon installation, select the edition you want to install using the drop-down menu and then click on Confirm. Take note that there are few reasons why you’d want to install the older version since most streaming services like PLEX and most games usually require version 1803.
• After that, wait until the request is validated. The download should begin in a few minutes automatically.
• Once the download is completed, open the installation executable file and follow the next on-screen instructions to install the Media Feature Pack on your computer.
• Restart your computer. After your computer has rebooted, open the application where you’re getting the mfplat.dll missing error and then check if the problem is now fixed.

Option 3 – Try to extract a copy of the mfplat.dll file from the windows.old directory

If you encounter the error shortly after you just upgraded to Windows 10 from an older version, the best thing you can do to resolve the problem is to use windows.old directory to fetch an old copy of the mfplat.dll file. To do so, follow the steps below.

• Go to the Windows drive and then look for the windows.old directory where it preserves a copy of your old operating system as well as associated files in case something goes out of hand during the upgrade process.
• After that, open the windows.old folder and then go to the syswow64 folder.
• Next, from the syswow64 folder, copy the mfplat.dll file and paste it to C:/windows/syswow64.
• Restart your computer and check if the error is now resolved or not.

What Is Error 2032?

Error 2032 is essentially the hexadecimal format of the error caused. This error code is actually a code format used by the Windows operating system. Manufacturers use this code to determine the cause behind the problem. This error is usually the result of the issues that arise with different applications. When this error occurs, individuals are not able to view multimedia content on their PC. They may also experience system crashes and this makes it crucial to resolve it.

Solution

Error Causes

Error 2032 is caused by problems in Windows system files. Improper registry entries may also cause this problem. Some of the common causes that trigger Error 2032 are improper deletion of hardware or applications. Similarly, incomplete hardware or application installations or uninstallations may also cause issues. These file errors are actually caused when a computer has recently been attacked by a virus, spyware, or malware or if the system is trying to recover from an unanticipated shutdown. Such activities often result in the corruption or deletion of registry entries in Windows system files. The corrupt files will obviously cause problems and the application will fail to perform correctly.

Further Information and Manual Repair

While there are several ways to solve this problem, some of the most useful and practical solutions are listed below as follows.

• If you are an advanced user, this workaround is for you. First and foremost, restart your computer and log on to it as the administrator. Now click on the ‘Start’ button.  Now follow this path: All programs ->Accessories-> System Tools->System Restore. Once you choose to perform System Restore, you will come across options where you can select to ‘Restore your computer to an earlier time’. This option will appear in a new window. Click on it and then click Next. Click on the Next button again that appears in the confirmation window. Restart your computer after the restoration is finished. You have just resolved the error.
• Another easier alternative to fix Error 2032 is for novice users. Download an Error 2032 repair utility. Install this program as you are most likely to come across a Scan button. If there is an option to fix and repair an error, select it after the scan is complete. You can then restart your computer again. Look for the error and you will realize that it has disappeared and that your system is now ready to use.

One of the cool and interesting features in Windows is the Screensaver which allows users to display animation or change the wallpaper automatically when the computer is not being used. This feature can also time out and lock your computer when it remains idle for quite some time. However, if you notice that the screensaver of your computer turns on a lot earlier, then you’ve come to the right place as this post will guide you on how you can change the timeout settings of the screensaver of your Windows 10 computer. Usually, the screensaver in Windows 10 is turned off by default, however, if some other user has turned it on or if you have turned it on, you can actually change the timeout settings of the screensaver using several methods. You can do it through the Personalization settings, Registry Editor, as well as the Group Policy Editor. Before you proceed with the instructions provided below, make sure that you create a System Restore point first. Once done, follow each one of the suggestions carefully to successfully change the Screensaver timeout settings in Windows 10.

Option 1 – Modify the timeout settings of Screensaver via Personalization settings

• Open the Start menu and type “screen saver” in the field.
• On the search results that appear, click on the “Change Screen Saver” option.
• From there, you have the option to change the screen saver type, preview, open settings, change the wait time, as well as choose to display lock screen on your resume.
• Now to change the timeout settings of your screensaver, you have to increase the wait time from 1 to 15 or anything that works for you.
• Once done, click OK and exit to save the changes made.

Option 2 – Try to change the screensaver time via Registry Editor

The next option you can try to change the timeout settings in the screensaver is using the Registry Editor. To get started, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows
• From there, right-click on Windows located in the right pane and select New > Key.
• Name the key as “Control Panel” and right-click on it and select New > Key and then name it as “Desktop”.
• Once done, click on the newly created Desktop key to highlight it.
• After that, right-click on any empty space in the right pane and select New > String Value and then type “ScreenSaveTimeOut” and hit Enter to save it.
• Now right-click on ScreenSaveTimeOut and select Modify and then set its value data in seconds.
• Click on OK and exit the Registry Editor to save the changes made.

Option 3 – Change Screensaver timeout settings via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to User Configuration > Administrative Templates > Control Panel > Personalization.
• Then look for a policy setting named “Screen saver timeout” and double click on it and then click on the Enabled option to enable it.
• Add the screen timeout in seconds and click on the Apply and OK buttons to save the changes.
• Restart your computer.

Note: If you want to disable the screensaver feature in your computer, you can always do so by disabling a policy setting named “Enable Screen Saver”.

What Is Error 126?

Error 126 is a very commonly occurring error that is often the result of damaged system files of Windows. They usually occur during the installation of some Windows program or application. When Error 126 is generated, it terminates the installation process almost instantly. It is important to take corrective measures immediately to ensure that no such problems are encountered again in the future.

Solution

Error Causes

There are a variety of conditions that may trigger Error 126. These conditions are listed below as follows.

• Corruption of the service-related DLL file
• Missing or damage service-related DLL file
• Corrupt, damaged, or Misconfigured system files
• Improper hardware or application installations or uninstallations
• Existence of viruses, malware, adware, or spyware in the system
• Corrupt or incorrect registry entries in the system files

When any of the above-listed conditions occur, the corrupt system files will go to the improper links or missing information. Eventually, the problems with the files will keep the applications or programs from responding in the usual manner. Whatever are the reasons for error generation, it is of utmost importance that the error is removed to ensure smooth functioning of the system.

Further Information and Manual Repair

There are many different ways this error can be rectified. However, the two most effective solutions are listed below as follows.

• This solution is for the advanced user. Turn on the system and log on to it as the Administrator. Now click on the Start button. Now click on All programs -> Accessories -> System Tools. Here you will come across the option for System Restore. Click on it. A new window will appear. Select 'restore my computer to an earlier time' point. Now clock on Next. A list of restore points will now appear in front of you. Choose the latest restore point you come across from this list and click on ‘Next’. In the next window that opens, click on ‘Next’ again. This is the confirmation window. Once the restoration finishes, restart your computer.
• This solution is for novice users. Download an Error 126 repair utility program. Install it on your system. Now use it to scan your system for errors. Find out if there is an option to fix/repair error. When you come across it, click on it as soon as the scan is complete. Restart your computer. Your system is now free of Error 126.

If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:

“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”

 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.

Recently, a number of users reported an error when they tried to open graphic-intensive apps like video games. According to users, when they tried to open an app, they get the “Display driver failed to start” error instead. Thus, if you encounter the same error, then you’ve come to the right place as this post will guide you on how exactly you can fix it. Here’s the full content of the error message:

“Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver.”

This kind of error could be due to several factors. It is possible that it could be a result of a corrupted or outdated graphics driver. Aside from that, it could also be due to some issues with the system settings. Worry not though for there are potential fixes that can help you fix the problem. But before you troubleshoot the problem, you need to update your Windows 10 computer first and if it didn’t help fix the problem, then here are the potential fixes that should help resolve the “Display driver failed to start” error.

Option 1 – Try to restart the Graphics driver

Although Windows 10 can recover the graphics driver on its own when it crashes, there are times when it fails to do its job. To restart the graphics driver in your computer, simply tap the Win + Ctrl + Shift + B key combination. After that, the graphics driver will be back in less than a second.

Option 2 – Try running the Hardware and Devices troubleshooter

Running the built-in hardware and devices troubleshooter can also help you in fixing the “Display driver failed to start” error.

• 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 Keyboard 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 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the “Display driver failed to start” error or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Option 4 – Try setting your system for maximum performance

If the first three options didn’t fix the error, you can try setting your computer for maximum performance since Windows 10 allows you to choose the effects you want to activate your system and you can do this by adjusting the performance ratio. Adjusting the performance ratio can be done via a certain setting in your computer – and this setting should be set to “Maximum Performance” to resolve the error.

• In the Windows Search bar, type in “performance” and from the search results that appear, select the “Adjust the appearance and performance of Windows” option.
• Next, a mini window will appear and from there, click on the radio button that says, “Adjust for best performance”.
• Once done, click on the Apply and OK buttons to save the changes made. This should resolve the problem.

If you have a BlueTooth device on your computer, you know that each time you need to receive or transfer the file you need to find the icon in the system tray, right-click on it and choose the desired option. But there is a simpler solution, create a Bluetooth icon on the desktop so it is always easy to access. Open File Explorer by pressing ⊞ WINDOWS + E Go to C:\Windows\System32 Find fsquirt.exe Right-click on it and choose copy Go to the desktop and right-click, choose paste Rename the file to Bluetooth And, you are done!

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.