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.
PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1
$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.
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:
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.
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.
-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1
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.
Error Code 0x8007000b has appeared on Windows operating systems from Windows 10 all the way back to Windows XP. In most cases, it occurs when there is a problem within the transaction log for the filing system within Windows.
Common symptoms include:
There are several different ways that you can attempt to resolve the problems that cause Error Code 0x800700b to appear on your operating system. Several of these methods are pretty easy for basic users, but others require some comfort and knowledge in working with advanced tools on your operating system.
If the methods below do not completely resolve the appearance of Error Code 0x800700b on your Windows operating system or if you are not confident in your ability to undertake these steps on your own, you may need to get in touch with a qualified computer repair professional to assist you with the error resolution process. If this error message is not resolved, you could expose your computer to other error codes such as error code 80070103.
The primary cause for Error Code 0x800700b is that there is an issue or corrupt entry in the transaction log for the file system within Windows. This makes it impossible for Windows to complete the Windows Update process. Although the error message states that an unknown error has been encountered, it is usually fairly simple to resolve the appearance of faulty or corrupt entries in the transaction log if you follow the steps below to complete.
There are several ways that you can attempt to resolve Error Code 0x800700b manually on your Windows operating system. At least one of these methods requires some advanced knowledge or skill in using the command prompt, so if you aren’t confident in your ability to follow these steps through to completion, be sure to get in touch with a qualified computer repair technician who can help you to resolve the error.
Here are the top three methods that can be used to resolve Error Code 0x800700b on your machine:
To clear and reset the entries in your transaction log, there are a few simple steps that you should follow:
An alternative method to resolving Error Code 0x800700b is to open and run the System Update Readiness Tool on your machine. This program runs a scan on your Windows operating system to determine whether it is ready for updates, attempting to resolve any errors it encounters along the way.
After you have scanned and run this tool, you should always take the time to restart your computer before attempting to perform the update process, so that any changes made can be successfully applied to your computer.
The System File Checker is a tool for Windows that runs a basic scan for problem files and attempts to resolve them. To run this tool, follow these steps:
This tool should tell you what the specific issues are so that you can resolve them. It may give you a message that the action couldn’t be performed, that corrupt files were fixed, or that corrupt files were encountered, but could not be fixed automatically.
Error code 0xc000021a occurs when the system is unable to start or there’s a failure in critical system processes. Normally, it would take about several seconds for the system to boot and while on the startup process, error code 0xc000021a may take place to block the system to boot up. Users will get a blue screen of death (BOSD) when this error occurs. When upgrading to Windows 10, be careful; you might encounter other error messages such as error code 8007002c.
There are several reasons why error code 0xc000021a occurs. It is important to have a full understanding of what caused the blue screen of death before attempting to fix the error by yourself. See below for a few common causes:
• Computer malware has infiltrated your device.
• Important files such as Winlogon.exe and Csrss.exe are damaged. Winlogon.exe file is responsible for handling the login and logout processes while Csrss.exe is a vital part of Microsoft Client or Server ‘Runtime Server Subsystem’. Once one of these files is damaged or deleted, a stop error will occur.
• When there are mismatched system files installed or system upgrading process failed or still incomplete.
• Premature unloading of Wbemprox.dll
• Newly installed third-party software is not compatible with the operating system.
• There are corrupted, outdated, or incorrectly configured device drivers.
• There’s insufficient space in the system partition. Once the system partition is full, certain errors such as error code 0xc000021a will manifest.
• Windows registry is corrupted or damaged due to a software or system change. This means there are registry entries that are not cleared after uninstalling an application.
In fixing error code 0xc000021a, you might want to try and manually do so. Manual repair methods can give users effective and efficient solutions, addressing the root problems in relation to Windows error codes. Once the manual repair method is correctly implemented, users will be able to resolve issues immediately. However, there might be instances when a Windows professional is needed. In such cases, seek help from a certified Windows expert or you might want to consider using an automated tool whenever necessary.
Dism /Online /Cleanup-Image /CheckHealth Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /RestoreHealthalso
nbtstat -R nbtstat -RR netsh int reset all netsh int ip reset netsh winsock reset