There are times when you might find it difficult to delete folders or files in File Explorer and it could be due to many reasons. One of these reasons can be attributed to the failure that can lock down the folders or files which prevents you from deleting them. In this kind of situation, you can utilize the Command Prompt to delete the folders, sub-folders, and files on your computer, and in this post, you will be guided on how exactly you can do that. Before you proceed, keep in mind that when you use the Command Prompt incorrectly, it might affect your computer and render it inoperable, thus, you must be extra careful when executing the steps given below and it would also be better if you create a System Restore Point. After that, refer to the following instructions. Step 1: First, in the Start Search, type “command prompt” in the field and from the search results, right-click on Command Prompt and then select the “Run as administrator” option to open Command Prompt with admin privileges. Step 2: After opening Command Prompt as admin, navigate to the folder where the file you want to delete is located. Note that you have to execute the “cd” or the change directory command. Step 3: Next, execute the following command in Command Prompt:

DEL /F /A <file path with extension>

Note: In the given command, “/F” is the force delete command, while “/A” is the command that selects the files with the ready for archiving attribute. Step 4: After that, go to the location where you can find the folder you want to delete by using the “cd” command again. And then execute the following command right after:

RD /S <folder path>

Note: In the given command, “RD” is the command that removes the folder from the directory, while “/S” removes all of its sub-folders and files. On the other hand, if you also use the “/Q” parameter, you won’t see the “Y/N” confirmation but if you didn’t use it, then simply tap the Y button to proceed.

The Windows 10 operating system supports the logging in of multiple users at the same time. Aside from that, it also allows administrators to create a Guest Account that has limited rights. However, there are some instances when you could encounter an error when you use the Guest Account. The error may state:

“Shell Infrastructure Host has stopped working. A problem caused the program to stop working correctly. Please close the program”.

This error indicates that the Shell Infrastructure Host or SiHost.exe process that is used for handling graphical elements, has crashed. And to fix this error, there are several options you can check out. You can try to reinstall the Microsoft Redistributable Packages or run a System File Checker scan. In addition, you can also use a new Guest Account or troubleshoot the problem in a Clean Boot State.

Option 1 – Try to install or repair Microsoft Visual C++ Redistributable 2013

A corrupted Microsoft Visual C++ Redistributable package or the absence of it can trigger the “Shell Infrastructure Host has stopped working” error – so if you do not have this package yet, you have to install it but if you already have it, follow the steps below to repair it.

• Open Control Panel and proceed to Program and Features.
• Under Programs and Features, look for Microsoft Visual C++ Redistributable package among the list.
• Then right-click on it and click the Change button.
• Next, you should see the Repair option – click on it to repair the installation of the Microsoft Visual C++ Redistributable package.
• The process may take a couple of minutes before it finishes so once it does, you have to restart your PC.

After doing all these steps and you still encounter the problem, you might have to uninstall this package and download it directly from Microsoft’s website. However, if you are using Windows 10, you might not be able to do so since it only supports Windows versions up to Windows 8.1 so just proceed to the next option below.

Option 2 – Try to run a System File Checker scan

• In the Windows Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, type the “sfc /scannow” and tap Enter to execute it.
• Once the scan is finished, restart your computer and see if the Windows Script Host error.

Option 3 – Try using a new Guest Account

You might want to use a new Guest Account as it could help get rid of the error. All you have to do is have your admin delete the old Guest Account and create a new one and see if it helps in fixing the error.

Option 4 – Try troubleshooting the problem in a Clean Boot State

Setting your computer in a Clean Boot State can help you diagnose and later troubleshoot the problems in your computer. During this state, the system will start with a minimal number of drivers and startup programs that help in isolating the problem with the interfering software. To put your computer in a Clean Boot State, follow the given steps below.

• Log onto your computer as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

A guide to fixing Error Code 80070490

Error Code 80070490 - What is it?

This error 80070490 code may occur when you try to update your PC either through the Microsoft Update website or with a Windows update. The error message is displayed in the following format:

Error 80070490 (Element not found)

Solution

Error Causes

Error Code 80070490 is triggered because of a couple of reasons. It indicates the file CBS Manifest that is needed to install Windows update is corrupt or damaged. CBS (Component Based Servicing) Manifest is the file that is used to help your computer recognize various components inside your PC. Another reason for error occurrence is registry corruption. If the registry that stores all the information and activities performed is not cleaned frequently, the obsolete files saved in the registry like the junk files, bad entries and cookies eventually accumulate and corrupt it thereby generating such error codes.

Further Information and Manual Repair

Here are some effective and proven methods that you can try by yourself to resolve error code 80070490 on your PC.

Method 1 - Use the System Update Readiness Tool

Download the System Update Readiness Tool from the Windows website and run it on your PC. This tool is designed to detect and scan for abnormalities and inconsistencies that could be preventing and causing problems during the system update. Once you have downloaded and scanned your PC, try to install the updates again. If the error still persists, try other methods illustrated below.

Method 2 - Repair Windows

Here are the steps that you need to follow to repair Windows:

• First, close all programs and then reboot your PC. Insert the Windows DVD into the computer’s disk drive and wait for the setup to begin.
• If for any reason, the setup doesn’t start automatically, then don’t worry simply click start, then type Drive: setup.exe in the search box. Please note, in the drive insert the letter of your computer’s DVD drive for example D:setup.exe.
• Now in the programs list, click setup.exe  And then click install now.
• After that click ‘go online to obtain the latest updates for installation’, if you are asked for the Windows Product Key, then simply type it to proceed.
• In the ‘Which kind of Installation do you want?’ option, click Upgrade.

When the Windows installation is complete, restart your PC and then run Windows update.

Method 3 - Clean the Registry

If the cause of error code 80070490 on your PC is related to registry corruption, then it is advisable to download Restoro. This is an advanced and easy-to-use PC Repair Tool embedded with a registry cleaner. The registry cleaner scans your entire PC, removes all obsolete and unnecessary files corrupting the registry, and cleans it right away. Click here to download Restoro to repair error code 80070490

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.

If you are trying to open a folder or run a program or delete a file but you encounter an error message instead saying, “Error (740), The requested operation requires elevation” on your Windows 10 computer, then this post should help. Make sure that you follow each one of the options given below carefully.

Option 1 – Always run the program as an administrator

There are some apps that require administrator privilege before they can be opened. So if you are got the “Error (740), The requested operation requires elevation” error when you try to open a particular app on your computer, you have to try opening it as administrator instead. On the other hand, if you are already using an administrator account or if you are a member of the administrator group, this option may not work for you so just proceed to the next one but if you’re only using a regular account, then follow these steps:

• First, right-click on the app you are trying to open and select Properties.
• After that, go to the Compatibility tab and check the checkbox labeled “Run this program as an administrator”.
• Next, click the Apply and OK buttons and see if the app opens without any problem.

Option 2 – Try to change the folder permissions

If you encounter Error 740 while opening a folder, then you need to try changing the folder permissions.

• First, right-click on the folder and click Properties.
• Next, go to the Security tab and click the Advanced button.
• After that, check the checkbox labeled, “Replace all child object permission entries with inheritable permission entries from this object” and then click the Apply and OK buttons to save the changes made.

Option 3 – Try disabling UAC

The User Account Control or UAC settings might be the one that’s responsible for Error 740 which is why you have to disable the User Account Control and then verify if it’s the one that triggers the error or not. To do that, simply search for “Change user account control settings” in the Taskbar search box and then drag the blue bar down to the bottom and click the OK button to save the change made.

Option 4 – Select the Elevate without prompting option in the Group Policy Editor

There is an option in the Group Policy Editor which allows you to disable the UAC prompt. Disabling the “Elevate without prompting” option can help in resolving Error 740 and to disable it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to the following path:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

• From there, go to the Security Options folder where you can find a policy named “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode”. Double click on it to open its options.
• Now select the Elevate without prompting option from the drop-down menu and click OK.

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given options below.

Option 2 – Ensure that all the supporting processes and services are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 3 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox error.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

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 that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s causing the problem.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

If you are trying to install or update Microsoft Edge on your Windows 10 computer but ended up getting HTTP Error 500 or Error 0x8004xxxx or 0x8007xxxx, then you’ve come to the right place as this post will help you sort this problem out. The aforementioned errors when either installing or updating the Edge browser occur due to a Network issue. There is actually a range of error codes that are associated with the network connection issue. These error codes include Error 500 or 0x80010108, 0x80040801, 0x80042193, 0x80042194, 0x800421F4, 0x800421F6, 0x800421F7, 0x800421F8, 0x80072742, 0x80072EE2, 0x80072EE7, 0x80072EFD, and 0x80072EFE. To fix them, there are several options you can try. You can try to run the Network Adapter troubleshooter or update or reset the Network Adapter as well as check and the proxy configuration.

Option 1- Try updating the Network Adapter Driver

Follow the steps below to update your Network Adapter Driver:

• 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.
• From there, expand the list of all the network drives and update each one of them.

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 2 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 3 – Try to reset the Network Adapter

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Option 4 – Try to fix the Proxy Settings

• In the Cortana search box, search for Internet Explorer and then click on the related search result.
• After that, tap the Win + T keys on your keyboard and click on Internet Options.
• Next, navigate to the Connections tab and click on LAN Settings.
• Then click on the Advanced button and delete all the entries in the list generated in the Exceptions section. And if the Advanced button is disabled because the “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)” option is disabled then you are good to go. Now proceed to the next step.
• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also search for “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• If a User Account Control appears, click on Yes to proceed. After that, type each one of the commands listed below, and don’t forget to hit Enter after you type each one of them.
  • netsh winhttp reset proxy
  • net stop wuauserv
  • net start wuauserv

• Now restart your computer and check if the problem is fixed or not by installing or updating Microsoft Edge again.

If you are having issues with your network connection and you have it configured to DHCP, then you shouldn’t have any issues in figuring your IP address out. If you want to prevent conflicts between network devices and enable their easy management, then you have to set a static IP address in your Windows 10 computer, worry not for this post will show you how it’s done. The IP addresses for computers are usually configured to the Dynamic Host Configuration Protocol or DHCP automatically by the respective router. This is really convenient since the devices instantly connect to your network and through this, you can save yourself the trouble of configuring the IP address for each new device manually. However, there’s a shortfall in the process – the computer’s IP address can change every now and then. Moreover, you might also find it a lot easier to share a printer or configure a Port forwarding when you set a static IP address. There are three ways to do it – you can set it via Control Panel or Windows Settings or using Windows PowerShell. For more details, follow the options provided below.

Option 1 – Set a static IP address via Control Panel

• Right-click on the network or Wi-Fi icon located in the Taskbar.
• Then select the “Open Network and Internet settings” option from the given list of options.
• Next, go to Wi-Fi settings and scroll down until you see the “Related Settings” section. Here, click on the “Change adapter options” link which will open a new window that will direct you to the Network Connections section of the Control Panel.
• After that, right-click on the network connection you want to set a static IP address for and then select the Properties option.
• Then select Internet Protocol Version 4 (TCP/IPv4) under the Networking tab and click the Properties button.
• Now switch the selector to the “Use the following IP address” option and make the entry for the following fields that correspond to your network setup.
  • IP address (Find it using the “ipconfig /all” command)
  • Subnet Mask (On a home network, it is 255.255.255.0)
  • Default Gateway (It is your router’s IP address.)

• Then check the “Validate settings upon exit” option to help Windows check your new IP address quickly as well as the other relevant information to make sure that it’s working.
• Once you’re done, click the OK button and close the network adapter’s properties window.

Option 2 – Assign Static IP address using Settings

• First, click on the gear icon for Settings and select the Network & Internet tab.
• Next, select Wi-Fi > Current connection where you’ll have to select the network connection your computer is connected to.
• After that, scroll down until you reach the IP settings section and then click the Edit button.
• Now click the drop-down arrow when the IP settings window pops up and select the Manual option.
• Now turn on the IPv4 toggle switch and set the static IP address. You also have to set the Subnet prefix length (subnet mask). For instance, if your subnet mask is “255.255.255.0”, then the subnet prefix length in bits should be 24.
• Afterward, configure the Default Gateway address and the Preferred DNS address and then save the changes you’ve made.

Option 3 – Assign the static IP address using Windows PowerShell

• In the Start Search, type “PowerShell” and right-click on Windows PowerShell from the search results to open PowerShell with admin privileges.
• After that, enter this command to view your computer’s current network configuration: Get-NetIPConfiguration
• Next, take note of the following information:
  • InterfaceIndex
  • IPv4Address
  • IPv4DefaultGateway
  • DNSServer

• Once you’re done, execute this command to set a static IP address: New-NetIPAddress -InterfaceIndex 15 -IPAddress 192.168.29.34 -PrefixLength 24 -DefaultGateway 192.168.29.1
• Afterward, change the default gateway with the default gateway address of your network and make sure that you change the InterfaceIndex number with the one that corresponds to your adapter and IPAddress with the IP address you want to assign to your computer.
• Now execute this command to assign a DNS server address: Set-DnsClientServerAddress -InterfaceIndex 4 -ServerAddresses 10.1.2.1
• Finally, save the changes you’ve made and restart your computer.