How to Fix Error 80070103 in Windows 10

One of the biggest annoyances in Windows 10 is that it’s upgrading from one version to another. Although these upgrades are necessary to fix some bugs or improve user experience, some of them actually bring bugs into the computers instead. And in one of the recent Windows 10 updates, a lot of issues were found especially for users who use Remote Desktop on a daily basis. The error stacks up as Windows 10 Remote Desktop Protocol client is not working or won’t connect and can’t find the computer HOSTNAME generally. Based on the reports by users who experienced this issue, there are two cases around it:

1. Users who try to reach a specific website or folder on the network

Some users encounter this error when they try to run the Network Troubleshooter. Even when they add the server name inside it, it still won’t identify the problem, and unpredictably, the driver seems to appear and disappear every now and then. And even after connecting, the network commands don’t work at all. This is really troublesome for users who have lots of PCs and all the other systems do not appear on the network.

2. Remote Desktop isn’t able to find the computer HOSTNAME

Some other users reported that the error appeared when they use the classic remote desktop software. It keeps on failing and throwing the error message, “Remote Desktop can’t find the computer “HOSTNAME”. If this is the same scenario you are having, it means that “HOSTNAME” does not belong to the specified network. So you need to verify the computer name and domain where you are trying to connect to. There are times when it used to work after some users tried connecting to the domain a couple of times. However, when users try to use the UWP version of Remote Desktop, it seems to connect most of the time. This kind of problem is definitely a DNS issue. It could be that there are two different records on the DNS server which is why it connects and other times it doesn’t. When it is able to resolve the correct address, the drives connect to the PC however, after a couple of minutes, they will suddenly go missing. Using “nslookup” for the hostname, multiple times, you can check this and see if you’ll get identical results all the time.

nslookup [–SubCommand …] [{ComputerToFind| [–Server]}]

If you’ve determined that the drives disappear each time, you may have to change the DNS server or ask your admin to resolve the problem for you. Alternatively, you can also check out another option that has worked for a lot of users. This second option is disabling the IPv6 on the network adapter. In case you don’t know, Windows 10 prefers IPv6 over IPv4 so if you now have issues using IPv6 to connect to the servers, you can change your computer’s settings so that it’ll only use IPv4 instead of IPv6. To do so, follow these instructions:

• Open Settings > Network and Internet > Ethernet > Change Adapter options.
• From there, right-click on the adapter for where you want to disable it and then select Properties.
• Next, look for the checkbox labeled, “Internet Protocol Version 6 (TCP/IPv6)” then uncheck it.
• Now click on OK and restart your PC to save the changes made.

Error Code 0x803f7001 – What is it?

Error code 0x803f7001 results when users fail to update their Windows operating system. This often occurs when they seek to update from Windows 8 or 8.1 to Windows 10. Users will be able to identify error code 0x803f7001 because of the following common symptoms which occur:

• Inability to upgrade your Windows operating system to Windows 10
• Message box with error code 0x803f7001

Solution

Error Causes

The causes for error code 0x803f7001 are usually associated with the use of an unlicensed version of Windows 8 when upgrading to Windows 10. In such cases, the error code occurs when there is no valid Windows license or product key on your device.

Further Information and Manual Repair

To fix error code 0x803f7001, users may not necessarily need technical knowledge or the help of a Windows repair technician. Usually, the process is simple and can be resolved with the use of a valid product key. However, if users have trouble implementing the instructions found in the manual repair methods listed below, contact a Windows repair specialist for help or use an automated tool that provides the best solutions for problems like error code 0x803f7001.

Method One: Use a Valid Product Key

A product key is a 25-character code that enables users to activate their Windows operating system. To successfully activate your operating system and resolve error code 0x803f7001, enter the product key in the correct order. Once you have a valid product key in your possession, begin to resolve the error code by following the instructions below:

• Step one: Click the Start button then select Settings
• Step two: Select Update & security then Activation
• Step three: Click the Change product key
• Step four: Type in your valid product key. (Ensure you include the 25 characters of your product key in the correct order.)

Once you type in the valid product key, you should be able to successfully upgrade to the latest version of Windows. However, this method is only effective if the error code 0x803f7001 on your device is caused by issues related to the product key.

If the error code reappears after attempting manual repair method one, move to the next manual method suggested below.

Method Two: Reinstall Genuine Version of Windows 8

This method is crucial for you to perform if method one was not successful. Begin the reinstallation process by ensuring you have a genuine version of Windows 8. After reinstalling this version of your Windows operating system, attempt to upgrade to Windows 10 by following the instructions below:

• Step one: Type Settings in the search box near the Start button or click the Start button and select Settings
• Step two: After clicking Settings, select Update & Security
• Step three: Select Windows Update then the Check for updates tab
• Step four: Activate Windows 10 update

If this method is successful, you will no longer see error code 0x803f7001 pop up in a message box. You will also be able to access Windows 10, and all the benefits it provides users, on your device.

Method Three: Install an Automated Tool

Automated tools help PC users eliminate common issues such as Windows error codes. To address or rectify error codes like error code 0x803f7001 download a powerful automated tool on your machine. This tool enables users to access quick solutions. It also scans for and corrects issues that may result in error codes or poor PC performance.

This post will guide you in what to do if you are trying to share the internet connection from your Android smartphone to your Windows 10 computer but USB tethering is not working. Although you can always connect your Android phone to your computer using a USB cable, you still won’t be able to access the internet. However, if you’ve already enabled the USB tethering option in your smartphone, you should be able to access the internet but if you still can’t then you can fix this issue by reading this post. There are several potential fixes you can check out to fix the USB tethering issue. You can try running both the Internet Connections and Network Adapter troubleshooters or try installing the USB RNDIS adapter or disable any unnecessary network adapters.

Option 1 – Try to run the Internet Connections and Network Adapter troubleshooter

There are various built-in troubleshooters in Windows 10 that can help fix system issues. Since you are dealing with an internet connection problem, you can try running both the Internet Connections and the Network Adapter troubleshooters. To run them, follow these steps:

• Go to Settings > Update & security > Troubleshoot.
• From there, you can select the Internet Connections troubleshooter.
• Click on the Run troubleshooter button to troubleshoot the problem.
• Wait until the troubleshooter is done identifying and fixing the problem automatically.
• Then follow the next on-screen instructions that may appear.
• Once it’s done, check if the USB tethering issue is now fixed.

Note: You can also try to run the Network Adapter troubleshooter. It is also located under the Troubleshoot section. Just scroll down until you see it and then run it.

Option 2 – Try installing or updating the USB RNDIS adapter

RNDIS or Remote Network Driver Interface Specification can also help you resolve the 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.

Option 3 – Try disabling any unnecessary network adapters/connections

Assuming that your Ethernet connection is showing ping loss which indicates that the internet is not stable. In such time, if you use the USB tethering functionality, you won’t be able to access the internet connection from your smartphone. The internet connection will be frequently disconnected since your computer gives priority to the Ethernet connection. Thus, you have to disable the Ethernet connection temporarily.

• Right-click the network icon on your Taskbar and select the option “Network and Sharing Center”.
• After that, click the network connection. And then click the Disable button from the status box that opens.
• After that, check if you can now connect to the internet or not.

What is Mscomctl.ocx?

Mscomctl.ocx is a Microsoft library Windows Common Controls file. The Mscomctl.ocx error occurs when this file is either lost or gets corrupt. The error is displayed on the screen when the user tries to run a program that is dependent on this file. It appears as:

“Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid”

Solution

Download Available to Completely Repair the Error Mscomctl.ocx

Error Causes

Installing and then uninstalling a large number of applications on the Windows operating system often corrupts or unregisters the Mscomctl.ocx library. This message will continue to appear on the screen until you re-register the library file again on your system.

Further Information and Manual Repair

You don’t need to have the sound technical knowledge or call a professional to resolve Mscomctl.ocx error on your PC. The Mscomctl.ocx error is easy to repair and can be fixed in a couple of minutes. Here are 2 solutions to repair the Mscomctl ocx error code on your system:

Cause: Error occurs because the Mscomctl ocx file is unregistered

Solution:

1. Go to the start menu and type ‘Mscomctl.oxc and press enter
2. Copy the ‘Mscomctl.ocx’ file and paste it in "C:WindowsSystem32" folder
3. Now click the start menu again and type ‘CMD’ in the search box. This will open your computer's command prompt.
4. Once this opens, type either of the following commands and then press enter. If you have a 64-bit operating system, then type: Regsvr32 "C:WindowsSysWOW64MSCOMCTL.OCX” and if you have 32-bit operating system, then you should type ‘Regsvr32 "C:WindowsSystem32MSCOMCTL.OCX"

By doing this, you will be able to register the Mscomctl.ocx file on your PC and then you will no longer receive Mscomctl.ocx error code.

Cause: Error code occurs because the Mscomctl.ocx file is missing

Solution:

1. First search for MScomctl ocx on your local drive to see if it is missing.
2. If the file is missing, then download the MScomctl.exe file from a reliable website.
3. Now extract the file to your C:WINDOWSsystem32 directory
4. Then click start and run.
5. Now type ‘REGSVR32 MSCOMCTL.OCX’ and press enter

Please note to implement any of the two solutions stated above, you will need administrator rights. If you have the administrator rights then only can you make the above registry changes. Therefore to make the following changes you will have to access the PC using the Administrator account. Simply follow the instructions given above to repair this error code problem right away!

Error 101 - What is it?

Error 101 is a Google Chrome error. You may experience this error if you browse the internet using Google Chrome. This error results when the existing HTTP connection between Chrome and the website is broken. The error is displayed in the following format: “Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.”

Solution

Error Causes

The cause of Google Chrome error 101 cannot be narrowed down. This error can be triggered on your PC due to multiple reasons. These include:

• The inability of the Google Chrome installer to create a temporary directory on your PC during the installation process
• Enabled DNS Prefetching
• Firewall
• Viral Infection
• Bad Registry Entries
• Poor Internet Connection

Though this error code is not fatal, nonetheless it is advisable to fix it to ensure you are able to browse the internet using Google Chrome.

Further Information and Manual Repair

The good news is that this error is quite easy to resolve. Even if you are not a technical whiz you can still manage to fix it by trying these easy and effective DIY methods we have listed below:

Method 1: Reload the Website link on Chrome or Check Your Internet Connection

Sometimes refreshing the webpage can resolve the issue easily. Try doing it. Reload the link by pressing Ctrl +R. This will refresh the webpage. If it starts working then that’s great but if it doesn’t then it is advisable to check your internet connection. Disable and Enable the connection and then try browsing on Chrome again. If websites are accessible then the problem is resolved. If the error persists then try other methods.

Method 2: Disable DNS Pre-fetching

Sometimes this error may occur due to enabled DNS pre-fetching. To resolve the issue, open Chrome, then click on the wrench key. Go to setting and under the bonnet and Privacy section, look for the DNS perfecting option. If it is enabled, then uncheck it to disable DNS Pre-fetching. Save the changes and then close the browser. Now open it again and try browsing on Chrome. If error 101 does not appear and you are able to access websites then the issue is fixed.

Method 3: Scan for Viruses

Another way to fix this is to download and run a powerful antivirus. Scan and remove viruses to fix the problem.

Method 4: Check the permission for your temporary folder

As mentioned above, another underlying reason for error 101 can be Google Chrome installer was unable to create a temporary directory on your system during the installation process. To resolve it, check the permission for your temporary folder. Here’s how to do it: First go to the start menu and type Run. Now enter one of the following directories in the text fields 1. Windows XP: %USERPROFILE%Local Settings 2. Windows Vista: %USERPROFILE%AppDataLocal After that press OK. This will open a new window. In the Window that opens, right-click the temp folder. Now select properties and press the security tab to continue. In the group and user names section, select your user profile name. In the permissions, section verify that the checkboxes for READ, WRITE, and READ  & EXECUTE permissions in the DENY column are not selected. After you have verified, click apply and then ok. Now try reinstalling the Google Chrome browser again on your system.

Method 5: Remove Bad Entries by Cleaning the Registry

Bad entries and cookies saved in the registry can also lead to error 101. You can remove them manually but that will take a great deal of time and can be slightly difficult if you are not technically sound. Therefore, it is advisable to download Restoro. This is a user-friendly PC Fixer integrated with a registry cleaner that scans and removes all registry issues in a few clicks. It removes all the bad entries and junk files cluttering the registry and repairs it instantly. Click here to download Restoro.

There are a lot of users who use their Windows 10 PCs to create and access data on their servers using their network. However, some of them reported getting an error saying that the server is not accessible. Here’s the full content of the error message:

“\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect.”

If you are among the users who experience the same issue, read on as this post will help you resolve this error when accessing your server. But before you start troubleshooting the problem, you might want to perform System Restore, especially if tend to create one. To use System Restore, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the ACPI.sys Blue Screen error now’s the time for you to make use of the potential fixes laid out below.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try checking the status of the Workstation Service

You might want to check the status of the Workstation Service as the error might have something to do with it.

• Tap the Win + R keys on your keyboard to launch the Run utility.
• Then type “services.msc” in the field and click OK or hit Enter to open the Windows Services Manager.
• After opening the Services Manager, you will see a list of all the services on your computer and from there, locate the Workstation Service.
• Double click on the Workstation Service to open its Properties.
• Next, Stop the Service and Start it again or you can also right-click on it and select Restart and then make sure that its Startup type is set to Automatic.
• Now restart your computer and check if the error is fixed.

Option 3 – Try to change the File Sharing Connections setting

You can also try to change the File Sharing connections setting. All you have to do is go to Control Panel > Network and sharing center > Advanced sharing settings > File sharing connections. From there, you need to select “Enable file sharing for devices that use 40 or 56-bit encryption and check if it helps in fixing the problem. If not, undo the changes you’ve made and proceed to the next given option.

Option 4 – Try checking the Network Configuration

Checking the Network Configuration can also help you fix the error. Refer to the steps below to do so:

• Right-click on the Wi-Fi connection or on the Ethernet connection icon located in the system tray.
• Then select open Network and Internet Settings and then click on the “Change Adapter Options”.
• After that, a new window will appear and from there, select the network connection that connects your computer to your network – this can either be a Wi-Fi connection or Ethernet connection.
• Right-click on that connection and select Properties where you will see a list of items.
• Select the Internet Protocol Version 4 or Internet Protocol Version 6 from those items according to your system requirement.
• Then click on the Properties button.
• Check if everything is now configured as to how it is supposed to be and then check if the error is resolved.

Option 5 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 6 – Run the Network Adapter Troubleshooter

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

Disk cleanup is part of Windows 10 tools and it is essential in keeping your computer up and running in optimal settings and to free so much needed space as well as remove temporary files that can accumulate over time. Using disk cleanup from time to time is recommended and a very useful habit that will save you some headaches and optimize your computer running time, speed up boot sequence, etc. Think of it like cleaning up your desk, from time to time it can get too overwhelmed with junk and non-important things and if you are keeping it tidy all the time each time you need to find something it will be much faster and easier, same goes with computers, so if you do not have it, try to develop a habit that once per month you start disk clean up and remove trash from your hard drive. In order to do so, press ⊞ WINDOWS + E to bring File Explorer up Once File Explorer is up and running right-click on the hard drive you wish to run disk cleanup on and click on properties. Properties Windows will open on the general tab, on that tab you have disk cleanup on the lower right part of properties, click on it. Wait for Windows to gather information about your hard drive and files on it. After it is finished you will be greeted with the next screen: Here you can thick and mark which items you would like to get rid of and which ones you would like to keep. Note that you can freely tick all of them and remove them since removing these files will not break WIndows in any way. make your choices and click on ok. You can also click on Clean up system files to run system files cleaner and get rid of junk there, you will not be able to choose any options there, Windows will alone clean up what is not needed. After disk cleanup is finished least thing you will have is more free disk space, but like mentioned, keeping your Windows and computer healthy goes a long way in its usability, speed, and performance.

In case you don’t know, the .Net Framework is a programming infrastructure introduced by Microsoft. You will need it to run on lots of services and applications. Note that most of the applications that require the .Net Framework are packed with their installation files which is why it will be installed automatically on your computer when you install an application. However, there are instances when you’ll get an error message saying, “The .NET Framework 4.7 is not supported on this operating system” while trying to install the .NET Framework as a standalone service. The very reason why this error message appears is stated in the error message itself. Although the .Net Framework is supported on Windows 10, it is not actually compatible with some other Windows 10 versions. So it is most likely that you are seeing this error message because the .Net Framework in your computer is not compatible with the Windows 10 version you are running. Since that’s the case, you need to update Windows 10 to fix the problem. Updating your Windows 10 computer is the only solution you can try to fix this problem. Thus, it is advised that you check for Windows Updates even if you are now using the latest version of Windows 10. And since the issue is caused by an incompatible operating system version, once you install the exact version of Windows 10 required by the .Net Framework, the problem will be fixed. Simply follow the steps given below to do so.

• Step 1: Tap the Win + R keys to open the Run dialog box.
• Step 2: After that, type in “winver” in the field and tap Enter.
• Step 3: Next, your Windows 10 version should be given in the new window that appears. Take note that the number after the Version which is in the second line is your version number of Windows 10. And that the number must be 1507 or 1709. The first two digits in these numbers are the year while the second two represent the month when the update was released. So if you are running a 1709 version, this means that the Windows 10 version you are using was released in September 2017.
• Step 4: The next thing you have to do is to make sure that you have the Windows 10 version that’s compatible with the .Net Framework. To verify, you need to click here and click on the System Requirements.

After opening the link, take a look at the Supported Operating System section where it says, “Windows 10 Anniversary Update” and “Windows 10 Creators Update”. Since there are users who are not familiar with the version numbers related to both the Anniversary and Creators updates, refer to the list given below.

• November Update (1511)
• Anniversary Update (14393)
• Creators Update (1703)
• Fall Creators Update (1709)
• Spring Creators Update (1803)

As you can see, the Creators Update has version 1703 while the Anniversary Update has version number 14393 so if you are using a version lower than the 14393 version then it’s no wonder you aren’t able to install the .Net Framework 4.7 on your Windows 10 PC. Now all that’s left to do is to update your Windows 10 version and make sure that you will be updating it to the latest version available and then try installing the .Net Framework again.

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

• You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

• After that, save the file and name it “MapDrives.cmd”.
• Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

• Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
• From there, copy and paste the MapDrives.cmd.
• After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

• You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
• After that, open the Task Scheduler and select Action > Create Task.
• Next, type a name and description of the task in the General tab.
• Then click on the Change User or Group button and select a local user group and click OK.
• Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
• From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
• After that, switch to the Actions tab and create a new action then choose to Start a program.
• Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

• And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
• Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
• Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.

Windows 10 is has a lot of features that help a user in optimizing a computer. So when the operating system encounters a problem, it is able to provide users with proper resources to get the problem fixed. There are even times when a user is not notified and an issue is either being repaired or dodged in the background. This kind of feature is known as the Diagnosis of the Automatic Repair feature that starts when your computer is booting. In such times, you will either see the “Diagnosing your PC” or “Preparing Automatic Repair” message on your screen. Although this feature is useful and has proven to be effective, some users reported that the process gets stuck. If you experience the same problem, read on as this post will guide you on what to do to fix it but before you start troubleshooting the problem, you might want to perform a Hard Boot first. All you have to do is to power down your computer, remove the battery and the AC adapter and then reconnect them. After that, tap and hold the power button for about 20 seconds and see if your computer boots up properly. If it doesn’t, follow the given fixes below.

Option 1 – Try disabling the automatic Startup Repair

The Automatic Startup Repair window will automatically open during boot when you have some system driver-related problem. So if you think that this is where the problem lies, you can try to disable the automatic Startup Repair.

• Click on Troubleshoot and go to the Advanced options.
• After that, select Command Prompt and execute the following command:

bcdedit /set recoveryenabled NO

• Restart your computer after that and then check.

Option 2 – 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 you’re facing this problem. 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 – Run CHKDSK to check your disk for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

chkdsk /r /f

• Now if you are prompted to run CHKDSK after your reboot your computer, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.
• Once your computer has restarted, try accessing the file and check if the error persists.

Option 4 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like your computer getting stuck in the “Diagnosing your PC” or “Preparing Automatic Repair” screen.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 5 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.