Fix The drive is not a valid backup location

Error Code 0x80d02002? - What Is It?

Error Code 0x80d02002 is one of the common errors encountered by Windows users upgrading to Windows 10 or installing new Windows updates. This error results in program lock-ups, system crashes, and freezes, or slow PC performance. It can also cause possible loss of private data on your device.

Some of the common error messages involving Error Code 0x80d02002 include:

• Something went wrong, Please try again later. Windows update error dt_000 – 0x80d02002
• Error(s) found: Code 0x80d02002 Windows update encountered an unknown error. Windows update ran into a problem.
• Windows Update Cannot Check For Updates – 0x80d02002
• 0x80d02002 – Windows could not search for new updates. An error occurred while checking for new updates for your computer. Some updates were not installed.
• There were some problems installing updates, but we’ll try again later If you keep seeing this and want to search the web or contact support for information, this may help – 0x80d02002

While upgrading to Windows 10, depending on the state of your computer, you might encounter other error messages, including error code 0xc000021a. 

Solution

Error Causes

Error Code 0x80d02002 normally occurs when a user updates their system, upgrades to Windows 10 from Windows 7 or Windows 8/8.1, or installs new Windows updates. There are several reasons why this error happens which includes:

• Internet connection problems
• Blocked system ports
• Conflict on system level

Further Information and Manual Repair

In trying to fix Error Code 0x80d02002, you can employ manual repair methods to effectively and efficiently solve the issue. However, keep in mind that one tiny error made in using the command prompt can result in data loss or put your computer in a no-boot situation. In such cases, you can seek help from a Windows professional or consider using an automated tool whenever necessary.

You can try doing the following manual repair methods in an attempt to fix Error Code 0x80d02002:

Method One: Reset Windows Update Components

In trying to fix Error Code 0x80d02002, you may try resetting manually and check the Windows update components by doing the following steps:

1. Right-click on the Start button then select Command Prompt (Admin) from the list to open a Command Prompt window.
2. Once the Command Prompt window appears, type or copy and paste the following commands all at once then hit Enter:

net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver pause

3. Exit the Command Prompt then check if the issue is resolved.

Method Two: Check If The Region Is Correct

1. On the Start screen, type Region. Afterward, click on Settings then hit
2. Under the Format tab, choose English (United Kingdom).
3. Select Language Preferences then click on Add a language. Afterward, add “your language.”
4. After you’ve added your preferred language, choose it then click on Move Up to make it the first language. Close now the Language window.
5. On the Region window, select Additional Settings and see if the values are the same.
6. Select the Location tab then change the Home Location to “your country,” then hit

Method Three: Perform an SFC Scan

Check if there are system files that need to be repaired by running an SFC Scan. Follow the steps below:

1. Type CMD in the search bar then right-clicks on it. Select Run as Administrator. This will open a Command Prompt window in elevated mode.
2. In the next window, select
3. Once the Command Prompt window appears, type the command: sfc /scannow
4. Leave the Command Prompt window open and wait for the process to complete. This might take a while depending on how fast or slow your device is.
5. When everything’s fine, the message saying “Windows Resource Protection did not find any integrity violations” will appear.

 Method Four: Disable Skype or Antivirus

There are times when Skype or your installed antivirus can conflict in updating your system. You can disable first your antivirus or Skype as you update your system and enable them once again when you successfully update your system.

Method Five: Download A Powerful Automated Tool 

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

Copy & Paste function is an essential option in properly working Windows, from copying text to weblinks and many other sources like pictures and files it is one of the crucial features in Windows. When the copy and paste feature is not working we are somewhat left in Windows limbo, essentially Windows itself is working but without this specific feature it is very hard, almost impossible to get any work done, if you are an unfortunate user who has faced this particular issue do not worry, we have solutions for you.

1. Update Windows

   Glitches come in various forms and sometimes they are introduced in updates, check to see if it is available Windows update and if it, download and install it, there is a very high chance that the next update will bring fixes for known glitches.

2. Disable antivirus

   A good antivirus is an essential piece of software for any PC, however, sometimes it can interfere with the basic operations of windows itself. Disable it completely to see if copying and pasting will start to work, if this is a case, see can you somehow turn options off in antivirus or switch to another one.

3. Run Check disc

   Corrupted applications and system files can cause issues with Windows functioning, the easiest way to solve this issue is to run build-in Windows Check disk utility and let it scan and fix potential issues.

4. Run SFC

   If the check disk failed to fix the issue, run command prompt as administrator and type in sfc /scannow, file checker will go through all files and fix if it finds anything including corrupted system files. Reboot your system after the operation completes. Please note that an SFC scan can take a long time sometimes, do not interrupt the scanning process and leave it to finish.

5. Restart rdpclip process

   Restarting rdpclip.exe can solve the issue. Open task manager and under process find rdpclip.exe, right-click on it and end it, then go to windows/system32 and search for rdpclip.exe and double click it. Please note that you will be able to find this process only if you are on a remote PC machine, on a local user machine rdpclip is not running.

6. Rollback to the previous system restore point

   If this particular issue was introduced in the latest update and previous solutions have not worked, roll back to the restore point where everything was working as it should.

7. Stop virtualization

   if you are using virtual software there is a chance that the shared clipboard feature is interfering with Windows, turn the Virtual machine off and try copy & paste again.

A number of users reported lately that their Windows 10 PCs automatically boots into the BIOS whenever they start their computers. And when they tried to exit the BIOS and restart their computers, it still boots into the BIOS. If you are one of the users who experience the same problem, worry not for this post will walk you through what you can do to resolve the problem. Each time a Windows 10 computer boots, it goes through a lot of processes and one of them is where it checks the computer for any hardware issue such as hard drives, peripherals, as well as external devices. So if it finds some issue, the computer will halt the boot process and will boot into the BIOS. To fix this, there are several suggestions you can try. You have to check if you’ve pressed any key, especially the F2 or F12, or Del keys. You also have to check the peripherals and external devices in your computer or update the BIOS or reset it. For more information, make sure to follow each one of the options laid out below.

Option 1 – Try to check for any pressed key

The first thing you can do is to check for any pressed key. This might not make any sense but a pressed key can actually cause this problem. So you have to check if you have the F2 or F12 or Del buttons pressed since these are hardware keys that are usually set by the OEM to boot into the BIOS.

Option 2 – Try checking the physical device connections

You might also want to try checking if there are other devices that are connected to your PC. This is because the configuration of the BIOS or UEFI might be configured in a way that any external device connected to the computer has a higher boot priority compared to the hard disk.  And if it’s really the case, the externally attached disk might be the drive your computer is trying to boot into and not the hard disk. In such cases, Pen Drives, USB storage devices, CDs, DVDs, and so on, are included in this category of physical device connections.

Option 3 – Try to set a proper boot device

If the Boot Manager wasn’t able to locate a proper boot device, then it could be the reason why your computer boots into the BIOS when you turn it on. Thus, you have to check if there is an available proper boot device. You can usually find it under the Boot priority section. However, if you’re unable to locate your hard drive or SSD under the Boot device, then you have to change the hard drive but you have to check first if it is properly plugged in and that it works on other computers. If it works on other PCs, then the problem lies in the motherboard of your computer, and in that case, you have to consult its manufacturer.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the issue but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 5 – Try resetting the BIOS/UEFI configuration

You might also want to reset the BIOS configuration which will lead to arranging the boot configuration since it is intended by the manufacturer. Note that this will get rid of any blockage in the boot process. All you have to do is take out the CMOS battery for a couple of seconds and then put it back again. After that restart, your computer and will be booted directly into Windows. Resetting the BIOS would also get rid of any password set for BIOS and you need to change your CMOS battery in case it didn’t work.

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:

“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”

 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.

Error Code 0x8007267C – What is it?

Error code 0x8007267C is specific to Windows 10. This error is triggered when no DNS server is currently configured in your network settings during the Activation process. If you are fairly confident in your ability to address command-line tools and networking issues, you can follow the steps below to try to remedy the error code on your own. If not, you may need to contact a qualified technician in order to resolve the error successfully.

Solution

Error Causes

The cause of Error Code 0X8007267C within the Window 10 system is fairly straightforward. Windows Activation requires a valid DNS server to be configured in order to complete the Activation process; if one is not available or properly configured, then you may see this error code and Activation will fail.

Further Information and Manual Repair

The following methods may help you to resolve this error, but you’ll need to have some familiarity with command-line tools to complete the steps successfully. If these methods do not work or if you are uncomfortable in using the command prompt, you may need to consult a technician to fully resolve this particular error code on the Windows 10 system.

Method 1: Register a DNS server within your network properties and test the connection.

In order to resolve this error code, client connectivity to a DNS server must first be established. The following steps may help you to determine the root problem with your connectivity status:

1. Open a command prompt, after which you'll run IPCONFIG /all
2. Verify the following values: The IP address that has been assigned, the DNS server, the subnet mask, and the default gateway. Compare each to ensure that all are set with the values that correspond to your specific environment
3. Check for basic IP connectivity to the DNS server using the PING command. In using the PING command, utilize the address of the DNS server found in Step 1

ping <DNS Server IP address>

If basic connectivity to the DNS server in question is failing, then you will need to resolve that issue before going further in the process.

After troubleshooting the above basic connectivity issues to the DNS server, you can reattempt Windows Activation by using the command below from within an Elevated Command selection:

cscript windowssystem32slmgr.vbs -ato

If the steps above did not work for you, you may want to try the steps found in method 2.

Method 2: Use phone-based authentication with a MAK (multiple activation key).

If a DNS server is not connected to your network, you can use an alternative method to complete the Windows Activation process. Bypass Method 1 by using a MAK product key instead to activate the volume license installation. Certain MAK product key providers have a variation on the specific key numbers that you will need to use. If you are using TechNet media or MSDN media, you will have to change the product key listed to the product key provided. The product keys provided by either TechNet media or MSDN media for Windows Server 2008 or for Windows Vista Enterprise will be the MAK product key that you will enter in a later step.

Like the previous method, you will need to have some familiarity or confidence in your ability to operate Command Line tools before proceeding. Once you have found your MAK product key, you’ll need to open a command prompt and use the following command to change the product key to match the MAK product key, which should look something like the example below:

            slmgr –ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

After completing the product key change, use the following command to initiate the phone activation wizard, thereby completing the activation of the system:

            slui 04

The activation wizard should be able to walk you through the remainder of the process in a step-by-step manner. In addition to appearing as an error code in Windows 10, this particular error may apply to multiple versions of Windows, including:

• Windows 7 Enterprise
• Windows 7 Enterprise E
• Windows 7 Enterprise N
• Windows 7 Professional
• Windows 7 Professional E
• Windows 7 Professional N

Steps to address the error code may be different in any of these other versions of Windows. If you have difficulty in resolving the error effectively, seek professional technical help.

As you know, the Google Drive service is a Backup and Synchronization service provided by Google. It was launched way back in April 2012 which provides users with the options to synchronize, store and share files by uploading them to Google’s servers where they stay until they are deleted personally by the users and can be accessed anywhere using the Google Account that’s used to upload them. Recently, a lot of users reported that they were unable to connect to Google Drive from their Windows 10 computers. This kind of problem has been noticed in the middle of the upload process and can be seen at times after the app launches. If you also experience the same issue, then you’ve come to the right place as this post will guide you in fixing it. There are a lot of possible reasons why this kind of problem occurs. It could be that the app was not able to launch properly or the internet got disconnected when the app was about to launch. It is also possible that the Firewall has blocked the app from connecting to the internet or that the antivirus program is preventing the app from making contact with its database. Aside from that, it is possible that the account you are using on your computer is preventing Google Drive from connecting to the internet due to some configuration errors. Follow the suggestions provided below to fix the connection issue with Google Drive.

Option 1 – Configure the Firewall

As mentioned, the Windows Firewall might be blocking the app from contacting its database so, in this option, you have to allow Google Drive through the Firewall. To do so, follow these steps:

• In the Windows Start Search, type “firewall” and click on the “Allow an app or feature through Windows Firewall” option from the search results.
• After that, you will see a list of apps, and here, click on the “Change Settings” button.
• Next, scroll down and make sure to check both the “Public” and “Private” options for Google Drive.
• Now click on Ok to save the changes made and then try to launch Google Drive again.

Option 2 – Try to launch Google Drive again

Google Drive might have not launched properly that’s why it can’t connect to its servers so you can try to launch it again and see if it helps.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and click on the “View” option located at the top.
• After that, uncheck the “Group by Type” option and click on the “Google Drive Sync” from the list of processes.
• Then click on the “End Task” option and close the Task Manager.
• Launch Google Drive again and see if the issue is now resolved.

Option 3 – Temporarily disable third-party antivirus

Aside from Firewall, antivirus programs, especially the third party ones, are also known to block files applications the instant it detects a threat to the system. Thus, your antivirus program might be the reason why you can’t download anything on your Windows 10 computer. To fix this, you can try to disable the antivirus program on your computer in the meantime and then try to launch Google Drive again. Do not forget to enable them again as disabling them can leave your computer vulnerable to cyber threats.

Option 4 – Try to create a new account

There are times when a certain configuration for a user account might be blocking some elements of the Google Drive app. In such cases, you can try to create a new account to fix the problem.

• Click on the Windows key and then click on the icon for Settings.
• From there, click on the Accounts button and select the “Family & Other People” option from the left pane.
• Next, click the “Add someone else to this PC” option.
• After that, click on the “I don’t have this person’s sign-in information” option and select the “Add a user without a Microsoft Account” setting.
• Type in the credentials for the new account you are creating and click on Next.
• After the account is created, click on the account and then select the “Change account type” option.
• Click on the drop-down menu and select the “Administrator” option and then click on OK.
• Now sign out of the current account and sign in to the new one and then open Google Drive again.

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

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

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

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

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

Option 2 – Try to use Windows PowerShell

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

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

As you know, one of the most highlighted features of Windows 10 is Windows Updates. It was offered to the customers as a service rather than a product with the release of Windows 10 under the scenario of Software as a Service which led to Windows Updates being set by default on Windows 10 and without an option for any users to disable it. Although not all users are happy with what Microsoft did, this is an ultimate step towards the greater good of all its customers since Windows Updates helps users in keeping their computers secured against all kinds of threats as well as provide them with the greatest and latest updates from Microsoft. So if you are one of those users who approved of the Windows Updates service, then read on as this post will guide you in running Windows Updates from Command Line either via Command Prompt or Windows PowerShell. For the complete set of instructions, refer to the options given below.

Option 1 – Run Windows Update via Command Prompt

Command Prompt in the Windows operating system exists for a very long time now compared to the comparatively new Windows PowerShell. That’s why it has similar capabilities to run Windows Updates. However, the highlighting point here is that you don’t have to download any module for Windows Updates. To get started running Windows Updates using Command Prompt, refer to the steps below.

• First, type “cmd” in the Cortana search box, and from the search results, right-click on Command Prompt and select the Run as Administrator option to open it with Administrator privileges.
• If a User Account or UAC prompt appears, just click on Yes to proceed.
• Next, type in the commands listed below, and don’t forget to tap Enter right after you type each one of them.
  • UsoClient StartScan – use this command to start checking for updates.
  • UsoClient StartDownload – use this command to start downloading updates.
  • UsoClient StartInstall – use this command to start installing the downloaded updates.
  • UsoClient RestartDevice – use this command to restart your computer after you install.
  • UsoClient ScanInstallWait – use this command to check, download and install updates.

Note: Keep in mind that the commands in Command Prompt listed above are only meant for Windows 10. On the other hand, if you are using an older Windows version, you can try using the following commands instead:

• wuauclt /detectnow – use this command to start checking for updates.
• wuauclt /updatenow – use this command to start installing the updates detected.
• wuauclt /detectnow /updatenow – use this command to check, download and install updates.

Option 2 – Run Windows Updates via Windows PowerShell

If you run Windows Updates in the Windows PowerShell, it will require you to install the Windows Update module manually. Hence, you have to get the Windows Updates downloaded and install Windows Updates.

• Search for PowerShell in the Cortana search box and then run it with administrator privileges.
• Once you’ve opened the Windows PowerShell, type the following command and hit Enter.
  • Install-Module PSWindowsUpdate – use this command to install the Windows Update module for Windows PowerShell.
  • Get-WindowsUpdate – use this command to connect to the servers of Windows Update and download the updates if found.
  • Install-WindowsUpdate – use this command to install the Windows Updates you’ve downloaded to your computer.

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.