Change Legacy to UEFI without reinstalling

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

There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:

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

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

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

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

Option 2 – Convert MBR to GPT via the Recovery Environment

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

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

MMC.exe has been blocked for your protection
When trying to run Computer Management, or when running mmc.exe or compmgmt.msc from a command prompt you get the error that the application has been blocked for your protection then keep reading in order to solve the issue. This is a permission issue where if a regular user tries to run such system tools will result in saying that it has been blocked. Along with this, you may have a Group Policy issue. This can be fixed, but you will need admin permission to achieve it. It’s because when they are run from the command prompt with elevated privileges, it works.
  1. Change Group Policy Settings

    If your account is an admin account, and you are still facing the issue, then change the group policy settings: Open Group Policy Settings by typing gpedit.msc in the run prompt followed by pressing ENTER Navigate to User Configuration > Administrative Templates > Windows Components > Microsoft Management Console > Restricted/Permitted snap-ins Locate Computer Management policy, and double click to open it Enable it, exit Group Policy. When Enabled: The snap-in is permitted and can be added into the Microsoft Management Console or run from the command line as a standalone console. When Disabled: The snap-in is prohibited and cannot be added into the Microsoft Management Console or run from the command line as a standalone console. An error message is displayed stating that the policy is prohibiting the use of this snap-in.
  2. Temporarily disable UAC

    UAC is the user access control panel, and if you need to run the command right away, you can choose to disable it for some time. Click on the Start button, and then type UAC to find the User Account Control Settings. Click to open, and then slide down the notification setting at the bottom. It will temporarily allow launching the application as there is no check. However, make sure to switch to default once you are done.
Read More
10 Worst Computer Viruses in history
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.

viruses10 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.
Read More
Automatically Turn Off Hotspot when idle
One of the useful features that came with Windows 10 is the Mobile Hotspot although there’s a downside to it – it drains your battery faster especially if your Windows 10 device is running on battery. Another one of its flaws in the implementation of this feature is that it stays activated even when the connection is idle. In other words, it is still activated even if no devices are connected to it. As a result, it consumes battery life and affects it. There are also instances when it affects the performance of the network connection. At the time of writing, Microsoft hasn’t done anything about this dilemma yet so in the meantime, you can continue reading this post to resolve this issue on your Windows 10 device. You can remedy this Mobile Hotspot issue by running a command in Windows PowerShell. To get started, follow the given instructions below.

Turn off Mobile Hotspot Automatically:

Step 1: The first thing you have to do is to copy the following command:
powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 1 /F & net start "icssvc"' -Verb runAs"
Step 2: After copying the command given above, open the Notepad app and paste the command you copied there and save it. And when saving it, select the “Save as” option and its File type as “All files”. Step 3: After that, put “TurnOnTimer.bat” as the file’s name and save it on your Desktop. Step 4: Once done, run the file you just created, and when a User Account Control or UAC prompt appears, just click on Yes. Step 5: After you run the file, it will run a series of scripts in a command line which will turn off the Mobile Hotspot automatically when idle. And that’s how you automatically turn off the Mobile Hotspot when your Windows 10 device is idle. On the other hand, if you want to undo the changes made, you can always do so using the steps provided below.

Turn on Mobile Hotspot:

Step 1: Copy and paste the following command in the Notepad app:
powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 0 /F & net start "icssvc"' -Verb runAs"
Step 2: After copying and pasting the command, save it as “TurnOffTimer.bat” on the Desktop. Step 3: Once done, run the file like what you did earlier and select Yes when a UAC prompt pops up. This will run a series of scripts on a command line which will revert the changes back to their default state.
Read More
Windows 11 Insider Preview Build 22000.71
Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

windows insider 2000Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

  • We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
  • Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
  • After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
  • Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
  • We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
  • We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
  • When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
  • The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
  • When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
  • We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
  • We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
  • We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
  • This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
  • Right-clicking the focus assist icon in the taskbar should now show a context menu.
  • The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
  • The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

  • We fixed an issue making Settings crash on launch periodically.
  • Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
  • We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
  • There was a non-functional verify link under Backup Settings – this has been fixed.
  • The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
  • The Power and Battery Settings page should also now not crash when launched from Quick Settings.
  • We fixed a grammatical error in the Sign-in Settings text.
  • The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
  • The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
  • We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
  • We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
  • We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
  • We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
  • Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
  • Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
  • The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

  • Clicking the command bar button twice should now close any dropdown that appeared.
  • The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
  • This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
  • Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

  • We fixed an issue where the option to verify your account in Search wasn’t working.
  • Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
  • Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

  • When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
  • We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
  • We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
  • The traffic widget should now follow the Windows mode (light or dark).
  • The title of the sports widget should no longer mismatch with the content of the widget.

Other:

  • This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
  • We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
  • Magnifier’s lens view has been updated so the lens now has rounded corners.
  • We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
  • We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
  • Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
  • We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
  • We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
  • We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
  • We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

  • In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
  • Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

  • There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
  • The Taskbar will sometimes flicker when switching input methods.
  • Taskbar previews may draw partially offscreen.

Settings:

  • When launching the Settings app, a brief green flash may appear.
  • When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
  • The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
  • Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
  • Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
  • Choose Reset this PC to perform a reset.
  • Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

  • exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
  • When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
  • Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

  • After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
  • When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
  • The search panel might appear black and not display any content below the search box.

Widgets:

  • Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
  • Launching links from the widgets board may not invoke apps to the foreground.
  • Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

  • The install button might not be functional yet in some limited scenarios.
  • Rating and reviews are not available for some apps.

Windows Security:

  • Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
  • “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

  • There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.
That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.
Read More
Fix Windows Update Install Error 0x80070005
If you are checking for an update on your Windows 10 PC and you got the error 0x80070005 due to some ACCESS DENIED permissions issue, then read on as this post will show you what you can do to fix the problem. For some reason, the Windows Update does not have enough rights or permissions to continue further which is why you’re getting an error instead. Thus, the first thing you can do before you troubleshoot further is to make sure that you’re logged in as admin. However, if you’re already logged in as one, then here are some suggestions that might help you fix the Windows Update Install Error 0x80070005.

Option 1 – Restart your computer and try installing the Updates again

You can restart your computer and then try installing the updates once again. There are instances when a simple restart resolves Windows Update errors. Thus, after you restart your computer, check for updates once again and see if you’re still getting the error or not.

Option 2 – Delete the contents in the Software Distribution folder and Catroot2 folder

  • Open the WinX Menu.
  • From there, open Command Prompt as admin.
  • Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauserv net start cryptSvc net start bits net start msiserver
  • After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
  • Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:
  • Type each one of the following commands.
net start wuauserv net start cryptSvc net start bits net start msiserver
  • After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error 0x80070005. 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.

Option 4 – Take control of the User App Data

There are times when permission to access the files is not configured correctly. As a result, it blocks the downloading of the updates. Thus, you have to take full control of the User App Data which is placed at C:/Users/USERNAME/AppData.
  • First, go to C:/Users/USERNAME/AppData and right-click on it then select Properties.
  • Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
  • After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
  • Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
  • Now edit the permission to Full Control for “Everyone”.
  • Click OK to save the changes made and then exit.

Option 5 – Try to update Windows after a couple of minutes or an hour

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it a couple of minutes or an hour or so before trying to run Windows Update again.
Read More
A Quick Guide to Fixing the Flash.ocx Error on Your PC

Flash.ocx Error - What is it?

To understand this error, first, it is important to understand what Flash.ocx actually is. Flash.ocx is basically a flash plug-in or ActiveX file that is responsible for the adobe flash player to work on the system. The Flash.ocx error triggers due to issues in the Adobe flash player.

Solution

Restoro box imageError Causes

The error Flash.ocx may occur due to many reasons. These include:
  • Flash player corruption
  • Corrupted and broken Active X components
To this error code is not fatal but nonetheless it is still advisable to fix it right away to avoid inconvenience when using Flash player. The inability to run the Flash Player smoothly will hinder you from watching videos on your PC and playing exciting web-based games.

Further Information and Manual Repair

To resolve this error on your system, you don’t have to hire a professional and spend hundreds of dollars. This error code is quite easy to fix. You don’t need to be technically sound to resolve this error code. Simply follow the methods give below to fix the Flash.ocx error code in a few minutes.

Method 1: Reinstall the Flash Player

If the error occurs due to the corruption of the Flash Player, then it is advisable to reinstall the player on your PC. However, before you do that first remove the previous versions of Adobe Flash Player on your system. If the previous corrupted version is not removed properly, then you will be unable to re-install it properly on your PC again. Go to the Add/Remove Programs and find the Flash Player and uninstall it. Make sure the files are also removed from the registry. Once you have successfully uninstalled the corrupted version, now go to the official website of Adobe Flash Player and download the utility from the website. Install it and run it on your system. If it works, then this means the error is resolved. However, if the error still persists, then try method 2.

Method 2: Download Restoro to Fix Active X components

Another reason for Flash.ocx error code can be broken or corrupted Active X components. If this is the issue, then the best way to resolve it is to download Restoro. This is a multi Reimagefunctional and advanced PC Fixer deployed with multiple high-performance scanners including Active X and Class scanner. The Active X and Class scanner perform an entire PC scans for corrupt and broken Active X entries along with missing software paths and invalid combinations. After the scanning process is complete, it repairs and restores the components back to normal. Thereby resolving the Flash.ocx error right away and ensuring smooth video browsing over the web. Restoro is an efficient and a safe program. It has a user-friendly interface and easy navigations. It can be used by all level of users. Besides the Active X scanner, it includes 5 more value-added utilities like a registry scanner and an antivirus to name a few. It is compatible with all Windows versions Click here to download Restoro on your PC and resolve Flash.ocx error code now!
Read More
Enable or Disable Windows 10 Boot Log
Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type in “msconfig” and click OK to open System Configuration.
  • After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
  • Then click on OK to save the changes made.
  • Next, click on the Restart button in the prompt window to get started with the Boot Log process.
  • After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.
Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type in “msconfig” and click OK to open System Configuration.
  • After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
  • Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:
  • Go to the Start Menu and then type in “command prompt” in the search bar.
  • After that, right-click on the Command Prompt option and select the “Run as administrator” option.
  • After opening Command Prompt, type in “bcdedit” and tap Enter.
Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.
  • To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
  • Next, type in the following command with the operating system identifier to enable the boot log.
bcdedit /set {identifier} bootlog Yes
Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.
bcdedit /set {current} bootlog Yes
  • Afterward, restart the system to start the Boot log process.
  • After the restart, go to C:Windowsntbtlog.txt to open the boot log.
Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:
  • Go to the Start Menu and then type in “command prompt” in the search bar.
  • After that, right-click on the Command Prompt option and select the “Run as administrator” option.
  • Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.
bcdedit/ set {identifier} bootlog No
Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.
bcdedit /set {current} bootlog No
  • Now close the Command Prompt.
Read More
Couldn’t open PDF in Edge Error in Windows
As you know, Microsoft Edge is the default web browser in Windows 10 operating system. It is a built-in browser that replaced the ancient Internet Explorer for its performance and features. Aside from being the default web browser, it is also set as a default PDF viewer in Windows 10. So if you open a PDF file, it will be automatically opened in the Edge browser even if you have installed a PDF reader on your computer. However, some users recently reported getting an error that says, “Couldn’t open PDF in Edge, Something’s keeping this PDF from the opening” when they tried to open a PDF file or view an internet link that has a downloadable PDF file in the Edge browser. If you are one of these users, read on as this post will help you troubleshoot the problem and fix it. This kind of error mostly occurs if you have installed other PDF viewers on your computer. They could be interrupting Edge while it tries to open the PDF documents. To fix it, check if Microsoft Edge is set as the default PDF viewer or you could also try to clear its browsing cache. In addition, you could also reset or repair Edge. For detailed instructions, refer to the given options below.

Option 1 – Check if Microsoft Edge is set as the default PDF viewer

The first thing you can do is to check if Edge is set as the default PDF viewer. If it’s not, you have to set it as one to fix the problem.
  • Open Control Panel and go to Default Programs.
  • Then click on the “Associate a file type or protocol with a program” option.
  • Next, select the PDF file option and click on Change program.
  • After that, select Microsoft Edge in the pop-up window and then select the “Always use this app to open .pdf” option.
  • Now click the OK button to set Edge as the default PDF viewer and then check if you can now open the PDF file in the Edge browser.

Option 2 – Clear the browser cache of Microsoft Edge

  • Open Microsoft Edge.
  • Then click on the three horizontal dots to open the menu.
  • From there, click on Settings. And under Settings, click the “Choose what to clear” button under the Clear browsing data section.
  • Next, check all the checkboxes and then click the Clear button to clear the browsing data in the Edge browser.
  • Restart Edge.

Option 3 – Reset, repair or reinstall Microsoft Edge via Settings

You can reset, repair or reinstall the Edge browser through Settings. If none of it helped, you can try the following:
  • Open File Explorer and then go to this path – C:/Users/YourUsername/AppData/Local/Packages
Note: Before you type in the path in the Address bar, make sure that you put your user account name in place with the “YourUsername”.
  • Tap Enter to proceed.
  • Next, look for the folder named “MicrosoftEdge_8wekyb3d8bbwe” then right-click on it.
  • Click on Properties and uncheck the option “Read-only” under the General tab in the Properties window.
  • Click on Apply and then OK to save the changes made.
  • After that, look for the MicrosoftEdge_8wekyb3d8bbwe folder again and delete it. And if a prompt stating “Folder Access Denied” appears on your screen, just click on the Continue button to proceed – doing so will delete most of the content inside the folder except for the folder named “AC”.
  • Restart your PC.
  • Now all you have to do is to re-register Microsoft Edge using PowerShell. In the Start Menu, search “Windows PowerShell”.
  • Right-click on Windows PowerShell from the search results and select the “Run as administrator” option.
  • Type in this command in the PowerShell windows and tap Enter – Cd C:/Users/YourUsername
Note: Once again, make sure that you key in your user account name in place of “YourUsername.
  • After that, type in this command and tap Enter – Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml" -Verbose}
  • Restart your PC.
Read More
Fix SPECIAL POOL DETECTED MEMORY CORRUPTION
If you suddenly encounter the SPECIAL POOL DETECTED MEMORY CORRUPTION Blue Screen error with a bug check value of “0x000000C1” while you are using your computer then it might be due to some problem with the hardware of your Windows 10 computer. According to security experts, it is most likely caused by the physical RAM which could be due to some error in the Realtek driver for Wireless USB 2.0 as well as corruption of the files inside the RAM, and so on. This kind of problem indicates that the driver wrote to an invalid section of the special pool. On the other hand, system files like the rtwlanu.sys or nvlddmkm.sys can also trigger the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error. To resolve this Blue Screen error, you can use the options provided below as reference but before you do that, make sure to create a System Restore point first. After you have that covered, proceed to the given options below.

Option 1 – Delete the settings of the Driver Verifier Manager

  • Open the Driver Verifier Manager using the Start search.
  • After that, select or click on the “Delete existing settings” option and then click on Finish.
  • Reboot your computer and see if it fixes the Blue Screen error or not.

Option 2 – Try to update or rollback your Network driver

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 “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.
  • From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
  • Restart your PC and see if it helped in fixing the BSOD error.
Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.
  • Realtek High-Definition (HD) Audio Driver
  • Realtek Card Reader Driver
  • Realtek Local Area Network (LAN) Driver
On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.
  • Open the Device Manager again and then look for Network Drivers.
  • Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then 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 the Realtek driver.
  • Now restart your computer to successfully apply the changes made.

Option 3 – Try running the ChkDsk utility

You can also run the ChkDsk utility to fix the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error.
  • First, open This PC and right-click on your operating system partition for Windows.
  • Next, click on Properties and navigate to the Tools tab.
  • Then click on Check under the Error Checking section.
  • After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

Option 4 – Use the Windows Memory Diagnostics

Since the problem has something to do with the physical RAM, you need to use Windows Memory Diagnostics. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 5 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. It can be found in 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.
Read More
All wallpapers of Windows 11
We have gathered and want to share with you all of the Windows 11 wallpapers if you would like to place them on your desktop now and now wait for the official W11 release. Hope that you will like some of them and I hope to see you again on errortools.com Download Windows 11 Wallpapers here!

And here is the preview of them

W11_32W11_31W11_30W11_29W11_28W11_27W11_26W11_25W11_24W11_23W11_22W11_21W11_20W11_19W11_18W11_17W11_16W11_15W11_14W11_13W11_12W11_11W11_10W11_09W11_08W11_07W11_06W11_05W11_04W11_03W11_02W11_01
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status