KFConsole enters the console competition

There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
• After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
• From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
• Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
• Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
• You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
• Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
• Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.

RocketDock is one of the most popular app launchers as it has been used excessively back in several windows versions. This was modeled based on the Mac OS X launch bar and offers an animated response when you hover the mouse over the apps gathered on the Dock. This is perched at the top of your screen, and you can easily drag your favorite app icons to have them in one place. The dock keeps all your most favorite shortcuts intact for faster and easy access. Like other apps, you can easily customize the dock with skins and other add-ons. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

The author of the famous software library mode-ipc that gets over a million downloads per week found that it has some questionable code inside. The code itself behaves like this: if it finds out that your location is within Russia or Belarus it will try to replace the contents of all files on the computer with a heart emoji.

One important thing is that we here are not supporting the current Ukrainian situation and are against any type of violence or war but we also do not support this kind of behavior as well. If we look at this only from a technical perspective, we would then classify the mode-ipc library as malware and a harmful piece of code no matter the motivation behind it.

So this so-called protestware is well basically malware, but not always, it will protest when certain conditions are met. The issue with this is that companies and users should not be placed under harm if they do not share the personal view of the code author. Imagine if, for example, I would publish code to delete all pictures from your computer if my code found out that you do not like metal music. I guess you not liking metal music and war in Ukraine are two very different things but the source is the same, unreliable code that invades your privacy in order to serve one purpose, punishment for disagreeing with my personal views and that should not be allowed.

Not all protestware are equal, some will not harm your computer on purpose, they will just annoy you with some messages like viruses did in their infancy stages, others might place some developer sanctions but no matter the outcome basic principle is the same, it does something without user consent and without informing the user that something like that might happen.

On the internet, many blog posts and discussions were open about this issue and its morality. Discussion is still active with different takes on the situation and how to prevent it. Our take on this matter is that professional developers should have standards and not submit to doing harm for the sake of personal views and feelings.

In the long run, this kind of behavior and practice can only harm developers involved in this kind of entanglement. Infected libraries will in time stop being used since people would not trust them and authors will have a stain on their name as impulsive or not trustworthy.

Microsoft has released Windows 11 as a public beta release for all the people that are not willing to be in the insider program. Beta release as of this moment is identical to Insider Preview build 22000.100. and updates will not roll so fast as in insider preview and it is marked as unstable release, same as insider build. I would not install Windows 11 beta on the main PC since some drivers still have issues and may lead to some blue screens. Be aware that the beta build will have all Windows 11 system requirements including TPM 2.0. This is a big difference from insider build which can be installed on systems lacking official requirements. So basically if you have a spare PC that could run Windows 11 install it so you can see what it brings and feel it so you can make a decision will upgrade once it is released later this year.

CPU Not Compatible – What Is It

Some users wanting to upgrade to Windows 10 from Windows 7 or Windows 8.1 experienced errors with installation. One of these errors is CPU Not Compatible. When you click and run the “Get Windows 10” from your system tray bar, you’ll receive the “CPU is not compatible with Windows 10” error. When this happens, it might be good to check if there’s a bug or if your NX feature (a requirement for the Windows 10 installation) is enabled.

Solution

Error Causes

The “CPU is not compatible with Windows 10” error normally occurs when:

• NX feature is not enabled
• You experienced the Windows 10 bug

Further Information and Manual Repair

To successfully upgrade to Windows 10, your CPU must support Physical Address Extension (PAE), SSE2, and NX features. If any of these features are not activated on your system, it’ll cause the CPU not compatible error. However, some users still reported experiencing this error even though their CPU has these features activated. Normally, this is due to the bug that Windows acknowledged.

If any of these two scenarios apply to your computer, the following methods will help you fix the problem:

Method 1 – Check for bugs

The bug applies to some Windows 7 and Windows 8.1 systems. The bug occurs when the “Get Windows 10” app fails to recognize CPUs as being compatible. This produces a false negative result with a message, “Here’s why Windows 10 cannot be installed on this PC: The CPU isn’t supported”. To fix this bug, Microsoft released an update.

Unfortunately, the patch update (KB2976978 for Windows 8/8.1 and KB2952664 for Windows 7 SP1) to fix the bug may not be automatically downloaded to your computer. If this is the case, you need to verify first if the patch was installed correctly. To do this, follow the steps below:

1. Click ‘Start’ and type in View Installed Updates. The “View installed updates” icon should appear. Click the icon.

2. Go to the Search bar (Top right portion) then type the patch name for your system. Make sure that you type the correct patch name for your system since Windows 7 and Windows 8/8.1 have different names. If you find the patch, it means it’s already installed. You can now upgrade to Windows 10 without the CPU not-compatible error.

3. But, if you can’t find it you need to install the patch manually.

4. Go to Windows Update then click the “Check for Updates” button.

5. Browse through the available updates and look for KB2976978 for Windows 8/8.1 or KB2952664 for Windows 7 SP1

6. Download the right patch. You may need to reboot your system once it’s done.

7. The downloaded patch should be applied after a day or two with the Windows Task Scheduler. Once the patch is applied, you can now upgrade to Windows 10.

Method 2 – Check CPU features and activate them if needed

A major requirement for Windows 10 upgrade is for the CPU to have Physical Address Extension (PAE), SSE2, and NX features enabled on your system. If you receive the CPU not compatible error, one possible cause is that any of the mentioned features are not available OR not enabled on your system. Here’s how you can fix this:

1. Verify if your CPU supports the three instruction sets. You can use software that provides information like this. If all three are available, proceed to the next step.

2. Go to your computer’s BIOS. To do this, reboot your computer. You will need to press a key specific to your computer’s manufacturer (usually it’s F12, F8, F2, or DEL).

3. Look for the NX (No Execute Bit) settings. This is normally found in the “Advanced Configuration” menu, or something similar to this. Just take note that the NX setting can be named differently in BIOS. Some other names include EDB (Execute Disabled Bit), EVP (Enhanced Virus Protection), Execute Disabled Memory Protection or No Excuse Memory Protect.

4. Once you’re in the NX settings, make sure that it’s enabled.

5. Exit the BIOS and SAVE your changes.

6. Boot your computer normally, then try upgrading to Windows 10 again through the “Get Windows 10” app found in the system tray.

Method 3 – Force enabling NX Bit

If changing the settings in your BIOS doesn’t do the trick, your final option is to force enable the NX bit in your Windows system. However, this is only applicable IF and ONLY IF your CPU does support it. To force enable NX bit, do the following:

1. Click Start and go to command prompt (Type “cmd” – no quotes) and press enter.

2. Copy and paste the text below to the command prompt.bcdedit.exe /set {current} nx AlwaysOn

3. Execute the command. You will need to reboot your computer once this is done.

4. Download and install Windows 10

Method 4 – 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.

What is AppCrash Error?

As the name implies the AppCrash error is an error code that indicates a crashed program/application on your system. This term is used by Windows to designate an application crash. It is reported and displayed on the system as “Problem Event Name: AppCrash,” which is followed by additional technical information which unless you are a computer programmer, you may not fully decode. There are various symptoms that trigger the occurrence of this error code on your system such as:

• Application becoming unresponsive and intermittent
• Momentary application freezing
• Application times out and then successfully recovers itself

Solution

Error Causes

The reason for AppCrash error occurrence cannot be narrowed down to a specific cause. This error code is triggered by multiple causes such as:

• The system is stressed out. This happens when your CPU is held at 100% usage for an unacceptable length of time.
• Lack of system resources
• Windows version incompatibility with the application
• Malware and viral infection
• Poor PC maintenance
• Registry damage and corruption
• Data overload

No matter what the cause for the AppCrash error may be, if you experience this error on your system you must repair it right away before the damage sets in. This is a serious error posing severe consequences. If not repaired on time, it not only hampers your ability to use your desired application but also exposes your PC to fatal crashes, data loss, and system failure.

Further Information and Manual Repair

Though this is a serious Windows error, the good news is that it is an easy-to-fix error code, so resolving it is not a problem. There are three ways to fix the AppCrash error:

• Hiring a technician, this by the way is quite costly. You may have to pay hundreds of dollars to get professional assistance to fix this error code.
• Giving your computer adequate rest to cool down. Stressing out your PC heats the hardware which triggers such errors and eventually results in system failure. Try cooling it, and see if it fixes the error.
• Downloading Restoro. This is by far the best, simple, quick, and money-saving way to resolve the AppCrash error on your system. Restoro is an innovative, performance-driven and multi-functional user-friendly PC Fixer that helps resolve practically all types of PC-related errors including the AppCrash error. It has an intuitive and powerful in-built registry cleaner which scans and detects all types of registry issues on your PC in seconds. It helps you clear up all the unnecessary files saved on your hard disk like junk files, internet history, invalid entries and files from the programs that you’ve uninstalled. Such files not only occupy a lot of disk space but they also lead to registry damage and corruption thus shooting error code pop-ups like the AppCrash error.

Restoro features

Restoro performs an in-depth scan and removes all these files cluttering the system and repairs the damaged registry. It resolves the error AppCrash and simultaneously boosts the speed of your PC making it easy for you to access and run applications fast and smoothly without any application errors. Sometimes malicious software programs like malware and viruses may also damage and corrupt the registry. If the underlying cause of the AppCrash error is a viral infection on your PC corrupting the registry, then don’t worry; Restoro, with the help of its built-in anti-virus program, resolves it too. It scans for viruses on your system and removes them immediately. Restoro is easy to use. Whether you are a novice or an experienced user, working around this PC Fixer is simple. It has a user-friendly interface that allows users to navigate through it without any hassle. In addition to this, it offers enhanced compatibility. It smoothly runs on all Windows versions.

Get Restoro

To get started, all you need to do is Click here to download Restoro. Once it is installed on your system, run it to scan for registry issues like the AppCrash error. This intuitive tool will detect all the errors on your PC in just a few seconds and display them on your Windows screen in the form of a comprehensive scan report. Now simply hit the repair tab to resolve. Once repairing is successfully complete, try running your desired application. You will notice two significant differences:

1. No AppCrash error code message pop-ups
2. The application runs fast and smoothly regardless of whether it’s Windows Media Player or any gaming application.

If you spend a large amount of time gaming or working on a computer gaming chair is a very important asset. One other thing that is mostly looked past but could help greatly is a good desk. A great chair accompanied by a great desk can make your long sitting sessions more pleasant and more healthy which is very important in the long run. Hey, but it is only a desk, what is so special about having an expensive desk? Well truth to be told desk is just a desk and any kind of desk can serve the purpose of hosting a keyboard, mice, and screen. But a good desk will offer some other advantages that may not seem so important but they could mean a lot like adjusting desk height so it fits perfectly on your size and sitting position making long hours more pleasant and lower stress on hands sitting on it.

Advanced desk features

Bytezone might not be a company that will sound familiar to you, mostly because they manufacture gaming chairs and desks, now in the gaming chairs world there are a lot of competitors and Bytezone has managed to make a name for itself despite this fact. But they are more popular in their gaming and office modern-looking desk category. The advanced desk is made from carbon steel and plastic combination, it is very durable and it weighs 27kg. Now that is not really light but it is not very heavy if we compare it to wood desks. The top layer of the table is made from easy-to-clean material and the desk comes with a large mouse and keyboard pad. The table itself includes a cup holder, headphones bracket under the table and it has a cable management drawer in the back. The desk is sized 66x120x76 cm. Also for anyone interested desk itself comes also with RGB lights for that true gaming feel.

In case you don’t know, Driver Verifier is a built-in utility in the Windows 10 operating system. It is the one that ensures the integrity of all the drivers in the system. It can detect any suspicious behaviors of the drivers and if it finds the driver signature of some suspicious activity during runtime, it stops the suspected action by triggering a BSOD or Blue Screen of Death error and one of these Stop errors is the DRIVER_VERIFIER_DMA_VIOLATION error. When you encounter such an error, you will see the following message on your screen:

“Your PC ran into a problem that it couldn’t handle, and now it needs to restart. If you’d like to know more, you can search online later for this error: DRIVER_VERIFIER_DMA_VIOLATION”

There are several ways you can fix this error. You can try to disable the Driver Verifier or run the Hardware troubleshooter. You could also try to update, roll back or uninstall the drivers on your computer. For more details, refer to each one of the options provided below.

Option 1 – Try to disable the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_VERIFIER_DMA_VIOLATION. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Note: You could also run the Hardware and Devices troubleshooter as it could also help in fixing the DRIVER_VERIFIER_DMA_VIOLATION error.

Option 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

As of late, users have been reporting about getting an error saying, SAFE_OS phase error during Replicate_OC operation when they tried to upgrade their Windows 7 or Windows 8.1 computers to Windows 10. Although the error code in this problem could vary, in this situation, it states:

0xC1900101 – 0x20017, The installation failed in the SAFE_OS phase error during Replicate_OC operation

To fix this issue, you need to follow the given options below. But before you do, you need to create a System Restore point first so that if anything goes wrong, you can always undo the changes you’ve made.

Option 1 – Try to change the Windows 10 installation

According to security experts, one of the main causes of this error is the KB3064209Windows Update. This particular update is the one responsible for updating the CPU Microcode for processors made by Intel. Thus, if you don’t use an Intel processor, you can skip this option and proceed to the next one. However, if you use Intel, make sure to follow the instructions in this option carefully. Take note that in this solution, C: partition is referred to as the OS Partition while H: partition is referred to as the USB Pen Drive.

• First, you need to download the Windows 10 ISO from the Windows 10 Media Creation tool and then copy its contents to the Pen Drive H.
• Next, tap the Win + X keys and click on the Command Prompt (Admin0 option. If a User Account Control appears, simply click Yes.
• After opening Command Prompt, type the following command:

dism /Mount-Image /ImageFile:H:sourcesboot.wim /index:1 /MountDir:C:UsersUserDesktopmount

• Now navigate to the following path in the Windows File Explorer:

C:UsersUserDesktopmountWindowsSystem32mcupdate_GenuineIntel.dll

• From there, right-click on the file named “mcupdate_GenuineIntel.dll and click on Properties.
• Next, go to the Security tab and click on Advanced. In the Advanced section, change the Owner to your User Account and click OK.
• And then back to the Security tab, click on the Edit button and check on Full control to make sure that your User Account has all the privileges.
• Now click on Apply and then OK.
• After that, delete the file you saw earlier which is named mcupdate_Genuine.dll.
• Then close all the Windows File Explorer instances and go back to the Command Prompt window and unmounts the image you mounted before by typing the following command:

dism /Unmount-Image /MountDir:C:UsersUserDesktopmount /commit

• Afterward, repeat the steps from mounting up until here for these files:
  • wim /index:2
  • wim /index:1
  • wim /index:2
• Now delete the mount folder and remove the USB Pen Drive and then boot with the installer.

Option 2 – Try to perform a Disk Cleanup

Chances are, some unnecessary files in your computer might be interrupting the installation process which explains why you’re getting SAFE_OS phase error during Replicate_OC operation instead so you need to perform a Disk Cleanup in order to fix the problem.

Option 3 – Try updating all your drivers

Every now and then, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the SAFE_OS phase error during the Replicate_OC operation. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 4 – Try to update your system’s BIOS

Aside from outdated drivers, outdated BIOS could also be the reason why you’re getting the SAFE_OS phase error during Replicate_OC operation which is why you need to update your system’s BIOS in order to resolve the issue.

Option 5 – Try checking the Windows Services status

• In the Cortana search box, search for “Services” and then click on the Services icon.
• After that, the Services utility will be opened in a new window.
• Next, look for the following services:
  • BITS (Background Intelligent Transfer Service)
  • Windows Update Service
  • Cryptographic Service
• Then right-click on each one of the services and click on Properties. From there, select Automatic from the drop-down of the Startup Type menu.
• Now click on OK for each one of them and restart your PC to apply the changes made.

Option 6 – Try to check the RAM modules

There are many times when all the components of the RAM weren’t able to be used by the computer so you need to check the RAM modules.

• You need to first turn off your PC and then take out your RAM physically.
• Next, clean it with a soft cloth and blow some air into the RAM slot in the motherboard.
• After that, put your RAM back in the same slot.
• Then try updating your computer system again.

If you receive an error message that says, “Entry point not found, The procedure entry point could not be located in the dynamic link library” on your Windows 10 PC, then you will find this post useful for this will provide you some potential fixes to fix the error. This kind of error can occur if a program fails to locate the DLL library that it needs in order to run. It can also occur if the library is not in the specified directory in the path or if the DLL file has gone missing or has become corrupted. To fix the “The procedure entry point could not be located in the dynamic link library” error, check out the following options given below.

Option 1 – Try to reinstall the program

The first thing you can do to resolve the error is to uninstall the program that throws the error and download its latest version from its official site and then install it again.

Option 2 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

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

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Reboot your computer.

Option 3 – Try checking the details in the Event Viewer

The Event Viewer can also help you resolve the error as it contains detailed information about the error that could help you pinpoint its root cause and resolve it.

Option 4 – 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 error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls 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 5 – Try to replace the DLL file with 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 6– Try to scan your computer using Windows Defender

It is also possible that the DLL file might be infected with malware or virus which could explain why you’re getting the error. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.