Capture screen with Windows 10

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

If you encounter an error message saying, “ERR SSL VERSION OR CIPHER MISMATCH” while visiting a website, then it is not primarily your fault as an end-user. In fact, it can happen on any website like Chrome, Edge, Firefox, and even Internet Explorer. Getting this error means that the website you are visiting is using an SSL certificate which your browser seems to be rejected because there is some issue with the certificate. It is also possible that the certificate that’s downloaded on your computer is corrupted or that your computer configuration for TSL/SSL is misconfigured. Here are the complete details of the error message:

“A secure connection cannot be established because this site uses an unsupported protocol, Error code ERR_SSL_VERSION_OR_CIPHER_MISMATCH”

To resolve the ERR_SSL_VERSION_OR_CIPHER_MISMATCH error, refer to the options given below and see which one works for you.

Option 1 – Try to access the website with the only HTTP

The first thing you can do is to try accessing the website using HTTP instead of HTTPS. If you can open the website using HTTP then it means that the problem is in the website itself. And if you are the website owner, you can check the following:

Check if your website’s SSL certificate name is mismatched. Here you need to ensure that the name and alias of the websites match with the actual website URL where the certificate is installed.
Second, check if your server is using the RC4 Cipher. If it is, then you need to fix that.

On the other hand, you may also check if your CDN also supports SSL since most of the CDN nowadays supports SSL. All you have to do is configure it correctly and it should be good to go.

Option 2 – Try enabling SSL 3 / TLS and disable QUIC Protocol

If you were using Google Chrome when you got the ERR SSL VERSION OR CIPHER MISMATCH error, then you need to follow the protocol fixes for SSL3/TLS and QUIC which are usually some of the reasons that cause the SSL version / Cipher Mismatch. It also has a few fixes for Windows 10 computer where you can clear the certificates and make sure that your computer date and time is in sync with your time zone and so on. If you were using Edge or Internet Explorer when you got the error, then you have to follow the steps below.

Type “Internet” in the search box of your browser. After that, you should see the Internet Options from the search results.
Next, open the Internet Properties window and switch to the Advanced tab and then scroll down to the Security section.
From there, check the “Use TLS 1.1” checkbox as well as the “Use TLS 1.2” checkbox and then click OK to save the changes made.
Restart the browser.

On the other hand, if you were using Firefox when you go the error, here’s what you have to do.

Open Firefox and in the address bar, type “about:config” and hit Enter.
If a warning appears, just click on the “I accept the risk!” button to proceed.
Next, type in “TLS” in the search field and hit Enter.
Then look for “security.tls.version.min” and double click on it and set its integer value to 3 to force the protocol of TLS 1.3.
Now click OK and restart Firefox and do the same thing with SSL.

Fix Windows Activation Error Code 0x8007007B in Windows 10

If you recently upgraded your computer or if you’ve just switched to a new Windows 10 PC, the most common errors you might encounter are the Windows Activation errors. This issue boils down to the Windows Activation server which has either failed to validate or recognize the license tied to the digital account. In this post, you will be guided on how to fix an activation error in an organization with an error code 0x8007007B. It contains this exact error message: “We can’t activate Windows on this device as we can’t connect to your organization’s activation server. Make sure that you’re connected to your organization’s network and try again. If you continue having problems with activation, contact your organization’s support person. Error code 0x8007007B.” Various computers are activated via the KMS licensing (Key Management Server) in organizations. Computers that are activated using this process do not get a permanent activation and have to stay connected to the organization instead of for at least 7 months or 180 days. It is common in Pro and Enterprise versions that are deployed in bulk for at least hundreds or thousands of computers. So imagine a user with a personal computer in the office who decided to leave the organization but will still have an activated Windows key. And so to prevent that from happening, organizations use the KMS licensing. Another possible cause of the error is in case some user used an organization key and later on, the PC just got upgraded or downgraded to a version that is not compatible with that copy of Windows. To fix this Windows Activation error, here are some suggestions that might help.

Option 1 – You can try connecting to the organization’s network and activate the computer. But before that, you need to first check if the computer actually belongs to an organization or not.

Tap the Win + R keys to open the Run dialog box.
Type “cmd” and hit Enter to open an elevated Command Prompt.
After that type the vbs /dlv command and hit Enter to execute it.
Next, check if the Product Key Channel says “GVLK”. If it does, then it means that your computer was activated using volume licensing.

Option 2 – Change Licence Key

If you’ve recently left an organization then it’s best if you buy another copy of Windows 10 and then change the license key. This time, make sure that the license key is for the same version of Windows. However, if it’s different, you need to format your computer.

Option 3 – You can try activating Windows 10 using a mobile phone

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

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

Option 4 – If you think that the issue is caused by some hardware changes, you can try using the Activation Troubleshooter.

There are times when users already have the license keys and were able to activate Windows. However, it doesn’t last long and only works for a while and it’s suddenly throwing up an activation error like this one. To use the Windows Activation Troubleshooter, just go to Settings and to Activation and then run the troubleshooter from there. If you've made some modifications to your hardware, you have to click the “I changed hardware on this device recently” option for further suggestions.

Fix Windows was unable to repair the drive

If you connected your Hard Disk, USB, or SD card to your Windows 10 computer and you suddenly encounter an error that says, “Windows was unable to repair the drive”, read on as this post will help you fix the problem. This kind of error indicates that the file system on the drive has become corrupted and that ChkDsk was not able to repair the problem. You can also encounter this error when you try to run the ChkDsk utility to repair the system. This kind of error is most likely due to the general corruption of the contents in the drive. It is also possible that you removed the external drive without using the “Safely remove hardware” option or it could be that the drive is still in use. To fix the problem, the obvious thing to do is to safely remove the external drive by using the “Safely remove hardware” option. If it didn’t work, you can try to run the CHKDSK utility from the command line or you could also restart your computer in a Clean Boot State and then run the scan. Before you proceed with the potential fixes provided below, make sure that you create a system restore point first or you could also create a backup copy of the data to an external drive.

Option 1 – Run the CHKDSK utility from the command line

Although some users reported getting the “Windows was unable to repair the drive” when they run a CHKDSK scan, other users reported that running it also fixed the error. Thus, you can try to run it and see if it works or not.

In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f
The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 2 – Restart your computer in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that triggers the “Windows was unable to repair the drive” error to appear when you connect your external drive or run the CHKDSK utility. 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.)
Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Fix ndis.sys failed BSOD error on Windows 10

NDIS or Network Driver Interface Specification is a programming interface for the network interface cards that aids in the proper functioning of a system driver in a computer network. The NDIS helps the computer system in order to communicate with other connected devices and hardware components on a computer network. In relation, the ndis.sys file is a critical system file developed by Microsoft for the Windows operating system. As you know, sys files or system files are important parts of the Windows operating system as well as a repository of system driver settings used by Windows to communicate with the connected hardware and devices. The ndis.sys files are stored mostly in a driver folder at C:/Windows/System32/drivers and as mentioned, these files are essential for the system to function properly. Although the presence of ndis.sys system file is not yet known to affect the normal functioning of the Windows OS, some of the Windows 10 users reported that they encountered ndis.sys blue screen errors on their PCs. Blue Screen of Death errors or Stop errors usually occurs when you open a program or a function. Moreover, it could also occur when the driver gets loaded during the system startup or during system shutdown. It isn’t yet clear what really causes the ndis.sys blue screen error. However, like other Stop errors, it may occur due to corrupted files, misconfigured device drivers, bad drivers, corrupted Windows Registry, missing or damaged system files, and malicious programs. Aside from the aforementioned reasons, the ndis.sys blue screen error might also occur if your hard disk is damaged and if the RAM is corrupted. In such cases, a lot of users usually disable the ndis.sys file. However, it won’t really resolve the issue since the file is required for the normal functioning of the operating system and even when you disable the file, it’s pretty useless as the file will start all over again. In addition, you might want to disable security programs or firewalls and antivirus programs in the meantime to check if these programs are the ones that are causing the error. And if you’ve determined that none of the security programs or firewalls and antivirus programs are to blame, refer to the options below that might help you resolve the DRIVER_IRQL_NOT_LESS_OR_EQUAL or ndis.sys Blue Screen of Death error.

Option 1 – Try to update or reinstall the PC device driver

The Ndis.sys Blue screen error can occur when the device driver in your computer is outdated or corrupted. Thus, you either have to update or reinstall it to fix the issue.

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

Option 2 – Rollback your Network drivers

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
Then select each one of them and double-click to open a new mini window.
After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the ndis.sys Blue Screen of Death error. 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. 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 and hit Enter.

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:

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

Option 4 – Try running the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Netwtw04.sys failed BSOD error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

Open Command Prompt with admin privileges.
After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

Wait for the process to be completed and then restart your computer.

Option 5 – Run the DISM Tool

The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

Open the Command Prompt as admin.
Then type in this command: DISM /Online /Cleanup-Image /RestoreHealth
The DISM command you entered will repair the corrupted system image. Do not close the window if the process takes a while as it will probably take a few minutes to finish.
Restart your PC.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the ndis.sys Blue Screen of Death error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

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

Media Player can't detect the length of file

Even with the new Groove Music in Windows 10, a lot of users still prefer to use the old Windows Media Player. This isn’t surprising since Windows Media Player still remains to be one of the best players you can find. However, that does not mean that it is without flaws as it could still encounter some issues from time to time. One of the issues you might encounter when using the Windows Media Player is when you try to burn DVDs or CDs but end up failing due to an error that pops up that says, Windows Media Player cannot detect the length of the file. At the time of writing, it isn’t clear yet what the real cause of the error is. However, there are several fixes that are provided in this post for you to check out so you can resolve the problem. You can try to get rid of any unsupported files from the burning list or you could also try running the Windows Media Player troubleshooters. Aside from that, you could also try to drag and drop music or change the burning speed. For more details, refer to the following options.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try running the Windows Media Player troubleshooters

The next thing you can do to fix the error is to run the built-in troubleshooters for the Windows Media Player. Windows 10 actually comes pre-packed with three troubleshooters designed for Windows Media Player. They can help in fixing the “Windows Media Player cannot detect the length of the file” error. To run these troubleshooters, simply tap the Win + R keys to open the Run dialog box and type “msdt.exe -id WindowsMediaPlayerConfigurationDiagnostic” for the Windows Media Player Settings troubleshooter or type “msdt.exe -id WindowsMediaPlayerLibraryDiagnostic” for the Windows Media Player Library troubleshooter, or type “msdt.exe -id WindowsMediaPlayerDVDDiagnostic” for the Windows Media Player DVD troubleshooter.

Option 3 – Try to drag and drop music

Another thing you can check out is to drag and drop all the tracks into the Windows Media Player before you burn them. All you have to do is open the folder where the tracks are located and highlight all of them and then drag them to the Windows Media Player. It should now be able to detect the length of each one of the tracks without any errors.

Option 4 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. Just open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

PowerShell script Error 0xFFFD0000 in Windows

If you like to schedule different tasks on your Windows 10 computer and automate them, then you would find the Windows Task Scheduler very useful. It is commonly used by a lot of users to schedule various tasks like scheduling periodic execution of scripts and some programs to make sure that the intended tasks are automatically carried out. Apart from being a preinstalled application, the Task Scheduler is already available on your computer. However, there are times when you might encounter some errors while using it. One of these errors is error 0xFFFD0000. You can encounter this error while executing some PowerShell scripts. It can occur to any tasks as well especially to the ones that have a file executed using a particular program. And just like the PowerShell script, files also use PowerShell to be executed. To fix Error 0xFFFD0000, you need to follow the instructions provided below carefully. Step 1: In the Start Search, type “task scheduler” and click on Task Scheduler from the results to open it. Step 2: After opening Task Scheduler, right-click on the task that’s giving you the error and then click on Properties. Step 3: After that, navigate to the Actions tab in the new mini window that appears. Step 4: From there, select the action for the task and click on the Edit button which will open another mini window. Step 5: Next, make sure that the path to the executing program is properly typed inside the field of Program/script. Note that it should be set to the executable file for that particular program. For instance, you have to set it to “C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” for the Windows PowerShell program. Step 6: You can also utilize the Browse button and navigate through Windows Explorer to locate that particular executable file for the program. Step 7: Now make sure to use the file argument in the Add arguments field followed by the path of the file to be executed. It should look like this:

-file "C:/Users/Ayush/Desktop/Powershell Script Sample.ps1"

Step 8: Once done, click on OK to save the changes made and see if the task is still giving you an error or not. On the other hand, if you are still getting the same error, you can try to repair the Task Scheduler by deleting corrupted tasks. Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

Tap the Win + R keys to open the dialog box for Run.
Next, type in regedit and click on OK or tap Enter to open the Registry Editor.
Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take a note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

Right-click on the task name and then delete it.
After that, delete the very same GUID which you have copied earlier from these folders:
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

Next, navigate to this location: C:WindowsSystem32Tasks
Delete the very same tasks you just deleted from the Registry Editor.
Restart your PC and check if the Task Scheduler is back to its normal state or not.

Could not find this item, no longer in path

If you were trying to copy, move modify or delete a folder or a file in your computer but you’re not able to do so and encountered an error instead that says, “Could not find this item, This is no longer located in <path>, Verify the item’s location and try again”, then you’ve come to the right place as this post will guide you on how you can fix this error. You can encounter this error when you delete, rename, open or copy a certain file which is often created by third-party software and lacks important information like file format, and so on. Although you can see these files in File Explorer, you might not be able to perform some operations in them. To fix this problem, you need to check out the given suggestions below.

Option 1 – Try to rename the file via Command Prompt

If you were trying to rename the file but unable to do so, you can achieve that by executing a command in Command Prompt. Make sure to follow the steps carefully.

Type in “Command Prompt” In the Start menu to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator” to open Command Prompt with admin privileges.
Next, type in “cd” followed by the path where the file is located with this format – “C:/Folder1/Folder2/Folder3”. However, you have to omit the problematic file this time. To put it simply, the last folder in the command must be the folder where the file is located.
After inputting the command, press Enter on your keyboard and then use the set of commands given below. Note that each command is a new line so you need to tap Enter after copying each line.
- DIR /A /X /P
- RENAME (the current name of the problematic file) (a non-problematic name)
- EXIT

Note: Make sure that you only input the current name and the new name separated by a space. You must not write the brackets in the command. If everything goes well, you will now be able to operate the file like you used to before.

Option 2 – Try to delete the file using Command Prompt

On the other hand, if you were trying to delete the file instead of renaming it, you can execute another command in Command Prompt.

Open Command Prompt with admin privileges like what you did earlier.
Once you’ve opened Command Prompt, copy and paste the command given below and tap Entre after you do so. You also have to make sure that you key in the correct path where the file is located as well as its name.

rd /s \?X:badfolderpath

Note: In the command above, “X” is the placeholder letter so you must input the letter that corresponds to the drive’s letter where the file is located.

After that, you will see the “Operation completed successfully” message on your screen. If you don’t, check if you’ve really inputted the correct location of the file or its name.

Option 3 – Delete the file without any extension

If the file you were trying to delete does not have an extension, this means that Windows does not know what to do with this file which is why it’s throwing an error message. The best thing to do in such cases is to delete the file especially if it takes up a lot of memory. To delete these kinds of files, here’s what you have to do:

Follow the first two steps from the previous option above so you can navigate to the location of the file accurately just be careful in inputting the folders.
Don’t forget to tap Enter right after each command and then use the next command below so you can delete the affected file which has no extension:

del *.*

After you’re done, open the File Explorer and then check if the file is now deleted or not.

Malware Guide: How to Remove Bandoo

What is Bandoo?

Bandoo application, specifically product version 5.0.2.4762, is a bundled program. What does this mean? Simply, Bandoo, upon installation, installs additional programs, extensions, and add-ons to a computer and computer’s browser, without the knowledge of the user. This version of Bandoo concentrates on providing features for entertainment and also functionality/tools for backing up your computer files. Once executed, the file installs the iLivid Download Manager Software. Additional tools installed within the bundle include a Movie Toolbar and the thriving search engine ‘Ask.com.’ Technical details about Bandoo include:

Digital Signature/Publisher: Bandoo Media, Inc. Product Version: 5.0.2.4762 Entry Point: 0x000038AF

Assessment of Bandoo Potentially Unwanted Program

Interestingly, before the installation of Bandoo product version 5.0.2.4762 was complete, Spyhunter detected that the software was a PUP. After the installation was complete, product version 5.0.2.4762 of Bandoo added add-ons and extensions to both Internet Explorer and Chrome Browsers (these were the only 2 browsers used within the assessment). These appeared in the form of a Movie toolbar, providing quick access to movie trailers, reviews, ratings, and other video functionality, and ‘Ask’ (Ask.com) search engine.

Areas of Infiltration by Bandoo

Bandoo product version 5.0.2.4762 infiltrated several areas of the computer system. After installation, folders were neatly placed as files within all programs. Within “All Programs” there were 3 newly added programs. These included:

iLivid
Movies Search App for Chrome
Movies Search App for Internet Explorer

The iLiVid application seems to be the main offer while the others, namely Movies App for Internet Explorer by Ask was featured as promotions or advertisements. Additionally, just below the 'END USER LICENSE AGREEMENT AND PRIVACY POLICY' a request was made that the user set Ask.com as both their homepage, new tab, and default search engine. This is just another well-concocted plan to get Internet users onto the 'Ask.com' search engine. Along with the 3 programs installed as a bundle, a new folder was found within the computer's local drive. This program was termed OLBPre.

What is OLBPre?

OLBPre.exe is reputed as dangerous adware that weakens the security settings of a computer system. It's also covertly used for dropping files on a targeted computer, often without the user's consent or knowledge.

Manual Steps for Removal of Movie Search Apps

I found this removal pretty simple. Depending on your Operating System, there will be slight discrepancies in the manual removal steps. Using the Windows 8 (8.1) OS on your computer:

Step 1: from your desktop, right-click on the ‘Start Button’. A menu box will then appear.
Step 2: from the menu box, click ‘Search’.
Step 3: enter “Programs and Features” within the Input Box.
Step 4: locate the installed apps. You should be able to see “Movies Search App for Chrome” & “Movies Search App for Internet Explorer”.
Step 5: right-click on the names of the Apps (the ones you want to remove) when you’ve located them.
Note: you will have to remove the apps one after the other.
Step 6: after right-clicking the app, click the uninstall option (probably the only option available anyway).
Note: If a box appears asking If you wish to ‘block’ or ‘allow’, select the allow option. That’s just the Publisher’s way to annoy you out of uninstalling the app.
Step 7: follow instructions until the app is fully removed.
Step 8: Repeat steps for the other app.

Since Bandoo also changed your search engine, you’ll have to reset that manually for Internet Explorer and Chrome. Follow the steps below:

Step 1: Open your Internet Explorer browser.
Step 2: Click the tool option located in the top right-hand corner of the page.
Step 3: Click the “Internet Options” option.
Step 4: Under the “General” tab, you’ll be able to see approximately 3 buttons. Click the button labeled ‘Use Default”.
Step 5: At the bottom right-hand corner of the pop-up menu, select the “Apply” button and “OK”. That should do the trick.

Removal for Chrome Extension

This removal is simple.

Step 1: Open your Chrome browser.
Step 2: A pop-up box will be visible.
Step 3: Click the “Remove from Chrome” option.

After removing the extensions/add-ons, perform another scan with Spyhunter. You’ll pick up a few threats. The second scan should clear up everything. To completely remove Bandoo from your computer, click here to download and install Spyhunter.

Apple gaming is coming!!!

New Apple's upscaling technology called MetalFX will place iOS and macOS devices back into the gaming world. Apple had great games back in the old days and some all-time hits like the prince of Persia have been made first for apple but along the way, it just lost it.

Same as NVIDIA's DLSS and Intel's XeSS systems, Apple MetalFX also uses AI algorithms to upscale the resolution of output game frames. So, for example, the GPU inside your MAC might render the game at 1080p, but through MetalFX and AI upscaling it will look like a 4K image but have a good frame rate since it is rendered in base resolution.

The ability to make AI strike a good balance between performance and image quality is a key to technology in today's modern gaming and having this technology will help developers a ton to be able to achieve great results on Apple hardware.

The First MetalFX Games

So far three official games that will use this technology and be released natively for Appl hardware are Resident Evil 8 Village, GRID legends, and No Man's Sky. All three games have been confirmed and Resident Evil 8 Village is already sent for review people are impressed since the game can run smoothly on all Apple devices, even ones with an M1 CPU.

Apple is back into gaming

When you say Apple gaming is probably the last thing that comes to your mind but truth be told Apple makes more money from games than Microsoft, Nintendo and Sony combined. Also, Apple itself was a big player once regarding computer games as well, Myst and Prince of Persia are games that were made and have been released for Apple first. Bungie was also founded by Apple developers and Halo was originally announced as a Mac game.

Apple has been trying and pushing gaming on its platform since it kind of died down. Today all Sony, Nintendo, and Microsoft controllers work without any issues with all Apple products. Apple also has its own gaming subscription service, Apple Arcade, and its Apple TV is packed with GPU that can rival Xbox ones.

MetalFX API ties and brings it all together, it is designed to get the most performance from the hardware by minimizing overhead.

Now, computers and laptops do not hold any large numbers if we look at the user base, and that could deter developers but if we look at iPad and iPhone things are different there, much different. How same CPU power these devices and how MetalFX is available across all products it is clear that there is a market for games there. No Man's Sky is coming to iPad using these technologies and bringing full computer experience to tablets.

Makecab.exe is running & consuming CPU

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