Customize Lock Screen in Windows 11

If you suddenly encounter Activation Error codes such as 0xC004E016, 0xC004F210, 0xC004F034, and 0xC004F00F on your Windows 10 computer, then they all point to the same issue – Invalid Product Key or Version mismatch. When you see any of the aforementioned error codes above, it indicates that you are either entering a wrong product key or you are using an incorrect ISO when installing it on your computer. In such cases, you may see either of the following error messages:

“You are running Windows 10 Pro, but you have a valid digital license for Windows 10 Home.” Or: “The specified product key is invalid or is unsupported by this version.”

If you got the error code 0xC004F00F then it means that you’ve entered a product key for the Enterprise edition of Windows to activate Windows 10 Pro or Windows 10 Home. It could be that you have a key from your work and you accidentally use it on your Home PC. If you got the error codes 0xC004E016, 0xC004F210, then it means that you have entered a product key that is meant for a different edition or version of Windows. On the other hand, if you got the error code 0xC004F034 instead, then it means that you have entered an invalid product key or a product key for a different Windows version. Whichever error codes you have, refer to the possible solutions given below to fix the Invalid Product Key or Version mismatch Activation Error in Windows 10.

Option 1 – Try running the Windows 10 Activation Troubleshooter

The first thing you can do to resolve this Activation error is to run the Windows 10 Activation Troubleshooter. 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.

Option 2 – Try purchasing a new license

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 to 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.

Option 3 – Try activating Windows 10 via mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

Code 39 - What is it?

Code 39 is a device driver error code that pops up when the Windows operating system cannot load the driver for the hardware you want to use.

This hampers your ability to use the hardware properly. The error code is almost always presented in the following format:

“Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.” Code 39

Error Causes

A device driver is a software program that tells the operating system how to control a particular hardware device. Each hardware device has a different driver.

There are separate device drivers for printers, CD-ROM readers, and keyboards, to name a few.

Many device drivers are already built into the operating system. But sometimes you will need to install a new device driver when you want to use a new piece of hardware device that the operating system is not familiar with, or does not anticipate.

Regardless of whether or not the drivers are already integrated into the operating system, you may still experience code 39, typically because of the corrupted or outdated drivers.

Outdated and corrupted drivers cause hardware malfunction and failure, which trigger device driver error codes like code 39. Other causes include incorrect registry values.

Further Information and Manual Repair

Below are some of the easiest and most effective methods to resolve Device Manager error code 39 on your PC.

To follow and implement these methods, you don’t require any technical knowledge or expertise. Simply follow these instructions to fix the error right away.

Method 1 - Fix with a Simple Reboot

There is a possibility that the error code 39 is caused by some fluke within the Device Manager or your BIOS.

If that’s the reason, then a simple PC reboot can resolve the issue immediately. Therefore, before you try anything, it is advisable to restart your system.

If it works, then that is great, but if it doesn’t, then don’t worry, try other methods given below to fix this problem successfully.

Method 2 - Uninstall and Reinstall Drivers

If the error code 39 is generated due to faulty or outdated drivers, then simply uninstall and remove them and then reinstall new driver versions. There are two ways to remove faulty drivers.

Method One

• One is, to go to the start menu, click on Control Panel, and then Add/Remove Programs.
• Remove the program and the driver you think is causing problems. This will thoroughly remove all traces of the faulty driver.
• To reinstall, follow the same steps but this time install the new device driver version.

Method Two

• The other way is to go to the start menu, type Device Manager in the search bar, and then press enter to continue.
• In the Device Manager, find and locate the problematic device.
• After that, double-click the category of device that you wish to uninstall. Let’s say, Windows is unable to load the graphics card driver.
• This means you will have to click on the Display Adapter category in the Device Manager to uninstall the graphics card.
• After you have successfully uninstalled, Windows will prompt you to confirm device removal.
• Simply click OK to confirm and proceed. To activate the changes, restart your PC.
• To reinstall, go to the Device Manager, click on the Action tab and then select the option ‘Scan for Hardware Changes.’

This method, although effective in resolving error code 39,  can be time-consuming. To avoid the hassle and save time, try method 3.

Method 3 - Update Drivers Automatically with DRIVERFIX

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

What is Error 0xe06d7363?

Error 0xe06d7363 is displayed when a process or an operation is not launched, or completed by an application.

This error can prevent the user from performing some operations. It might close the application unconditionally. Sometimes a ‘GetLastError()’, a ‘GetExceptionCode()’, or a ‘GetExceptionInformation()’ is displayed with this error.

Error Causes

Error 0xe06d7363 can occur for a number of reasons. Damaged, corrupted, or missing files in the registry database are the main reasons why the error might occur. Another reason is when the system files are not configured correctly, thus they corrupt system files in applications. They can also affect the hardware devices.

All code-generated exceptions in the Microsoft Visual C + + compiler will contain this error. As this error is compiler-generated, the code will not be listed in Win32 API header files. This code is a cryptic device, with ‘e’ for exception while the final 3 bytes represent ‘msc’ ASCII values.

Further Information and Manual Repair

To resolve this error, you will have to debug an application. While using Microsoft Visual Studio, you can stop the program when the error 0xe06d7363 occurs. To start debugging, follow these steps:

• Start debugging application
• From Debug menu, click on Exceptions
• In the Exceptions window, select error 0xe06d7363
• In Action, Change to Stop always from Stop if not handled

Another fix for this issue is reverting back to an earlier copy or the last update of the same Windows. Error 0xe06d7363 can occur is when you try running a client application using Microsoft.SqlServer.Types.dll component on your computer that has Microsoft SQL Server 2008 Server Pack 2 installed. With the error, the following text can be seen:

“unable to load DLL ‘SqlServerSpatial.dll’ Exception from HRESULT 0xe06d7363".

A Cumulative Update 7 was initially released for SQL Server 2008 Service Pack 2 in order to fix this issue. Since the builds are cumulative, every new fix released contains hotfixes and all security fixes which were also included in the previous SQL Server 2008 fix release. This error can be found in all Microsoft products that are listed in the Applies to Category.

Microsoft SQL Server 2008 hotfixes are created to resolve errors like 0xe06d7363 on specific SQL Server service packs. This error is by design and has commonly occurred in the previous versions of Windows before Windows 7.

Congratulations, you have just fixed Error 0xe06d7363 in Windows 10 all by yourself. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily. Now that’s how you fix Error 0xe06d7363 in Windows 10 on a computer. On the other hand, if your computer is going through some system-related issues that have to get fixed, there is a one-click solution known as Restoro you could check out to resolve them. This program is a useful tool that could repair corrupted registries and optimize your PC’s overall performance. Aside from that, it also cleans out your computer for any junk or corrupted files that help you eliminate any unwanted files from your system. This is basically a solution that’s within your grasp with just a click. It’s easy to use as it is user-friendly. For a complete set of instructions in downloading and using it, refer to the steps below Perform a full system scan using Restoro. To do so, follow the instructions below.

1. 1. 1. Download and install Restoro from the official site.
      2. Once the installation process is completed, run Restoro to perform a full system scan.
      3. After the scan is completed click the “Start Repair” button.

FLoC is Google’s alternative to third-party cookies and is based on machine learning. This will allow the browser, any browser, to anonymously study how users are browsing and then group them into ‘cohorts’. Following this, you will be served ads based on your cohort and not on your individual data. So, you are still going to be targeted with ads but in a more anonymous manner. Google claims that this will improve user privacy since this “federated learning” happens on the user’s device and artificial intelligence-based learning involves sharing lesser users than what happens with third-party cookies. If something like this gets widely adopted by ad companies and services, it should “protect users” from tracking methods that are more intrusive than third-party cookies, like browser fingerprinting.

Who is against it?

Privacy-focused browsers DuckDuckGo, Brave, and Vivaldi have all warned users against FLoC and have said that they are going to block it on their end. Brave says that Google FLoC has a design that does not respect the customer’s privacy and consent. It has been designed to provide browsing behavior and interest data with any website that users may interact with, and this process does not involve fully informed consent. Vivaldi, another popular Chromium-based web browser, has also made its stance clear regarding the status of FLoC. The company said in a Reddit thread that the FLoC experiment does not work in Vivaldi. It happens because for FLoC to work, some features need to be enabled under the hood, but Vivaldi does not provide those options. The company also added that it plans to stop the entire FLoC component from being a part of the browser, regardless of how Google may implement it. Considering that Brave and Vivaldi have been privacy-focused browsers since their beginnings, the decision to stay away from FLoC is not surprising.

Logitech announced the Logitech G CLOUD gaming handheld, somewhat of a STEAM Deck competitor. Somewhat, because the reason is that not like Deck this device is not packing huge power in order to run locally PC games, instead it is made with one goal in mind to connect to Cloud gaming and let you play games in that way.

The device is packed with a 7-inch display featuring 1080p resolution in a 16:9 ratio with a refresh rate of 60Hz, an analog thumbstick, a D-pad, 4 action buttons, and triggers. Inside the device beats Snapdragon 720G (CPU used in most Android phones), 4GB of LPDDR4X RAM & 64GB of internal storage. As seen hardware is way less impressive than one that is packed inside the STEAM deck but as stated this handheld is not meant to run natively PC games so this hardware will suffice for its purpose.

Logitech has partnered with both Nvidia and Microsoft to add GeForce now and Xbox Cloud Gaming access to its device. If you have an account on either one of these services you can fully use them on the Logitech G Cloud gaming handheld. You can also play some Android games via the Google play store but the main goal is Cloud gaming.

The price of 350$ USD is not very impressive since STEAM Deck which is a way more capable device is running for 400$ USD, for the difference of only 50$ USD Deck has an advantage, and the price itself is a hard point for selling and if we place into this mix som retro handhelds that go as low as 100$ USD Logitech is in an awkward position. Note that Nintendo Switch is 300$ USD.

Internal Error 2753 - What is it?

Internal error 2753 is associated with Windows Installer failure. The Windows Installer is basically an in-built software program in Windows 7 and 8. It installs all programs on the system smoothly, saves the program in the computer program files and in the Windows Registry. Though this can be carried manually Windows Installer makes the installation process much easier. However, internal error 2753 can cause a great deal of distress and frustration during program installation. This error prevents you from installing your desired program successfully.

Solution

Error Causes

The 2 known causes for Internal Error 2753 are:

• Viral infection
• Windows Installer not properly registered

Further Information and Manual Repair

To resolve internal error 2753 on your system, try the methods discussed below. These methods are easy and require no technical expertise. Let’s get started:

Method 1 - Remove All Malicious Programs

Malicious programs like viruses, malware, adware, Trojan and spyware can corrupt programs on your PC like Windows Installer. If this is the underlying cause of error code 2753, then simply download a powerful antivirus on your system. Run it to scan for all such malicious programs and remove them. Once your PC is clean, try installing your desired program. This will hopefully resolve the issue. If the error still pops up then try method 2.

Method 2 - Register Windows Installer Properly

To do this, go to the start menu and then open Run and type ‘cmd’ in the box, and press OK. This will open the DOS command window. In the command prompt type "regsvr32 vbscript.dll" and then press Enter to proceed. After that, you will see a message that will read as "DllRegisterServer in vbscript.dll succeeded." This means Window Installer files have been successfully registered on your PC.  Now you can try installing your desired program again. If the installation begins and completes successfully, then the error is resolved.

Method 3 - Undo Recent Changes

If nothing works, then use the Windows System Restore Utility tool to undo recent changes. This will bring back your PC in the former state before you experienced the error 2753 on your PC. To access System Restore Utility, press Start and type System Restore in the search box. Now follow the steps in the Wizard to choose a restore point. Once you select the point, reboot your system to activate changes.

Internal Error 2771 - What is it?

Internal Error 2771 is an internal error code associated with Kaspersky Internet Security and Antivirus software. This error pops up when Kaspersky Internet Security software fails to install on your PC successfully. Installation of the software is interrupted and therefore it ends prematurely. This happens mostly when you try to install a new build on an existing installation. Internal Error 2771 is displayed in one of the following formats:

Internal Error 2771, Sandbox Feature or Internal Error 2771, WholeProduct Feature

Solution

Error Causes

This error may result on your computer screen due to several reasons. Some of the most common underlying causes include:

• A leftover Registry Key
• Bad entries from previous Security Package
• INFCACHE.1 file corrupted
• Conflicts with other security software installed on your system

Further Information and Manual Repair

To successfully overcome this problem and ensure the successful installation of Kaspersky Internet Security software on your system, try the methods given below.

Method 1- Remove the Leftover Registry Key

Sometimes Internal error code 2771 may appear during installation due to the leftover registry key from the previous Kaspersky software removal. A registry key is often created when uninstalling the previous Kaspersky version from the PC. This key is left behind even after you reboot your system. This key is called AVP**_post_ uninstall, you need to delete it to ensure the new version of the Kaspersky program is installed successfully on your PC.  For this, simply go to the start menu and type Regedit in the search bar. Now navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun and then look here for the registry key called AVP**_post_ uninstall. In order to delete this file, right-click it and then select delete. Once uninstalled, reboot your PC and then try installing the Kaspersky Internet Security program again. Hopefully, this will resolve the issue. If the software installs smoothly, then the error is fixed, in case it still persists, then try other methods illustrated below.

Method 2 - Remove the INFCAHCE.1  Corrupt File

Another reason for the error pop-up may be INFCAHCHE.1 corruption. This file is basically used to store driver information and inf file locations. However, if it contains corrupted information, then you must remove it. To do this, go to the start menu and type cmd into the search bar. This will open a command prompt. Here type del C:\Windows\infinfcache.1. Now reboot your PC and try installing Kaspersky software on again.

Method 3 - Fix Software Conflict

Security software conflict can also result in internal error 2771 code display. And when this happens, the installation of Kaspersky prematurely ends. Security software conflict may occur if you have Comodo Firewall installed on your PC. A firewall is known to cause issues with Kaspersky software programs. The best way to resolve this issue is to uninstall all security software programs on your PC. Once all security software is removed, then install Kaspersky on your system. If the installation is successfully completed, then reinstall the other software again.

Method 4 - Download Restoro

Error 2771 can also result on your computer screen if traces of the previously installed Kaspersky software still remain in the registry despite the program removal. In such an event it is advisable to download Restoro. This is a cutting-edge and user-friendly PC Repair Tool deployed with an intuitive interface and a powerful registry cleaner. The registry cleaner scans your entire PC in seconds and detects all registry-related problems. It removes all the bad entries, invalid registry keys, traces of previously uninstalled programs, junk files, and cookies that are known for registry corruption. It takes just a few clicks to perform this process. Once all traces are removed, you can install the new version of the Kaspersky Internet Security program on your PC without interruption. Click here to download Restoro and be on your way to resolve Internal Error 2771 on your computer!

Windows 11 release date is closing in, some people have tried it via insider build, some have decided not to. It has come to our attention that there is a little website made by BlueEdge that offers a virtual Windows 11 desktop. Opening the Website will put you right inside Windows 11 desktop, now take note that this is not Windows 11, it is a simulation of Microsoft’s newest OS and therefore many things will not work like File Explorer, etc. One thing you can make sure it is working is UI itself, you can see how you do like the new Taskbar, start menu, widgets, and some other things. You can just pop up on the site and check how you do like the overall new look and feel of Windows 11 UI before installing it or trying it. We are sure that many more options will come in time but even now you can get a feel of the newest OS. Windows 11 BlueEdge site: https://win11.blueedge.me/

Recently, a lot of users experience issues after the Windows 10 v1903 upgrade and one of them is that the Cortana Web Preview is not functioning like it’s supposed to. Even though Microsoft has already replaced the unified search where you no longer have to use Cortana, it is still undeniably useful and is packed with some great features, one of which is the Web view. Each time you type a search query, it will open a web view where you can see the results using Bing. However, some users reported experiencing some issue wherein the web view does not show anything and appears to be broken and users have to click on the Open in Browser link. Thus, if you are one of the users who experience the same problem, then this post is for you – it will guide you on what you can do if the web preview in Cortana is not working on your Windows 10 device. To fix the Web Preview issue in Cortana, you can try to restart Cortana or reset it using the Windows Settings app or change the Search filter level. You could also try to run the Windows Store App troubleshooter or re-register or reinstall Cortana. For more details refer to the options provided below.

Option 1 – Try to restart the process of Cortana

There are times when the running process of Cortana might encounter an error and breaks a particular component of the whole service so the first thing you can do is to restart Cortana’s process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and look for Cortana’s entry.
• Once you find it, right-click on it and select the End task option.
• Afterward, open Cortana again and see if it fixes the web view problem or not.

Option 2 – Try changing the search filter level

The next thing you can do to fix the Web View is to change the search filter level. All you have to do is go to Settings > Search and change filter level and from there, modify the search filter level and then see if it fixes the problem.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the Web Preview problem in Cortana. 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 Cortana via Settings

• Launch the Windows 10 Settings app and go to Apps > Apps & Features.
• Next, look for the entry of Cortana on the right-side panel and select it.
• After that, select the Advanced options and then select the Terminate button under the Terminate section.
• Once done, click on the Reset button under the Reset section.
• Restart your PC.
• After your computer boots, launch Cortana again and check.

Option 5 – Try to re-register and reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.

• First, right-click on the Start button and click on the Windows Powershell (Admin) option from the list.
• Next, type the following command and hit Enter to execute it:

Set-ExecutionPolicy Unrestricted

• After that, execute this second command to reinstall Cortana:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

• Restart your computer and check if the Web Preview in Cortana is now working.

This post will guide you in what to do if the DisplayLink in Windows 10 is not working. There are several users who reported that their DisplayLink device has stopped working with the Windows 20 Anniversary or the Creators update all of a sudden. According to users, this issue occurs right after they finish installing a big Windows Update like the Anniversary Update or the Creators Update or right when the DisplayLink driver is updated using Windows Update. DisplayLink is a graphics transport technology that allows users to connect to any computer that supports USB or Wi-Fi. Aside from that, it is also an excellent universal docking solution to any platform which makes it a great solution for enabling multiple displays. Thus, it can be quite annoying when DisplayLink suddenly stops working. There really is no actual error message when it happens. The only telltale sign is that all the devices that use the DisplayLink technology will also stop functioning. There could be tons of reasons why DisplayLink stopped working. It could be due to an incompatible driver, or the DisplayLink driver itself is corrupted or is connected to a USB 2.0 port. In addition, the problem could also be due to the Nvidia Share (ShadowPlay) that conflicts with DisplayLink or that the Universal Serial Bus is broken. To resolve the issue, refer to the following options laid out below.

Option 1 – Run the Hardware and Devices troubleshooter

As you know, Windows comes with a built-in tool that you can use to troubleshoot the problem with DisplayLink. You can find it in Settings > Update & Security > Troubleshoot. For further instructions, follow these steps:

• 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.

Option 2 – Try to uninstall DisplayLink and reconnect the docking station

If the Hardware and Device troubleshooter is of no help, you can try uninstalling DisplayLink and reconnecting the docking station. To do so, follow these steps:

• Disconnect the docking station or any other device that uses DisplayLink.
• Tap the Win + R keys to open the Run dialog box.
• Then type “cpl” and hit Enter to open Programs and Features.
• From there, look for DisplayLink, right-click on it and click Uninstall.
• After that, follow the next on-screen instructions that appear on your screen to completely remove DisplayLink from your computer.
• Once you’ve uninstalled DisplayLink, click this link to download and install DisplayLink again.
• Now reconnect the docking station as well as other devices that use DisplayLink and follow the next on-screen instructions to reinstall the required drivers in your computer.
• Restart your computer and then check if DisplayLink is now working fine or not.

Option 3 – Try using a USB 3.0 port

If you are experiencing this issue with DisplayLink with a monitor that you’re trying to connect using DisplayLink, then you have to make sure that you are using a USB 3.0 port. Based on some reports, there are certain monitors that will not work with DisplayLink while connected to a USB 2.0 port since they have insufficient power to run the monitor. Like pointed out earlier, the problem with DisplayLink might have something to do with the Nvidia ShadowPlay. This streaming feature was often reported to crash the DisplayLink monitors which is why you might want to try disabling it for a while to check if it’s really true. Once you’ve disabled Nvidia ShadowPlay, restart your computer and check if your DisplayLink monitor now works.

Option 5 – Reinstall the Universal Serial Bus controller

You can also reinstall the Universal Serial Bus controller to fix DisplayLink since a malfunctioning USB port can sometimes cause issues with DisplayLink.

• Tap the Win + R keys to open the Run dialog box.
• Then type “msc” in the field and hit Enter to open the Device Manager.
• From there, look for the Universal Serial Bus controllers and expand its drop-down menu.
• Next, right-click on every Host Controller and then click on Uninstall Device.
• After uninstalling every entry, restart your computer to force your system to reinstall the drivers you’ve just uninstalled.
• Once your computer has rebooted, wait until the drivers are reinstalled and then try opening DisplayLink again.

Option 5 – Reinstall the Universal Serial Bus controller

You can also try to perform a System Restore as it can also help you fix DisplayLink. 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.