Creating custom Keyboard shortcuts in Windows

Blue Yeti has gained popularity among streamers and users that want a high-quality mic for their setup. Without going into details of the hardware itself I will say it is a pretty good mic. Now the issues that have been reported with it are that Windows 11 can have issues with it resulting in the microphone not being recognized by the operating system. If you are one of the unfortunate Blue Yeti users and have this issue, do not despair because we have a solution for you, several to be more precise so you can easily fix the issue and get back to talking.

Check cables

Sometimes it is not a software problem at all. First thing is to check if by any chance cable of the mic is disconnected, damaged, or similar. If the cable seems fine next step is to plug in the mic into another port in order to eliminate faulty jack on the computer. If nothing happened the last thing to try is to connect the mic to another computer so we can be sure that the mic itself is in working order so we can focus on software. If by any chance mic is not working on another computer that some hardware inspection of it will be required.

Set Blue Yeti as a default device

There is a chance that Windows 11 has not set Blue Yeti as a default audio device for recording and therefore you can not use it. In order to eliminate and fix this issue, right-click on the speaker icon on the taskbar in the far-right part of it and choose sound settings. Go down to the input section and pick Blue Yeti beside Choose device for speaking or recording.

Update driver

More often than not device not working is tied to malfunctioning or a bad driver. In order to eliminate and resolve this issue right click on the Start icon and choose device manager. Inside device manager expand the Sound, video and game controllers section. Right-click on each device in the section and choose update driver. Wait for the update to complete and restart your system.

Run the troubleshooter

Press ⊞ WINDOWS + I to open Windows settings. Go to System in the left pane and click on it. In the right panel choose and click on troubleshoot. Inside troubleshoot click on Other. Scroll down and locate the Recording Audio troubleshooter and then click on Run next to it. Wait for the troubleshooter to finish and follow on-screen instructions to resolve the issue.

Check Blue Yeti microphone privacy setting

Not very often, but sometimes privacy settings can be the issue even when everything else is working perfectly. In order to check privacy settings press ⊞ WINDOWS + I to open Windows settings and go to Privacy & Security on the left panel and click on it. On the right panel click on the microphone. Make sure that toggle next to Let apps access your microphone is ON.

Error 0146 - What is it?

Dell laptop is a great choice for laptop users who like to have the best configuration, fast working platform, and long warranty period. But this does not mean that your errors can’t pop up on Dell laptops. Users can experience a variety of hardware and software-related issues on Dell laptops. And one such error is the error code 0146. This is a typical Dell laptop hard drive-related error code. It can cause your Dell laptop to freeze and system applications to stop responding for a long period of time. Therefore, it is recommended to fix the error immediately.

Solution

Error Causes

Error 0146 may be triggered due to several reasons on your system. These include:

• Program corruption
• Viral infection
• Hard drive issues

Further Information and Manual Repair

The good news is that error 0146 is easy to fix. Here are some of the easy do it yourself methods that you can try to resolve error 0146 on your system:

Method 1 - Run a Virus Scan

Malware and viruses can corrupt and damage the hard drive and trigger error 0146. In such an event, it is recommended that you open your antivirus, update it and run a full virus scan on your PC. Once the scan is complete, remove all the viruses. This will hopefully resolve the error 0146.

Method 2 - Run Your Laptop in Safe Mode and Clean Boot

Another alternative is to run your Dell laptop in safe mode and clean boot. To do this, simply disconnect all the attached devices like wireless printers, routers, and USB keys and turn off your laptop. Turn it on again and then press and hold the F8 key. Make sure you do it quickly before the Windows logo comes up. Now select ‘Safe mode with networking’ and press enter. After that, open System Configuration Utility by going to the start menu and typing ‘msconfig’ in RUN, and then click OK. In the System Configuration Utility click General then selective startup. Now uncheck the load startup items box ad select services and then check the hide all Microsoft services box and disable all. To apply these changes, click ‘Apply’ and then OK.  Now restart your laptop.

Method 3 - Change to SATA Drive

Sometimes error 0146 may pop up due to hard drive configuration changes. If this is the reason for error occurrence, then simply go to Dell Laptop BIOS. Check whether the hard drive configuration has been changed to AHCI SATA from SATA Drive. If it has changed, then it is advisable to change it back to SATA Drive. When you are done back up all your data, and then format your hard drive. It is important to create a backup because formatting will make you lose all your data. Once you format the hard drive, reinstall Windows from scratch.

Method 4 - Run a Registry Scan

If the error 0146 results due to program corruption then there is a possibility that the underlying reason might be registry damage. Therefore it is advisable to run a registry scan and repair it. To do so, download Restoro. This is a cutting-edge and user-friendly PC Fixer integrated with a registry cleaner. Run it to scan for registry issues. It removes all obsolete files corrupting and damaging the registry, repairs important and damaged system files and cleans the registry in the shortest time. Click here to download Restoro and resolve error 0146.

Minecraft has taken the world by the storm, it was an indie project game and it went mainstream. Dream of every game developer I guess. The dream of every gamer on the other hand is to double click on the game and to play it and not to deal with various issues, especially if they are launch issues. Luckily for all of you gamers, here at errortools we game as well and we are happy to bring you a solution on how to fix Minecraft won't launch issue. So sit back, relax and keep on reading, and hopefully enough you will be gaming again in no time. Follow the guide presented step by step, point by point how it is presented for the quickest way to get back in Minecraft. This guide also presumes that your hardware configurations meet at least the minimum system requirements for running Minecraft.

1. Disable antivirus and firewall

   90% of the time this is the issue why Minecraft is not working, your antivirus or firewall has detected it as a false positive, and access to system internet, etc has been cut. Try disabling it and if everything is working fine add it to the antivirus or the firewall exception list.

2. Run Minecraft as admin

   Minecraft will sometimes refuse to run if it does not has administrator privileges. To make sure this is the case locate the Minecraft executable, right-click on it and choose properties. Go to the compatibility tab and check Run as Administrator box.

3. End Minecraft process

   It came to knowledge that even if Minecraft is not running it can have its processes active in the background. Press CTRL + SHIFT + ESC to open task manager Locate if Minecraft has a process running If you find the Minecraft process right-click on it and choose End Task

4. Run Minecraft in compatibility mode

   If Minecraft still refuses to start try running it in compatibility mode in the previous Windows version Locate Minecraft executable file in its install location Right-click on it and choose properties In the properties, windows go to the compatibility tab Check run this program in compatibility mode for: Select previous version of the operating system, try Windows 8 or Windows 7

5. Update graphic card driver

   The best bet is to go to your GPU manufacturer's website and download the latest version of the driver of your GPU.

6. Remove mods, plugins, texture packs

   Mods, plugins, texture packs are all great but sometimes they can cause GPU overloads and other issues to see if this is the case try running Minecraft in Vannila mode without anything installed, just pure and clean Minecraft as it was just downloaded and installed.

7. Reinstall Minecraft

   If everything else failed, reinstall Minecraft. There might be a chance that some DLL file was deleted or corrupted by mistake or that some crucial files are missing. Clean reinstallation will fix all of these issues.

Apple introduced the Live Photo feature way with iPhone 6S in their iOS9. Live Photo idea was that each time you take a photo, your phone will capture a few seconds of video along with sound and all of that is sent when you share your photo. This of course can sometimes be really bad when some not wanted audio gets recorded in the background.

Since the feature was introduced it has been set as the default option when taking pictures so each time you snap one you just capture a small amount of video and audio along. Good thing is that this feature can be turned off and the even better news is that you can edit your old photos to remove back video and audio.

How to share only photo

You can keep your Live Photos but share only a single still typical photo if you wish. Go to the photos app on your phone and select the photo you wish to share. Press the Share button on the bottom left part of the screen and once the Share menu appears tap on the Live button in the upper left corner of the selected photo. The button should turn grey and become slashed and now you can share only still photo. This is only temporary for this one specific share so next time you want to do this you will have to go through the process again.

How to disable Live Photo

If you are not happy with the previous solution and really do not want to turn off the Live feature each time you want to share a photo or you just simply do not want the feature at all there is way to turn if off for good. Take note that you can temporarily not use this feature just by opening the camera, switching to photo mode, and then tapping on the Live photo button on the toolbar that looks like three circles one inside another. This will temporarily turn the Live Photo feature for this session but next time when you open the camera by default it will be turned on again. This is a good approach if you want the feature but sometimes you just want not to use it.

In order to turn it off completely go to the settings of your phone and go to Camera and then preserve settings. inside the preserve setting turn the switch Live Photo to ON position, now go-to camera and again click on the live photo button to turn it off but this time setting will be saved and next time you open the camera it will not be ON.

Editing old Live Photos

As stated before you can edit your old pictures in order to make them stills. You can edit them to remove audio only but keep the video part, or you can completely remove everything and convert them into typical still images.

In order to only remove audio from your Live Photos go to pictures and select one that you wish to change, click on edit, and inside edit tap on the Live Photo icon (three circles). Next tap on the audio icon located in the top left corner of your screen and it will change into the mute icon. Click on done and you are finished.

To completely remove the Live photo go to Photos, select picture, click on edit and select the live photo button again. This time tap and hold the Live button next to the sound until it turns gray with a strike through it. Click on done and you are finished.

The screen flickers into black, it comes back and on-screen there is a message Driver stopped responding and has recovered. If you have been through this you are aware that the issue is not serious but it can get pretty annoying fast since you are not aware when will it happen again, and it will happen again. In this guide, we will go through the usual reasons for this error and offer solutions to them. Follow the guide step by step in order to resolve the problem.

1. Clean your PC Dirt and dust are your enemy no1, dirty graphic card can not be properly called and can cause overheating which can result in this particular error, make sure that your PC is clean and tidy in order to eliminate dust and dirt as a cause for malfunction.
2. Turn off multiple applications and try running just one at a time Overburdening GPU can cause this error to appear since the graphic card can not handle all requests it gets from multiple active applications. Try to run just one application at a time for some time period to see if the error will appear again.
3. Update driver Update your GPU driver to the latest version from the manufacturer's website, Display Driver Stopped Responding and Has Recovered Error in Windows 10 can be from outdated drivers not able to handle modern tasks
4. Get newer GPU As hard as this advice is, sometimes the reason is an old graphic card that simply can not keep up with modern games and applications, upgrade it to a more modern GPU and watch errors go away.

As you know, Windows programs depend on several operations to get executed and at the same time, there are also numerous parameters that have to be fulfilled for a program to get executed. However, based on some reports, there was an error when some users tried to run a program. This error says, “The application was unable to start correctly (0xc00007b)”. There could be various reasons why this error occurs but the main one is most likely due to an x86 application that is not compatible with the x64-based operating system. To fix this problem, you can run the Check Disk utility or reinstall the application or the Microsoft .NET Framework. You can also try reinstalling DirectX or replace the corrupted DLL file(s). For more details, refer to the given options below.

Option 1 – Try running the Check Disk utility

• 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 – Re-enable the Microsoft .NET Framework

You could also try to disable the Microsoft .NET Framework then enable the latest version of the .NET Framework on your PC and check if the error is fixed

Option 3 – Try to reinstall the program

There are times when some supporting module for your application under the hood could have messed up the application where you get the error. To fix this, you have to uninstall the program and then download its latest version from its official site and then install it again. Once you’re done, run the application and see if the error is fixed.

Option 4 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

• Reboot your computer.

Option 5 – Try running the DirectX Diagnostic Tool

Since the error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 6 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Error Causes

The common causes of propsys.dll file error are:

• Registry problem
• The propsys.dll file is damaged due to a virus or spyware
• Improper software removal
• Hardware Failure

The propsys.dll error message is displayed in either of the following forms:

• Propsys.dll not found
• Cannot find [Path]propsys.dll
• This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
• The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.

• Recommended Solution for Registry Issue

If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.

• Recommended Solution for File Damage and Corruption

Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.

• Recommended Solution for Hardware Failure

If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.

Installing Windows Updates in your Windows 10 computer does not always go smoothly as there are instances when you could encounter some errors along the way. One of these errors is error code 0x80244022 –WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL HTTP 503. This kind of error can be encountered when you check, download or install any updates. At the time of writing, it isn’t known yet what the exact cause of this error is. However, there are some potential fixes you can check out to fix it. When this error occurs, you will see the following error message on your screen:

“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80244022).”

To fix error code 0x80244022, refer to the potential fixes provided below.

Option 1 – Disable the Proxy server

The first thing you can do is to try disabling the Proxy server as it might be the reason why you’re getting error 0x80244022 for Windows Updates. To disable the proxy server, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it. In addition, if you are also using a VPN, you can try to disable it as well.

Option 2 – Run the DISM tool

You can run the DISM tool as well to help fix the error code 0x80244022 during Windows Update. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 3 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing error code 0x80244022 to appear when you try to update your Windows 10 computer. 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:

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.

• Once done, restart your computer.

Option 4 – Try disabling the Firewall or antivirus program

Disabling the antivirus program or Firewall or any other security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 5 – Try resetting the Windows Update components

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:/Windows/SoftwareDistribution/SoftwareDistribution.old
  • ren C:/Windows/System32/catroot2/Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 6 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Computers viruses, worms, ransomware, etc. are kinds of malicious software that no user should take lightly. On several occasions, we have touched upon security steps that each user should take in order to protect its identity and data. Sadly sometimes even when all precautions are taken some malware can still slip through and wreak havoc. Today we are looking at some of the worst or the best, depending on your view that has indeed wreaked plenty of havoc.

10 worst computer viruses in history

In the list of the 10 most famous computer viruses below, we show the costs, dates, reach, and other key facts. First a note about terms: we use the words “virus” and “worm” interchangeably because most readers search for them that way. But there’s a subtle difference that we explain after the list.

1. Mydoom – $38 billion

The worst computer virus outbreak in history, Mydoom caused estimated damage of $38 billion in 2004, but its inflation-adjusted cost is actually $52.2 billion. Also known as Novarg, this malware is technically a “worm,” spread by mass emailing. At one point, the Mydoom virus was responsible for 25% of all emails sent. Mydoom scraped addresses from infected machines, then sent copies of itself to those addresses. It also roped those infected machines into a web of computers called a botnet that performed distributed denial of service (DDoS) attacks. These attacks were intended to shut down a target website or server. Mydoom is still around today, generating 1% of all phishing emails. That’s no small feat considering the 3.4 billion phishing emails sent each day. By that figure, Mydoom has taken on a life of its own, infecting enough poorly-protected machines to send 1.2 billion copies of itself per year, 16 years after its creation. Though a $250,000 reward was offered, the developer of this dangerous computer worm was never caught. Wondering what makes the world’s most secure computers so safe? See the Tech@Work guide: Upgrade to the World's Most Secure and Manageable PC

2. Sobig – $30 billion

The 2003 Sobig computer virus is actually another worm. It is second only to the Mydoom virus in its scope. The $30 billion figure is a worldwide total, including Canada, the U.K., the U.S., mainland Europe, and Asia. Several versions of the worm were released in quick succession, named Sobig.A through Sobig.F, with Sobig.F being the most damaging. This cybercriminal program masqueraded as legitimate computer software attached to emails. It disrupted ticketing at Air Canada and interfered with countless other businesses. Despite its widespread damage, the creator of the successful bug was never caught.

3. Klez – $19.8 billion

Klez is a close third on the list of the worst computer viruses ever created. With nearly $20 billion in estimated damages, it infected about 7.2% of all computers in 2001, or 7 million PCs. The Klez worm sent fake emails, spoofed recognized senders and, among other things, attempted to deactivate other viruses. As with other viruses and worms, Klez was released in several variants. It infected files, copied itself, and spread throughout each victim’s network. It hung around for years, with each version more destructive than the last. Windows has come a long way since most of the computer viruses on this list hit the web. Thankfully, built-in protection with Microsoft Defender is always on the watch.

4. ILOVEYOU – $15 billion

The year 2000’s ILOVEYOU virus worked by sending a bogus “love letter” that looked like a harmless text file. Like Mydoom, this attacker sent copies of itself to every email address in the infected machine’s contact list. Shortly after its May 4 release, it had spread to more than 10 million PCs. The virus was created by a college student in the Philippines named Onel de Guzman. Lacking funds, he wrote the virus to steal passwords so he could log into online services he wanted to use for free. He reportedly had no idea how far his creation would spread. This virus is also known as Loveletter. Need to up your remote work security game before there’s another entry on the list of most deadly computer viruses? See our guide: How to Work Remotely and Securely

5. WannaCry – $4 billion

The 2017 WannaCry computer virus is ransomware, a virus that takes over your computer (or cloud files) and holds them hostage. The WannaCry ransomware ripped through computers in 150 countries, causing massive productivity losses as businesses, hospitals, and government organizations that didn’t pay were forced to rebuild systems from scratch. The malware raged like wildfire through 200,000 computers worldwide. It stopped when a 22-year-old security researcher in the U.K. found a way to turn it off. Computers with out-of-date operating systems were hit especially hard. That’s why security experts always recommend updating your systems frequently.

Ransomware strikes again

In September 2020, one of the potentially largest computer virus attacks in medical history hit Universal Health Services. The U.S. hospital chain, which has more than 400 locations, was reportedly struck by damaging ransomware. The attack forced the cancellation of surgeries and made healthcare workers switch to paper records.

6. Zeus – $3 billion

The Zeus computer virus is an online theft tool that hit the web in 2007. A whitepaper by Unisys three years later estimated that it was behind 44% of all banking malware attacks. By then, it had breached 88% of all Fortune 500 companies, 2,500 organizations total, and 76,000 computers in 196 countries. The Zeus botnet was a group of programs that worked together to take over machines for a remote “bot master.” It originated in Eastern Europe and was used to transfer money to secret bank accounts. More than 100 members of the crime ring behind the virus, mostly in the U.S., were arrested in 2010. It’s not as prominent today, but some of the virus’ source code lives on in newer botnet viruses and worms. Zeus caused documented damage of $100 million. But the real cost in terms of lost productivity, removal, and undocumented theft is undoubtedly much higher. A $3 billion estimate, adjusted for inflation, puts this virus at a cost of $3.7 billion in today’s dollars.

7. Code Red – $2.4 billion

First observed in 2001, the Code Red computer virus was yet another worm that penetrated 975,000 hosts. It displayed the words “Hacked by Chinese!” across infected web pages, and it ran entirely in each machine’s memory. In most cases it left no trace in hard drives or other storage. Financial costs are pegged at $2.4 billion. The virus attacked websites of infected computers and delivered a distributed denial of service (DDoS) attack on the U.S. White House’s website, www.whitehouse.gov. In fact, the White House had to change its IP address to defend against Cod Red. Can your printer get a virus? See our cool infographic: The State of Printer Security

8. Slammer – $1.2 billion

The SQL Slammer worm cost an estimated $750 million across 200,000 computer users in 2003. This computer virus randomly selected IP addresses, exploiting vulnerabilities and sending itself on to other machines. It used these victim machines to launch a DDoS attack on several internet hosts, significantly slowing internet traffic. The Slammer worm hit banks in the U.S. and Canada especially hard, taking ATMs offline in many locations. Customers of Toronto’s Imperial Bank of Commerce found themselves unable to access funds. The attack reared its ugly head again in 2016, launching from IP addresses in Ukraine, China, and Mexico.

9. CryptoLocker – $665 million

Thankfully, ransomware attacks like the 2013 CryptoLocker virus have dipped since their 2017 peak. This malware attacked upwards of 250,000 machines by encrypting their files. It displayed a red ransom note informing users that “your important files encryption produced on this computer.” A payment window accompanied the note. The virus’ creators used a worm called the Gameover Zeus botnet to make and send copies of the CryptoLocker virus. According to a report by security firm Sophos, the average ransomware attack costs a business $133,000. If we estimate that CryptoLocker hit 5,000 companies, that would put its total cost at $665 million. Where will cybersecurity go next? See our guide: The Future of Cybersecurity

10. Sasser – $500 million

The Sasser worm was written by a 17-year-old German computer science student named Sven Jaschan. He was arrested at the age of 18 in 2004 after a $250,000 bounty was posted for the computer virus’ creator. A friend of Jaschan’s tipped authorities that the youth had penned not only the Sasser worm but also the damaging Netsky.AC attack. Jaschan was given a suspended sentence after it was found he was a minor when he wrote the malware. The Sasser worm crashed millions of PCs, and though some reports put damages at $18 billion, the relatively low infection rate suggests a more likely cost of $500 million. Other notable viruses The top 10 worst computer viruses above are just the ugly tip of a gargantuan digital iceberg. With a million new malware programs popping up every 3 years, we may miss the forest for a few outstanding trees. Here are just a few more viruses that have wreaked havoc over the years: Mimail: This worm tried to harvest data from infected machines to launch a string of DDoS attacks, but was relatively easy to remove. Yaha: Yet another worm with several variants, thought to be the result of a cyber-war between Pakistan and India. Swen: Written in C++, the Swen computer worm disguised itself to look like a 2003 OS update. Its financial cost has been pegged at $10.4 billion, but not reliably. Storm Worm: This worm showed up in 2007 and attacked millions of computers with an email about approaching bad weather. Tanatos/Bugbear: A 2002 keylogger virus that targeted financial institutions and spread to 150 countries. Sircam: A computer worm from 2001 that used counterfeit emails with the subject line, “I send you this file in order to have your advice.” Explorezip: This worm used fake emails to spread to every machine on thousands of local networks. Melissa: The most dangerous computer virus in 1999, Melissa sent copies of itself that looked like NSFW pics. The U.S. FBI estimated cleanup and repair costs at $80 million. Flashback: A Mac-only virus, Flashback infected over 600,000 Macs in 2012 and even infected Apple’s home base in Cupertino, Calif. In 2020, there’s now more malware on Macs than on PCs. Conficker: This 2009 virus still infects many legacy systems and could do significant damage if it ever activates. Stuxnet: This worm is reported to have destroyed Iranian nuclear centrifuges by sending damaging instructions.

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.