Keyboard wont type numbers in Windows

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given options below.

Option 2 – Ensure that all the supporting processes and services are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 3 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox error.

BigTech platforms Google and Facebook were hit with a series of antitrust lawsuits by the US federal government and states on charges they are operating monopolies and abusing their power. Below is the status of the cases, as well as government probes of Apple and Amazon in their current states

Two lawsuits against Facebook

In a defeat, Judge James Boasberg said the Federal Trade Commission, which had sued Facebook in December asking that Facebook be forced to sell WhatsApp and Instagram, failed to show that Facebook had monopoly power in the social-networking market, among other problems. However, the FTC could file a new complaint by July 29. He threw out a related state lawsuit entirely, saying that the attorney's general had waited too long. They are looking at their options.

Four lawsuits against Google

The US Justice Department sued Google in October, accusing the $1 trillion company of illegally using its market muscle to hobble rivals. A trial date was set for September 12, 2023. A lawsuit by 38 US states and territories accuses Google of abusing its market power to try to make its search engine as dominant inside cars, TVs, and speakers as it is in phones. This was consolidated with the federal lawsuit for purposes of discovery. Texas, backed by other states, filed a separate lawsuit against Google, accusing it of breaking antitrust law in how it runs its online advertising business. Dozens of state attorneys general sued Google on July 7, alleging that it bought off competitors and used restrictive contracts to unlawfully maintain a monopoly for its app store on Android phones.

Justice Department investigates Apple

This probe, revealed in June 2019, appears to focus on Apple's app store. Some app developers have accused Apple of introducing new products very similar to existing apps created by other developers and sold in the Apple Store, and then trying to banish the older apps from the store because they compete with Apple's new product. Apple says it seeks to have only the highest-quality apps in the app store.

Justice Department probing Facebook and Amazon

In July 2019, the Justice Department said it was expanding its Big Tech probes to include "search, social media, and some retail services online", an apparent reference to Facebook and Amazon.

Federal Trade Commission on Amazon

In its investigation of Amazon, the FTC is likely looking at the inherent conflict of interest of Amazon competing with small sellers on its marketplace platform, including allegations that it used information from sellers on its platform to decide what products it would introduce.

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

What is Error 1706?

Error 1706 is a Windows PC error. It occurs when you insert a Microsoft CD-ROM either to repair an Office or to install a feature set to Installed on First Use. The error message is displayed in the following format: Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Program Files\Microsoft Office\Office101033\Setup.hlp.

Solution

Error Causes

Error 1706 may occur due to several reasons. These include:

• You originally installed MS Office from a network administrative installation
• You are trying to use Office CD-ROM when the error is prompted by the Windows Installer for an Office source location
• Viral Infection

Further Information and Manual Repair

The good news is that this error code is not fatal. However, to avoid inconvenience, it is recommended to resolve the error right away. To fix the problem you don’t have to be a computer programmer or hire one. In fact, this error code can be resolved quite easily. Here are some of the best and easiest do it yourself methods to resolve error 1706 on your PC:

Method 1

To resolve this issue find a different administrative installation for the Office source file location. To do this, go to the start menu and then click run. In the open box, simply type this command line new network pathSetup.exe /fvm package name.msi and press OK to continue and update changes. Once the update is complete and finished press OK to save and proceed. Please note after you follow these steps, the Windows Installer uses this new server location whenever it needs to reinstall, repair, or add a feature to your Office Installation.

Method 2

Another alternative method to resolve this method is to use CD-ROM for the Office Source Location. To do this you will have to remove Office and then re-install Office from the CD-ROM. Here are the steps to remove the Office program. First, quit all Office programs.

1. Go to the Control Panel then click on the Program and Features option.
2. Now double click the Add/Remove programs and remove the entry for the Microsoft Office 2003 or Microsoft Office XP product installed on your PC.
3. After that, click on the Maintenance Mode Options dialog box, select Uninstall Office, and then click Next to proceed.
4. Click Yes to confirm changes.
5. Now insert Office 2003 or Office XP CD-ROM and follow the setup dialog boxes to reinstall the program on your system from CD-ROM.

Download Restoro to Correct Registry Errors

However, to ensure the installation is successful this time around, it is advisable to clean the registry and ensure the uninstalled program is not located in the registry. To do this, download Restoro and run it on your computer. This is a powerful PC Fixer integrated with a registry cleaner. The registry cleaner wipes out all the unnecessary files and uninstalled program files saved in the registry. Once the registry is cleaned, try reinstalling MS Office again. This will resolve the error 1706. Click here to download Restoro and repair error 1706.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

If you suddenly encounter an error message saying, “ File Record Segment is Unreadable ” on a blue screen while booting your PC, it means that your hard drive is in an error state. This particular blue screen of death error might have a lot of bad sectors or might have reached its end. The workarounds you can try to resolve the issue is by locating the bad sectors or checking your hard drive for any discrepancies in the mapping and fix them. Follow the detailed instructions laid out below for these workarounds.

Option 1 – Try to check for any bad sectors and wrong configurations in your hard drive

The first thing you have to check is the boot files on your PC. As you know, your PC boots from these files and if there is anything wrong with any one of them or if one of them ends up getting corrupted, you will most likely see the blue screen of death error or a prompt with an error message saying, “File record segment is unreadable”. According to some users who reported this issue, new hard drives aren’t exempted from this error. That’s why it is recommended that you carry out this solution no matter what kind of scenario you are in. You will have to launch the Command Prompt in recovery mode and see if you can fix the problem by executing the check disk commands.

• Upon booting, restart your PC and tap F11 to go to the recovery environment then select Troubleshoot.
• Next, click Advanced from the given options and select Command Prompt.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed. And depending on the situation, it might even take a day at most so patience is really the key here.

Option 2 – Try connecting the hard drive to a different computer

If option 1 didn’t work for you and you’re still seeing the error, you can try connecting the hard drive to a different computer and then copy the data first. Make it a priority to salvage the data just in case the hard drive won’t make it in the future. After replicating your hard drive, you can then try running the chkdsk commands that are listed in option 1 above in the new computer you’re connecting your hard drive to and make sure that you key in the correct drive letter that’s assigned to the hard drive you’re using. After executing the chkdsk commands, plug your hard drive back into the previous computer and then check if you can now boot it without any issues.

Option 4 – Replace the faulty hard drive

If none of the options provided above really worked out then maybe it’s time to consider getting a replacement for your hard drive. In about 50% of the cases about this error, some unfortunate users were left with no choice but to replace the hard drive since the problem is with the hard drive itself. Hard drives have a complex running mechanism which includes a head and the disk that rotates accordingly so you can check if the cables connected to the hard drive are connected properly and if it is in a correct position or not. In addition, you also have to make sure that the SATA adapters where the hard drive is connected are working properly. If the drive is showing problems in the I/O operation, there is little chance for you to use it as a normal hard drive. If the hard drive is in warranty, get it checked and replace it. If not, you might consider taking it to the service center for the specialists to take a look into it.

In case you don’t know, Windows 10 now allows users to check the Bluetooth battery level of devices. More often than not, the accessories or peripherals users use for their Windows 10 devices are connected to it using Bluetooth technology. This high-speed low-powered wireless technology is designed to link mobile devices, computers, and other network devices over a short distance wirelessly. Monitoring the battery level of a device where Bluetooth is enabled isn’t an easy task as most of these devices do not support the Bluetooth battery monitor or the battery level display. And even when on devices that do, you still have to install additional software to find it. However, Windows 10 eliminates this requirement and all you have to do is add a Bluetooth device and connect that Bluetooth device. How? Follow the instructions provided below. Step 1: Adding a Bluetooth Device The easiest way to get your Bluetooth device battery to be displayed on your Windows 10 screen is to simply add a Bluetooth device. To do so, follow these sub-steps:

• First, turn on the Bluetooth mode on your device.
• Next, go to Windows Settings > Devices > Bluetooth & other devices.
• From there, click on the “+” button next to the ‘Add Bluetooth or other devices” option and select the type of device you want to add.

Step 2: Connecting the Bluetooth Device Once you’ve added the device, it will be visible under the “Add a device” screen.

• Now select the newly added Bluetooth device and click the “Done” button.
• After that, it will now be connected. Go back to the “Bluetooth & other devices” window and scroll down to the section of “Mouse, Keyboard, and Pen”.
• From there, move the cursor alongside the connected device to display its battery level.

Keep in mind that there are several ways in which you can display the battery information of the Bluetooth device. However, Windows 10 understands only one of them per se. So if your device is not a Bluetooth Low Energy device, Windows 10 won’t be able to show its battery information and won’t display its battery level.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

When you try to open Outlook 20016 and other programs on your Windows 10 PC and end up getting an error instead saying, “Failed to register a VB Script DLL. Reinstall or run Regsvr32.exe Vbscript.dll to self-register”, read on as this post will help you resolve the problem and help you re-register the vbscript.dll file. Follow each one of the steps below carefully to fix the problem.

• Step 1: In the Start search, type “cmd” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option from the context menu.
• Step 2: After opening Command Prompt as admin, type the regsvr32.exe vbscript.dll command and hit Enter to execute it.
• Step 3: After entering the command, it will re-register the concerned DLL file using the regsvr32.exe, a Windows OS tool. The Regsvr32 tool is a command-line utility that allows users to register or unregister OLE controls like the DLL and ActiveX (OCX) controls in the Windows operating system. After the command you entered has successfully run, you will see a message saying, “DllRegisterServer in vbscript.dll succeeded.”

On the other hand, if re-registering the DLL file didn’t work, you might have to log on to your computer using an administrator account and then try re-registering the DLL file once more. But before you do that, you need to create a system restore point first so that if anything goes wrong, you can always undo the changes you’ve made. After creating a system restore point, double-click on the downloaded .reg file to add its contents to the Registry. After that, try opening the program you were trying to open but weren’t able to because of the error. If it doesn’t work, you can always reinstall the affected programs that throw up the error and see if it resolves the problem. You could also seek the help of a one-click solution to fix the problem for you. This program is a useful tool that does not only repair corrupted registries and optimize your PC’s overall performance but also resolves any DLL issues like the Failed to register a VB Script DLL. Reinstall or run Regsvr32.exe Vbscript.dll to self-register” error. 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 for downloading and using it, refer to the steps below.

If the Task Manager is either blank or is not showing processes on your Windows 10 computer, then here are a few things you can do to resolve this issue. This kind of problem can occur due to some system file corruption or some malware infection in the system. Here are some suggestions you can try to resolve the problem with the Task Manager on your Windows 10 PC.

Option 1 – Try restarting your computer

The most common and most of the time effective way to resolve this kind of issue is to simply restart your computer. Thus, you have to restart your computer and see if it helps in fixing the Task Manager issue or not. If not, you can try the next given options below.

Option 2 – Run the DISM tool

If the first option didn’t work, then running the Deployment Imaging and Servicing Management tool can help you resolve the issue with the Task Manager as it will repair the Windows System Image as well as the Windows Component Store in Windows 10.

• After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
• Next, type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 3 – Make sure that the display columns are selected in the Task Manager

You have to make sure that you have checked or selected the display columns you want to be displayed. So if none of them are selected, you might not see any details at all. Thus, you need to right-click on the space near Name and select the columns.

Option 4 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the reason why the Task Manager is blank or is not showing processes. To run the SFC command, follow the steps given below.

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

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

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

• Restart your computer.

Option 5 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Task Manager issue. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try scanning your computer using Windows Defender

As mentioned, the Task Manager issue might be caused by some malware in the system and so to eliminate the malware, 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.