Logo

Windows Upgrade/Activation error 0xc03f6506

There are a lot of home users that often get a computer that comes installed with the Windows 10 Home. And since Windows 10 Pro offers more features and utilities compared to Windows 10 Home, a lot of users also prefer to upgrade their Windows 10 Home computers to Windows 10 Pro. However, while doing so, a number of users reported that they encountered error 0xc03f6506 and they were not able to proceed with the upgrade.

If you are one of these users, when you encounter error 0xc03f6506, you will see the following error message on your screen:

“The last product key you entered can’t be used on this copy of Windows (0xc03f6506).”

This particular error tends to occur when you go on to activate Windows 10 although it can also appear during the upgrade process. In such cases, you will see the following error message:

“Unable to upgrade your edition, We can’t upgrade your edition of Windows. Try upgrading your edition of Windows again. (0xc03f6506).”

To fix the Activation Error Code 0xc03f6506 in Windows 10, use the options provided below as references but before you proceed, make sure that you create a System Restore point first.

Option 1 – Try to use the Registry Editor

If you have already upgraded from Windows 10 Home to Windows 10 Pro and you’re having trouble with its Activation, then you might want to apply some registry tweaks to fix the problem. How? Refer to these steps:

  • Tap the Win + R key combination to open the Run dialog box.
  • Then type “Regedit” in the field and click OK or tap Enter to open the Registry Editor.
  • Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion
  • From there, look for a DWORD named “EditionID” and once you found it, double click on it and change its Value data to Windows 10 Professional.
  • After that, look for another DWORD named “ProductName” and double click on it to change its Value data to Windows 10 Professional.
  • Once you’re done, restart your computer to apply the changes made successfully.

Option 2 – Try to use Command Prompt

If the registry tweaks you applied didn’t fix the Activation error, then you can try using Command Prompt instead. Note that you can use this option in both scenarios pointed out above.

  • First, you have to insert a bootable drive of the Windows10 installer.
  • Next, tap the Win + X keys and select Command Prompt (Admin) from the menu.
  • After opening Command Prompt as admin, navigate to the root location of the bootable drive inside the Command Prompt command line.
  • Once you’re already there, type the following command and tap Enter:

setup.exe /auto upgrade /pkey <YOUR WINDOWS 10 PRO EDITION PRODUCT KEY>

After entering the command, check if it was able to fix the Windows Upgrade or Activation error 0xc03f6506. If not, refer to the next given option below.

Option 3 – Try to disable the Network Adapter

Just like the second option, you can also use this option for both the given scenarios above.

  • Tap the Win + X keys and select Network Connections from the menu.
  • This will open the settings for your network and on the left side panel, click on the “Change adapter settings” link. This will open Control Panel.
  • From there, click on the network your computer is connected to, and then right-click on the Network Adapter that you are using and select Disable.
  • After disabling the Network Adapter, try to switch to the edition of your copy of Windows 10 again and see if the problem is now fixed and don’t forget to double click on the disabled Network Adapter to get back on the Network.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

How to Fix Error Code 0x80073afc

Error Code 0x80073afc - What is it?

Error code 0x80073afc deals with an antivirus program first built into Windows 8/8.1 This error occurs when Windows Defender, the built-in anti-virus software in Windows 8/8.1 and higher, does not start automatically and users attempt to manually start the program. During the initialization period of the program start-up, something goes wrong and users get a 0x80073afc Error message. The error message states there was a problem with the initialization of the program. Windows Defender provides protection of your computer and it is advised by the Microsoft Corporation that you ensure it starts up automatically on every start-up.

Solution

Restoro box imageFurther Information and Manual Repair

Users have found several manual repairs that have fixed the problem without needing to contact technicians for extra help. While the methods below should solve your problem easily, if this is the first time you have encountered the issue you may want to do a simple restart. This has fixed the problem for some users and is the easiest first troubleshooting move. If it doesn’t work move on to the methods listed below, which are easily completed without extra help.

Before trying any of these methods, please make sure that you are logged into a profile that is listed as the administrator of the computer of his administrative powers enabled. If this is not the case you will not be able to complete the following methods. Please log out and log back in on the administrator profile.

Method 1:

First, check to see if you have a third-party anti-virus program installed on your computer. Some users believe that the built-in Windows Defender program is not powerful enough to handle the safety of their computer so they usually download a third-party program. However, that program may have caused a conflict with Windows Defender and may not allow it to open. If you do have a third-party program installed, try uninstalling it then manually starting Windows Defender.

Method 2:

If method one does not work, you may be infected by malware or a virus that has tampered with the settings on your computer and will not allow Windows Defender to start automatically or manually.

First, open Run by holding the “Win” key and pressing the “R” key. Then type “Regedit”. The program will ask for permission to follow through with this action. Click on “Yes” and the Open Registry Editor will open.

Find the HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionImage File Execution Option and check to see if there are any files similar to MSASCui.exe or MpCmdRun.exe. If there are any file entries that resemble that, you will want to right-click on them before selecting the “Delete” option. If you do not see any entries that match, this is not the issue with your Windows Defender and you will want to try another method.

The Registry on your computer is very important. It helps tell your computer what programs are safe to run, what programs should be run, and what programs should not be run. If it is tampered with by a virus or Malware, multiple system operations can be affected.

However, if you did find similar file names, and you deleted them, try to start Windows Defender manually. If it does not work again, move on to the next method. 

Method 3:

If the first two methods do not work for your issue, and you are still receiving error code 0x80073afc when attempting to start Windows Defender, this step should solve the problem if you have Restore Point installed on your computer, which you most likely do.

For this method, we will be restoring your computer to a previous Restore Point. First, just like in method two, hold the “Win” key and press the “R” key. This will open run. Next type “Rstrui.exe” and click “ok”. After some time, you will see System Restore Windows. Click “Next” and select the restore point that you would like to go back to. After your computer has restored to the point you selected, check to ensure that Windows Defender has started correctly.

If the above methods aren't able to rectify the issue, you might have to download and install a powerful automated tool to get the job done.

Read More
A Simple Guide to Fixing Error Code 0x80070424

Error Code 0x80070424 - What is it?

The error code 0x80070424 is a Windows PC error. It may occur when using Windows Update, Microsoft Update or while trying to change Windows Firewall settings. This error does not allow you to enable or disable the Firewall on your PC. It is quite common on Windows 7 and Vista. Symptoms of error code 0x80070424 include Windows Firewall may not be listed on Services.msc, inability to change Windows Firewall settings and you may come across this error message when restarting your PC, “Base Filtering Engine Service could not be found in the system”.

Solution

Restoro box imageError Causes

Some of the common causes of the error code 0x80070424 include:
  • Base Filtering Engine Service file corruption
  • Registry issues
When you encounter this error code on your system, it is recommended to fix it immediately as this error can lead to serious PC damages.

Further Information and Manual Repair

To resolve the error code 0x80070424 here are some of the best DIY solutions for you. By following these solutions, you can fix the error all by yourself. These are simple, easy, and quick PC fixers that require no technical expertise. Just follow the simple steps and the error will be resolved in the shortest time.

Re-Install Windows Firewall & Filtering Engine

If the underlying cause of the error 0x80070424 is Base Filtering Engine Service file corruption, then the best way to resolve it is to download the Firewall and register file from a reliable website. Once you download it extract the zip on your desktop.
  • Double click on both files one by one to confirm their installation on your PC. Once installed, restart your PC and click on the start button. Search file type and run and then press enter.
  • When the Run window opens, type REGEDIT and click OK. After that, from the left sidebar navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesBFE.
  • Now simply right-click on BFE folder and choose permission. Once that’s done, click on add button and type everyone then press OK to confirm settings.  Here you will see the ‘everyone’ added field.
  • After that in the below permission panel, tick the box that says Full Control and confirm. Now close the window and go to the menu and type services MSC.
This will open the service window. From the list search for ‘Base Filtering engine file’ right-click on it. Now search for Windows Firewall and see if you can change the settings. This procedure is most likely to resolve the error code 0x80070424 on your PC. It is time-consuming but worth it.

Use a Registry Cleaner

None the less, if the error is triggered by registry issues, then it is advisable to download Restoro. This is an advanced and highly functional PC fixer integrated with multiple utilities including a powerful registry cleaner. The registry cleaner utility detects all registry issues on your system and fixes them in seconds. It wipes out the excess, unnecessary, and obsolete registry entries and files corrupting your system cleans, and restores the registry. It is user-friendly and compatible with all Windows versions. So whether you are using Windows 7, 8, XP or Vista, you can run it on all versions with ease and resolve the error code 0x80070424 generated by registry issues. This software also includes other functional and value-added features like antivirus and a system optimizer. Click here to download Restoro and resolve error code 0x80070424  on your PC today!
Read More
How to Fix the Socket Error 10060

Socket Error 10060 - What is it?

Socket Error 10060 is a typical Outlook Express error. This error often occurs when the connection to the server fails. It specifically refers to a timeout while communicating with the email providers servers. The vast majority of all emails use SMTP for outgoing mail. Socket error 10060 in most instances is related to the SMTP settings for the user’s email. The error message is sometimes displayed in the following format:
Outlook Express Socket Error10060 - The connection to the server failed Account:’ your account’
Another thing you must know about this error is that it only stops the user from sending emails. This means that you can only receive emails, not send them.

Solution

Restoro box imageError Causes

The cause of this error code is hard to narrow down typically because there are many causes that can trigger the socket error code 10060. Some of the most common causes of this error code are:
  • Issues in email settings
  • Authentication settings
  • Firewall settings
  • Malware
Though this is not a critical error code it is advisable to fix it immediately without any delays. This error can hamper your communication via email and slow down your work productivity especially if you use Outlook for communication across the organization.

Further Information and Manual Repair

Here are some of the many methods to fix and resolve this error code. To help you resolve this issue, we have selected and listed down the best, quick, and easy do-it-yourself methods. Try them and repair Socket error code 10060 all by yourself without any professional assistance.

Method 1 - Check the Names of POP3 and SMTP Servers

To begin with, first check the names of the POP3 and SMTP servers to ensure that they are correct. Then check the outgoing SMTP port. Contact your email provider to determine the correct settings. Sometimes email providers change this value more than any other in their individual settings. Get it verified. Change the settings if needed.

Method 2 - Outgoing SMTP Server Requires Authentication

Sometimes the error code may occur due to authentication issues. If this is the reason then, don’t worry it is easy to fix. Simply go to the settings options and check the box ‘My server requires authentication’. Once you check the box, try sending the email again. This is most likely to resolve the socket error 10060 on your PC.

Method 3 - Disable Firewall

Your Firewall security may sometimes be the reason for socket error 10060 too. Therefore if after trying method 1 and 2, the error still persists, then it is advisable to disable firewall. Once you disable it, try sending an email using your Outlook account. If it works, the error is resolved.

Method 4 - Scan for Malware

There is a possibility that the Socket error 10060 is popping on your PC due to malware infection. If so, then it is advisable to download Restoro. This is a highly functional and a user-friendly PC fixer deployed with a powerful antivirus and several other scanners. Run it on your PC to scan for malware. It detects and removes all types of malware including Trojans, viruses, adware, spyware, and more in seconds. Click here to download Restoro to resolve socket error 10060 on your system today.
Read More
Fix VIDEO_SCHEDULER_INTERNAL_ERROR
As you know, the Graphics Card in a computer is one of the important components in an operating system as they are responsible for rendering various objects in your computer. However, there are cases when the performance of this rendering can degrade and your computer can trigger a VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen of Death error instead. The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119 which means that the video scheduler has detected a fatal violation in your computer. Before you troubleshoot the problem, you might want to perform System Restore first as it might help you fix the Stop error. To perform System Restore, refer to these steps:
  • First, press 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 Stop error is fixed or not.
If the VIDEO_SCHEDULER_INTERNAL_ERROR BSOD error is still not fixed after System Restore, then follow the given options below to further troubleshoot the problem.

Option 1 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error is fixed or not.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like VIDEO_SCHEDULER_INTERNAL_ERROR. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Try to rollback, update, or disable the Graphics card drivers

Since the VIDEO_SCHEDULER_INTERNAL_ERROR Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
  • After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 4 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:
  • Tap the Win + R keys to launch the Run dialog box.
  • Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
  • From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
  • Now click on the entries of every faulty driver and click on the Uninstall option.
  • Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

Option 5 – Run System File Checker at boot time

  • Once you get to the Welcome Screen part, click on Next.
  • Afterward, click on the Repair your computer option located on the bottom-left part of the window.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
  • Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 6 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the VIDEO_SCHEDULER_INTERNAL_ERROR error. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.
Read More
Fixing SYNTP.SYS Blue Screen error in Windows
What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:
  • IRQL_NOT_LESS_EQUAL
  • KMODE_EXCEPTION_NOT_HANDLED
  • INVALID_PROCESS_ATTACH_ATTEMPT
To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

  • Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
  • Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
  • Restart your PC and then check for updates under the Windows Update section.
  • After that, it will find the latest available and stable Synaptics driver and then install it.
  • Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
  • Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:
  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • 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.
  • Restart your computer after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • 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.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • Wait for the process to be completed and then restart your computer.

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.SYS Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.
Read More
Fix Error Code 0x80072EE7 in Windows
Installing or updating Google Chrome does not always go smoothly as there are times when it also encounters some errors like the error code 0x80072EE7. This kind of error in Chrome is most likely caused by the Windows Firewall or third-party Firewall (if you’re using one) that blocks the installation or update process. Aside from this known culprit, there are also other factors to consider such as corrupted or incompatible installation files or it could also be caused by some issue with your internet connection. If you face this kind of problem when installing or updating Chrome, you will see the following error message on your screen:
“An error occurred while checking for updates: Unable to connect to the Internet. If you use a firewall, please whitelist GoogleUpdate.exe. (error code 7: 0x80072EE7 — system level).”
Whatever the cause of this error is, you need to use the options prepared below to fix it.

Option 1 – Whitelist the “googleupdate.exe” in Firewall

If the issue is really caused by the Firewall, you need to whitelist the googleupdate.exe program to fix the error. To do that, follow these steps:
  • Tap the Win + E keys to open the File Explorer.
  • Next, copy and paste the following location in the address bar and tap Enter to go there.
Control Panel/All Control Panel Items/Windows Defender Firewall/Allowed apps
  • After that, click on the Change Settings button, and from the given list, look for Google Chrome.
  • Now check both Private and Public connections for it and then click on OK and see if it fixes the error or not.

Option 2 – Disable the proxy server for LAN

If the problem has something to do with your internet connection, then you can try disabling the proxy server for LAN and see if that helps.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
  • After that, go to the Connections tab and select the LAN settings.
  • From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
  • Now click the OK and the Apply buttons.
  • Restart your PC.
Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Check your VPN

If you are using a VPN application, then this option should apply to you, if not, skip this option and proceed to the next one. There are times when VPN software causes some issues like this error. If that’s the case, you can try to disable your VPN temporarily and see if the error is resolved or not and if turns out that your VPN is the culprit, you have to uninstall it and install a new one or its latest version. To uninstall it, follow the steps below.
  • Tap the Win + R keys to open the Run dialog box
  • Then type “appwiz.cpl” in the field and hit Enter to open the Programs and Features in Control Panel.
  • From there, look for the VPN service you are using, select it and then click on Uninstall to remove it.
  • After that, restart your computer and try to install the latest version of the program again. It should work now. If not, proceed to the next available option below.

Option 4 – Try to run the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 5 – Reset Google Chrome

Before you proceed, make sure that the Chrome browser is not running anywhere in the background via Task Manager. Once you’ve made sure that it’s no longer running, refer to these steps:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “%USERPROFILE%AppDataLocalGoogleChromeUser Data” in the field and tap Enter to open this location.
  • From there, look for the Default folder and then tap the Shift + Delete button and if a confirmation prompt appears, click on Yes.
  • After deleting the Default folder, open Google Chrome and click on the three vertical dots icon located in the top-right corner to open the menu.
  • Next, click on Settings and scroll down and then click on Advanced to open the Advanced Settings.
  • Then scroll down until you see the “Reset and clean up” section and click the “Restore Settings to their original defaults” option.
  • After that, you will see a confirmation box and from there, click on the Reset settings button to reset your Google Chrome browser.
Read More
Mapped network drives are not working
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.
Read More
Fix DISM Error: The scratch directory size ...
One of the most useful and powerful built-in utility in Windows 10 is the DISM tool. This tool can be used with the Command Prompt command line as well as for other purposes. However, it is not without flaws and there are times when you may encounter some issues while using it. One of the problems you can get while using the DISM tool is the following error:
“The scratch directory size might be insufficient to perform this operation”
This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:
mkdir C:Scratch
Note: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:
/ScratchDir:C:Scratch
 Note: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.
Read More
Something went wrong, We couldn’t start
There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:
  • Open any Office app.
  • Then click on File and look for your name located in the top-right portion.
  • Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.
  • Open Windows settings and click the Apps and Features option.
  • Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
  • This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.
Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.
Read More
Fix CLOCK_WATCHDOG_TIMEOUT in Windows
If you encounter the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death error while using your Windows 10 computer then it is most likely caused by a specified processor which is not processing interrupts. This occurs when the processor is deadlocked or nonresponsive. Specifically, this kind of Stop error occurs when the processor is having a hard time with the cooperation of its threads and cores. The threads are the tasks performed by cores and some cores can have many threads at the same time. And this is where the problem begins – one thread is waiting for an adequate response from another thread or one kernel is waiting for a response from another kernel and those responses are not coming. In other words, when the processor is unable to continue the processing of tasks since its resources are occupied and are interdependent to get free, such a state is called Deadlock. The CLOCK WATCHDOG TIMEOUT bug check has a value of 0x00000101 which means that an expected clock interrupt on a secondary processor, in a multiprocessor system, was not received within the allocated interval. To troubleshoot the problem, you can check out the possible fixes provided below but before you proceed, make sure that you boot your computer into Safe Mode with Networking only.

Option 1 – Undo or disable overclocking if you have overclocked your system

  • Go to the Start Menu and open Settings.
  • Next, select Update and Security and go to the Recover tab.
  • From there, click on Restart now in Advanced startup. This will restart your computer.
  • Once you’re in the Advanced startup, go to Troubleshoot and then select the Advanced Options.
  • From there, select the UEFU Firmware Settings.
  • Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
  • From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
  • Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
  • Start your computer normally and check if the CLOCK_WATCHDOG_TIMEOUT 0x00000101 error is now fixed.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like CLOCK_WATCHDOG_TIMEOUT 0x00000101. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 5 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the CLOCK_WATCHDOG_TIMEOUT Blue Screen error.

Option 6 – Troubleshoot the BSOD error in Clean Boot State

You can also troubleshoot the Blue Screen error in a Clean Boot state. There are times when third-party applications cause BSOD errors. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 7 – Try to update the BIOS

Updating the BIOS can help you fix the CLOCK_WATCHDOG_TIMEOUT BSOD error 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.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status