Fix Windows is not starting

If you are trying to copy or move files to and from your external storage device but you suddenly encounter the error 0x800703EE, then you’ve come to the right place as this post will guide you on how you can fix this error in your Windows 10 computer. This kind of error when copying files may be accompanied by an error message that says, “The volume for a file has been externally altered so that the opened file is no longer valid”. This error prevents you from copying or moving the files to and from the external storage device. This kind of issue might be caused by a service that belongs to a backup program that could be blocking the operation or a conflict with your third-party antivirus program. In addition, the error could also be due to corrupted or outdated USB drivers or it could be caused by a disabled Windows Backup and Volume Shadow copy service. It is also possible that some system files are corrupted or that the drivers for the external device are also corrupted. Whatever the cause is, here are some options you need to check out to fix the error. Before you troubleshoot the error, you might want to try moving the files to another location on your local drive and remove the USB drive and insert it back again. After that, try to move or copy the file to the USB drive and see if it still throws an error. If it does, then you need to troubleshoot the problem further by following each one of the suggestions given below.

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

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

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

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

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

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

Option 2 – Try checking the Volume Shadow Copy and Windows Backup services

The next thing you can do to fix error 0x800703EE is to check the Volume Shadow Copy and Windows Backup service.

• First, tap the Win + R keys to open the Run dialog box and type “services.msc” in the field, and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Copy service and right-click on it, and then select Properties.
• After that, make sure that its Startup type is set to Manual and that its status is “Started” so if it isn’t, you need to click on the Start button and then on the Apply and OK buttons to save the changes made.
• Once done, look for the Windows Backup Service and repeat the same process you did with the Volume Shadow Copy service.
• After you complete the steps, restart your computer and see if the error is now fixed.

Option 3 – Restart your computer in a Clean Boot State

If a third party program like antivirus is the one that’s causing the problem, you can try to put your computer in a Clean Boot State to isolate the issue by following these steps:

• 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.)
• Now try to copy the files to your external storage device again and check if the error is now gone.

Option 4 – Try to run System File Checker or SFC scan

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

Option 5 – Try to delete the Filter drivers

Note that this option is only applicable if you see the error 0x800703EE accompanied with the “The volume for a file has been externally altered so that the opened file is no longer valid” error message. Before you start, create a System Restore Point first.

• Open the Registry Editor and navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E965-E325-11CE-BFC1-08002BE10318}
• After that, select the “{4D36E965-E325-11CE-BFC1-08002BE10318}” key and check if you can find the “Upperfilters” and “Lowerfilters” value in the right pane. If you can find them, right-click on them and select Delete.
• Once done, exit the Registry Editor and restart your computer.

Windows 10 has displayed one of the most efficient and user-friendly interfaces. However there have been many issues on the backend of this commonly praised operating system: For example, Windows Update is still a wonky and error-laded system application. One example of this error is Windows Update Error 0x80073712 which stands in the way of users just wanting to keep their PCs updated hassle-free. The error code 0x80073712 signifies that a file needed by Windows Update to function is either damaged, missing, or corrupted. However, this does not mean that your Windows version will forever stay as-is with no mode to update it. Windows Update Error 0x80073712 is perfectly fixable with the set of provided steps below and some of Windows’ built-in troubleshooting steps:

Solution 1: Open Windows Update Troubleshooter

1. Open the Windows Update Troubleshooter by pressing the Window Key and  “S” keys simultaneously.
2. Enter the word “Troubleshoot” in the search box and select the Troubleshoot result
3. On the new window, select “Windows Update” to troubleshoot.
4. Run the troubleshooter, then open Windows Update and try to install the update again.

Solution 2: Run the DISM tool

1. Open the command prompt by pressing Windows Key and “S” key simultaneously
2. Enter “cmd” in the search box. Right Click command prompt among the results and select “Run as administrator”
3. In the Command Prompt window type the following and press the Enter key after every command

DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth

4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
5. Run Windows Update again.

Solution 3: Rename the Software Distribution folder

1. Open the command prompt as previously mentioned
2. Input the following command pressing Enter after every line net stop wuauserv net stop cryptSvc net stop bits net stop msiserver rename c:windowsSoftwareDistribution softwaredistribution.old net start wuauserv net start cryptSvc net start bits net start msiserver exit
3. Restart the PC and run the updater if it works again.

Solution 4: Restart Windows Update Services

1. Press the Windows logo key and R together to open Run -> Input services.msc -> and press Enter
2. Search for the Windows Update service -> Check its status
3. If it is not indicated, right-click on the service and select Start to force start your Windows Update
4. If you see an error, locate the Startup Type option and set it to Automatic
5. Now you should reboot your computer and see if your Windows Update is OK

Solution 5: Fix Registry Issues

If after all the aforementioned solutions, you still experience problems with Windows Update, the problem may lie in the registry that is either damaged or corrupted. You may choose to do manual editing of your Windows registry by opening your Windows registry editor. But doing so is risky as one wrong letter may do incalculable damage to your system. To do so safely for more inexperienced users., we recommend using a third-party registry cleaner/tools, many of which can be found online.

Error 2738 - What is it?

Error 2738 is associated with the VBScript engine. VBScript is the abbreviation for Visual Basic Scripting. It is an Active Scripting programming language developed by Microsoft and modeled on Visual Basic. It is used with a fast interpreter in a large variety of Microsoft environments. Error 2738 indicates that the VBScript engine is not registered properly on your PC. It occurs when you try to install or uninstall VBScript-supported applications on your system. The error message is displayed in the following format:

"Error 2738. Could not access VBScript run time for custom action."

Solution

Error Causes

There are several reasons for the error 2738 message pop up. These include: Incorrect or corrupt registry entries on your system. These entries interfere with VBScript support in Windows thereby generating such error codes.

• Removal of McAfee Antivirus
• Windows registry values are not updated accurately during the uninstallation of McAfee Software
• The Visual Basic Script is registered in the registry under the local user instead of the local machine

No matter what the cause of the error may be, it is recommended that you resolve the issue immediately without any delay.

Further Information and Manual Repair

Here are some of the easy and proven DIY methods to repair error 2738 on your PC:

Method 1

If the error 2738 occurs because the VBScript is not registered correctly, then follow these steps to resolve.

1. Go to the start menu, open Run, and type RegEdit in the box and then press OK. This will open the Windows Registry Editor.
2. Now type KEY_LOCAL_MACHINESOFTWAREClassesCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32, if the key does not have a data value of C:\Windows\System32\vbscript.dll then simply add it.
3. Now go to the All programs option and then Accessories.
4. Here right-click on Command Prompt and then ‘Run as Administrator’.
5. Now type egsvr32 vbscript.dll then press enter. After that type regsvr32 jscript.dll and then press enter.
6. Restart your PC to activate changes.

Method 2

Sometimes error 2738 may occur when you uninstall preinstalled MacAfee antivirus software on your system. Un-installation usually leaves some trace components in the registry. These components must be removed completely otherwise error codes like 2738 may keep occurring on your computer screen. In such an event, the best way to resolve it is to download the McAfee Consumer Product Removal utility from McAfee's official website. Save this file on your desktop. Double click the file and follow the steps to remove this software completely and successfully from your PC. Proper removal of the McAfee program will resolve error 2738 right away. But if the error still persists then try other methods illustrated below.

Method 3

Download Restoro to remove incorrect and corrupt registry entries on your system that may be interfering with VBScript support. Restoro is a new and easy-to-use PC Repair Tool deployed with an intuitive interface and a powerful registry cleaner. The registry cleaner removes all entries corrupting the registry, cleans it, and resumes it to its normal state. Click here to download Restoro.

As you know, the Windows Update process takes compatibility seriously. The Windows Updates need to be compatible with the hardware as well as all the installed applications in the computer else the Windows Updates will only get stuck in the process. Two of the Windows 10 errors that shows up during this case is the error 0xC1900208, 0x4000C. These error codes are caused by incompatible applications which means that there might be an incompatible app installed in your computer that’s blocking the upgrade process and prevents it from finishing. That’s why you need to make sure that all the applications on your computer are updated to their latest versions and then check the compatibility. So if there are any incompatible apps, be sure to uninstall them and then try doing the upgrade once again. Take note that these error codes are just among many compatibility issues that the Windows Update throws up. Since the error is caused by a compatibility issue, you have three options – first, you can update the incompatible application to the latest version, second, uninstall the application or trick Windows and make it seem like it’s compatible.

Option 1 – Try updating the application or software

As mentioned, you can try updating the concerned application or software to its latest version to resolve the compatibility issue and in turn, fix the errors 0xC1900208 – 0x4000C. Note that depending on where you had installed the application, your steps will change. So if you have it installed directly from the website, refer to these steps:

• Look for the built-in option to check the updates since the most application has this option.
• You also have the option to go to the website of the application and check if there is a new version available. If there is, download and update the app.

On the other hand, if you have downloaded the app from the Microsoft Store, here’s what you have to do:

• Open the Store and click on the three dots located at the top-right of the window.
• Next, click the Download and Updates option.
• From there, check if there is an update available for the store. If there is, update it.

Option 2 – Try to uninstall the application or software

If updating the app or software to its latest version didn’t help and you’re still getting the error 0xC1900208 – 0x4000C every time you attempt to install the Windows Updates, you may have to uninstall it. You will need to use the usual Program and Features to uninstall it if you have downloaded it from the website.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 3 – Try bypassing the Upgrade Advisor

There are times when a software developer fails to pass the compatibility test for their apps. It could be that they work on Windows 10 upgraded version but just didn’t pass the compatibility check. So if you are pretty certain that the app really works on Windows 10, you can just bypass the Upgrade Advisor.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

We have talked about gaming on old computers and have covered new and upcoming Steam deck handheld console. Today we are combining old gaming with a handheld console and our target of talk is Retroid pocket 2. This product is packed with really high-quality plastic and with some great features in it. So let's dive into this cool handheld in more detail and find out why we like it so much.

Good manufacturing quality

Plastic and overall manufacturing quality are really, really good. The battery is great, packing 4000mAh that can hold over 3 hours of nonstop gaming, and all buttons and joysticks are great. The screen is a 640 x 480 60Hz 3.5″ IPS screen (4:3 aspect ratio) that performs really great for its purpose, retro gaming. There is a Digital D-Pad and dual analog joysticks. The right joystick is the lower profile to avoid being accidentally moved when pressing the four gaming buttons. There are three buttons at the bottom which are Home, Start, and Select. On either side are good-quality stereo speakers. On the bottom of the device are a Micro SD Card slot and a 3.5mm headphone port. On the top of the device are Left and Right shoulder and trigger buttons. There are the power button and volume adjustments. There are a USB Type-C OTG port and a Micro HDMI output for connection to a TV.

Good technical statistics

Good, not great but then again since this is retro handheld you cannot really expect some crazy stuff like alder lake inside. So the console is punching ARM Cortex A7 CPU with 2 cores and a clock of 1.5GHz paired with ARM Mali 400-MP2 500MHz GPU. The console has 1GB LPDDR3 RAM memory and 8GB eMMC Storage where 5GB is freely available, the rest is taken for OS. As mentioned before the display is 640x480 resolution with a size of 3.5″. The battery is Lithium-Ion with a power of 4000mAh and on the handheld, there is a USB Type-C connector, 3.5mm headphone jack, and Micro-HDMI. It also has Wifi/Bluetooth 4.0

Retroid Pocket 2 OS and support

Pocket 2 comes with Android 6 but you can update its firmware to the 8.1 version on the official site that I would highly recommend. New versions of the handheld will come with 8.1 on it from the box. Having Android as OS opens many possibilities like you can download Android apps such as Steam Link, allowing you to play actual PC games on your Retroid Pocket 2. Not just that, if it does get a newer version of Android it could even have the ability to use xCloud, Xbox’s cloud gaming service. Of course, hardware will not be able to handle modern games but the option is still there and for some old PC titles available on steam like Commander Keen, for example, this is a great option. The console can emulate basically everything up to Dreamcast, including N64, PSP, and Playstation 1. It can emulate Nintendo DS also, but it can only do so with one screen. The only problem with this console is you will need to install and update Apps. You’ll need to learn about RetroArch, an app that lets you download emulators or cores to play games.

Retroid price

The last thing on the list is the price of the console itself. Going just under the 100$ mark this really makes it an affordable option for plenty of people that would like to experience retro handheld gaming or for ones like me, nostalgic gamers wanting to relive some era of playing games on the road.

Conclusion

Among Chinese handheld devices for retro gaming, Retroid Pocket 2 is really on top of what the market can offer. If you are looking for a great handheld retro console and are not afraid of little dive-ins into the OS and various configurations, Pocket 2 will reward you with plenty and wide emulation support.

As you know, Windows Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

Among other things and innovations, Windows 11 brings to the table is the game mode. The game mode is a system designed to release some resources and optimize your system when Windows 11 detects that you are playing games. It also turns off automatic updates while the game is active. The game mode is active at all times and usually, everything works great but in some instances, it can sadly cause some performance issues. If you are one of these unlucky people where game mode is not working as supposed to do, don’t panic, we have a quick guide for you on how to turn it off.

1. Press ⊞ WINDOWS + I to open settings
2. Inside click on Gaming
3. Select Game mode
4. Click switch beside Game mode to turn it off
5. Close settings

Everything will be automatically saved and applied and you should not have any issues from now on. If for any reason you wish to turn game mode back ON, just follow the same steps and turn the switch to ON.

Recently, a number of users reported not being able to use the Restore, Minimize and Close buttons on their Windows 10 computers. This kind of issue can be quite annoying as you won’t be able to use your computer properly, especially when you navigate between programs and windows. In such cases, the buttons on the right side of the title bar won’t respond to any inputs which could be caused by a number of factors such as different input modes, corrupted system files, and many more. If you are one of the users who are currently facing this problem, worry not for this post will guide you on what you can do to resolve it. There are several potential fixes you can check out to fix the issue. You can try to check if Tablet Mode is enabled and if it is, you have to disable it. You could also boot your computer in a Clean Boot State to check if a third-party program is the one that’s causing the problem. In addition, you could also reinstall the program where you experience the problem or run built-in utilities like System File Checker and DISM tool.

Option 1 – Make sure that you are not in Tablet Mode

Since Windows 10 is designed to work on both desktop and mobile devices, it could be that your computer has slipped into Tablet Mode which explains why you’re not seeing the Taskbar. To check if your computer is really in Tablet Mode, follow these steps:

• Go to the Start menu and select Settings.
• Next, select the System setting and from the left pane select the Tablet Mode.
• From there, make sure that the buttons next to the options given below are set to the off position:
  • Hide app icons on the taskbar in tablet mode
  • Automatically hide the taskbar in tablet mode

Option 2 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into 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.)
• Once your computer is in a Clean Boot State, try to open the program where the problem occurred.

Option 3 – Try reinstalling the program

If the first two options didn’t work, then you might want to consider uninstalling the program and then install it back with its latest version. This should resolve the problem.

Option 4 – Try to run System File Checker

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 to good system files that might be the cause why the Restore, Minimize and Close buttons don’t work. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

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

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

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

Option 5 – Run the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the problem. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /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. Once it’s done, restart your computer.

Sometimes, some applications after they are installed will put their shortcut in the context menu (right-click on desktop) for easy access, most of the time these are some system tied applications like AMD and Nvidia control panels or archives like WinRAR or 7ZIP but it can happen even for some usual application to do this.

There are some applications that you use frequently and they could be worth putting in the context menu, if you want to avoid clutter on the desktop or in the taskbar this is the third place that you should consider placing shortcuts.

Doing this will require some playing and tweaking in the Windows registry editor so be careful when editing the registry since bad entries can lead to system crash or instability. Follow step-by-step instructions.

Adding apps to the context menu in the registry

Creating entry

Open the registry editor by searching Regedit and pressing enter than inside of the registry editor search for the next key:

HKEY_CLASSES_ROOT\Directory\Background\shell

Select shell and right-click on it, hover over New and in the submenu click on Key. In the next step, you need to name a key, this name will be the thing that will be shown in the context menu when you right-click on a desktop so type in the name that you would like or the name of the application that you wish to add to the menu.

If you wish you can even add a keyboard shortcut to launch this specific application. To do this select entry that you have created and edit the default value, inside the edit string in the Value data field type first & and after that key that you would like as a shortcut. Now after right click if you hit your shortcut key app will be launched right away.

Adding command

The next task is to create a command key that will actually hold the command to launch the application. Right-click on the entry that you have created, hover over New, and click on Key.

Next, you’ll need to create the command key that will actually hold the command used to launch the application. Right-click on the new Notepad key, and then choose New \ Key from the menu. Name this key 'command', all in lower case and without hyphens.

Now in order to finish setting the launcher, you need the full path of the file that you would like to run. Locate your file in file explorer or in another tool and copy its path by SHIFT + right-clicking on the file itself and choosing copy as path option.

Now click on the command key and double click on the default key on right to edit it, inside the field value data paste your path to executable. close and save the registry and you are done.