Should you upgrade to Windows 11

If you aren’t able to pull up any website and instead got the ERR QUIC PROTOCOL ERROR error message in Google Chrome then read on as this post will help you resolve the problem. When you encounter such an error in Chrome, you will see the following error message:

“This site can’t be reached, The webpage at [website URL] might be temporarily down or it may have moved permanently to a new web address, ERR_QUIC_PROTOCOL_ERROR”

This kind of error message pops up when the URL is down. However, if you are certain that the site is not down and you’re still seeing this error message, then troubleshoot further using the suggestions given below.

Option 1 – Try to disable the QUIC Protocol

QUIC is an experimental transport layer network protocol that is present in Google Chrome in order to establish a connection between two endpoints over UDP. So if there is any problem on the development side, you will most likely encounter ERR_QUIC_PROTOCOL_ERROR on your Google Chrome browser when you try to open any website. Thus, you have to disable the QUIC protocol in order to resolve the error. How? Simply follow the steps below.

• Open your Google Chrome browser.
• Now type in “chrome://flags/” in the address bar and hit Enter.
• After that, look for the Experimental QUIC protocol which should be set by default.
• Then expand the drop-down menu and select Disable.
• Restart Google Chrome and see if the error is fixed or not.

Option 2 – Disable VPN

As mentioned, if you are using VPN, this could be the reason why you’re getting the Windows Update error 0x800F0922 so the most obvious thing to do is for you to turn off the VPN and try to run the Windows Update once more. And if you use a VPN software that works using their software, you can just completely exit or log-off from its account. On the other hand, if you are using a built-in Windows 10 VPN, you can simply turn it off or delete all the settings you have created there. Although it’s understandable that you might have to use a VPN connection to connect to the work network, you really have to disable it at least until the Windows Update is no longer stuck in the error 0x800F0922. It would be best if you do this when you are not working.

Option 3 – Disable the Proxy server

You can also try to disable the Proxy server to fix the ERR_QUIC_PROTOCOL_ERROR in Chrome. Refer to these steps to do so:

• 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.

If you notice that your tabs in your Firefox browser keep on crashing recently, then there might be something wrong with your browser. Every time any of your tabs crashes, you might encounter an error message saying, “Gah, Your tab just crashed”. If you encounter this kind of error message then it is most likely that your Firefox Profile is having some issues with the existing installation of Firefox. The “Gah, Your tab just crashed” error rarely happens but when it does, it can get quite annoying as you won’t get to browse the internet peacefully. So to fix it, here are some suggestions you could check out.

Option 1 – Try disabling multi-process tabs in Firefox

Since Mozilla has one process for Firefox itself, while one process handles all the tabs, you have the option to disable these multi-process tabs in Firefox. To do that, follow these steps:

• In the address bar of Firefox, type “about: config” and hit Enter.
• Next, look for the following configurations and set them to false.
  • tabs.remote.autostart = false
  • tabs.remote.autostart.2 = false
• After that, double-click on the toggle switch between true and false.

Option 2 – Try checking your Add-ons

In this option, you need to start Firefox in Safe Mode and then check if the problem is fixed. If it is, you may have to check your Firefox add-ons as well as extensions as one of them might be the one that's causing the “Gah, Your tab just crashed” error.

Option 3 – Downgrade the Firefox version you’re using

It could be that the current version of Firefox you’re using has some issues so you might have to downgrade it, especially if you are already using the latest version. To downgrade your Firefox browser, go to the directory of the other versions and languages and select an older version that worked for you. After that, you have to disable automatic Firefox updates.

• First, click the menu button and select Preferences.
• Next, go to the Firefox Updates section under the General panel.
• Then select the radio button labeled “Check for updates but let you choose to install them”. This will ensure that you will not have the same issue with the new update.

Note that this is only a temporary fix since updating your programs, including browsers.

Option 4 – Try sending Crash Reports

You might want to send crash reports to Mozilla. This way, Mozilla might come up with some fix to resolve the problem. All you have to do is type “about: crashes” in the address bar. This will list all the crash reports. Now send it to Mozilla using the built-in interface. Although this won’t instantly fix the problem, a lot of user finds it useful. And besides, the issue will get fixed in future releases or with minor updates.

A lot of programs in Windows utilize the helper processes to ensure that they can get the job done as early as possible. And one of the programs that use these processes is Microsoft Edge. This built-in browser uses a process called the Edge Content process. The moment you start your computer, these system processes are loaded which makes the Edge browser load faster. To be specific, these are the three processes that are related to Microsoft Edge:

• MicrosoftEdge.exe
• MicrosoftEdgeCP.exe
• MicrosoftEdgeSH.exe

The process that ends with the “CP.exe” is the content process in Edge. However, when this process stopped working, this can affect the Edge browser. In such cases, when you check the Reliability Monitor, you will see that the state of the “Microsoft Edge Content Process” is “Stopped working” which keeps on appearing. To resolve this issue, you can try to clear the browsing data of Microsoft Edge or repair or reset it. You can also try re-registering Edge via Windows PowerShell as well as check your security programs that might be causing interference with the process.

Option 1 – Clear the browsing data 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 2 – Try to reset, repair or reinstall 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 computer

Option 3 – Re-register Edge via Windows 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
• 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.

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml” -Verbose}

Option 4 – Try to check your security program

It is possible that a security program installed in your computer is the one that’s causing the problem which is why you have to check it. According to security experts, there are some security programs that could be detecting the Edge’s content process as suspicious, blocking or terminating it as a result. Thus, you need to modify your security program’s settings to fix the problem.

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

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

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

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

Option 2 – Try modifying some entries in the Windows Registry

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

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

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes 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.

If you continuously encountered the “VirtualBox FATAL: No bootable medium found, System halted” error when you try to install Windows 10 in VirtualBox, read on as this post will give you some potential fixes to resolve the problem – you will be guided on how to choose the ISO image to fix this error in VirtualBox. This kind of error is a very common one especially if you have a corrupted ISO file or if you have not selected an ISO file for your virtual machine. Like pointed out, this error pops up when you have a corrupted ISO file or if the ISO file is not attached to the virtual machine. You have to select the ISO file while you create the virtual hard disk, else, you will most likely face this problem, and to fix it, you need to download fresh Windows ISO, create a new IDE Controller, assign Windows ISO to the IDE Controller and then boot your virtual machine. For detailed steps, follow the instructions below but before you start, make sure that you have a valid and uncorrupted Windows ISO. Step 1: First, you need to open the VirtualBox program on your computer and select the virtual machine. Step 2: Next, click on the Settings button or you can also right-click on the virtual machine and select Settings from the context menu. Step 3: Once you’re in the Settings panel, go to the Storage section and from there, create a Controller: IDE. Step 4: To create a Controller: IDE, click the Add new storage controller icon and select the “Add IDE Controller” option. Step 5: After that, click the Add optical drive icon and click on the Choose disk button. You will then see all the attached and non-attached ISO files. However, you have to add the new ISO file that you just downloaded. Step 6: To add the new ISO file, click the Add button and select the ISO file and then select the .iso file from the Non Attached section. Step 7: Now click the Choose button and afterward, make a checkmark in the Live CD/DVD checkbox and then select the IDE Primary Master from the drop-down menu of the Optical Drive. Step 8: Once you’re done, save the changes made and try booting into your virtual machine again.

There is one service in the Windows operating system that is responsible for managing all the print jobs as well as handles the interaction with the printer. This service is known as the Print Spooler service. However, if it stops running, then you won’t be able to print anything on your computer. In such a case, you can try to restart the Print Spooler service, and to do that, you have to open the Windows Services Manager and look for the Print Spooler Service. Once you found it, right-click on it and select Restart. If it isn’t running, select Start and if the Service starts working again, then good but if not and you got an error message instead that says, “Windows could not start the Print Spooler service on Local Computer, Error 1068, The dependency service or group failed to start”, then read on as this post will give you a couple of suggestions you can try to resolve the issue. The reason why you could not start the service is most likely because the Print Spooler service is dependent on other services which might not be properly running. If the following services are not running then it’s no wonder why you’re getting the error.

• HTTP Service
• Remote Procedure Control (RPC) Service

You might not see the RPC service which means that the Print Spooler Service does not recognize its dependency on the RPC service. In such a case, you have to manually configure the dependency by following the options given below.

Option 1 – Try configuring the dependency via CMD

The first thing you have to do is to configure the dependency using CMD. Refer to the steps below to do so:

• Open an elevated Command Prompt.
• Then type in “sc config spooler depend= RPCSS” and hit Enter.
• After the command has been executed, restart your computer and then check if it fixed the problem. If not, proceed to the next given option below.

Option 2 – Fix dependency via the Registry Editor

You can also resolve dependency using the Registry Editor. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSpooler
• Next, right-click on the “DependOnService” entry located on the right pane and select Modify.
• Now change its value data to “RPCSS” and click OK to save the changes made and then exit the Registry Editor.
• Reboot your computer and see if the issue is resolved.

Option 3 – Try running the Printer Troubleshooter

Another option you can check out is the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

As you know, both the Windows Update and Windows Store are inter-dependable services in Windows 10 operating system. So when one of these services encounters an error like the “0x80070424, ERROR_SERVICE_DOES_NOT_EXIST”, the other service will most likely get this error as well. Note that this kind of error can occur to both the Windows Update Standalone Installer and to the Windows Update section in the Windows 10 Settings app. Some users also reported getting this error while trying to update Windows Defender as well. You can see the following error message in the Windows Update Standalone Installer:

“Installer encountered an error: 0x80070424, The specified service does not exist as an installed service.”

While you’ll see the following error message in the Windows Store:

“The 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: (0x80070424).”

To fix this error, you can try to re-register the Background Intelligent Transfer Service DLL file or run the Windows Update and Store apps troubleshooters. You can also reset the Windows Update-related folders or the Microsoft Store or fix the Windows Update files by using the DISM tool. On the other hand, you can also use the Registry Editor or check Windows Services. For more details regarding these potential fixes, refer to each one of the given options below.

Option 1 – Try to re-register the Background Intelligent Transfer Service DLL file

You may have to re-register the Background Intelligent Transfer Service DLL file using the regsvr32.exe before you can successfully install the program and fix ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and un-register OLE controls as DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • regsvr32 Qmgr.dll /s
  • regsvr32 Qmgrprxy.dll /s

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully.
• Now restart your computer and check if the error is now fixed.

Option 2 – Try to run the Windows Store or the Windows Update Troubleshooters

The Windows 10 Store Apps Troubleshooter will help you in fixing the Error code 0x80070424. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• On your right hand side, scroll down to find the Windows Store Apps and then click on Run the troubleshooter option and see if it fixes the problem.

Note: You can also try running the Windows Update troubleshooter to fix the error. You can run it under the Windows Update section of Update & Security.

Option 3 – Delete the files from Software Distribution Folder & Catroot2 folders

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to these steps.

• 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, got to the C:WindowsSoftwareDistribution folder and get rid of all the folders and files there by 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 4 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterwards, try opening Microsoft Store again and then see if Error Code 0x80070424 is resolved or not.

Option 5 – Try to check the Windows Update or WU setting in the Registry

• Tap the Win + R keys to open the Run utility and type “regedit” in the field and tap Enter to open the Registry Editor.
• Next, go to this registry path: ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdate
• Here, look for the DWORD named “DisableWindowsUpdateAccess” and double click on it and then set its value data to “0”.
• Exit the Registry Editor once you’re done and restart your computer.

Option 6 – Try to check the status of some Windows Update Services

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter or click OK to open Services.
• From the list of Services, look for the following services and make sure that their Startup type is as follows:
  • Windows Update Service – Manual (Triggered)
  • Background Intelligent Transfer Service – Manual
  • Workstation Service – Automatic
• After that, check if the Service status of the listed services above are set to Running. If they’re not, click on the Start button to start these services and then check if you can now enable the Windows Update service or not.

Option 7 – Run the DISM tool

You can also run the Deployment Imaging and Servicing Management or DISM tool to fix the error code 0x80070424. 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.
• Once it’s done, reboot your computer and check if it has fixed the error.

Among other things and innovations, Windows 11 brings to the table is the game mode. The game mode is a system designed to release some resources and optimize your system when Windows 11 detects that you are playing games. It also turns off automatic updates while the game is active. The game mode is active at all times and usually, everything works great but in some instances, it can sadly cause some performance issues. If you are one of these unlucky people where game mode is not working as supposed to do, don’t panic, we have a quick guide for you on how to turn it off.

1. Press ⊞ WINDOWS + I to open settings
2. Inside click on Gaming
3. Select Game mode
4. Click switch beside Game mode to turn it off
5. Close settings

Everything will be automatically saved and applied and you should not have any issues from now on. If for any reason you wish to turn game mode back ON, just follow the same steps and turn the switch to ON.

Error Code 0x8024001b- What is it?

At its most basic level, Error Code 0x8024001b is an error that can cause problems with the installation and updates of software and operating system updates. The most common version of this error appears in Windows 10, but a similar error with a matching code number has been present in previous versions of the operating system, back through Windows 7.

Common symptoms include:

• Programs freezing or locking up during use
• The appearance of an error message regarding installation difficulties
• Computer shutting down or freezing during operation
• Difficulty in running multiple programs at the same time

Solution

Error Causes

There are two main causes for Error Code 0x8024001b, both of which are fairly simple:  Updates needed for the Windows Update tool itself and software that causes Windows Update to fail during installations through conflicts in system files. While these may seem like technical issues, these problems are actually easily resolved with a few simple steps. The average user can use the methods listed below to fix the problems on their own.

Further Information and Manual Repair

For users who want to address Error Code 0x8024001b for themselves, the steps below can be followed to address the two primary causes for the error. If you have difficulty in completing these steps or are not confident in your computing skills and ability to follow the listed steps, contact a Windows repair technician.

Here are the top methods to resolve Error Code 0x8024001b on your own:

Method One:  Check for Updates to Windows Update

In some cases, the Windows Update tool may need an update for itself. When you attempt to run updates or install wizards for other software, it can cause conflicts with the Windows Update process, slowing down your computer or causing it to freeze.

If you are attempting to run multiple installations or updates at the same time, it may also cause Error Code 0x8024001b to arise on your computer.

To resolve this issue, close out all programs, with the exception of the Windows Update tool. Within the tool, select “Check for Updates” and install any updates that are needed. When finished, you should restart your computer to ensure that all updates have been fully applied before attempting any other installations or updates.

Method Two:  Uninstall Conflicting Software

Another problem that can cause Error Code 0x8024001b is the presence of conflicting software. If Error Code 0x8024001b has only recently appeared on your computer, consider removing any software that has been added to your computer, running the Windows Update process, and restarting your computer before attempting to reinstall the problem software.

With any method that you use, it is important to remember to keep your Windows Updates current at all times. This is the best way to avoid the appearance of Error Code 0x8024001b and similar errors in the future, as stacked up updates are more likely to cause issues and conflicts with your other installed software and operating system.

While there are some tools out there that claim to be able to fix Error Code 0x8024001b for you, it is important to always thoroughly investigate the publisher and distributor of such software, as some of the tools available on the Internet will actually introduce malware and adware on your computer in the name of “protecting” your computer or resolving an error.

If you have tried to use both methods above and have not fully resolved Error Code 0x8024001b, get in touch with someone who is a qualified computer repair professional and is familiar with your particular version of the Windows operating system to assist you in finalizing your resolution.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.