Can’t download anything on your Windows PC

If you have a BlueTooth device on your computer, you know that each time you need to receive or transfer the file you need to find the icon in the system tray, right-click on it and choose the desired option. But there is a simpler solution, create a Bluetooth icon on the desktop so it is always easy to access. Open File Explorer by pressing ⊞ WINDOWS + E Go to C:\Windows\System32 Find fsquirt.exe Right-click on it and choose copy Go to the desktop and right-click, choose paste Rename the file to Bluetooth And, you are done!

Both the Windows 10 and Windows Server operating systems have a number of common system files that vary from the ones that support the installation, boot process, and other operations or tasks in the system. However, if any of these files get corrupted, it might cause some errors during the setup of the Windows 10 operating system. One of these errors is the “Windows cannot find the Microsoft Software License Terms” error.

“Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.”

The only option given when you encounter this error is to click on the OK button and nothing else and then the setup gets interrupted and won’t push through. To fix this error and proceed with the installation, you can try to get a new installation image or switch ports, or fix the CFG file. For more details, follow each one of the potential fixes provided below.

Option 1 – Try to get a new installation image

It is possible that there might be some issues with the installation image. It could be corrupted or was modified illegally. Or it could be that the bootable storage device created might have damaged sectors or installation. To resolve this problem, you need to download a fresh copy of the Windows 10 installation image using the Windows Media Creation tool or simply use the ISO image separately and then build a bootable USB.

Option 2 – Try to switch Ports

The error might be caused by the connection to the USB port. It could be that the port is unstable due to a number of factors that resulted in the interruption of the installation process. To fix this problem, you can try switching the USB port or if you are using an optical drive, you can get an external USB optical drive or connect it to another port internally and see if it fixes the problem.

Option 3 – Try to fix the CFG file

If none of the first two options worked, then you might want to fix the CFG file. This file is a configuration file format used for storing settings. All you have to do is download the CFG file. Once you’ve downloaded this file, copy this file to the root of your bootable drive and then check if it fixes the error. If not, then try to copy the same file inside the “/sources/” folder inside the root of the drive. This should fix the error.

If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

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.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.

Error code 0x8007007b - What is it?

Error code 0x8007007b will present itself when Windows users are trying to activate Windows. You may try to activate it through the update and security option, but it is likely that you will receive the same error code. Error code 0x8007007b may be presented when Windows 7 and Windows 8.1 users try to upgrade and activate Windows 10 on their computer.

Common symptoms include:

• An error message will display that says Windows cannot be activated. The KMS host cannot be located in the DNS, please have the system administrator verify that the KMS is published correctly in DNS.
• Error 0x8007007b will be displayed, stating that the file or directory name or the volume label syntax is not correct.

Solution

Error Causes

There are multiple causes for the user to see this error code, including if a user is using volume-licensed media while installing a number of various Windows operating systems. This error may also be caused because the activation wizard cannot connect to a KMS host computer. It is likely that if the user has a volume-licensed form of media, they were likely given a MAK (multiple activation keys).

Further Information and Manual Repair

There are several ways to go about repairing error code 0x8007007b. It is important to try all of the methods, but if it is too difficult or you do not know what you are doing, please do contact a Windows repair technician. They will likely be able to fix the problem with ease.

Method One: Instead of KMS activation, use a Multiple Key Activation

When KMS activation is not used, and when there is not a KMS server, the product key type should then be changed to a MAK. For MSDN (Microsoft Developer Network) or TechNet, the SKUs that are listed on the media are generally volume-licensed media, and that means that the product key that is supplied is a Multiple Activation Key.

To change the KMS to a MAK, click Start, All Programs, Accessories, and then right-click on Command Prompt. Click Run as Administrator. If prompted for a password or confirmation, enter it now.

When the command prompt opens, type in the following command, and press enter after:

slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx (these x's are representative of the MAK product key).

Method Two

While on the desktop, press the Windows key and R. The Run window should appear, and then you should enter the following command: Slui 3. Press Enter and then wait for the window to appear. This window will ask for the operating system activation product key. Enter the product key and then press the Activate button. Reboot the computer. Now the Error Code 0x8007007b should be gone.

Method Three

Open the Command Prompt with access as administrator as mentioned previously. Enter the following command: sfc /scannow. The command will then complete its task. This will take a good bit of time, so leave the computer to do its work. The sfc must finish the scan. When the scan has finished, reboot the computer. Now you can check for activation. The error code should be gone.

Method Four: When the client can't locate a KMS host on the network to complete activation

This method for correction should be used when the network does have a KMS host computer setup, and the client is not able to locate the KMS host on the network to complete activation.

To verify that the computer does in fact have the KMS host installed. Click Start, All Programs, Accessories, and then right-click on Command Prompt. Run as administrator. If you are now prompted to enter a password or confirmation, do so. When the command prompt box comes up, type in the following command, and then press Enter: nxlookup -type=all_vlmcs._tcp>kms.txt

The command will generate a file, open this KMS file. The file will contain one or more entries. As a default, the KMS host server will dynamically register a DNS SRV server evidence once every 24 hours. In order to check the registry to ensure that this is happening, follow these steps:

• Click Start, type in regedit, and then press Enter.
• Locate the key HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSL and then click on it.
• The DisableDnsPublishing subkey should be present and have a value of 1. If it is missing, create a DWORD value by right clicking DisableDnsPublishing, click Modify, in the Value Data box type in 0, and then click Okay.

Method Five: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

if you were following our articles you are aware that Windows 10 has a build-in-game mode that you can summon by pressing ⊞ WINDOWS + G. But did you know that you can use this to capture and record your screen? Hello and welcome to another great tutorial about how to get the maximum out of your Windows 10, today our topic will be recording your screen using Windows 10 game mode.

• In order to start recording first, we need to bring game mode by pressing ⊞ WINDOWS + G
• In the Game Bar overlay screen, look for the “Capture” window.
• If you don’t see it, click the Widget menu icon on the left. It looks like several lines with bullet points to their left.
• A drop-down list will appear; click “Capture.” The “Capture” shortcut may also be in the Game Bar toolbar.
• Look for the “Capture” widget window in the overlay. There are four buttons on the Capture widget (from left to right):
  • Screenshot: Takes a screenshot of the active window.
  • Record last 30 seconds: Creates a recording of the previous 30 seconds.
  • Start recording: Starts recording your active window.
  • Turn on the mic while recording: If this option is enabled, Windows 10 will capture audio from your computer’s microphone and include it in the recording.
• You’ll notice text underneath the buttons. This is how you’ll know what the active window is, aka what will be recorded. For example, if you’re browsing the web, it will show the title of the open tab.
• To start recording your screen, you must first decide whether you want to use your mic, which is useful if you’re trying to explain something on the screen.
• Next, simply click the Start Recording button.
• The screen recording will begin, and you’ll see a little toolbar appear in the corner of the screen. It will show the running time of the recording, and it also has buttons to stop recording and toggle the microphone.
• When you’re finished, click the Stop icon to end the recording.
• From the Capture widget, click “Show All Captures” to see your recording.
• Your recording will be at the top of the list. Click the folder icon to see all recordings and screenshots in File Explorer.
• These recordings are stored under your Windows user folder at C:\Users\NAME\Videos\Captures by default.

If you got an Activation Error 0xC004F211 after having installed or upgraded your Windows 10 PC, then this indicates that some hardware in your computer has changed which’s causing the error to pop up. Windows might not be able to determine if the key is used on a new computer or if it’s still the same one if you have just removed or upgraded old hardware. But worry not for this post will guide you in fixing the Windows Activation Error 0xC004F211 on your Windows 10 computer. When you encounter this error, you will see the following error message on your screen:

“Cannot activate Windows 10. Try activating again later. If that doesn’t work, contact support. Error code: 0xC004F211.”

Note that although hardware changes cause this error, the minor ones don’t really cause any issues with activation, however, if you have made any significant hardware change such as replacing your motherboard, it will most likely cause the activation error. In such cases, the Windows Activation system will treat this as new hardware and you will need a new license for that. Even if your Windows 10 computer has a genuine key, it might still fail to get activated which results in the Windows Activation Error 0xC004F211. Thus, before you do other troubleshooting steps, you need to run the Windows 10 Activation Troubleshooter first. To do so, follow these steps:

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

In addition, there is an exception offered by Microsoft – if you are connected to a Microsoft account prior to the hardware change, then you can most certainly use the same license key to reactivate Windows 10 again. Microsoft calls this an “Exception path” which should be fixed easily by the Windows Activation Troubleshooter as pointed out earlier. However, if the Windows Activation Troubleshooter isn’t able to resolve the error you can try purchasing a new license. In such rate case, even if you do have a Microsoft account available on your Windows 10 computer, and if Windows was never activated, this solution will not work. And if you haven’t connected your Microsoft account with your Windows 10 computer prior to the major hardware change, then your only option left is to purchase a new license. For you to do that here are some steps you can follow.

• To purchase a new Windows license, the first thing you have to do is click on the Start button > Settings > Update & Security.
• From there, go to Activation and select the “Go to Microsoft Store” option.
• After receiving your new license, you need to go back to Update & Security then go to Activation and select the “Change product key” option.
• Now update your Windows 10 computer using the new key and it should automatically activate your computer.
• Next, you have to create a Microsoft account or connect your existing local account to your online account.
• Once the system links the key and the account, you need not buy a new license in case something like this happens again.

Note: If you are an IT administrator, you need to keep in mind that there is a limit to the number of times you can reactivate Windows on your computer. Moreover, if you don’t see any option to reactivate the license, and it is a work computer, you need to contact your organization’s tech support.

0x800ccc7d - What is it?

0x800ccc7d is an SSL (Secure Sockets Layer) error message code that occurs in applications like Microsoft Outlook or Outlook Express. The error message is displayed as: ‘ unknown error 0x800ccc7d- secure sockets layer ’. Many offices use Microsoft Outlook for email communication and sending instant messages within the office. This is a highly functional application that enables users to interact with peers efficiently, manage contacts, journals, and reminders. However, the error 0x800ccc7d may hamper your ability to send and receive emails efficiently. Therefore it is advisable to repair it right away.

Solution

Error Causes

The error 0x800ccc7d is triggered by the following causes:

• Damaged profile in Outlook
• Incorrect email account settings
• The Outlook installation is corrupt and damaged. This usually happens due to issues in hard disk storage.
• The outgoing SMTP server does not support secure connections

Further Information and Manual Repair

If you come across 0800ccc7d error code while using Microsoft Outlook or Outlook Express, then don’t you worry! This problem can be easily resolved. In fact, it is so easy to repair that you can do it by yourself even if you are not a technical expert. Here are some ways to fix the 0800ccc7d SSL Outlook error:

Solution 1: Use Scanpst.exe

You may not know this but Microsoft offers an inbuilt Outlook Repair tool. This tool is technically known as Scanpst.exe. This tool is useful when you need to repair Basic header corruption. However, it may not be the best choice if the problem is big and complex.

Solution 2: Reset Your Outlook Settings

Sometimes this error message may occur when the STMP server requires authentication or does not recognize the senders' email addresses. In this scenario, you should check your Outlook settings to make sure that your STMP username and server are correct. For this follow this procedure:

• Go to the Tools menu and then click on Accounts
• Now click on your email account then check its properties
• Click general and make sure that your email address is created in your account’s control panel. If not, then edit and create.
• Next, click servers and see if the box next to the option that says My server requires authentication is checked or not. If not, then check it to resolve the error.

Solution 3: Disable any Anti-Virus

Another alternative to resolve this error is to disable any Anti-virus or Firewall you have installed on your PC. Once you disable it then try sending or receiving the email again. This usually works.

Solution 4: Download 0x800ccc7d Repair Tool

The fourth solution available to resolve this issue is by downloading the 0x800ccc7d repair tool. Though it is similar to Microsoft Outlook built-in scanpst.exe tool, but as compared to it the 0x800ccc7d repair tool is a highly functional tool. There are many 0x800ccc7d repair tools available but we recommend you to Restoro. This tool is a third-party tool that can deal, scan, and fix 0x800cc7d error in no time. What makes this repair tool an excellent choice is that it can repair all broken PST files and emails, recover Outlook items, retrieve deleted files, recover password-protected data, split files to recover oversize PST files, and more. To access and install the 0x800ccc7d repair tool all you need to do is download it here and install it on your PC. Now run it to scan errors. Once the errors are scanned, hit the repair tab to resolve. So, next time when you experience the error 0x800ccc7d, try using these solutions to fix the problem right away!

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.

KMODE_EXCEPTION_NOT_HANDLED – What is it?

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

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

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

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

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

Method 1 – Check The Cause of The BSOD Error

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

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

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

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

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

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

Method 3 – Disable/Disconnect From Hardware

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

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

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

Method 5 – Use A Trusted Automated Tool

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

Computer upgrades are the most common and most efficient ones. RAM upgrade is one of the easiest ones you can do and the most common ones but even as simple an upgrade as this one can cause certain issues. If you are experiencing error 0164, memory size decreased after RAM upgrade we are offering you solutions on how to fix this particular error and get your computer back in working order.

1. Change BIOS settings

   Enter your motherboard BIOS (usually by pressing the del key on startup) Load BIOS defaults Save changes and exit If the Error 0164: Memory size decreased issue persists even after loading setup defaults, then it must be configured manually inside the BIOS.

2. Clear CMOS

   Follow the instructions precisely:
   • Turn off all peripheral devices connected to the computer.
   • Disconnect the power cord from the AC power source.
   • Remove the computer cover.
   • Find the battery on the board. The battery may be in a horizontal or vertical battery holder or connected to an onboard header with a wire.
   If the battery is in a holder, note the orientation of the + and – on the battery. With a medium flat-blade screwdriver, gently pry the battery-free from its connector. If the battery is connected to an onboard header with a wire, disconnect the wire from the onboard header.
   • Wait one hour, then reconnect the battery.
   • Put the computer cover back on.
   • Plug the computer and all devices back in.
   • Power on the computer.