How to Fix Windows 10 Error 8024402C

If by any chance you are working on a touchscreen PC, tablet, or any similar device and have no access to a hardware keyboard there is a way to place Touch Keyboard on your screen for easy typing, and you can enable icon on the taskbar for easy access.

Enabling the Touch Keyboard

1. Right-click on the Taskbar
2. Select Taskbar Settings
3. Go to Personalization > Taskbar
4. Click on Taskbar Corner Icons to expand it
5. Click on the switch next to Touch Keyboard to turn it ON
6. Close settings

The icon will immediately appear on the Taskbar in the lower right corner. Clicking the icon virtual keyboard will appear on the lower part of the screen. You can use this keyboard to type in applications the same as you were typing on hardware one. By taping on X in the upper right corner, you will hide the keyboard. Tap on the icon in Taskbar to bring it up again.

Hide the Taskbar icon

If you do not want to use Touch Keyboard anymore you can easily hide the icon:

1. Right-click on the Taskbar
2. Select Taskbar Settings
3. Go to Personalization > Taskbar
4. Click on Taskbar Corner Icons to expand it
5. Click on the switch next to Touch Keyboard to turn it OFF
6. Close settings

There are cases when you encounter some issues while updating your Windows 10 computer. One of these issues is the error 0x80240034. This particular error is a Windows Update Error that appears on the Windows Update pane every time an update fails to install. When this happens, your Windows Update will only get stuck at 1% and nothing happens afterward and eventually fails. If you click on the View Installed Update History, you will see the error code 0x80240034 for the failed updates. You will see this error each time you try to update your Windows PC. Take note that this issue doesn’t only happen to a specific version of the Windows Update but on various different Windows builds based on many users. What’s more, is that some users are also seeing a different error code when their Windows Update fails but they still end up seeing the error code 0x80240034 when they check the Windows Update history. At the time of writing, it isn’t determined yet what really causes this error but it’s most likely due to some corrupted files in the computer which is why the most common solution you can try is resetting the Windows Update cache. On the other hand, other users also resolved the issue by using the ISO and selecting the “Do not keep previous settings” option during the Windows Update so it might be something to do with transferring the previous settings through the update client. For clear instructions in fixing this issue, refer to the two options provided below.

Option 1 – Try to clear the Windows Update Cache/Distribution Folder

As mentioned earlier, a lot of users tried clearing the Windows Update cache to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Step 1: Tap the Windows key once.
• Step 2: Next, type in “command prompt” in the Windows Start Search, and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option from the context menu.
• Step 3: After opening Command Prompt, type in “net start wuauserv” and hit Enter.
• Step 4: Then type in “rmdir %windir%SoftwareDistribution /S /Q” and hit Enter.
• Step 5: Now type in “net start wuauserv” and hit Enter. Once it’s done, try updating your Windows PC again, it should now work just fine.

Option 2 – Update Windows via ISO file

If option 1 didn’t work for you, you can try this second option of updating your Windows 10 computer using an ISO file which means that you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. The most user reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seems to create issues such as the error 0x80240034. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Step 1: Click this link and then click the Download Tool Now button.
• Step 2: Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Step 3: Now select the ISO file option in step 5.
• Step 4: After that, you should now have an ISO file.
• Step 5: Next, go to the location where you’ve downloaded the ISO file.
• Step 6: Then right-click on the Windows 10 ISO file and select the Open with an option and then select File Explorer.
• Step 7: Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either: Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Hello all the wonderful people and welcome to our new article where we take a little different turn than usual and discuss why keeping old electronics around the house is not such a good idea. We all have some drawer or in some bag around the house and in the end of the day if that electronic has battery inside it is probably not the smart thing to keep it.

So naturally, the question comes why it is a bad idea to have old electronics with batteries in them? Well unlike a battery failure with, say, some AA batteries jammed in the back of an old toy, the risk with a lithium-ion battery failing isn’t just some leaking and corrosion in the battery compartment, it’s a potential fire as the battery swells up and the gases (combined with the stored energy) turn the battery into a potential fire hazard.

Good thing is that the battery will not explode just like that, it will swallow over time and get bigger and bigger until the breaking point is reached and all the fire breaks lose. So if by any chance you have some old gadgets lying around you can check up on them and see if has swelling process started, if yes, dispose properly of that piece of the old device immediately.

How to keep old electronics

If you’re not ready to get rid of the gadget then it’s best to charge it properly for storage. Proper charging keeps the battery cells and circuits in optimum health.

While recommendations vary by manufacturer and application, the general consensus is that lithium-ion batteries should be charged to approximately 40%. (Some manufacturers recommend charging 50% or 60% instead.)

Really, the important part here isn’t the exact percentage. What’s important is ensuring that the battery is charged to roughly half capacity and not stored with a completely discharged or completely full battery.

Discharge rates on lithium-ion batteries in completely powered-off devices are very slow, but you should still plan to top off the charge every 12-18 months or so to keep it around 50%.

If you wanted to go above and beyond, a metal storage container with a snug lid on a basement shelf with a desiccant pack inside to control the moisture would offer optimum conditions.

The Windows 10 Orange Screen of Death, unlike Blue Screen of Errors, is quite an uncommon error where the hardware is the culprit which is mostly caused by some issues with the GPU. If you are currently facing this problem, then you’ve come to the right place as this post will guide you on what you can do to fix it. There have been reports from users that the Orange Screen of Death is caused by various reasons. Some users reported that they encountered Orange Screen of Death when they were watching a YouTube video, while some were not able to boot into their Windows 10 PCs and encountered an error instead of that either says, FAULTY_HARDWARE_CORRUPTED_PAGE or WHEA_UNCORRECTABLE_ERROR error. In addition, this error can also occur when your computer wakes up from Sleep or while using BitLocker, or while you use a second monitor. Whatever the case is, you can try updating your drivers or lower the clock speed of the GPU. You could also try to fix the DRIVER_IRQL issue in case it’s the one that triggers the error or performs Automatic Repair or uninstalls any recently installed software.

Option 1 – Update your Graphics card drivers

One of the possible reasons why you’re getting the Orange Screen of Death error is most likely related to the Graphics card drivers in your computer. Thus, the first thing you can do to resolve it is to update these drivers by following these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Try to uninstall software you’ve installed recently

If you have installed a software or two recently and then suddenly encounter this Orange Screen of Death, then they are most likely the culprits. The best thing you can do is to first check the System Log in the Event Viewer for any additional information in case it’s not the GPU but some other driver or device that’s causing the error. Once you have identified the culprits, uninstall them and see if the error is fixed.

Option 3 – Try disabling Overclocking

If overclocking is enabled, you might have to disable it as some users reported that the WHEA_UNCORRECTABLE_ERROR 0x00000124 error started to appear right after overclocking. To disable it, follow the steps below.

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the WHEA_UNCORRECTABLE_ERROR 0x00000124 error is now fixed.

Option 4 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the Wdf01000.sys Blue Screen error, you need to use the Driver Verifier Manager:

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

Option 5 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

If you recently made some changes in your Windows 10 computer using the Group Policy Editor but they were not reflected and you got errors instead, it could be that your Windows computer wasn’t able to read the Group Policy file (registry.pol). To resolve this kind of issue, you have to repair the potentially corrupted Group Policy using the options given in this post. .As you know, Group Policy is a feature in the Microsoft Windows Active Directory which allows an admin to make changes in the features on Windows PCs that are on the network. So if the modifications you just made weren’t successfully applied, then there could be something wrong with the registry.pol file on the client or it could also be that the Group Policy folder is missing. To fix this issue in the Group Policy, you need to refer to the given suggestions below and make sure that you have admin privileges as you execute them.

Option 1 – Try to delete or recreate the missing registry.pol file

The entire settings of the Group Policy are stored in the registry.pol file so if it went missing, all the changes you make will not be reflected. The good thing is that you can recreate it but if the file exists and is corrupted, you need to delete it first before you recreate it.

• First, go to the C:/Windows/System32/GroupPolicy/Machine location.
• And from there, check if the registry.pol file exists or not. If it’s there, just delete it permanently by tapping the Shift + Delete keys.
• Now it’s time to recreate the file. Just open Windows PowerShell with admin privileges by tapping Win + X + A keys.
• After opening PowerShell, type this command: gpupdate /force
• The command you entered will recreate the registry.pol file and will refresh the Group Policy. Restart your computer.

Option 2 – Try recreating the secedit.sdb file

The security settings of Group Policy are stored in the secedit.sdb file so if you made some changes to security and they weren’t reflected, you can try to delete and recreate the secedit.sdb file instead of deleting the Group Policy file. All you have to do is navigate to the C:/WINDOWS/security/Database folder and look for the secedit.sdb file and rename it or move it to another folder. After that, restart your computer. Once your computer has restarted, the secedit.sdb file will be created again.

Option 3 – Try to reset the Group Policy to default

You can also try to reset the Group Policy back to its default state. There are several ways you can do that. You can either use the gpupdate or the secedit command in the Windows PowerShell to do that. Resetting the Group Policy will resolve any issues that could be caused by its current settings.

Option 4 – Try to perform System Restore

System Restore can also help resolve the Group Policy issue. It could be that prior to the issue, you’ve made some changes in the system that might have affected the Group Policy. To undo these changes, perform System Restore.

• First, 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 5 – Use the DISM tool

You can also try running the Deployment Imaging and Servicing Management or DISM tool. This tool will repair the Windows System Image as well as the Windows Component Store in your Windows 10 computer. So if there are any missing or corrupted folders and files, the DISM tool can restore and repair them. As a result, any system consistencies and corruptions will be fixed. To run this tool, follow these steps:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer.

If you encounter an error saying, “Invalid file handle” when you try to rename, copy, delete a file or other operations in your Windows 10 computer, then read on as this post will guide you in what you can do to fix it. This kind of error pops up when the operating system tries to carry out an operation on a folder or file using the following words:

CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

When you rename or create a folder or file using the reserved words given above, you could encounter an error that says, “The specified device name is invalid”. This occurs since these words are Windows system reserved words that you can’t use, unlike any other words. Thus, if you have a folder or file which contains any of the reserved words on another computer that runs a non-Windows operating system and you try to copy or rename it Windows, then it’s no wonder why you’re getting this error message. In such cases, you can always click on the Skip button to stop the operation. However, if there are various folders or files, you can just use the Command Prompt to carry out the task. All it takes is a simple command that will get rid of the folder as well as the files in it. How? Refer to the instructions given below. Step 1: Tap the Win + R keys to open the Run utility. Step 2: Next, type “cmd” in the field and then tap Enter to open Command Prompt. Step 3: After opening Command Prompt, execute the following command:

rd \.file-folder-path /S /Q

Note: The “rd” command will remove the directory or the folder while the “\.” command will select the current computer. The “/S” command, on the other hand, helps you in removing all the sub-directories and the files that are in the CON folder. The “/Q” command is not really mandatory since it helps you remove everything silently without any confirmation message. For example, if you have a folder named “CON” located on your Desktop, the path will be like this “C:/Users/<username>/Desktop/CON”. In this case, the command should be like this:

rd \.C:Users<username>DesktopCON /S /Q

However, if the error pops up for a whole different reason, you could use the following command instead to remove the reparse point extended functionality. Once you’ve entered the given command below, you should now be able to delete the file.

FSUTIL reparsepoint delete C:Users<username>DesktopFileName DEL C:Users<username>DesktopFileName

BSOD or Blue Screen of Death errors are one of the toughest issues you can encounter in Windows 10 as well as the hardest ones to resolve as they simply shut the system down or restart it abruptly and claims that it isn’t possible to boot Windows again. One of the difficult BSOD errors is the Machine Check Exception BSOD error. The reason why it is hard to fix is that in most cases, it occurs soon after Windows loads which gives users little to no time in resolving it. To make things worse, the system also freezes right before it displays the blue screen error and shuts the system down. Usually, the Machine Check Exception Stop error occurs due to the failure or overstressing of the hardware components. And in the case of almost all Blue Screen of Death errors, the issue usually has something to do with the drivers. So if you frequently see this BSOD error from time to time, now’s the time to act on it by following the solutions given in this post.

Option 1 – Update the Device drivers

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. Look for the device driver you and then select either “Update driver” or “Uninstall device”. 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.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 2 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

Option 3 – Try running the 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 with good system files that might be causing the Machine Check Exception BSOD error. 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.

Option 4 – Run the Startup Repair

In the Blue Screen where the Machine Check Exception error is displayed, tap the F8 key to go to the Startup Settings where you can find Startup Repair and then run it. Note that this is a must-try option especially if you are unable to start your computer and if you can use your computer for a few moments.

Option 5 – Run the DISM tool

There are cases when the Machine Check Exception error is caused by the Windows System Image so you need to repair it using the DISM or Deployment Imaging and Servicing Management 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 /CheckHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 6 – Try resetting the BIOS

If you have made some modifications in the BIOS that might have caused this error, you have to revert those changes to resolve the issue. On the other hand, if you have made a couple of changes and you do not remember which is which, you might have to reset the BIOS.

Option 7 – Try resetting Windows 10

To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.

If you encountered an error message saying, “We couldn’t find any drives, To get a storage driver, click Load driver” when you try to install Windows in a VirtualBox machine, then you’ve come to the right place as this post will guide you in fixing this error. This error message is displayed on the screen where you have to choose a partition to install the guest operating system. This error is most likely due to the lack of correct settings as well as a corrupted virtual disk. To fix this error, you have to remove existing storage devices, create a new storage device and select the correct ISO file.

For complete instructions, follow the given steps below.

Step_1: The first thing you have to do is remove all the existing Storage devices and since this option is already available in VirtualBox by default, there is no need for you to install any third-party software. Step_2: After that, open VirtualBox and select the virtual machine and then click the Settings button. Step_3: Next, switch to the Storage section and on your right-hand side, you will see “Controller: SATA” and two other sub-labels. From there, select Controller: SATA and then click on the red cross button that says, “Remove selected storage controller”. Step_4: Now click on the Add new storage controller icon and select the “Add SATA Controller” option from the given list. Step_5: Afterwards, click the “Add hard disk” button and select the “Create new disk” option, and then you have to create a new virtual disk for your virtual machine. Step_6: Verify if you have selected Dynamically allocated while you create the virtual hard disk. Once the process is completed, you will get a “.vdi” file in the list. Step_7: Next, click on the “Add optical drive” button and select the “Choose disk” option. Here, you have to select the ISO file and if you can find an ISO file in the given list, select it from there, else, you have to click the Add button and navigate to the folder where the ISO file is located. Step_8: Once you’re done, click the OK button and boot your virtual machine. You should see options instead of the “We couldn’t find any drives, To get a storage driver, click Load driver” error message. If you see the options, you can now create a new partition and start the installation process of the Windows operating system in the VirtualBox machine without any problem.

There are times when you see a message in Windows Defender saying, “The Threat Services has stopped, Restart it now” when you try to use it. This kind of error is usually fixed by simply clicking on the Restart now button. However, if the error still appears even after you restart your computer and you see another message that says, “Unexpected error, Sorry, we ran into a problem”, then continue reading as this post will guide you in resolving this issue in Windows Defender. Before you proceed with the given fixes below, you have to create a System Restore point first. This way, you can always undo any changes you’ve made in case something goes wrong.

Option 1 – Make sure that the Windows Defender Services are started

The Windows Defender Advanced Threat Protection service is the one that protects your computer from advanced threats by monitoring and reporting security events that happen on your computer. This is why you have to make sure that this, as well as other required services in Windows Defender, are set to their default values and are started. To do so, follow these steps:

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager
• After opening the Services Manager, look for the following services and make sure that their Startup type is set to their default values:
  • Windows Defender Advanced Threat Protection Service – Manual
  • Windows Defender Antivirus Network Inspection Service – Manual
  • Windows Defender Antivirus Service – Manual
  • Windows Defender Firewall Service – Automatic
• You can right-click on each one of the listed services and then select Start to start them.
• And if some of the services don’t have their default values, just double-click on the Services to change the Startup types and select the correct option from the drop-down menu of the Startup type under the Properties box.
• Next, set up the Startup type of these services to Automatic and then click on the Start button if the services are not running yet.
• Now click on the Apply and OK buttons to save the changes made and then see if it fixed the problem or not.

Option 2 – Try modifying some entries in the Windows Registry

If the first option didn’t work in fixing the problem, you can try to alter some entries in the Windows Registry using the Registry Editor.

• First, tap Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKLMSoftwarePoliciesMicrosoftWindows Defender
• From there, look for the “DisabledAntivirus” and “DisableAntiSpyware” DWORDS from the right pane and change each one of their values to “0”. On the other hand, if you don’t see any of these DWORDS, you can create them instead and give each one of them a 0 value.
• To create a DWORD, simply right-click on any empty space and select New > DWORD. Then name them both as “DisabledAntivirus” and “DisableAntiSpyware”.
• Afterward, set the value of the newly-created DWORDS to 0.
• Now exit the Registry Editor and reboot your PC to apply the changes made and then check if it has fixed the error in Windows Defender or not.

REevil is one of the most active and successful hacking groups connected to Russia and operating all over the world. The group recently demanded a huge bitcoin ransom for an attack targeting IT firm Kaseya in the USA. Since Tuesday blog and payment site run by REvil group cannot be longer reached without any kind of explanation or why. The reason behind the disappearance is unknown but has sparked speculation that the group may have been targeted deliberately by authorities. US President Joe Biden said he raised the issue with Vladimir Putin during a phone call on Friday, after discussing the subject during a summit with the Russian president in Geneva last month. Mr. Biden told reporters that he had "made it very clear to him...we expect them to act" on information and also hinted the US could take direct digital retaliation on servers used for intrusions. The timing of Tuesday's outage has sparked speculation that either the US or Russian officials may have taken action against REvil - though officials have so far declined to comment and cyber experts say sudden disappearances of groups are not necessarily uncommon. The development comes after a series of high-profile ransomware attacks which have hit major US businesses this year. The FBI accused REvil - also known as Sodinokibi - of being behind a ransomware attack on the world's largest meat processing company JBS last month.