Keyboard shortcuts and hotkeys are not working

If you have a USB that has stopped working and does not show any signs of life do not throw it away just jet. Hello and welcome to another great tutorial on errortools.com, today we will explore how to bring back to life dead USB memories.

Detect a Corrupted  Drive:

If your computer is still able to detect your USB drive, you might want to know if it’s been corrupted. Select the Properties of the drive folder and check the device status. If it says This device is working properly this USB drive is worth saving. There’s no need to worry if you can’t see the USB drive folder.

Erase the USB Drive with Diskpart Tool

Press ⊞ WINDOWS + X top open start menu and choose Command prompt (admin) Type diskpart and press ENTER Type in list disk and press ENTER Locate your USB drive by size and type in select disk#, where # is the number of removable disks.

Reallocate the USB Drive Volume

Press ⊞ WINDOWS + R to open the run dialog and type in diskmgmt.msc Select the USB drive and Right-click on it and select create simple volume. It will lead to a new simple volume wizard window. Once you click next, you can specify the volume size for the pen drive. Select the maximum volume, which is shown as a default unit in MB. As soon as you see the next step, select assign drive letter which will help you view your pen drive once again. Format the partition in the next step. This may be just an extra step because you have already wiped the data clean. But it is always better to be sure. Click Finish to complete the new simple volume wizard which will now be allocated to the USB drive. After you reallocate the unallocated USB drive space, you will be able to view the USB drive storage once again.

If you have a dual monitor setup on your Windows 10 computer and you mostly use the second screen when you are presenting something, this makes the Taskbar completely unnecessary and is not really required. So if you are using your computer generally and do not want the taskbar on your second screen, read on as this post will guide you in disabling Taskbar on your second display. The good thing is, Windows comes with a built-in feature to disable Taskbar on your second screen or projector connected to your computer. In this post, you will be guided on how you can hide or disable the Taskbar from the second monitor in Windows 10. This post is coming in handy especially if you are using projectors or multiple displays. Refer to the steps given below to disable Taskbar on the second display in Windows 10. Step 1: Go to Settings and click on Taskbar from the left menu. Step 2: After that, scroll down to lo look for Multiple Displays. Step 3: Next, turn off the toggle labeled, “Show taskbar on all displays”. Note: After completing the steps given above, it will disable the Taskbar on all the secondary displays. Bear in mind that these settings will work only if you are running a second screen in Extended mode. Contrariwise, if you are in the Duplicate mode, this setting will not work but you can always set your Taskbar to Autohide so that it won’t be displayed.

On the other hand, if you are facing some issues in finding which screen is primary and which one is secondary, refer to these steps:

Step 1: Go to Settings and select System. Step 2: Next, from the left menu open Display. Step 3: From there, select the desired display and make it the primary one as required by your setup.

There are times when an IT admin has to set up multiple IP addresses to the same network adapter. Setting up multiple IP addresses in scenarios like hosting various SSL sites, speed up traffic exchanges can help in avoiding being blacklisted in the SPAM filters, and so on. So in this post, you will be guided on how exactly you can assign multiple IP addresses to the network adapter in your Windows 10 computer. There are several ways to assign multiple IP addresses in a network adapter. You can do it using the Network Adapter settings or using the Netsh utility, as well as the Windows PowerShell utility. To get started, refer to each one of the options provided below.

Option 1 – Assign multiple IP addresses via Network Adapter settings

• Go to Settings first and from there, select Network & Internet, and then click on the Change adapter options. This will show you a list of both the physical and virtual network adapters in your computer.
• Next, double click on the Ethernet adapter where you want to assign the multiple IP addresses and then click on the Properties button.
• After that, you should see the Ethernet properties where you have to select the “TCP/IPv4” or “TCP/IPv6”.
• Once done, click on the Properties button and then select the “Use the following IP address” option under the General tab.
• Now you have to add an IP address, subnet, and default gateway to the network adapter and then click on the Advanced button.
• This will open the Advanced TCP/IP settings where you have to click on the Add button so you can add an IP address. From here, you can keep adding multiple IP addresses to the network adapter. You also have the option to add multiple gateways or DNS IP addresses.
• Once done, if you execute the “ipconfig” command, you should see all the secondary IP addresses listed.

Option 2 – Assign multiple IP addresses using the Netsh command

Another way to assign multiple IP addresses to your network adapter is via the Netsh command.

• In the Start Search, type “command prompt” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” to open it with admin privileges.
• If a User Account Control or UAC prompt pops up, just click on Yes.
• After that, run this command: Netsh int ipv4 add address name="Local Area Connection" 192.168.100.100 255.255.255.0 SkipAsSource=True

Note: You have the option to set “SkepAsSource” since it depends on your needs using the Netsh command. When it is configured as true, the IP address won’t be used by the OS for outbound connections.

Option 3 – Assign multiple IP addresses via Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option.
• After opening Windows PowerShell as admin, use the NetIPAddress command so you can add more IP addresses. Execute this command: Get-NetIPAddress | ft IPAddress, InterfaceAlias, SkipAsSource
• Next, assign an IP address to a network adapter by executing this command: New-NetIPAddress –IPAddress 192.168.100.100 –PrefixLength 24 –InterfaceAlias “vEthernet” –SkipAsSource $True
• Now to modify the “SkipAsSource” parameter, use this command: Get-NetIPAddress 192.168.100.100 | Set-NetIPAddress -SkipAsSource $False

If you have received a BSOD error message that says, “Tcpip.sys”, read on as this post will show you how you can fix the problem. The “Tcpip.sys” means Transmission Control Protocol over Internet Protocol. It is a library of a set of rules that are used to interconnect different devices all over the internet. The Tcpip.sys file is a driver and if a BSOD error message includes this one, it could only mean that the driver file is corrupted or incompatible with your system or there are some conflicting programs installed in your computer. To fix this error, you can try the following workarounds. Make sure to carefully follow each one of them.

Option 1 – Check for conflicting or incompatible programs by putting your PC in a Clean Boot state

As mentioned, the “tcpip.sys” BSOD error might be caused by some problematic programs that clash with your existing operating system. Several users reported that numerous programs that are supposedly designed to enhance computer performance are causing conflict in the system instead. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• 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” checkbox 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” checkbox.
• 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.)

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

Option 2 – Disabling Antivirus Software

There are cases when the “tcpip.sys” BSOD error is caused by the antivirus program installed in your computer that’s blocking some essential operations. Because of this, the operating system fails which throws up the BSOD error. As you know, the antivirus program is designed to protect the computer and monitor every action in the system. However, there are instances when the antivirus program gives false positives and shuts down some modules even if it’s harmless. So this could be the case for the “tcpip.sys” error. To verify if the problem is indeed caused by the antivirus program in your computer, you need to temporarily disable it. After you’ve disabled it, restart your PC and then check if the problem’s fixed or not.

Option 3 – Try to update all your Drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the “tcpip.sys” BSOD error. To fix the problem, you need to update all your drivers especially the network driver since the “tcpip.sys” error is closely related to this driver. Follow the steps below to update your drivers.

• 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

Most scrollbars are hidden by default if they are not used in Windows 11. If you are not ok with this feature and want scrollbars to be always visible and available do not worry, turning them ON is very easy.

• Press ⊞ WINDOWS + I to open Windows settings
• Click on Accessibility in the sidebar
• Select Visual Effects
• Inside visual effects settings find Always show scrollbars and switch it ON

Windows 11 will save settings automatically and apply setting right away. Close settings and continue with work.

The TWCU.EXE or TP-LINK Wireless Client Utility is a configuration application required to run wireless adapters successfully. The TP-LINK Wireless Client Utility application only exists on computers that are using the TP-LINK adapters. Upon the installation of this application, the service will be automatically added to the Windows service list that will continuously run in the background. The Twcu.exe is placed at the C:\Program Files\TP-LINKTP-LINK\Wireless Utility folder and is used by TP-LINK to connect to the internet. The name of the main executable file is twcu.exe and can be viewed in the Services tab of the Task Manager. If you are one of the users who just upgraded to Windows 10 from the previous Windows versions, then you’ll most likely see an error saying, “Failed to load the library file!” that has something to do with twcu.exe or TWCU. This error pops up when you go to your desktop and every time you log into your Windows 10 PC. Like pointed out, this error is related to the TP-LINK Wireless Client Utility and every user who is using the TP-LINK Wireless Client Utility is experiencing this problem which may be due to some compatibility issues especially when you start getting this error right after you upgraded to Windows 10. To fix this problem, follow each one of the options given below.

Option 1 – Try running in Compatibility Mode

The best thing you can do is to run the TP-LINK Wireless Client Utility in the compatibility mode since the problem is due to some compatibility issue. To run this utility in the compatibility mode, here’s what you have to do:

• Look for the TP-LINK Wireless Client Utility which should be located on your desktop.
• Once you find it, right-click on it and select Properties from the context menu.
• After that, go to the Compatibility tab and mark the checkbox for “Run this program in compatibility mode for:” and from the drop-down list, select either Windows 7 or Windows 8.
• Click the Apply button and then click OK to save the changes made and check if it has resolved the issue or not.

Option 2 – Try troubleshooting compatibility

This option is almost the same as the first one except it is an alternative way of fixing the TP-LINK Wireless Client Utility in case the first one didn’t work. In this option, you will troubleshoot the compatibility issue of the TP-LINK Wireless Client Utility.

• Look for the TP-LINK Wireless Client Utility which as mentioned, is on your desktop.
• Then right-click on it and select the “Troubleshoot compatibility” from the context menu.
• After that, click on the “Try recommended setting” option. Once the process is done, the error message should be gone.

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.

Signing in to a computer that runs a Windows 10 version OS is usually fast and straightforward. However, there are instances when signing in takes too long especially if there are a lot of programs in the Startup. So if many things are loading as soon as you log into your computer, it will slow down the sign-in process. Aside from programs in Startup, it is also possible that there are too many users that are logged in to the account. In such a case, you will most likely encounter an error that says, “Your computer is running low on resources, so no new users can sign in. Please use an account that has already been signed in”. If you’ve encountered such an error when you try to log into your computer, read on as this post will be guiding you on how you can fix it. Each time a user signs in to Windows 10, it will allocate resources in order to work smoothly. But, in many cases, the system is running low on resources which is why this error pops up and blocks a sign-in of a new user. To fix it, you can try to log out the existing users, or perform a Cold Boot, as well as run both the DISM tool and System File Checker scan.

Option 1 - Try to logout existing users

The first thing you can do is to log out the existing users. If you have a shared Windows 10 computer, you have to check if someone hasn’t logged out. It could be that some background task or there is an existing program that is still running under that account. So you have to make sure to ask the same user to log out in case there is some unsaved work. On the other hand, if that user is not around, then you reboot the computer right away.

Option 2 - Try Performing a Cold Boot

You could also try to perform a Cold Boot to fix the problem. A Cold Boot is a process that makes sure that the Windows 10 Kernel shuts down properly and releases all the resources held by any account. To perform a Cold Boot, just press and hold the physical power button on your CPU until it goes off. After that, boot your computer regularly and see if you can now log into your account without any error.

Option 3 - Try to run a System File Checker scan

System File Checker is a built-in command utility in Windows that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you log into your computer. To run the SFC command, follow the steps given below.

• Boot your computer into the Advanced Recovery mode and from there open Command Prompt.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer and see if the problem is fixed or not.

Option 4 - run the dism tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “Your computer is running low on resources, so no new users can sign in” error. To repair these corrupted system files, you can run the DISM commands:

• Go to the Advanced Recovery mode and select Command Prompt.
• 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 problem is now fixed.