KVM switch and its usage

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

A command is not recognized Error, what it is? If you are constantly using programs like CMD or DISM directly from the Run prompt, you might have wondered how they launched instantly and how is it that the Windows operating system is able to find them right away. For instance, when you create a shortcut of a program, the shortcut knows where exactly the program is located and launches it quickly. The Windows operating system keeps a list of paths where the most common system programs are located so when you use the Run prompt, it opens easily. The list kept by Windows is called the Windows Environment Variables. If something goes wrong with this list, the programs won’t work. So in this guide, you will be guided on how you can troubleshoot the problem where any command you use is not recognized as an internal or external command, operable program, or batch file. Before you start troubleshooting the problem, you need to make sure that the program you are trying to run really exists. In fact, this can also happen to the Run program which is pulled up using the Win + R shortcut. To check, go to C:\Windows\System32 and there, check if the program exists or not or you can also try searching for the EXE in the System 32 folder. After making sure that the program exists, refer to the instructions given below.

Modify the Windows Environment Variables:

• Step 1: Tap the Win + X keys and then select System. After that, it will open the section where you can see all the properties on your computer.
• Step 2: Next, select the Advanced system setting located on the left pane and click on the Environment Variables.
• Step 3: After that, locate Path under the System Variables and select EDIT.
• Step 4: Before you edit, you need to copy the entire string and paste it into the Notepad app so that in case something went wrong, you can paste it back.
• Step 5: Next, look for the directory path, “C:\Windows\System32”. If you can’t find it, try adding a semi-colon at the end.
• Step 6: Afterwards, click OK to save the changes made and then exit.
• Step 7: Now restart your computer as all the paths are picked up when your computer restarts.

Note: Now all you have to do is to try executing the programs once again – the ones where you got the error, “ is not recognized as an internal or external command, operable program or batch file” every time you open them and then see if you can now open these programs or not.

Modem Error 633 error is a dial-up error that usually occurs when using a USB modem with a Windows computer. The Modem Error 633 error message is displayed as the following:

“Error 633: The Modem is already in use or not configured properly.”

Solution

Error Causes

This error can be triggered due to several reasons such as:

• A software program conflicts with the USB modem
• The modem is not configured properly
• The Telephon.ini file is missing or damaged
• There is some issue with the way Windows is managing the communication (COM) ports on your computer.

Further Information and Manual Repair

If you experience the Modem Error 633 on your PC, you don’t have to panic. Though this error does not pose any major threats like data loss, it may hamper your ability to use the internet therefore it is advisable to resolve the error. Repairing the Modem Error 633 is quite easy. There are a number of ways to fix this error. So, let’s get started:

Solution 1: Delete Incompatible Software and Non-Present Modems

• Click on the start menu and go to the ‘Control Panel’. Now choose the option ‘Phone and Modem’.
• Here you will see three tabs, the dialing rules, modems, and advanced. Choose the tab ‘Modems’. As you click on it, you will see modems installed on your PC. To repair the Modem Error 633, select and remove all the incompatible software and modems that are not present and click ‘OK’.
• Now to bring the changes into effect, restart your system with the modem plugged in and try connecting to the internet again.

Solution 2: Change the Communication Ports

If the error occurs because the modem is not properly configured, then this solution is possibly the best way to resolve this error. Here’s what you need to do:

• Click on the Start menu and choose My Computer.
• Now click on the option ‘Manage’ to open the Computer Management Window.
• Once it opens, click the option ‘Device Manager and then expand the option modems. Click on Properties, then the Advanced tab, and the Advanced Port Settings button.
• As you click on the Advanced Port Settings, then click on the COM Port Number drop-down box.
• Choose a new Communication Port. However, make sure it is not already in use.
• Once you make changes, click ‘OK’ and then restart your PC.
• Now Open Device Manager again. Open the Modern Properties Window and then Click the Diagnostics tab.
• After that view the command response window to verify if the error is fixed. If yes, then create a new dial-up connection and connect to the internet with ease.

Solution 3: Disable the Startup items

• Another way to resolve Modem Error 633 on your PC is to go to the start menu and type ‘msconfig’ into the search box and then press ‘enter’.
• Open the misconfig.exe program. As you open it, you will see 4 tabs, General, Boot, Service, Start-up, and Tools.
• Now click on the ‘Start-up’, ‘Disable All’, and then press Apply.
• After you press Apply, a window will pop up asking to restart the computer.
• Confirm it and click restart.
• Once the computer restarts now try connecting to the internet again. This will hopefully resolve the Modem Error 633.

Program and features are Control panel section where once accessed contains all programs installed on the operating system. From these windows, any logged-in user can modify applications, uninstall them, etc. If for whatever reason you want to limit this access to users and remove this group from the control panel please do keep reading as we show you how you can achieve this desired result using two methods: via policy editor or registry editor. Feel free to use any provided method as both works (except on Windows 10 Home edition) and achieve the same thing, it all comes down to preferred preference on how you wish to do things.

Local group policy editor method

This method is more straightforward and easier perhaps than its counterpart but it has one significant drawback, it will not work on Windows 10 Home edition which does not have in itself a policy editor included. If you are using Windows 10 Home edition then feel free to skip this method and do it via registry editor. That being said let's start:

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in gpedit.msc followed by ENTER to open Group policy editor
• Go to User Configuration\ Administrative Templates\ Control Panel\ Programs\
• Double-click on the setting named Hide Programs and Features page
• Change the toggle option from Not Configured to Enabled
• Click on the Apply button and then the Ok button to save the changes
• at this point, everything is supposed to be applied and your changes should take effect immediately. However, it has come to our attention that sometimes this is not the case. If you are one of these users which for whatever reason have not experienced applying to set momentarily do not despair and follow this quick guide on how to refresh settings and apply them right away.
• Press ⊞ WINDOWS + X to open the hidden menu
• Click on command prompt (admin)
• In command prompt type in gpupdate /force and press ENTER in order to force update and set setting right away

Registry editor method

The registry editor method is a more complex one but it will be your only way of doing it if as mentioned you are running Windows 10 Home edition. As always it is highly recommended to make a backup of the Windows registry before tempering with it.

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in regedit and press ENTER to open the registry editor
• If you would like to make a backup of the Windows registry go to File > Export and save the backup on a secure location naming it as you wish
• Locate the following key inside the registry editor HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Programs
• Right-click on the right pane of the Programs key and choose the New > DWORD (32-bit) Value option
• Name the value as NoProgramsAndFeatures
• Double-click on the NoProgramsAndFeatures value to open it
• Change the value data to 1
• Save the changes
• Reboot the computer in order for changes to take effect.

note: you can always change values back in order to show again panel by changing the value to 0 in registry editor or choosing Not Configured or Disabled in the local group policy editor

Skinning of applications is not new to PC users, but did you knew you could skin Steam? With skin, you can customize the UI and style of the client to what you want making it more personal and to your liking. First thing is to find the skin that you would like to install. There are a lot of sites where you could find custom made Steam skins but we would recommend steamskins.org The site itself is organized in tabs with different sections, once you click on the tab you will get a list of skins available for chosen section. If you click on the skin you will be taken to skin page detail where you can find what skin is aiming for, its legibility, a record of how the skin has been altered over time, or some mix of these aspects. Note that some skins might have issues like some buttons might be missing from big picture mode but so far none of the skins has any kind of client breaking feature, only functionality one.

Downloading skin

Once you have chosen desired skin and while on the skin details page, scroll to the middle of the page just above the Related Skins sections with two options: Direct Download and External Download. Now usually I would recommend Direct download but in this case, I would advise going with External Download for the simple reason that the External link will send you to the developer's website where there is a higher chance to get the latest updated skin.

Installing it in Steam

Once the skin is downloaded you will first need to create a skin folder inside your Steam installation location. Navigate to your Steam installation folder (default: C:\Program Files (x86)\Steam) and create a new folder inside it. Give new folder name Skins and confirm. Extract the skin zip file in the newly made folder. Once the file is extracted you can delete the ZIP file if you wish. Go to your Steam client and go to Steam>Settings. In settings select Interface on the left bar and on the right part then click the Select the skin you wish Steam to use the drop-down menu and select the skin that you wish to use. Confirm and restart your Steam client

Reverting to old skin

If you found skin unappealing or, unfortunately, has some functions missing you can always choose another skin or revert back to default Steam skin. Default Steam skin is named in the drop-down menu as < default skin >.

What is the Error 421?

Error 421 is a common SMTP (Simple Mail Transfer Protocol) Outlook error message. MS Outlook is one of the best and popular email applications widely used by PC Windows users for sending and receiving emails within and outside workplaces. It is most commonly used in offices by professionals for faster communication. This error may occur while sending and receiving emails on the server. The error 421 messages is displayed in either of the following formats:

“An unknown error has occurred: Server error 421” "Could not send your message. Error 421" 421 4.2.1 : (DYN:T1) http://postmaster.info.aol.com/errors/421dynt1.html 421 4.3.1 Out of disk space for temp file 421 4.3.2 All server ports are busy 421 Downstream server error 421 Fork failed 421 Greylisting enabled, please try later “An unknown error has occurred. Subject ‘Testing’, Account: ‘pop.charter.net’, Server: ‘mail.charter.net’, Protocol: SMTP, Server Response: ’421 Message rejected’, Port: 25, Secure(SSL): No, Server Error: 421, Error Number: 0x800CCC67”

Solution

Error Causes

Some common causes for this critical Outlook error are:

• PST storage size exceeds 2GB file size
• Improper ISP settings
• Slow internet connection
• PST file corruption
• Trojan attack and viral infection

This is a critical Outlook error that should be resolved timely. If you delay, it may cause you a great deal of inconvenience. The error code 421 hampers your ability to access your email account, send and receive emails, add new contacts, view emails, calendar entries, and journals. In other words, it just brings your email activities to a standstill locking you out of the account.

Further Information and Manual Repair

To resolve this error code on your system, you don’t always have to hire a professional or call the network personnel to do the job. It may be a critical error but the good news is that it is quite easy to fix. Even if you don’t have technical expertise, you can still repair it. Here are some of the best methods to repair this issue on your system:

1. Change the Server Settings to its Maximum Limit

Try changing your server settings. Here set the inbound connections limit at the maximum limit.

• To do this, open the Microsoft Exchange Server Administrator utility. The access path of this utility will vary depending on the installation procedure used to set up Exchange Server.
• Once you open the MS Exchange Server Administrator utility, click the ‘Connections’ icon in the left side navigation pane. Now double click the internet mail service icon in the right side pane. As you click it, the Properties window will open.
• Now click the ‘Connections’ tab in the Properties window and then click the ‘Advanced’ button. This will open the configuration window.
• Here reset the number for ‘Maximum Number of Inbound Connections’ to a high number, its maximum limit. After changing the settings, close all open Exchange Server Administrator program windows to successfully complete the process.

After the process is complete, try accessing your Outlook email account again; if it works, then that’s great the error 421 is resolved. However, if it doesn’t, then the problem could be related to viral infection.

2. Download a PST Repair Tool

If the cause of the error is PST files corruption, then not only will you be locked out of your email account, you are also at risk of losing all the data stored in your email account. However, the best way to resolve the error and ensure full data recovery is to download a reliable PST repair tool. By running a PST repair tool on your system, you can resolve the error 421 right away. It recovers your data, repairs corrupt and damaged PST files.

3. Scan Your PC with Restoro.

If viral infection and Trojans are causing the error 421 to pop up on your system, then it is recommended to download and scan your PC with Restoro. This is an advanced, intuitive, and user-friendly PC fixer. It is not just an antivirus but also a system optimizer and a registry cleaner. Unlike common antivirus software that only removes viruses and simultaneously slows down the system’s speed, Restoro removes all types of malicious software on your PC including malware, spyware, Trojans, and viruses, and also boosts the speed of your PC significantly. It is safe, easy to operate, and a quick fixer. It is compatible with all Windows versions. Click here to download Restoro and resolve error 421 today!

Blue Screen of Death errors or Stop errors are indications that something’s wrong with your computer. So when you encounter one, you must find out what the root cause of the problem is before it gets out of hand. One of the BSOD errors you might encounter on your Windows 10 computer is the “DRIVER IRQL NOT LESS OR EQUAL or SYSTEM THREAD EXCEPTION NOT HANDLED, Netwtw04.sys failed” error. As you know, system files or .sys files are some of the essential parts of the Windows operating system. It is a repository of system driver settings used by the Windows operating system in order to communicate with the connected hardware and devices. They are essential for the normal functioning of the operating system. A lot of Windows 10 users are facing this particular Blue Screen of Death error whenever they open an app or disconnect external devices from the system. The Netwtw04.sys file is a part of the Intel PROSet/Wireless Wi-Fi software. And so when you might encounter two kinds of Stop errors for the Netwtw04.sys driver file such as:

1. “DRIVER_IRQL_NOT_LESS_OR_EQUAL What failed: Netwtw04.sys.” – This kind of error message signifies that a kernel-mode driver tried to access pageable memory at a process IRQL that was too high.
2. “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED What failed: Netwtw04.sys” – This error message indicates that the root cause of the error might be incompatible drivers with the operating system. In general, the root cause of the Netwtw04.sys BSOD error might be due to several reasons such as corrupted files, incorrect device driver configuration, malicious programs, outdated drivers, bad drivers, corrupted Windows Registry as well as some damaged or corrupted system files.

Whichever of the two error messages you got, you can try the troubleshooting options given below to fix the “DRIVER IRQL NOT LESS OR EQUAL or SYSTEM THREAD EXCEPTION NOT HANDLED, Netwtw04.sys failed” BSOD error.

Option 1 – Try to rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
• Then select each one of them and double-click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
• Now restart your computer to successfully apply the changes made.

Option 2 – Try to update the Network drivers

If the present Network driver is giving you a headache that is the “DRIVER IRQL NOT LESS OR EQUAL or SYSTEM THREAD EXCEPTION NOT HANDLED, Netwtw04.sys failed” BSOD error, then you need to update the Network drivers. To do so, here’s what you have to do:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 3 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Netwtw04.sys failed BSOD error. 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.

Option 4 – Run the DISM Tool

The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• The DISM command you entered will repair the corrupted system image. Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Run the CHKDSK Utility

Running the CHKDSK utility might also help you resolve the Netwtw04.sys failed BSOD 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.

As you know, Microsoft Edge is the default web browser in Windows 10 operating system. It is a built-in browser that replaced the ancient Internet Explorer for its performance and features. Aside from being the default web browser, it is also set as a default PDF viewer in Windows 10. So if you open a PDF file, it will be automatically opened in the Edge browser even if you have installed a PDF reader on your computer. However, some users recently reported getting an error that says, “Couldn’t open PDF in Edge, Something’s keeping this PDF from the opening” when they tried to open a PDF file or view an internet link that has a downloadable PDF file in the Edge browser. If you are one of these users, read on as this post will help you troubleshoot the problem and fix it. This kind of error mostly occurs if you have installed other PDF viewers on your computer. They could be interrupting Edge while it tries to open the PDF documents. To fix it, check if Microsoft Edge is set as the default PDF viewer or you could also try to clear its browsing cache. In addition, you could also reset or repair Edge. For detailed instructions, refer to the given options below.

Option 1 – Check if Microsoft Edge is set as the default PDF viewer

The first thing you can do is to check if Edge is set as the default PDF viewer. If it’s not, you have to set it as one to fix the problem.

• Open Control Panel and go to Default Programs.
• Then click on the “Associate a file type or protocol with a program” option.
• Next, select the PDF file option and click on Change program.
• After that, select Microsoft Edge in the pop-up window and then select the “Always use this app to open .pdf” option.
• Now click the OK button to set Edge as the default PDF viewer and then check if you can now open the PDF file in the Edge browser.

Option 2 – Clear the browser cache of Microsoft Edge

• Open Microsoft Edge.
• Then click on the three horizontal dots to open the menu.
• From there, click on Settings. And under Settings, click the “Choose what to clear” button under the Clear browsing data section.
• Next, check all the checkboxes and then click the Clear button to clear the browsing data in the Edge browser.
• Restart Edge.

Option 3 – Reset, repair or reinstall Microsoft Edge via Settings

You can reset, repair or reinstall the Edge browser through Settings. If none of it helped, you can try the following:

• Open File Explorer and then go to this path – C:/Users/YourUsername/AppData/Local/Packages

Note: Before you type in the path in the Address bar, make sure that you put your user account name in place with the “YourUsername”.

• Tap Enter to proceed.
• Next, look for the folder named “MicrosoftEdge_8wekyb3d8bbwe” then right-click on it.
• Click on Properties and uncheck the option “Read-only” under the General tab in the Properties window.
• Click on Apply and then OK to save the changes made.
• After that, look for the MicrosoftEdge_8wekyb3d8bbwe folder again and delete it. And if a prompt stating “Folder Access Denied” appears on your screen, just click on the Continue button to proceed – doing so will delete most of the content inside the folder except for the folder named “AC”.
• Restart your PC.
• Now all you have to do is to re-register Microsoft Edge using PowerShell. In the Start Menu, search “Windows PowerShell”.
• Right-click on Windows PowerShell from the search results and select the “Run as administrator” option.
• Type in this command in the PowerShell windows and tap Enter – Cd C:/Users/YourUsername

Note: Once again, make sure that you key in your user account name in place of “YourUsername.

• After that, type in this command and tap Enter – Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml" -Verbose}
• Restart your PC.

This post will walk you through fixing the rtwlane.sys Blue Screen error. This kind of BSOD error belongs under the category of the “DRIVER IRQL NOT LESS OR EQUAL” Stop errors. If you encounter this kind of Stop error then it means that a kernel-mode driver tried to access pageable memory at a process IRQL that was too high. The main issue with the rtwlane.sys Blue Screen error has something to do with the Realtek PCI-E Wireless LAN PCI-E NIC driver. In other words, it has some issues with the wireless card of your computer which is built by Realtek. And since it this error concerns your wireless card, you might also experience some connectivity problems with your computer as the wireless card refuses to find any network connections and even randomly disconnects. To resolve this problem, you need to refer to the given options below.

Option 1 – 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 rtwlane.sys Blue Screen error. 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 2 – Try to update or rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.

• Realtek High-Definition (HD) Audio Driver
• Realtek Card Reader Driver
• Realtek Local Area Network (LAN) Driver

On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.

• Open the Device Manager again and then look for Network Drivers.
• Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the Realtek driver.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Netwtw04.sys failed BSOD error. 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.

Whether you’re using Windows Update or upgrading or installing on your Windows 10 computer, you can’t really tell if things will go smoothly as there are times when you might encounter some issues that prevent you from completing the update or upgrade or the installation. One of the errors you can encounter is error 0x80070057. Usually, when you receive this error, it means that one or more arguments are not valid. You can encounter this error in the following cases:

• Windows Update, Upgrade, or Installation
• Windows Backup, The parameter is incorrect
• Partitioning a Disk
• System Image Restore error 0x80070057
• Downloading Windows Store apps

Keep in mind that the troubleshooting steps you need to take will depend on the scenarios you are in. Thus, you need to go over each one of the troubleshooting options given below and make sure to carefully follow each one of them but before you proceed, you have to create a System Restore Point first.

Option 1 – Run the Windows Update Troubleshooter

The first thing you can do to fix error 0x80070057 is by running the Windows Update Troubleshooter. It is a built-in tool in Windows that helps users resolve any issues with Windows Update. All you need to do to run it is go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 2 – Use the Registry Editor

If you get the error 0x80070057 during Windows Backup, then you need to make some modifications to the Windows Registry. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftSystem

• Then create a new DWORD value and input “CopyFileBufferedSynchronousIo” as its name and put “1” as its value.
• Close the Registry Editor and restart your computer then check if the error is fixed or not.

Option 3 – Run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Note: If it happens that the Windows Update client is broken, you need to run the following command to repair it then restart your PC and click on Update once again.

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 4 – Flush the contents of the SoftwareDistribution folder

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

Option 5 – Reset Windows Store Cache

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.

Option 6 – Run SFC scan

Running the SFC scan or System File Checker might also help in fixing error 0x80070057.

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