Logo

Fix Storport.sys BSOD errors in Windows

As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few.

Here are some of the common Blue Screen errors related to the Storport.sys file:

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

Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:

  • “Improved performance, both in terms of throughput and the system resources that are utilized.
  • Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”

If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:

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

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

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.

  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and right-click on them to open the Properties. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • 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.

Option 2 – Try to recreate the Storport.sys file

If the first option didn’t work, the next thing you can do is to recreate the Storport.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 sys and rename it to Storport.old.

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

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

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 to 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 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

  • Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – 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 Storport.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.

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

Touchpad Set user settings to driver failed
One of the useful things you can use on your laptop is touchpads. They help users in achieving tasks through the gestures and multi-finger tap or touch support it brings in the scope for various shortcuts. However, not all times touchpad brings productivity as it can also encounter some issue every now and then. One of these issues has been reported on a couple of Lenovo laptops that use touchpad drivers from the Alps Pointing Device. According to the reports, an error saying, “Set user settings to driver failed” when they use the touchpad. This type of error on the touchpad usually occurs when a computer boots up and it could be caused by a faulty update on the Alps pointing device driver which is being installed in the background. To fix this error on the touchpad, you could try to disable the Alps pointing device entry from the MSConfig or you could try to get the latest version of the driver or uninstall the driver altogether. Before you proceed with the troubleshooting tips given below, make sure that you create a System Restore point first. Once you have that covered, proceed to the following options.

Option 1 – Try disabling the entry of the Alps pointing device from MSConfig

This first given option was able to fix the problem for many users so to get started, follow these steps:
  • In the Start Search box, type “MSConfig” and select System Configuration from the search results.
  • Next, go to the Services tab and look for the Alps pointing device entry from the list that appears, and uncheck it.
  • Then click the Apply and OK buttons to save the changes made.
  • Now restart your computer and see if the error in the touchpad is now fixed.

Option 2 – Try to download and install the latest version of the driver

The next option you can check out to fix the error is to download and install the latest version of the driver from the official website of Lenovo support. Note that an updated version of the touchpad driver will most likely get rid of the error. However, you have to make sure that the version you’re going to get is compatible with your existing Windows version.

Option 3 – Try to uninstall the Alps Pointing device driver

If the first two given options didn’t work, you can try uninstalling the Alps Pointing-device driver instead. You can do this under the Mice and other pointing devices section. After you uninstall the driver, restart your computer and delete the driver’s leftover folder inside this location in File Explorer (C:/Program Files). Once you’re done, restart your computer and check if the error is now gone. Keep in mind that after you’ve uninstalled the driver, any extra configuration features that Lenovo drivers offered before the uninstallation will no longer be available.
Read More
Moving Taskbar to second monitor in Windows
If you are using a multi-monitor, then you might find it quite useful. It helps many users with their work and brings more productivity. And over the past few years, Windows has managed to offer one of the excellent multi-monitor features where users can plug in an additional monitor and access their work or use their computer seamlessly on both displays. This is really handy, especially for users who are graphic designers, gamers, and other professionals who have to use a larger screen for their work. One of the biggest inconveniences for users who use multi-monitor is that the Taskbar is switched on, on both displays, by default. This default arrangement is most likely to cause clutter on the second display. So if you are one of these users who find such a thing annoying, then you will find this post useful for you as we will walk you through how you can move the Taskbar to a second monitor. To get started, follow the instructions laid out below. Step 1: The first thing you have to do is right-click on the Taskbar. Step 2: Next, uncheck the “Lock the taskbar” option. Step 3: After that, click and hold the taskbar and drag it to the second monitor. Step 4: Once done, click the mouse button on the place where you want to place the taskbar. Step 5: Now right-click on the “Lock the taskbar” option to lock the taskbar. Once you’re done carrying out the steps given above, there are Advanced Options you can explore. This array of advanced options are offered by Windows 10 to fine-tune the multi-monitor experience of users. For instance, you have the option to choose to show the taskbar on an active screen only or combine the buttons on other taskbars. It would be better if you try out different variations and stick with the best one. In addition, you could also move the taskbar from one display to another.
Read More
Blizzard caught destroying evidence
Blizzard employeesCalifornia's Department of Fair Employment & Housing has widened its anti-discrimination lawsuit against Activision Blizzard and claims the publisher has been shredding vital documents relevant to the ongoing investigation. A recent report from Kotaku described the department as offering poorly paid, highly insecure positions, with a culture of hostility towards LGBTQ+ testers. The DFEH's rewording of "employees" to "workers" now hopes to take these contractors' experiences into account. "As a contract employee, I feel there's a lot of pressure to excel, impress, and move through the ranks as fast as you can before your contract ends and you're forced to go 3 months without income or find another job," Axios reports one worker saying. "I take pride in what I do, but it feels like it's never enough." Activision's contentious hiring of union-busting third-party law firm WilmerHale "directly interferes" with its own investigation, it says. By going to WilmerHale, Activision appears to be claiming that all work related to the investigation is privileged and can't be shared with DFEH. The suit also claims that Activision HR shredded documents related to "investigations and complaints", against its legal obligation to retain them during the investigation. The relevant parts of the updated lawsuit were shared by Axios reporters Stephen Totilo and Megan Farokhmanesh, the former also noting that the DFEH "fixed their misspelling of Bill Cosby's name". "DFEH is also informed and aware that documents and records have not been maintained as required by law or by the DFEH's Document Retention Notice," the complaint reads, "including but not limited to documents related to investigations and complaints were shredded by human resource personnel and emails are deleted thirty days after an employees separation."

Speculation and answer from Activision Blizzard

Blizzard employee Jessica Gonzalez suspects that the costs of fines associated with destroying these documents may have been an easier blow for Blizzard to take than any penalties drawn from their existence in helping the lawsuit go through. In an email to Kotaku, Activision denied the shredding allegations and issued a statement outlining steps it had taken to improve company culture—including the ousting of high-level executives like Blizzard president J. Allen Brack. The full statement reads: "Throughout our engagement with the DFEH, we have complied with every proper request in support of its review even as we had been implementing reforms to ensure our workplaces are welcoming and safe for every employee. Those changes continue today, and include:
  •     Several high-level personnel changes
  •     Revamped hiring and recruiting practices requiring diverse interview panels
  •     Greater transparency on pay equity
  •     Expanded and improved training and investigative capabilities for human resource and compliance staff
  •     Created investigation teams outside of business units to support greater independence
  •     Restructured divisions to support greater accountability
  •     Enhanced review processes to include evaluation of managers by employees
  •     Clear boundaries on workplace behavior with a zero-tolerance approach to harassment and other actions that diminish or marginalize.
"We strive to be a company that recognizes and celebrates the diverse talents and perspectives that lead to the creation of great, globally appealing entertainment. We have provided the DFEH with clear evidence that we do not have gender pay or promotion disparities. Our senior leadership is increasingly diverse, with a growing number of women in key leadership roles across the company. "We share DFEH’s goal of a safe, inclusive workplace that rewards employees equitably and is committed to setting an example that others can follow."

California and RIOT

Beyond Activision Blizzard, California's DFEH has also probed into League of Legends creator Riot Games, accusing the studio of dragging its heels over sexual harassment allegations dating back to 2019. Riot denied the allegations, telling us that it "will never retaliate against anyone for talking to any government agency".
Read More
How to Fix athwbx.sys Blue Screen error
Athwbx.sys or the Qualcomm Atheros driver file is known to trigger several Blue Screen of Death errors. This occurs when the driver gets corrupted or when the operating system is unable to access or find it. In addition, bad sectors in the hard disk or RAM can also cause BSOD errors. The athwbx.sys file is known to cause the following BSOD errors listed below:
  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (athwbx.sys)
  • STOP 0x0000000A: IRQL_NOT_LESS_EQUAL (athwbx.sys)
  • STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (athwbx.sys)
  • STOP 0×00000050: PAGE_FAULT_IN_NONPAGED_AREA (athwbx.sys)
  • Your PC ran into a problem and needs to restart. You can search online later for this error: athwbx.sys
Before you proceed with the troubleshooting tips given below, you might want to try performing System Restore as it could resolve Blue Screen errors caused by the athwbx.sys file. To run System Restore, follow these steps:
  • 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.
If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Try recreating the athwbx.sys file

The first thing you can try is to recreate the athwbx.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 sys and rename it to athwbx.old.
Note: As you can see, the file’s extension has changed from .sys to .old.
  • Now restart your computer and check if the athwbx.sys Blue Screen error is now fixed.

Option 2 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time 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.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Run the System File Checker 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.
  • Restart your computer.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the athwbx.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • Wait for the process to be completed and then restart your computer.

Option 5 – Run the Memory Diagnostic Tool

Running the Windows Memory Diagnostic tool in Windows 10 might also help you in fixing the athwbx.sys Blue Screen error. Refer to the steps below on how to run this tool:
  • Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like athwbx.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.
Read More
How to Fix Windows 10 Error 0x800488AB

Code 0x800488AB – What is it?

The Error Code 0x800488AB will appear when a user is in the Windows 10 Mail app and has provided an Outlook.com e-mail address. The mail app will give a message that the “account information is out of date” and it does provide an option to fix the issue. After clicking the Fix button, this error code will show up to the user. Common symptoms include:
  • A dialog box will appear with the Error Code 0x800488AB
  • Microsoft Windows 10 Mail App will not retrieve (or subsequently send) mail
  • User cannot delete and re-add the Outlook email account in the Windows 10 Mail app
  • User can still access and log in to various Microsoft websites, including logging into the Outlook Mail website

Solution

Restoro box imageError Causes

This error can be caused by a few different actions of the user when they have changed a password or a PIN number to access their Outlook mail. This error does have a relatively easy fix after the cause is determined and where the break-in information has occurred. A few of the causes may be:
  • If the user changes their password on the Microsoft website and uses the alternative PIN login method to access the Mail App.
  • The log-in information on the Microsoft website does not match the login information on the Windows 10 App.
  • The login information was changed on the Microsoft website and was not updated to reflect on the Windows 10 Mail app.
The Microsoft website and Microsoft Mail app do not share the knowledge of the change in login credentials, therefore the log-in credentials appear to be incorrect when trying to access the Microsoft Mail app. It should be noted that a user may bypass the password option if they log in to the Microsoft Mail app while using the alternative PIN log-in method, thus still leaving the password undetected.

Further Information and Manual Repair

As is the case with all new technology and having a few wrinkles, the release of Microsoft Windows 10 is not left out. There have been a few discussions of errors and bugs, including Error Code 0x800488AB. As of right now, there are three different methods that can be utilized by any at-home user. These methods are rather simple and make sense when the problem has been identified.

Method 1:

Run the built-in Windows Store Apps troubleshooter:
  1. Press the Windows Key and then type ‘troubleshoot’ and hit Enter
  2. Select “View all” on the left panel and run the “Windows Store Apps” troubleshooter from the list displayed and see if it works.

Method 2:

Use the System File Checker tool to repair corrupted or missing system files:
  1. Click Start.
  2. Type cmd, and then press CTRL+SHIFT+ENTER to open the elevated command prompt (I.e. Command prompt with administrative rights).
  3. The User Account Control window should appear, be sure that the action it exhibits is correct, and then press the Continue button.
  4. Type or copy-paste the below command line into it without quotes:
“Sfc /scannow”

Method 3:

  1. Press the Windows Key
  2. Search for "Credentials Manager"
  3. Click on Windows Credentials
  4. Look for any reference to your windows account (generally your @outlook.com is listed)
  5. Delete them.
  6. Then select your account at the top of the start menu and select Log Out.
  7. If using a Pin Code, switch to type input and put your password into the box.
When you go to Mail, and select "Fix Issues" it will detect your password and your account should sync with new emails. In some cases, depending on why this particular error code was caused, you may have to use a powerful automated tool to have it resolved.
Read More
How to run old applications in Windows 10
Having the latest applications is often preferred for most users but sometimes we have some old applications which have not been updated or simply we just want to run oldie on our computer because it does everything we need and we do not want to upgrade in order to save some money. The issue is presented sometimes when we try to run an old application in Windows 10 and some components are missing in Windows itself or the application is simply coded in a way to work on older Windows versions. If by any chance you have this issue then this guide is for you since we are going to show you how to run old applications in Windows 10. This guide is made in a way to takes into account that the application itself is completely installed on your Windows 10 machine if you can not even install the application you will need to search solution for that particular application since that can not really be generalized and pinpointed issue, every application is different.

Running old applications using the compatibility option

All of that being said, let's start that old app you have. First thing is to locate an executable file or shortcut of the desired application. Once it is located, right-click on it to bring up the menu, and all the way to the bottom you will find properties. Left-click on properties. file properties drop down menuThe application settings screen will open, in upper tabs locate Compatibility and left-click on it. file properties compatibility tab markedAfter the click, you will find yourself in application compatibility settings. File properties compatibility optionsIn this window, you will face different options to run the chosen application in various modes in order to make it run. How settings are self-explanatory and different applications will need different settings sadly we can not cover them all but your safest bet is to run them in an environment where they have worked. For example, if the application was working fine in Windows XP and required administrator privileges, check Run this program as an administrator and Run this program in compatibility mode for Windows XP.
Read More
Switch audio devices in Windows 11 taskbar
windows 11 audio settingsWindows 11 has brought some new features and changed some of the existing ones. One of these changes includes quick switching of audio devices which will play audio. Audio switching can still be done under the taskbar, it is just a little different and one could say even hidden. Follow this quick guide and you will be switching from your headphones to speakers as an example in a matter of seconds.
  1. Click on the speaker icon located in the far-right part of the taskbar.
  2. After the quick settings menu appears click on the right arrow located right of the volume slider. If the arrow is not present, instead of click on the pencil icon, then on add, and finally select Volume from the list.
  3. After clicking on the arrow icon, a list of all enabled audio devices on the system will replace the volume slider. Click on the desired audio device in order to make it active.
  4. Click anywhere outside the quick setting menu to save changes and close it.
Note: in the Quick settings menu if you choose More Volume Settings it will bring you to System > Sound where you can access more sound input and output options.
Read More
Attempt was made to reference a token
If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
    • exe /[DLL file]
    • exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
  • After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

  • First, you need to get the new DLL file from another computer with preferably the same file version number.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • x86: This PC > C:/Windows/System32
    • x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 ntdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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 and hit Enter.
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.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.
Read More
New vulnerability found in Windows
Windows users need to be on high alert. Microsoft has confirmed a critical vulnerability has been found in all versions of Windows which presents an immediate threat, and you need to act now. A critical new zero-day hack has been found which affects all Windows versions. windows vulnerabilityTracked as CVE-2021-34484, the “zero-day” flaw enables hackers to breach all versions of Windows (including Windows 10, Windows 11, and Windows Server 2022) and take control of your computer. Microsoft mistakenly thought it had patched the vulnerability (which was first found in August) when it was publicly disclosed in October. But the fix itself was found to be flawed, something the company admitted, and this drew even more attention to the vulnerability. Microsoft subsequently promised to “take appropriate action to keep customers protected” but two weeks later, a new fix has still not arrived. Luckily the third-party security specialist 0patch has beaten Microsoft to the punch with a ‘micropatch that it has now made available for all Windows users “Micropatches for this vulnerability will be free until Microsoft has issued an official fix," 0patch confirmed. You will need to register for a 0patch account and install its download agent before the fix can be applied, but with 0patch fast becoming a go-to destination for hot fixes which beat software companies to the punch this is a no brainer. Hopes will be high that Microsoft can release an effective patch sooner rather than later but, until then, all Windows users must act now if they want to be safe. Download 0patch here: https://blog.0patch.com/2021/11/micropatching-incompletely-patched.html
Read More
Removing old drivers from Windows 10
So you have just got home from that new computer store with your fancy and all-new mouse, screen, keyboard, etc. You plugged in your new component, Windows detected it, installed drivers for it and it is working like a charm. A few months later down the road and the computer starts little by little to slow down. Plug and play is a great concept, and automatic detection is even greater but how time passes old unused stuff piles in your hard drive and in Windows itself thus slowing down your computer and taxing it more and more as new components and software are added. Old drivers from old components sadly are not removed from Windows itself and over some larger period of time they can pile up and slow down your daily operations on the computer or even cause some problems in it. This guide will teach you how to manually remove old unused device drivers from your Windows so it is fresh and like new again.

Making old devices visible

In order for us to remove old drivers, the first thing we must do is make them visible in our device manager, old drivers are hidden and will not show up, we must make this happen. We do this by pressing WINDOWS + X keys on your keyboard to bring up a hidden menu in Windows. keyboard with windows and x markedOnce the menu appears, click on Command Prompt (admin) Windows menu command prompt adminOnce the command prompt with administrator privileges comes on-screen type in it following string: The device manager will open, go to view > snow hidden devices in order to show unused devices. device manager show hidden devices

Removing old device

Open any category and if there is a device that was once used and still has its drivers in the system it will be shown as faded out. device manager hidden device shownRight-click on the device and click on uninstall device to remove it completely from your system. device manager uninstall device driverPlease always be careful when removing devices so you do not remove the device which is being used by mistake and always double-check that you are removing something that you used to have on your system. This method will show all hidden devices even ones that are hidden but crucial to the system working properly.
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