USB Keeps Connecting and Disconnecting

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004 To resolve the Windows Update error 0x80092004, here are some fixes you can try.

Option 1 – Try removing recent updates and packages

When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
• Now run the Remove Package program to remove the concerned update and package.

dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart

• Now restart your computer and log back in.
• After that, run the following command:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

• Then scan for updates.

Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

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

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

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

• After that, exit Command Prompt and restart your computer.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to manually install the Windows Updates

Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Even with the new Groove Music in Windows 10, a lot of users still prefer to use the old Windows Media Player. This isn’t surprising since Windows Media Player still remains to be one of the best players you can find. However, that does not mean that it is without flaws as it could still encounter some issues from time to time. One of the issues you might encounter when using the Windows Media Player is when you try to burn DVDs or CDs but end up failing due to an error that pops up that says, Windows Media Player cannot detect the length of the file. At the time of writing, it isn’t clear yet what the real cause of the error is. However, there are several fixes that are provided in this post for you to check out so you can resolve the problem. You can try to get rid of any unsupported files from the burning list or you could also try running the Windows Media Player troubleshooters. Aside from that, you could also try to drag and drop music or change the burning speed. For more details, refer to the following options.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try running the Windows Media Player troubleshooters

The next thing you can do to fix the error is to run the built-in troubleshooters for the Windows Media Player. Windows 10 actually comes pre-packed with three troubleshooters designed for Windows Media Player. They can help in fixing the “Windows Media Player cannot detect the length of the file” error. To run these troubleshooters, simply tap the Win + R keys to open the Run dialog box and type “msdt.exe -id WindowsMediaPlayerConfigurationDiagnostic” for the Windows Media Player Settings troubleshooter or type “msdt.exe -id WindowsMediaPlayerLibraryDiagnostic” for the Windows Media Player Library troubleshooter, or type “msdt.exe -id WindowsMediaPlayerDVDDiagnostic” for the Windows Media Player DVD troubleshooter.

Option 3 – Try to drag and drop music

Another thing you can check out is to drag and drop all the tracks into the Windows Media Player before you burn them. All you have to do is open the folder where the tracks are located and highlight all of them and then drag them to the Windows Media Player. It should now be able to detect the length of each one of the tracks without any errors.

Option 4 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. Just open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

Lately on EA forums question has appeared on what to do when Origin client does not load library. It seems that the latest update for the Origin client has brought some issues as not properly showing one library which appears empty. Do not worry, we have a solution for you, several to be precise and it will fix the issue guaranteed. It is advisable to try solutions in order how they are presented since they go from the most simple and fastest and most common ones.

1. Delete the cache

   Close origin client completely Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %ProgramData%/Origin and press ENTER Go into the Origin folder Delete all files and folders except the LocalContent folder Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Delete the Origin folder In the address bar click on AppData Go into the local folder Delete Origin folder Reboot your PC

2. Clear the temporary files

   Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Go into the roaming folder Delete Origin folder Go to the AppData folder and delete the Origin folder from there also Reboot system

3. Try Windows built-in tools to check compatibility

   Locate where Origin is installed and right-click on the executable file Click on properties Go to the compatibility tab Click on Run the compatibility troubleshooter and follow on-screen instructions

4. Update Origin

   Rarely this is the case but check manually to see if you can update your Origin client. Sometimes due to network issues client does not update automatically and can cause this strange behavior.

5. Add origin as an exception to antivirus and firewall

   Not rarely game clients can be detected as some form of malicious software and antivirus along with firewall can automatically block it. Go to your security software settings and add it as the exception.

6. Reinstall Origin

   If everything else fails, reinstall the Origin client

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.

If you are a person which spends a lot of time in front of the computer doing work, then you are aware of the importance of having a proper backup of your archive so if anything bad happens you will lose almost none of the work. We can never tell when we might experience HDD failures or when we might be a victim of cyber attacks, natural disasters,s and other unpredictable circumstances where we could lose all of our data in a matter of minutes. Having a backup of our data is very important but sometimes we are too busy or not around and we miss that data backup we wanted to do, and if in this case disaster strikes we are out of luck and data is lost. To avoid such circumstances, you can set up automatic Windows Backups at a scheduled time. This way it will help to have the loss of important files and documents from unexpected hazards. in order to create automatic backups of your files, you have several options, and below we will explore each one in hopes that you will find one that best suits your needs.

1. Create automatic file backup with OneDrive

   This is probably the best way to do it because each time when you sign in OneDrive files get backed up right away, files are stored in the cloud and can be accessed on any device via a Microsoft account. To get started, open the Settings app first. Click on the Update & Security category Select the Backup tab from the left pane. Move to the right page and click on the Back up files button that is available under Back up files to OneDrive. Select the folders you want to backup in the cloud, and remove those ones you don’t want to backup. On the next page, click the Start backup button to start the procedure.

2. Create a backup using File History

   File History is an inbuilt feature that allows users to create automatic file backup on Windows 10. File History allows the users to back up their files in an external or cloud drive at different intervals of time. To create automatic file backup using File History: Press the ⊞ WINDOWS + I to open the Settings app. Click on the Update & Security category and then select the Backup tab from the left pane. Under the Back up using File History section, click on Add a drive button. Now choose the drive to store the backup files. Windows will use this drive for File History. Then turn on the toggle button under Automatically back up my files. This will back up your data to the drive automatically whenever you connect it to the system. Below the toggle button, click on the “More options” link to set how frequently File History will back up. Use the Keep my backups drop-down menu to get the option to configure the time for how long you want to keep your backups. By default, it will keep your backups forever. Under the section Back up these folders, tap on the Add a folder button in order to add one more folder to the backup. Then click on the Add a folder button, under Exclude these folders. This will exclude the files that you don’t want to back up. You can stop the drive from storing backup files to change the backup storage location. To do this, click the Stop using drive option under the Back up to a different drive category.

3. Backup using Windows backup & restore tool

   Open Control Panel Click on the System and Security option Scroll down and select the Backup and Restore (Windows 7) button Next click on the Set up backup button, available under the Back up or restore your files section Under the Save backup on section, select the Backup Destination where you want your backup files to get stored On the “Set up backup” page, Windows will ask you to choose the way to backup, check Let me choose checkbox, and then hit the Next button Under the section Computer, select the files and folders you want to backup. Then uncheck the box next to the Include a system image of drives option, and then hit the Next button Now click on the Change schedule link. Set the time and check the box beside Run backup on a schedule button Click OK then select the Save settings and run backup option

There is one service in the Windows operating system that is responsible for managing all the print jobs as well as handles the interaction with the printer. This service is known as the Print Spooler service. However, if it stops running, then you won’t be able to print anything on your computer. In such a case, you can try to restart the Print Spooler service, and to do that, you have to open the Windows Services Manager and look for the Print Spooler Service. Once you found it, right-click on it and select Restart. If it isn’t running, select Start and if the Service starts working again, then good but if not and you got an error message instead that says, “Windows could not start the Print Spooler service on Local Computer, Error 1068, The dependency service or group failed to start”, then read on as this post will give you a couple of suggestions you can try to resolve the issue. The reason why you could not start the service is most likely because the Print Spooler service is dependent on other services which might not be properly running. If the following services are not running then it’s no wonder why you’re getting the error.

• HTTP Service
• Remote Procedure Control (RPC) Service

You might not see the RPC service which means that the Print Spooler Service does not recognize its dependency on the RPC service. In such a case, you have to manually configure the dependency by following the options given below.

Option 1 – Try configuring the dependency via CMD

The first thing you have to do is to configure the dependency using CMD. Refer to the steps below to do so:

• Open an elevated Command Prompt.
• Then type in “sc config spooler depend= RPCSS” and hit Enter.
• After the command has been executed, restart your computer and then check if it fixed the problem. If not, proceed to the next given option below.

Option 2 – Fix dependency via the Registry Editor

You can also resolve dependency using the Registry Editor. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSpooler
• Next, right-click on the “DependOnService” entry located on the right pane and select Modify.
• Now change its value data to “RPCSS” and click OK to save the changes made and then exit the Registry Editor.
• Reboot your computer and see if the issue is resolved.

Option 3 – Try running the Printer Troubleshooter

Another option you can check out is the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

In this post, you will be guided on how you can set up the USB tethering feature on your Windows 10 computer and share your mobile device’s mobile data so other devices can also access the internet. Tethering is usually known as Wi-Fi tethering which allows users to share mobile data to any device with Wi-Fi, laptops included. This is really useful especially when you have no other way to access the internet. For instance, if you are using a desktop computer and there is no way for you to connect to the Ethernet, and you have no Wi-Fi adapter that you can use to connect to a router as well, you can use USB tethering instead to access the internet. It is almost similar to Wi-Fi tethering except that it works over a USB connection instead of a Wi-Fi adapter. USB tethering is almost quite the same as an Ethernet connection except that it’s faster compared to Wi-Fi tethering as well as Bluetooth tethering. Just like Wi-Fi tethering, USB tethering is free unless your network carrier has blocked it. Thus, it’s better if you make that clear with your operator. Once you have that covered,

Follow the instructions provided below to set up USB tethering on your Windows 10 computer.

Step 1: First, connect your mobile device to your Windows 10 computer using a USB cable. Step 2: If it asks you to enable the file transfer feature, just cancel it. A prompt that says, “Tethering or Hotspot active—Tap to setup” should be available as soon as you get connected – tap on it. Note: If there is no prompt, just go to Settings > Network and Internet > Hotspot and Tethering and from there, toggle on the USB tethering option. Step 3: Afterwards, the setup will create a new network adapter in Windows 10 automatically and your computer should now be connected to the internet using USB tethering. Note: You have to make sure that the Wi-Fi connection in your mobile device is turned off and if it is connected to an existing network, the USB tethering will be disabled but if you see its status as enabled, then the USB tethering setup is successfully done. In addition, keep in mind that the location of tethering can be different for every phone, especially on a customized operating system such as RealMe, Redmi, Samsung, and any other mobile device although they are clubbed in the section of Mobile and Data Network. In case you encounter some problems when using USB tethering in your Windows 10 computer, there are troubleshooting tips you should follow. The NDIS-based Internet Sharing Device network adapter is what Windows 10 uses to make USB tethering possible so if it stops working, follow the options provided below.

Option 1 – Perform basic check

The first thing you can do if you encounter problems in USB tethering is to do a basic check like checking if Wi-Fi is enabled automatically as well as check if the USB cable is disconnected or if you’ve turned off USB tethering accidentally.

Option 2 – Try installing or updating the USB RNDIS adapter

RNDIS or Remote Network Driver Interface Specification can also help you resolve any USB tethering problem. If the pre-installed driver does not help you in connecting to the internet, then you can try installing the USB RNDIS driver that is, if it’s not installed yet. If it is already installed, you can try to update it instead.

• Tap the Win + R keys to open Run and type “devmgmt.msc” in the field and hit Enter to open the Device Manager.
• Next, expand the Network adapters section and look for the Remote NDIS based Internet Sharing Device. But if you are using a Samsung smartphone, you might see “Samsung” instead of under Network adapters.
• Right-click on it and then select the “Update driver” option.
• Then select the “Browse my computer for driver software” option.
• After that, select the “Let me pick from a list of available drivers on my computer” option.
• Now uncheck the checkbox for “Show compatible hardware”.
• From the given list on your left-hand side, look for Microsoft and then select the Remote NDIS based Internet Sharing Device on your right-hand side.
• Click on Next. A new popup will appear where you have to click on Yes. This will install the driver.
• Now click on the Close button and restart your computer.

Cache files are temporary files that have been created by various applications and services when used.  As temporary files, they are safe to be removed and deleted from the system since the application or service will create new ones when needed but sadly will not remove old ones, this task is left to OS itself. Automatic Windows cleanups can mostly take care of these things but for top-notch performance clearing cache manually is a far better option. We will here explore various cache temporary files, where they are, and how to clean them. Sit back and let’s do some cleaning!

Clear cache using Disk Cleanup

1. Open Start menu and search Disk Cleanup
2. Click on it in search results
3. Click on the drives drop-down menu and select the drive where is Windows 11 installed
4. In the Files to Delete section enable all boxes and click on OK
5. Click on delete Files to confirm

Clear Microsoft store cache

1. Press ⊞ WINDOWS + R to open the run dialog
2. Type in WSReset.exe and press ENTER
3. Black blank windows will appear, wait for the window to close itself and you are done

Clearing location cache

1. Press ⊞ WINDOWS + I to open location history
2. Select Privacy & Security
3. In the App Permissions section click on Location
4. On-Location page click on Clear

Clear and flush DNS

1. Press Start and search for Windows Terminal
2. Click on Terminal in search results
3. Type in: ipconfig /flushdns and press ENTER

And that is that!

As you know, Windows 10 comes with the option to create Mobile Hotspot for other devices. This allows you to share your Ethernet connection. However, there are times when one of your devices might fail to reconnect to the mobile hotspot again. For instance, you moved out of the Wi-Fi range because you have somewhere to be and whatnot and when you’re back you find that you are now unable to reconnect to the Windows 10 Hotspot or the shared network. Although you can always restart the mobile hotspot to resolve the problem, however, it might only be a temporary fix. So in this post, you will be given options for a much better solution to the problem. This kind of problem seems unusual and does not occur that often. To fix it, you can try to set up DNS on your Windows 10 device and then configure the settings on the mobile device. It seems that what’s happening here is that the mobile device is unable to lock on to the Mobile Hotspot when the IP address changes for some reason.

Option 1 – Try changing the DNS settings on your laptop

In this option, you need to make sure that IPv4 and IPv6 are selected on your Ethernet connection. You also have to change the Preferred DNS server as well as the Alternate DNS server to 8.8.8.8 and 8.8.4.4, respectively. You also have to validate the settings before you exit just to ensure that you’ve entered everything correctly. After that, open Command Prompt and run the ipconfig command and then take note of the IP address, Gateway DNS 1 and DNS 2.

Option 2 – Try changing the Wi-Fi settings on your mobile device

This option should be mostly the same on all your mobile devices. And given that OEMs build their customization and skin, you might have to fiddle around a little to get the settings. Refer to the steps below to change the Wi-Fi settings:

• Go to the Settings of your mobile device and tap on Wi-Fi.
• Then click the Mobile Hotspot connection that you’ve created on your laptop.
• After that, input the password and tap the Advanced options.
• From there, tap on IP settings and select the Static option instead of DHCP.
• Now you have to enter the IP address, Gateway, DNS 1, and DNS 2 of the laptop you’ve taken note of earlier and that’s it.

Note: If you are already connected to the Mobile Hotspot, long press on the Wi-Fi network and select the Modify Network option and then follow the steps given above to change from DHCP to static. Once you’re done, your mobile device should now be able to connect to the Windows 10 Mobile Hotspot all the time.