Apple gaming is coming!!!

Browsing your files on a computer seamlessly is made possible by the File Explorer in Windows 10 as it provides users with a great sense of customization for both listing and performing operations on a file. You have the option to arrange the folders and files being browsed by their name, type, date, size, and so on. Moreover, files that share a common attribute can be also be grouped accordingly using the grouping feature. However, there are times when instead of helping, it causes some problems for some users. This is why in this post, you will be guided on how you can disable the File Grouping feature in the File Explorer in Windows 10. There are two methods you need to consider in disabling the File Grouping feature in Windows 10. First, you can disable it for only one folder or you can disable it for all the folders on your computer. For more details, follow the instructions given below.

Option 1 – Disable File Grouping in only one folder

This first option is relatively straightforward and simple which will work if you only want to disable File Grouping in one folder.

• First, open File Explorer, and go to the folder you want to disable File Grouping.
• Next, right-click anywhere on that folder.
• And then select Group by > None. This will disable File Grouping for only that particular folder.

Option 2 – Disable File Grouping in all the folders

If you wish to disable File Grouping in all the folders on your computer, then you need to follow this option. If you have already tried the first one, then continue with the given steps below.

• Tap the Alt + V key combination.
• Then tap the Alt + Y keys and then tap Alt + O keys.
• After that, navigate to the View tab, and under the Folder views section, select Apply to Folders.
• Now click on the Apply and OK buttons to save the changes made. This will disable File Grouping in all the folders listed in the File Explorer.

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.

If you are trying to install or reinstall a program on your Windows 10 computer but encountered an error instead that says, “Fatal error, Installation fails, Installation ended prematurely because of an error”, then you’ve come to the right place as this post will guide you how you can fix it. This kind of error is most likely caused by some files that may have been left behind by the previous installation of the program. Each time a program is uninstalled, it leaves behind its files and if the uninstallation process wasn’t completed properly, then it would result in errors like the

“Fatal error, Installation fails, Installation ended prematurely because of an error”.

Moreover, this kind of error is a generic one that can also occur with any software reinstallation or installation. And to fix this error, there are several suggestions you must check out. You can try to install or reinstall the program in a Clean Boot State or restart the Windows Installer Service. You could also try to re-register the Windows Installer Service or re-register the VBScript.dll file.

Option 1 – Install or reinstall the program in a Clean Boot State

It is possible that there are some third-party applications in your computer that are preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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” checkbox 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” checkbox.
• 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.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.

Option 2 – Try to restart the Windows Installer Service

The next thing you can do to fix the problem is to restart the Windows Installer Service. To do this, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Windows Services Manager.
• Next, look for the Windows Installer service among the list of services shown.
• Once you found it, right-click on it and open its Properties.
• From there, click on the Stop button and then click on the Start button.
• But if it isn’t running, then just click on the Start button.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if unregistering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Try to re-register the vbscript.dll file

You may have to re-register the vbscript.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 un-register the OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type regsvr32.exe vbscript.dll 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.
• 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.

In case you don’t know, there is a built-in tool in Windows 10, known as Reliability Monitor that provides a day-to-day snapshot of the health of your system. It warns users of any looming issues or disasters before your computer breaks down finally. So obviously, Reliability Monitor is useful, however, there are times when it could behave incorrectly. For instance, it might fail to show you any updates even when they are installed. Thus, if you experience any malfunctions with the Reliability Monitor tool in Windows 10, read on as this post will guide you in updating or working in Windows 10. To fix the problem with the Reliability Monitor, there are several fixes you can check out. You can try to enable the data collection for Reliability Monitor or reset it, as well as put your computer in a Clean Boot State. For more information, refer to each one of the options given below.

Option 1 – Try to enable the Data Collection for Reliability Monitor

The Reliability Monitor tool uses data provided by the RAC Agent scheduled task and it will start to display a Stability Index rating and specific event information 24 hours after the system installation. The RACAgent scheduled task, by default, runs after the operating system is installed. And if it is disabled, it must be manually enabled from the Task Scheduler snap-in for MMC or Microsoft Management Console. Thus, you need to enable the Data Collection for Reliability Monitor to fix the problem.

Option 2 – Try to reset the Reliability Monitor

The next thing you can do to fix the issue with the Reliability Monitor might want to reset it to resolve the problem. If the Reliability Monitor is already open, you have to close it and open it again. After the reset is done, it may take up to 24 hours for the Reliability Monitor to display results again. This should fix the problem.

Option 3 – 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 Black border 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.

There are some new generation motherboards for laptops and PCs that bring in support for both the Unified Extensible Firmware Interface or UEFI as well as the Basic Input Output System or BIOS. The main advantage of UEFI over the traditional BIOS is the fact that UEFI supports a hard drive that has a capacity of more than 2 terabytes. However, the disadvantage of UEFI is that it only supports the x64 Windows operating system versions and that the hard drive is supposed to use the GPT structure. So if your PC is compatible with and supports UEFI and you want to change from Legacy to UEFI, then you’ve come to the right place as this post will guide you on how you can exactly do that without having to reinstall it. There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:

• Your PC’s motherboard should support both Legacy and UEFI.
• Your PC should be running at least the 1703 Windows 10 version or newer on an MBR partition.

Once you’ve made sure that your computer covers the aforementioned prerequisites, refer to the given options below.

Option 1 – Convert MBR to GPT via Windows built-in utilities

• In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that, execute this command: exe /convert /allowfullOS
• Now, wait until the process is completed since you can track its process on your screen.
• Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
• Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Now select the UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Convert MBR to GPT via the Recovery Environment

• When the message appears on your screen while running Windows Setup, you need to tap the Shift + F10 keys to open Command Prompt.
• Make sure to run Command Prompt as admin and then execute this command: exe /convert
• After that, wait until the process is completed. When it’s done, you have to go to the BIOS just like in the first given option above.
• As mentioned, you can usually find the Boot Mode under Boot > Boot Configuration. Once you’re there, set it to UEFI.
• Now save the changes made and exit as your computer will restart.

What Is STOP Code 0x0000008e

The STOP Code 0x0000008E is essentially an error code that is displayed on the STOP message. This STOP message is also commonly known as Blue Screen of Death or BSOD for short. When this error occurs, usually messages like, “STOP: 0x0000008E” or “KERNEL_MODE_EXCEPTION_NOT_HANDLED” are displayed to the user.

Solution

Download Available to Completely Repair Error 0x0000008e

Error Causes

These errors are commonly caused by failures of memory hardware. However, viruses, hardware failures or issues with the device drivers may also trigger them. If this error code appears but Windows is successfully able to recover from it, then the message ‘Windows has recovered from an unexpected shutdown’ is displayed to the users. Regardless of what causes these errors, it is of paramount importance that counteractive measures are taken as soon as the error appears.

Further Information and Manual Repair

While this error can be removed in many ways, the most effective ones are listed below as follows.

• The screen might be a fluke. Restart your system; the blue screen that appears to you may not be what it seems.
• Have you just modified or installed new hardware or driver? If yes, it is highly likely that the change you have made has triggered the error. If this is the case, it is strongly recommended that you revert back to the original settings and check whether the blue screen appears again or not. If it does, you can fix it by reconfiguring or removing the hardware you have recently installed. You can perform System Restore or you can go back to the previous versions if you have installed a new driver.
• To keep this error from occurring in the future, it is strongly advised that you test your RAM. Damaged memory or one that’s unable to perform in the usual manner is often the reason this error occurs.
• Ensure appropriate installation of your system memory. If you have installed memory in a way other than advised by your memory manufacturer that it may lead to STOP 0x0000008E error or other problems.
• Misconfigured or over-clocked memory settings can cause STOP 0x0000008E errors as well. To remedy this situation, it is best advised to return the BIOS settings to their default level.
• If you haven’t updated your Windows, apply all the updates you come across. Patches and service packs specifically address such issues.

One of the most useful and powerful built-in utility in Windows 10 is the DISM tool. This tool can be used with the Command Prompt command line as well as for other purposes. However, it is not without flaws and there are times when you may encounter some issues while using it. One of the problems you can get while using the DISM tool is the following error:

“The scratch directory size might be insufficient to perform this operation”

This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:

mkdir C:Scratch

Note: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:

/ScratchDir:C:Scratch

 Note: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.

When you upgrade your Windows 7 or Windows 8.1 system to Windows 10, you’ll undergo a phase called Out of Box Experience, or simply OOBE. This phase is intended to allow users to customize their Windows 10 experience, which includes defining personal settings, creating user accounts, and more. Some users reported having issues when creating their user account during the Out of Box Experience (OOBE) on Windows 10 upgrade. Some also reported issues about non-responsive behavior (Welcome Back) page.

Solution

Error Causes

Unfortunately, there’s no known cause for this error. However, some users reported that this occurs when:

• There’s a problem with the ISO or CD used to install Windows 10
• There’s hardware malfunctioning on the computer

Further Information and Manual Repair

Your Windows 10 upgrade will not be successful if you’re not able to create a user account or finish the Out of the Box (OOBE) phase of the installation. Here are some methods that will help you fix this manually.

Method 1 – Wait and retry

Some users reported that waiting for about an hour and retrying the process again will solve this problem. It’s also recommended that you keep your computer in a ventilated place while you wait to retry the process.

Method 2 – Load default user manually

This method has 2 requirements in order to work.

1. You need to be upgrading from a previous Windows version, and
2. Your Windows was originally configured to automatically boot to desktop

If you meet these two requirements, you can solve the error by following the steps below:

1. Hold CTRL+ESC keys. Windows should load the default user after doing this step.
2. Press the Windows key + X. Then, click the Computer Management icon
3. Choose “Local Users and Groups”
4. Double click on Users
5. Right-click on the right pane, and then choose “New User”
6. Create a new user account and password

Method 3 – Power down your laptop

This method only applies if you’re a laptop user.

1. Power down your laptop
2. Remove the battery of your laptop
3. Wait for about 10 minutes
4. Connect your laptop using direct current
5. Turn on your laptop again
6. Create a new user account and log in

Method 4 – Create a local account if you’re trying to set up a Microsoft account

Instead of connecting to a Microsoft Account after the set-up, you might want to try creating a local account. To do this, follow the steps below:

1. Power down your computer if you are to set up a Local Account.
2. Disconnect your computer from the Internet, either Wired or Wireless
3. Unplug your computer, and wait for about 10 minutes.
4. Reconnect your computer and start Windows. Do NOT connect to the Internet and make sure you’re disconnected to any devices you don’t need.
5. Try creating a user account again

 If the steps above don’t work, you might want to try Startup repair.

Method 5 – Boot your computer from Windows 10 media

In order to do this step, you need to have official Windows 10 ISO files.

1. Go to the “Install Now” screen
2. Choose Repair your computer
3. Click Advanced Options
4. Click Safe Mode

After doing the steps above, there’s a chance you get an error message that says “installation cannot be completed in safe mode”. When you see this, just press Shift+F10. This will execute and open the command prompt of your computer.

 From the command prompt, you can try and create a new user account.

 For example, net user Username Password /add

 The username here should be replaced with the account name you want to add, and the Password here should be replaced with the password you want to use for the account.

 After replacing the username and password on the text, press the Enter button on your keyboard. You’ll know if the command is successful once you see the message, “The command completed successfully.”

You can now close the command prompt. Restart your computer and try to log in using the account you just created.

Method 6 – Use a powerful automated software

If all the above methods still don’t work, it might be best to try automated software to help you fix this problem.

To make the Windows 10 operating system a lot more user-friendly, Microsoft introduced the Tablet Mode for Windows 10 devices, especially the 2-in-1 devices like Surface Pro and Surface Book. Despite the Tablet Mode’s efficiency, it also encounters some errors from time to time. One of the issues users reported about tablet mode is that they can’t turn off or exit tablet mode. If you are one of these users, read on as this post will guide you in what you can do to fix the issue. To fix the problem with Tablet Mode, there are several suggestions you can check out. You can try to check the full-screen setting, or perform a full shutdown or perform two buttons to restart the Surface devices. You could also disable Tablet Mode via Registry Editor or perform System Restore or change the settings in the System tab or the Action Center.

Option 1 – Try to check the full-screen setting

• Tap the Win + I keys to open the Windows Settings app.
• Then navigate to this path, Personalization > Start.
• Next, scroll down to toggle off the “Use Start Full Screen” option.
• After that, restart your computer and see if the problem is fixed.

Option 2 – Perform a full shutdown

• Open Command Prompt with admin privileges first.
• Next, execute this command to perform a full shutdown: shutdown /s /f /t 0
• The command you entered will shut down your computer and once it’s turned off, wait for a couple of minutes and then turn it back on.

Option 3 – Try to perform a two-button restart on your Surface device

• Tap and hold the power button for about 30 seconds.
• Then release them after 30 seconds.
• After that, tap and hold the volume up + the power button for 20 seconds. This will cause the display to flash a few times but you have to keep those buttons pressed until your Surface device is turned off.
• Wait for a couple of minutes and your Surface will turn back on. This should resolve the problem.

Option 4 – Try to disable the Tablet Mode via Registry Editor

• In the Start Search, type “registry editor” and right-click on the Registry Editor from the results, and then select the Run as administrator option. This will open the Registry Editor with admin privileges.
• Next, navigate to this registry key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionImmersiveShell
• From there, look for the DWORD named “SignInMode” and double click on it.
• Set its value to “1” and its base as hexadecimal.
• After that, click on OK to save the changes made. This will make sure that you are signed in to the desktop mode when you log into your account.
• Now look for the DWORD named “TabletMode” and double click on it and set its value data to “0” and it's base as hexadecimal.
• Click on OK to save the changes made and then restart your computer.

Option 5 – Run System Restore

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 6 – Try changing the settings in the System tab or the Action Center

• Go to Settings and navigate to System > Tablet Mode.
• After that, scroll down to set the “Use desktop mode” from the drop-down menu under the “When I sign in” section.
• Now restart your computer and see if the issue is fixed.

The Makecab.exe process that’s running on your Windows 10 computer is a program that compresses the Component-Based Servicing log or CBS log files and they can get really huge if they’re not compressed. As a result, it would utilize important space on your operating system although makecab.exe does not consume high CPU resources in doing so. However, there are times when it recreates thousands of instances of itself and could cause overconsumption of system resources which slows down your computer. So when the makecab.exe process causes high CPU usage in your system, this could mean that there is a failed Windows Update. In addition, the high CPU usage of the makecab.exe process could also mean that your computer is infected with a virus or malware. Whichever the case is, you can check out several possible solutions that are given in this post to resolve the problem.

Option 1 – Try to delete log file using File Explorer

The CBS log files could reach up to 20GB size and so if you delete them, it would help in saving space in your computer and since they’re not much of use, deleting them won’t negatively affect the system at all. To delete the CBS log files, all you have to do is open the File Explorer and then go to C:/Windows/Logs/CBS and from there, open the CBS log files and delete them all. Doing so should ease the load in the makecab.exe process since it no longer has to compress the CBS log files. As a result, the process would be more relaxed. After that, you can restart your computer and check if the problem’s now fixed.

Option 2 – Try deleting the log file via Command Prompt

You can also try to delete the log files using an elevated Command Prompt. Refer to these steps to do so:

• Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
• Next, type the following command and hit Enter to execute it:

del /f %windir%logscbs*.log

• Restart your computer afterward once the command has been executed. This should end the high disk usage by makecab.exe, if not, proceed to the next given options below.

Option 3 – Uninstall any suspicious programs you’ve installed recently

If you have recently installed some programs on your Windows 10 computer, and since then you’ve experienced high CPU usage brought on by makecab.exe, then you might want to uninstall those programs.

• Tap the Win + R keys to open the Run dialog box
• Then type “appwiz.cpl” in the field and hit Enter to open the Programs and Features in Control Panel.
• From there, look for the suspicious programs you’ve installed, select them and then click on Uninstall to remove them.
• After that, restart your computer and try to install the latest version of the program again. It should work now. If not, proceed to the next available option below.

Option 4 – Try running Disk Cleanup

You might want to run the Disk Cleanup utility as it is a useful tool that could delete temporary and useless files on your computer.

• Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
• After that, select the drive you want to clean.
• Now click OK to clean the disk and restart your computer.

Option 5 – Try to run System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files and missing files. It replaces bad and corrupted system files to good system files. 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 PC.

Option 6 – Try scanning your computer using Windows Defender

As mentioned, the high CPU usage of makecab.exe might be caused by some malware or virus in the system and so to eliminate it, 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.