Motitags Browser Hijacker Removal Guide

nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache. On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table. Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:

nslookup xyz.com Server: dns.company.com Address: 192.168.1.38 C:> ping xyz.com Ping request could not find host xyz.com. Please check the name and try again.

The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.

Option 1 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 2 – Force Windows to do a DNS lookup using FQDN

• Go to Settings > Network & Internet > Status > Change adapter options.
• From there, right-click on the network and select Properties.
• Next, in case you’re using IPv6, from the list of connections available in the list, select Internet Protocol Version 4.
• Then click on Properties and click Advanced.
• After that, switch to the DNS tab and select “Append these DNS suffixes (in order)” and click on the Add button and then add “.” as a suffix so that each time you query using PING and another tool, it will add a “.” at the end and will force the lookup.

Option 3 – Make sure that there is only one default gateway

If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.

Option 4 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 6 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the issue with nslookup and PING.

Option 7 – Reinstall the Network Adapter Drivers

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

Yes, you read that right, KFC is making a console partnered with Cooler Master. Bizzare at it sounds, it is even more bizarre that the console is designed to keep your food warm!!! You can pull out the drawer from the console out on its top and place some food there in order to keep it warm. The console itself is coming in cylindrical shape powered by Intel CPU and ASUS GPU of the unknown chipset. It has Seagate Baraccuda 1TB SSD and it is VR-ready. The console will have raytracing and will be 4K ready.

My thoughts

Well, my thoughts are somewhat strange, on one side I am not really sold on food heating gimmicks and without specific hardware specifications, it is difficult to say how much power the console will have. Price is also not leaked so that is also a stumbling stone for making an informed opinion. I am a little puzzled and concerned about this whole heating food thing because personally, I can see 2 issues: Console overheating and fat dripping on inside hardware, I am sure they have somehow eliminated this but I would be very interested to see how.

Shortcut virus is an easily spreadable and annoying combination of Worm and Trojan that hides all of your files and folders and then replaces them with shortcuts that look identical to replaced files and folders. Once disguised it will wait patiently for a user's click and once that happens it will replicate itself and further infect the system. This rapid spread can lead to stolen personal data, some system hick-ups, and other system-related issues. This malware mainly affects physical file transfer devices like for example and most USB drives, hard drives, and SD memory cards and it can easily transfer itself to the computer. The advantage of this shortcut virus comparing it to others is that it is mostly undetected by a vast variety of antivirus software. So running just anti-virus software maybe not be enough to remove it from your system. Luckily for all unfortunate users that have caught this annoyance, it can be easily removed fully manually in a short time.

How to Remove Virus from USB and other removable media

Firstly plugin USB, SD, or removable drive. The infection will transfer to your computer when the infected drive is plugged in so before we go to clean the computer itself, clean each removable drive that you have. Also know that infection will spread from computers into removable devices as well if it is not cleaned. Open the File Explorer and remember under which letter is removable drive registered. Open Command prompt but with administrator privileges and go to infected rive by typing its letter followed with “:” (for example D:) and press ENTER Once you have successfully gone to infected drive type in command prompt: Attrib -s -r -h /s /d *.* This will unlock all original files back into removable storage, next copy all files to your computer, and format the removable drive. Once the format is complete, unplug the removable device. Continue to clean all devices with the same method.

How to Permanently Remove a Shortcut Virus from Your PC

Now once we have cleaned all removable devices it is time to fully clean the PC Firstly open the task manager ( CTRL + SHIFT + ESC ), in the process tab find wscript.exe or wscript.vbs, right-click on it (or both if present), and select End Task. Now close the task manager and press Start. Inside start typing in registry editor to search for it and once found open it. Find the following key inside the registry editor: HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Run In the right panel, look for any strange-looking key names, such as odwcamszas, WXCKYz, OUzzckky, etc. For each one, run a Google search to see if it's related to shortcut viruses. If any returns a positive match, right-click on them and select Delete. !!! Accidentally deleting an important key can cause Windows to become unstable, so double-check everything !!!. Close the Registry Editor Now press ⊞ WINDOWS + R to open the run dialog and type in it Msconfig followed by ENTER. Once the System Configuration window opens go to the Startup tab. In the Startup tab, look for any strange-looking .EXE or .VBS programs, select each one and click Disable. Close the Window. Once again open the run dialog and type inside %TEMP% and press ENTER in order to open the Windows temp folder. Inside this folder delete everything. Next in the File explorer go to C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup Look for any strange-looking .EXE or .VBS files and delete them.

If you are trying to restore your computer using a System Image that has been created by the Windows Backup and Restore tool but encountered an error message instead that says, “Windows cannot find a system image on this computer”, you’ve come to the right place as this post will walk you through in fixing this error. Here’s the complete context of the error message:

“Windows cannot find a system image on this computer, Attach the backup hard disk or insert the final DVD from a backup set and click Retry. Alternatively, close this dialog for more options.”

In the error message, you are offered two choices – to either Retry or Cancel the operation. You can try to select Retry to try again but you will most likely get the same error if you do so. This kind of error can occur if the name of the WindowsImageBackup folder or any of its sub-folders has been modified. On the other hand, this error can also pop up if this folder or any of its sub-folders have gone missing or have become corrupted. To resolve the error, you can try to move the WindowsImageBackup folder or check its sub-folders. You can also try to isolate the System Image file or rename the System Image folder or remove all the unwanted sub-folders as well as use Command Prompt in Repair mode.

Option 1 – Try to move the WindowsImageBackup folder

The WindowsImageBackup folder must be stored in the root of the volume where it is stored, in line with the functioning of the System Restore utility. For example, if the WindowsImageBackup folder is stored in the “C:/Backups/System Restore Backups/New” location, then you have to move it to the C: drive as well.

Option 2 – Try to check the subfolders of the WindowsImageBackup folder

The classification of folders and files plays an important part to restore in restoring a computer from a System Restore point. Thus, if have modified the names of any files or folders inside the WindowsImageBackup folder, then you need to set the defaults. After that, run System Restore again and check if it fixes the error.

Option 3 – Try to isolate the System Image file

If the System Image file is stored in a USB storage device along with various System Restore images, then it’s no wonder why you’re getting this error. To set things right, you have to make sure that the System Restore image you wish to restore your computer from, is the only one that’s present at the root of the USB storage device.

Option 4 – Try renaming the System Image folder

If you have renamed the System Image folder prior to running System Restore, then it is most likely the reason why you’re getting the “Windows cannot find a system image on this computer” error. This error pops up because the System Restore utility in Windows 10 looks out for the WindowsImageBackup folder so if you have renamed it, you need to change its name back to what it originally was to fix the error.

Option 5 – Try to remove all the sub-folders of the WindowsImageBackup folder

If you have stored some foreign files inside the WindowsImageBackup folder, you need to get rid of them right away and return the folder to its default state as this folder must be left alone and should not be meddled with if you want to run System Restore smoothly.

Option 6 – Try to use Command Prompt in Repair Mode

• Open Command Prompt while your computer is in the Repair Mode.
• Next, type and enter this command where you need to replace “<Partition Letter>” with your drive’s letter: dir <Partition Letter>
• After you’ve found the WindowsImageBackup folder in any of the partitions, type and enter this command: dir <Parition Letter>WindowsImageBackup /s
• The command you entered will display all the contents of the folder exceeding 10 GB in total size. You can check and confirm the integrity of the folder and if you find that the integrity is violated, then it is the reason why you’re getting the error.

Signing in to a computer that runs a Windows 10 version OS is usually fast and straightforward. However, there are instances when signing in takes too long especially if there are a lot of programs in the Startup. So if many things are loading as soon as you log into your computer, it will slow down the sign-in process. Aside from programs in Startup, it is also possible that there are too many users that are logged in to the account. In such a case, you will most likely encounter an error that says, “Your computer is running low on resources, so no new users can sign in. Please use an account that has already been signed in”. If you’ve encountered such an error when you try to log into your computer, read on as this post will be guiding you on how you can fix it. Each time a user signs in to Windows 10, it will allocate resources in order to work smoothly. But, in many cases, the system is running low on resources which is why this error pops up and blocks a sign-in of a new user. To fix it, you can try to log out the existing users, or perform a Cold Boot, as well as run both the DISM tool and System File Checker scan.

Option 1 - Try to logout existing users

The first thing you can do is to log out the existing users. If you have a shared Windows 10 computer, you have to check if someone hasn’t logged out. It could be that some background task or there is an existing program that is still running under that account. So you have to make sure to ask the same user to log out in case there is some unsaved work. On the other hand, if that user is not around, then you reboot the computer right away.

Option 2 - Try Performing a Cold Boot

You could also try to perform a Cold Boot to fix the problem. A Cold Boot is a process that makes sure that the Windows 10 Kernel shuts down properly and releases all the resources held by any account. To perform a Cold Boot, just press and hold the physical power button on your CPU until it goes off. After that, boot your computer regularly and see if you can now log into your account without any error.

Option 3 - Try to run a System File Checker scan

System File Checker is a built-in command utility in Windows that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you log into your computer. To run the SFC command, follow the steps given below.

• Boot your computer into the Advanced Recovery mode and from there open Command Prompt.
• 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.

 Now restart your computer and see if the problem is fixed or not.

Option 4 - run the dism tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “Your computer is running low on resources, so no new users can sign in” error. To repair these corrupted system files, you can run the DISM commands:

• Go to the Advanced Recovery mode and select Command Prompt.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

One of the cool and interesting features in Windows is the Screensaver which allows users to display animation or change the wallpaper automatically when the computer is not being used. This feature can also time out and lock your computer when it remains idle for quite some time. However, if you notice that the screensaver of your computer turns on a lot earlier, then you’ve come to the right place as this post will guide you on how you can change the timeout settings of the screensaver of your Windows 10 computer. Usually, the screensaver in Windows 10 is turned off by default, however, if some other user has turned it on or if you have turned it on, you can actually change the timeout settings of the screensaver using several methods. You can do it through the Personalization settings, Registry Editor, as well as the Group Policy Editor. Before you proceed with the instructions provided below, make sure that you create a System Restore point first. Once done, follow each one of the suggestions carefully to successfully change the Screensaver timeout settings in Windows 10.

Option 1 – Modify the timeout settings of Screensaver via Personalization settings

• Open the Start menu and type “screen saver” in the field.
• On the search results that appear, click on the “Change Screen Saver” option.
• From there, you have the option to change the screen saver type, preview, open settings, change the wait time, as well as choose to display lock screen on your resume.
• Now to change the timeout settings of your screensaver, you have to increase the wait time from 1 to 15 or anything that works for you.
• Once done, click OK and exit to save the changes made.

Option 2 – Try to change the screensaver time via Registry Editor

The next option you can try to change the timeout settings in the screensaver is using the Registry Editor. To get started, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows
• From there, right-click on Windows located in the right pane and select New > Key.
• Name the key as “Control Panel” and right-click on it and select New > Key and then name it as “Desktop”.
• Once done, click on the newly created Desktop key to highlight it.
• After that, right-click on any empty space in the right pane and select New > String Value and then type “ScreenSaveTimeOut” and hit Enter to save it.
• Now right-click on ScreenSaveTimeOut and select Modify and then set its value data in seconds.
• Click on OK and exit the Registry Editor to save the changes made.

Option 3 – Change Screensaver timeout settings via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to User Configuration > Administrative Templates > Control Panel > Personalization.
• Then look for a policy setting named “Screen saver timeout” and double click on it and then click on the Enabled option to enable it.
• Add the screen timeout in seconds and click on the Apply and OK buttons to save the changes.
• Restart your computer.

Note: If you want to disable the screensaver feature in your computer, you can always do so by disabling a policy setting named “Enable Screen Saver”.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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.

USB devices are one of the commonly used devices every day – from plugging mobile devices for charging using pen drives, you are making use of USB drives. However, there are times when you might encounter an error message saying, “Unknown USB Device” as you plug your USB device on your Windows 10 computer. So if you encounter this kind of error message followed by either of the following explanations, read on as this post will give you a couple of suggestions you can check out to resolve the issue.

• Device Descriptor Request Failed
• Port reset failed
• The device failed enumeration
• Set address failed
• Error code 43

You can fix this error using several ways. You can try changing the Power Options, update or roll back the USB drivers, turn off Fast Startup, or run the USB troubleshooter. Follow the options given below for more details.

Option 1 – Try to change the Power Options

• Tap the Win + R keys to open the Run utility.
• Then type “powercfg.cpl” and tap Enter to open the Power Options window.
• Next, go to your selected power plan and click the “Change plan settings” option to open a new page.
• From there, click on the “Change advanced power settings” option. This will open a new window where you can see various power consumption options.
• Now look for the USB Settings option and expand it.
• Then set the USB selective suspend setting to “Disabled” for both scenarios: On Battery and Plugged in.
• After that, click on OK and restart your computer to apply the changes made.

Option 2 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 3 – Try turning off Fast Startup

• Tap the Win + R keys to open the Run dialog box and type in “control” to open the Control Panel.
• Next, click on the Hardware and Sound section and click on Power Options.
• Afterwards, select the “Choose what the power buttons do” option from the left side menu pane.
• Now click on Change settings that are currently unavailable and uncheck the entry that says, “Turn on fast startup (Recommended).
• Then click on Save Changes and restart your computer and see if it has fixed the problem or not.

Option 4 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

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.