Fix Windows Update error code 0x80d02002

There are instances when you have to connect to another Windows 10 PC via remote connection from another Windows 10 PC. However, when you encountered an error saying, “Your password may have expired or the remote pc might not accept blank passwords” while doing so then read on as this post will walk you through how you can fix it. Here is the full content of the error message:

“Your password may have expired, or the remote PC might not accept blank passwords. Try connecting again. If this keeps happening, ask your admin or tech support for help.”

It is unknown what the exact cause of the error message is as it could involve several factors. Even so, there are still various potential fixes you can try to fix this kind of error. You can try to check if your password has expired or troubleshoot any issues with the network. You could also use a remote desktop application or configure the settings of firewall or restart the remote desktop service. For more details, refer to each one of the given options below. But before you proceed, make sure that you have someone to help assist you on the other side to help you troubleshoot the issue.

Option 1 – Try to check if the password has expired

The first thing you can do to fix the problem is to check if the password has expired as it could be the reason why you’re experiencing this problem. You have to make sure that you are using a user account that is on the remote computer and then check if the user account password has not expired yet. And if your PC is not within your access, then you can just ask someone to verify the password for you.

Option 2 – Try to troubleshoot network issues

To troubleshoot network-related issues that might be the one that triggers the error, you need to run the Network Troubleshooter. To get started, refer to these steps:

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

Option 3 – Try to use a remote desktop software

A number of users reported that the issue occurred when they used the universal app for Remote Desktop and they were able to fix it by switching to the Remote Desktop application. Thus, you can try to switch to the remote desktop software and see if it fixes the problem or not.

Option 4 – Try to configure Firewall settings

You might also want to configure the settings of the Firewall as it could also help in fixing the problem. It is possible that the firewall is blocking the incoming connection on the remote computer. To check if whether the firewall is the culprit or not, follow the steps below.

• Go to Windows Security and then go to Firewall and network application.
• Next, click on the Advanced Settings link. This will open the classic Windows Defender Firewall and Advanced Security application.
• From there, look for the rule named “Remote Desktop – User Mode (TCP-In)” under inbound rules and check if it has been disabled or not.
• If the rule is disabled, you have to enable it.
• Once done, check if the error is now fixed or not.

Option 5 – Try to restart the Remote Desktop service

If none of the four given options given above worked, you might want to restart the Remote Desktop service as it can help you in fixing the problem. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the Remote Desktop Service and right-click on it, and then click on the Restart option.
• Once done, check it was able to fix the “Your password may have expired or the remote pc might not accept blank passwords” error or not.

Computer crashes are one of the most annoying things that can happen to users. It often loses your data and work, you must spend extra time if you were in the middle of something and can even break Windows itself. Before we move to the article I just want to say that technically there are no random crashes, there is always a reason why the system hangs up, why you received blue screen, annoying restarts out of nowhere and many more PC crashes. In this article, we will explore many possible reasons why something may occur and offer you straight forward solution on how to escape the situation and prevent it from happening again. Without further delay, let's begin:

1. Check switch connectors and power outlets

   Yes, sometimes the most basic approach provides the best results, check to see if your power outlet is stable and providing you with constant voltage, if not, maybe you want to invest in a UPS system so you do not face random shutdowns and restarts during work, also while you are at it, check to see if that reset and power switch are connected properly and that they are not dirty or loose.

2. Clean your PC and check connectors

   Dirt can cause many issues with computers, from overheating to shutdowns to blue screens and memory dumps, check to see if your computer is clean enough and that all connectors are connected tight into their respective sockets.

3. Check the temperature of your CPU

   CPU overheating can cause so-called random freezes and blue screens, the computer might shut down or restart also without any visible reason. Check to see if your fan on the CPU is working properly and change the thermal paste if needed.

4. Check the health of your hard drive

   If your hard drive is beginning to go down the path of dying out, many issues can come from this condition. There are many tools on the internet and in Windows itself to check if your hard drive is working properly.

5. Run antivirus and firewall

   Random lock-ups or similar issues can also occur if by any chance you have some malware on your system, run protection software, and keep it updated to make sure the issue does not come from the computer being infected with malicious applications.

6. Keep system clean

   Have a habit to clean regularly system files and registries, keep removing unnecessary files from your computer and regularly update your Windows and applications along with drivers.

7. Run memory test

   Bad RAM bank can cause many issues during the work, check it out to be sure the problem is not RAM itself.

8. Do not run applications that are too demanding for your system

   Some applications require stronger hardware, and some require the latest hardware, if your computer is a little outdated, running a demanding application can cause issues like freezing, restarts, etc.

9. Remove applications you do not use

   This does not seem like anything important but if you are not using a specific application just remove it from the system, why? Sometimes an application has some ties to certain services and if it is outdated can cause issues for newer ones.

10. Stop installing everything you find on the internet

    Yes, that extension for chrome looks cool, yes, that fancy new player seems sick but if it is from an unverified source and from the unknown publisher without any reviews maybe you are better off with it. You can never tell what you might be placing into your system from the internet.

And that's it, 10 reasons and solutions on what to do on random computer freezes, crashes, etc.

Error 0X800F080C is tied to corrupted system files and .NET framework issues. In this article, we will focus on how to fix it starting first with .NET fixes and then moving to system-related ones. Follow the guide step by step so you can fix this error fast and easily.

.NET issues

As previously stated 0X800F080C error can occur due to issues with .NET framework, 3.5 framework to be more precise and there are two ways we can fix this error. Follow the guide below as presented:

1. Install .NET 3.5 framework from Windows features

   First thing is to try and install the framework from Window features itself. Sometimes installation and activation of .NET 3.5 in other ways can result in this error. To install it do the following: Press ⊞ WINDOWS + R to open the run dialog Inside run type in appwiz.cpl and press ENTER to open up the Programs and Features menu Inside the Programs and Features menu click on Turn Windows features on or off. Check the box associated with .NET Framework 3.5 (this package includes .NET 2.0 and 3.0) Press OK Click on YES and wait for the package to be installed then reboot your PC

2. Run the .NET Repair Tool

   If the previous step was not successful or you already had .NET 3.5 installed then run the troubleshooter in order to fix issues. Go to the official Microsoft .NET framework repair tool website here and download it. Once downloaded install the tool and follow onscreen instructions.

Corrupted system files

If the previous solution has not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system files issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

Error Code 0x8007007B (Code 0x8007007B) – What is it?

Error code 0x8007007B (Code 0x8007007B) is an error that occurs when you attempt to activate Windows 10, as well as Windows Server 2008, Windows Vista, Windows 7, Windows 8, or Windows Server 2012.

Common symptoms include:

• You will see an error message like this: “Error 0x8007007B 'The filename, directory name, or volume label syntax is incorrect”.
• If you are using volume-licensed media to install: Windows 7, Windows 8, Windows Vista Business, Windows Vista Enterprise, Windows Server 2008 R2, Windows Server 2008, Windows Server 2012, Windows 10.
• Your computer is not connecting the activation wizard to a Key Management Service (KMS) host computer.

Solution

Further Information and Manual Repair

Error Code 0x8007007B usually occurs when a product key has been activated too many times. Blocking activation aids in avoiding abuse of the key. If abuse of the key is not the case, it is possible to get the key reset, or you may receive a new key altogether. When you are not sure that you can complete these methods yourself, as they do contain advanced steps, it would be wise to consult a computer repair technician to avoid making the problem any worse.

Generally, the solution can be simple; it is just dependent on how comfortable you are with getting technical in your computer. Volume licensed media means that the media has a preset number of times that it is allowed to be activated. This helps to avoid misuse of the product. Some people install the Windows 10 program multiple times on their computer if they are software developers or do certain types of software testing. It is important to know the cause in order to effectively find the solution.

Method One:

1. From the desktop screen, press the Windows key and S, type “Command Prompt”. Then, right-click on Command Prompt in the results. Select Run as Administrator.  Click Yes when asked about requesting permission.
2. In the Command Prompt box, enter the command: slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
3. The x's represent the product key. Replace these with your unique product key.
4. Type in the following command into the “Command Prompt” window: slmgr.vbs -ato
5. Click Enter
6. Restart your computer and try to activate windows again. It should not show the error code anymore.

Method Two:

1. While on the desktop, press the Windows key and R.
2. A window saying Run should open.
3. Type in the following command: Slui 3
4. Press ENTER and a window should appear.
5. This window asks for you to enter the operating system activation product key.
6. Enter this key in the space provided.
7. After entering this, click Activate.
8. Restart your computer now.
9. Check for activation. The Error code should be gone now.

Method Three:

1. Open the Command Prompt with access as administrator just as in Method One, and enter the following command: sfc /scannow
2. The command will complete the tasks. This will take some time so just let the computer do its thing and work. Let the sfc finish the scan.
3. When the scan is complete, restart the computer.
4. Check for the activation. The error code should be gone at this point.
5. If it is gone, revisit Method One or move on the Method Four.

Method Four:

Call the Microsoft Support Team and explain the problem in as much detail as you can give. Give the team the error code 0x8007007B and ask to have a different product key. When they give you the new product key, repeat Method 2. The Microsoft Support Team will either change your product key, or they will reset your current product key so that it can be used for activation again.

We have all experienced Windows errors over time and that can range from simple ones that will do very little to no harm and can be even system breaking making us lose our work or completely making the PC unusable. No one likes them but they happen, and usually, they happen once we least expect them.

No matter how frequent and unpleasant they might be there are ways to keep them at the minimum and even avoid them.

We will discuss steps that you can take in order to do this, simple tips and guides on how to keep your computer in top form and eliminate not just Windows, but any kind of errors altogether.

Keep your hardware clean

Believe it or not, some serious Windows errors like the dreaded blue screen of death can come from hardware issues not from the software at all. It is very important to keep your computer clean and with enough air flow so it can function properly.

Not so far ago we had an article about cleaning your hardware detailing what and how to do it. Here is a link to the article: https://errortools.com/windows/cleaning-your-pc/

Do not keep applications you are not using

Keeping applications on the drive might seem harmless but sadly that is not the case. Some applications have a certain impact on the system itself after all most of them are tweaking registry entries in Windows and sometimes having too many applications means an increased possibility of conflict over certain resources even when they are not running.

Some applications like adobe creative suite, for example, will have certain services always running in the background, and more of these kinds of applications you have, more services, more places for unexpected errors when they collide. Some of them will also install certain dependencies that could be problematic.

The general idea is: if you are not using it, uninstall it and you will be safer and more resilient to errors inside OS.

Do not use pirated or cracked software

Besides moral and law implications that using pirated or cracked software might bring you there are also certain other things that might be problematic. Certain "free" software might come packet with some problematic malware, for example, it is not uncommon for attackers to use some popular software to pack their malicious application with it.

Other things might be wrong and incomplete tweaking with application in order to bypass security and thus bringing some instability due to scripts needed to run in order to achieve this goal.

Keep your drivers updated

Errors can also come from old drivers or bad drivers, device manufacturers are not all-knowing and perfect, and sometimes drivers can wreak havoc on the system. Having updated drivers can minimize any kind of unexpected behaviors inside the operating system making it more stable and reliable.

You can check your driver version in the control panel inside the Windows OS and then compare it to the ones found on the manufacturer's site, if there are newer available it is recommended to download and install them,

Keep software updated

Applications can have bugs, and bugs can lead to certain errors both in the system and when using the app as well. It is in your best interest to get the latest patch or newer version of the software in order to avoid these unpleasant experiences.

Also, certain codecs and extensions that are installed directly in Windows can also have some unpredictable behavior, updating is the best solution to keep them in line.

Keep Windows updated

Same as with drivers and applications, Windows itself is not immune from bugs and some unpredictable issues. Luckily Microsoft is always working on fixes and features of Windows but in order to actually have benefited from that work, you will need to keep Windows updated. Sometimes a bad update can introduce some errors but you can always roll back to the previous and wait for them to fix everything and then download them all.

Check the health of your hardware regularly

Hardware components have their life cycle, more quality ones tend to last longer but eventually, they will reach the end of their lifecycle. There are a lot of testers for various components in your computer that can check different things and provide you with information about the state of your components.

If you are on Windows 11, Microsoft has included a basic health app inside OS, just type PC health check in search and start the app. For some more detailed information and advanced checks, you will have to use a custom application. There are plenty of them specialized for single components like RAM, SSD, etc. A simple google search with providing you with top results and most of them are free for personal use.

Remember, a faulty component or component that is reaching its life cycle can produce many errors inside the operating system.

If you are familiar with the Dynamic Lock feature in Windows 10, then it has probably made it easier for you to lock your computer the instant you move away from it. This interesting feature does not need any special software like IR Cameras to use this feature as long as your Windows 10 computer supports Bluetooth which it most likely does. However there are times when the Dynamic lock feature is either missing or not working. When that happens, here are some suggestions that could help you. But before anything else, you need to create a System Restore point first since you will be modifying some critical system settings as well as registry files. After you’ve created a System Restore point, refer to the following options below to fix the issue with Dynamic Lock.

Option 1 – Try using the Settings app

• Tap the Win + I keys to open the Settings app and then navigate to Accounts > Sing-in options.
• After that, scroll down until you see the Dynamic Lock section.
• Next, make sure that the checkbox for “Allow Windows to automatically lock your device when you are away” is checked.
• Now that you’re all set, exit the Settings app.

Note: If for some reason the above-given solution didn’t work, you can try the next options below.

Option 2 – Try to pair your Bluetooth Device

If you get a message saying, “Allow Windows to automatically lock your device when you are away” in the Notifications Center or in the Settings app, then you need to pair your Bluetooth device. To do so, follow the steps below.

• Go to Settings > Devices > Bluetooth & other devices.
• From there, make sure that Bluetooth is turned On and then pair your Bluetooth device.
• And if you open the Windows Defender Security Center, you will see the following message as well.
• Simply click on the Add Bluetooth device button and it will open the Bluetooth settings where you can also pair the device.

Option 3 – Try to reinstall or update the Bluetooth driver

The issue might have something to do with the Bluetooth drivers. It could be that it is outdated and needs to be updated or that you recently updated it and since then you have trouble removing the Bluetooth device and so to fix the issue, you can update, roll back or uninstall the Bluetooth drivers. How? Follow the steps below.

• Tap the Win + X keys to open the Device Manager.
• Next, look for the Bluetooth device and right-click on it.
• Select the option “Update driver”.
• After that, a new popup window will appear. In there, select the option, “Search automatically for updated driver software”.

Note: Checking the update may take a few minutes so you’ll have to wait until it finishes. If it is able to find an update, you must install it. And if you want to reinstall the Bluetooth driver, just select the “Uninstall driver” option and follow the next on-screen instructions that follow.

Option 4 – Try to use the Registry Editor

• Tap the Win + R keys to open the Run dialog box and then type “Regedit” in the field and hit Enter to open the Registry Editor.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• After that, navigate to the following registry key:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWinlogon

• Next, look for a DWORD named “EnableGoodbye” located on the right-side panel and then make sure that its value is set to 1 which means that it is enabled while 0 indicates disabled.
• Now close the Registry Editor and restart your computer to apply the changes made successfully.

Option 5 – Try checking the Group Policy setting

If your Windows 10 version has the Group Policy Editor, you can use it to fix the Dynamic Lock issue as well. Simply follow the steps below to use it.

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

Computer ConfigurationAdministrative TemplatesWindows ComponentsWindows Hello for Business

• After that, look for an entry named “Configure dynamic lock factors” and double click on it to open a new window.
• Once you enable this Group Policy setting, the signal rules will be evaluated to detect the absence of a user and will lock the device automatically. On the other hand, if you disable or don’t configure this setting, you can continue locking your computer with existing locking options. Take note that it may be Not configured or Enabled but shouldn’t be set to Disabled.
• Now select the radio button for Enabled and set the Signal rules then click OK.
• Then exit the Group Policy Editor and restart your computer.

Recent Windows updates have been slowly but surely moved a lot of control panel features into settings. This indicates that in the long term goal is probably to get rid of the control panel altogether. No matter how the setting app is easy to use and good there are still things in the control panel that we need and we will still need until they are all moved in the setting application. There are several ways to open and get to the control panel from run dialog to shortcut keys but one perhaps more convenient and easiest way is to just simply have in file explorer right beside hard drives double click away. In order to place the control panel icon inside file explorer, we will need the help of our old friend: the registry editor. As always playing with the registry editor can cause some instability and it is always a smart thing to back up it first before attempting any kind of edits.

Registry editor adding a key

To open registry editor press ⊞ WINDOWS + R to open the run dialog and inside type in REGEDIT followed by ENTER Once the registry editor is opened locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer Right-click on the NameSpace folder on the left navigation pane and then select New > Key Rename the key with {21EC2020-3AEA-1069-A2DD-08002B30309D} (This CLSID code will add access to the Category view of the Windows 10 Control Panel) or with {26EE0668-A00A-44D7-9371-BEB064C98683} (This CLSID code will add access to the large icons view of the Windows 10 Control Panel) Save and exit the registry editor Now when opened, file explorer will show a control panel icon for easy access.

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.

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.

A lot of users prefer to use Microsoft OneDrive when it comes down to cloud storage as it does not only come with the seal of approval from Microsoft but it’s also primarily good and better compared to other cloud storage services. However, that doesn’t mean that OneDrive isn’t without any issues. For one, you might encounter an issue where the OneDrive thumbnails do not show in File Explorer in Windows 10. If you are currently experiencing this problem, read on as this post will help you fix it. As you know, you can add OneDrive to your Windows 10 computer and have all the files locally synchronize to the cloud and so on. This means that whatever is available in the cloud will be seen on your computer. It is smooth and definitely saves you a lot of time which is why a lot of users prefer to use it. So if you suddenly not see any thumbnails in OneDrive, then that would be a problem. You are actually not the only one having this problem as there are other users who reported getting the same issue recently about the picture thumbnails that no longer show up in the OneDrive folders in the File Explorer. At the time of writing, it isn’t clear yet what the cause of the issue really is. Even so, there are still potential fixes you can check out to resolve it, and the sooner you do it, the better as this can be a major problem. To get started, refer to the instructions given below.

Option 1 – Try to disable Files on Demand

The first thing you can do to fix the problem is to disable the Files on Demand. This is what you have to do to get things under control.

• First, right-click on the OneDrive icon located in the taskbar and go-to of OneDrive.
• After that, click on More and Settings. This will open a new window where you have to click on the Settings tab and uncheck the “Files on Demand” service.
• Once done, restart your computer and check if you can now see the thumbnails in the OneDrive folder. However, if it didn’t work, then proceed to the next given option below.

Option 2 – Try to change the icon view

The next thing you can do to fix the problem is to change the icon view. It is possible that the problem might have something to do with the size of the icons than anything else. So you have to change the icon view and to do that, follow these steps:

• First, open Control Panel in Windows 10.
• Next, in the search box, type “folder” and then click on the File Explorer Options.
• From there, click on the View tab and uncheck the “Always show icons” option, and make sure that showing thumbnails is active.
• Now go back to Control Panel and type “system” in the search box. This will open a new window where you have to select the “View advanced system settings” option.
• Then under the Performance section, click on Settings and click on the option that allows you to show the thumbnails instead of icons.