Setting up USB tethering in Windows

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.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

The third time is charm saying goes but not when we are talking about Microsoft. Print spooler is again in focus, in a bad way. This is the third print spooler vulnerability to emerge in just five weeks. While a critical flaw was originally identified and patched in June, a similar flaw came to light shortly after and was subsequently patched (with mixed success). Microsoft is once again advising its customers to disable Windows print spooler after a new vulnerability that allows hackers to execute malicious code on machines has emerged. While a patch fixing the flaw will be released in due course, the most effective workaround currently on the table is to stop and disable the print spooler service entirely.

"An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."

Stop this service right away or you are risking a potential attack.

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on Power Shell (admin)
3. In Power Shell type in the following command to check if spool service is running: Get-Service -Name Spooler followed by ENTER
4. If spooler service is running type in the next command to stop it: Stop-Service -Name Spooler –Force and press ENTER
5. Then follow with this command to disable it at startup: Set-Service -Name Spooler -StartupType Disabled followed with ENTER

That’s it, we hope a patch will come soon for all the people that are using network printing and indeed need this service running in order to do work.

If you are typing inside the Search bar, Cortana, Taskbar, Windows 10 apps, etc., and then everything seems invisible then read on as this post will guide you in fixing this issue. At first, you might think that something is wrong with your keyboard but it really has nothing to do with it. The problem actually lies with the apps from Microsoft Store. Thus, if you can’t type anything in any of the apps from Microsoft Store in Windows 10, refer to the options given below to fix them.

Option 1 – Ensure that ctfmon.exe is running

Ctfmon.exe is a Microsoft process in Windows 10 that controls the Alternative User Input as well as the Office Language bar. In other words, it enables end-users to control the computer using on-screen keyboard inputs, speech, and even pen for various languages. It would be better if you launch the program once by going to the C:/Windows/system32 folder. Doing so will ensure that whatever API is needed for the keyboard typing to work properly again. You also have to make sure that its startup status is not disabled. In addition, you can also try the following steps, alternatively.

• Open the Task Scheduler.
• Then go to Microsoft > Windows > TextServicesFramework.
• And on the MsCtfMonitor, right-click and enable the task.
• Now restart your computer.

This will ensure that all the text boxes will start to work again. And if the task MsCtfMonitor is missing from the list of tasks, you can import it with the XML file from basics.net. Then download and create a task to run it each time you log in to your PC.

Option 2 – Use the Windows Store Apps Troubleshooter

You might also try running the Windows Store Apps Troubleshooter as it can help in resolving issues with the Windows Store apps. This built-in tool can resolve most of the app-related problems. To use it, go to Settings > Update & Security > Troubleshooting > Windows Store Apps and from there, click the start the troubleshooter button. The Windows Store Apps Troubleshooter will scan the computer for any issues with the Windows store apps and will automatically fix them if it finds any.

Option 3 – Re-register all the Windows 10 UWP apps using PowerShell

• First, make sure to close all the running applications on your computer.
• Next, in the Start search, type in PowerShell and right click on the result, and select the “Run as administrator” option.
• After that, type the following commands to re-register the Windows 10 apps. Make sure to hit Enter on each line:
  • reg delete "HKCUSoftwareMicrosoftWindows NTCurrentVersionTileDataModelMigrationTileStore" /va /f
  • get-appxpackage -packageType bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmetadataappxbundlemanifest.xml")}
  • $bundlefamilies = (get-appxpackage -packagetype Bundle).packagefamilyname
  • get-appxpackage -packagetype main |? {-not ($bundlefamilies -contains $_.packagefamilyname)} |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmanifest.xml")}

Option 4 – Try to run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the problem.

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

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

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

• Restart your PC.

There are cases when your Windows 10 PC can encounter an issue where it gets stuck and will display a message that says, “Preparing Security Options”. If this is happening to your Windows 10 PC, you won’t be able to use your keyboard or even mouse and your screen will only be stuck on the screen as mentioned above. As your computer is still stuck, you will be left with no choice but to shut it down and restart it. Tap the F11 key as soon as your PC powers on. This will take you to the Advanced Startup options where you can carry out some steps. If it still didn’t work, you have to boot your Windows 10 PC into Safe Mode and then try out the troubleshooting options below.

Option 1 – Try using System Restore

You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

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

Option 2 – Uninstall the Windows Updates you’ve installed recently

The issue could be caused by Windows Updates so you need to check if it’s indeed the case. The best way you can do so is via Safe Mode.

• Boot your PC into Safe Mode and then tap the Win + I keys to open Settings.
• After that, click on Update and Security and then select Windows Update from the left side menu column.
• Next, select the “View installed update history” option on the right-side column and click on Uninstall Updates which will open a window that will show the list of all the installed updates on your PC.
• From there, select the update you want to uninstall and click the Uninstall button located in the lower right corner of the window.

Option 3 – Try disabling the Fast Startup

• Boot your PC into Safe Mode.
• Then tap the Win + R keys to open the Run dialog box.
• Next, type in “control” to open Control Panel.
• After that, select Hardware and Sound and click on Power Options.
• Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
• Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
• Now restart your PC and check if the problem’s fixed.

Option 4 – Try running both the SFC scan and CHKDSK utility

You can do both SFC and CHKDSK using Safe Mode and Advanced Startup options. For Advanced Startup options, click on the Command Prompt option and proceed with the steps. And if you have booted your computer into Safe Mode, follow these steps:

• Tap the Win + X keys or right-click on the Start button and click Command Prompt (admin).
• After that, type in this command and tap Enter to run the System File Checker or SFC – “Sfc /scannow”.
• Alternatively, you can use this command instead if the previous command didn’t work – “sfc /scannow /offbootdir=c: /offwindir=c:windows”.
• Wait until the SFC scan is done with the process and then restart your PC.
• Next, run the CHKDSK utility and once it’s done checking your disk for errors and then reboot your PC to save the changes made.

Option 5 – Try resetting Windows 10

You can reset your Windows 10 PC using either the Advanced Startup Options or by booting into Safe Mode.

• Tap the Win + I keys and go to Update and Security > Recovery.
• Then click on Get Started under the Reset this PC section.
• After that, follow the on-screen instructions with how you want to reset your PC and what files and settings you want to revert.
• Then it will reset your PC by reinstalling it

Option 6 – Try to rename the SoftwareDistribution folder

In this option, the Command Prompt is supposed to be like the one in option 4. You can use both ways there to open the Command Prompt.

• Open an elevated Command Prompt as admin and type in the commands below and tap Enter right after you typed in each one of them
• net stop wuauserv
• net stop bits
• rename c:windowsSoftwareDistribution SoftwareDistribution.bak
• net start wuauserv
• net start bits

Note: You can also rename the SoftwareDistribution folder to “SoftwareDistribution.bak” or “SoftwareDistribution.old” after you boot your PC into Safe Mode.

Option 7 – Try rebuilding BCD

Rebuilding the BCD can help you in fixing the stuck Windows 10.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
• exe /FixMbr
• exe /FixBoot
  • exe /RebuildBcd

Error 1321 - What is it?

Error 1321 is a Windows PC error. This occurs when you try to install a Microsoft Office suite or program on your PC. The set-up program stops responding and the error message is displayed on the computer screen in the following format:

‘Error 1321. Setup cannot modify the file file_name. Verify that the file exists in your system and that you have sufficient permissions to update it.’

When this error occurs you cannot roll back the installation of the Office Suite or use the Add/Remove program option to remove the installed program.

Solution

Error Causes

Common causes of the occurrence of error 1321 are:

• Encrypt contents to secure data settings are enabled on the folder in which you are trying to install the Office suite/ program.
• PC infected by viruses
• Bad Registry Entries

Further Information and Manual Repair

The good news is that this error code is not fatal and besides it is also easy to resolve. Here are some easy do it yourself methods for you to repair this error on your system in a few minutes:

Method 1: Disable Encrypt Contents to Secure Data

To resolve this error code, make sure the encrypted contents to secure data settings are not enabled. To do so, simply right-click the folder in which you want to install the MS Office Suite or program. Now click properties and then the General tab. Now go to the Advanced option. In the Advanced Attributes dialog box, make sure that the Encrypt contents to secure data check box under Compress or Encrypt Attributes is disabled. If it is not then un-check to disable.

Method 2: Remove Viruses

Viral infection can also trigger error 1321. If this is the reason, then simply install and run a powerful antivirus on your system. An antivirus detects all types of malicious viruses such as malware, adware, spyware, and Trojans. Remove them to resolve the issue.

Method 3: Download Restoro.

If the issue is related to bad registry entries, then it is advisable to download Restoro on your PC. This is a user-friendly and powerful PC Fixer deployed with a registry cleaner. The registry cleaner scans your entire PC and wipes away all the bad entries cluttering and damaging the registry in seconds. Click here to download Restoro and resolve error code 1321 today.

As you know, one of the most popular browsers these days is the Google Chrome browser. Browsing the web every day using your Chrome browser, leaves a trail of browsing history. Google uses the browser history to streamline and make the browsing experience a lot better. But there are times when Chrome users experience trouble in deleting their web browsing history, data, cookies, and cache. In this post, you will be guided through specific settings that will help you in getting rid of the browsing history in Chrome. There are several options you can take in clearing the browsing history in Chrome. But before you try them, you can try the basic one first using the following steps:

• First, click on the three-dotted icon and click on History from the menu.
• Next, click on the Clear browsing data option and select “All time”.
• Then select the type of history you want to delete.
• After that, click on the Clear Data button.

If clearing the browsing history in Chrome the old way didn’t work, then you can try to check out the options provided below.

Option 1 – Clear the cache using the File Explorer

The first thing you can do is to clear the cache by using File Explorer. To get started, refer to these steps:

• Tap the Win + E keys to open File Explorer.
• Next, navigate to the following paths:
  • C:/Users/YOURUSERNAME/AppData/Local/GoogleChrome/User Data/DEFAULT/Cache
  • C:/Users/YOURUSERNAME/AppData/Local/GoogleChrome/User Data/PROFILENAMECache
• From the given locations above, replace “YOUR USERNAME” with the user profile name you use and then search for a file named “Cookies”.
• Now delete its contents.

Option 2 – Reset Chrome

Resetting Chrome can also help you fix the error. This means that you will be restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Option 3 – Try to clean reinstall Chrome

There are instances when programs leave files behind after you’ve uninstalled them and the same thing can happen to Chrome so before you reinstall Chrome, you have to make sure that you have deleted the User Data folder. To do so, refer to the following steps:

• Hit the Win + R keys to open the Run dialog box.
• Next, type “%LOCALAPPDATA%GoogleChromeUser Data” in the field and hit Enter to open the User Data folder.
• From there, rename the default folder and name it something else, e.g. “Default.old”.
• After that, install Google Chrome again and check if the issue is now fixed.

Code 0x80070070 – 0x50011 – What is it?

If you’ve recently tried installing Windows 10, you might have encountered error code 0x80070070 – 0x50011 or its alternatives (error code 0x80070070 – 0x50012 and 0x80070070 – 0x60000). Whatever formats this error code presents itself in, it's usually accompanied by a barrage of other errors, as underscored on Microsoft’s official site. If you’ve encountered this error code, it simply means that your computer system might not have the required or required space to install the upgrade.

Likely, if you’ve experienced error code 0x80070070 – 0x50011, it’ll likely appear in the formats highlighted below:

• 0x80070070 – 0x50011
• 0x80070070 – 0x50012
• 0x80070070 – 0x60000

Solution

Error Causes

At present, this Windows 10 upgrade error is triggered or caused by various factors:

• Lack of computer resources or space
• Virus/malware infestation
• A clogged registry

Further Information and Manual Repair

Whilst new, not much information has been propagated regarding this error. However, there are some manual / practical steps you can take to have your Windows 10 upgrade up and running. Since the primary aspect of solving this problem is to make space on your computer system, here are some ways in which you can do so manually.

Method 1: Get more space

• Check the current space on your computer  

Before making attempts to create space on your computer, it’s vital that you check to decipher how much free space you have available.

• Make use of Disk Clean-up 

Since there’s a free service available on your computer to create space, why not use it and save time? If the Disk Cleanup tool is employed regularly, this will free up hard drive space and optimize your computer to work better.

• Remove unwanted desktop apps 

There are several apps lying around on your computer that you simply don’t use, uninstall those and make space to elude error code 0x80070070 – 0x50011 or its alternatives (Code 0x80070070 – 0x50012, Code 0x80070070 – 0x60000)

• Remove or archive files  

If you have lots of photos, media, documents (files), videos, etc, that you don’t use or will only need in the future, try cloud storage. You’ll still have those files within your possession but just not in a physical location. However, they’re still accessible. Another suggestion: If you use programs such as One Drive or Google Drive for desktop, limit your use to only the online application.

• Add more storage

If you’re not able to implement the above steps to clear some space to accommodate your Windows 10 upgrade due to error code 0x80070070 – 0x50011, acquire more storage. This can be expanded by incorporating storage devices such as USB flash drives, CDs, cloud storage, and SD Cards.

Method 2: Scan your computer for virus/malware

If you regularly download stuff, especially software on the Internet from ‘not so secured’ sites, you might have picked up something. You might have downloaded malware or virus (along with other legit programs).

To resolve this issue, it’s advised and very important that you download a powerful antivirus and perform a complete scan of your computer system. After you’ve detected and removed the suspected malware/virus, you’ll then be able to eliminate error code 0x80070070 – 0x50011 and resume with your Windows 10 upgrade.

Method 3: Clean up your computer’s registry

If you do not clean your computer’s registry often, it could become congested or clogged by .XML files, junk files, and cookies. To resolve this problem, clean your registry by using a powerful and user-friendly tool to clean up the problem.

Click here to download Restoro.

DRIVER_IRQL_NOT_LESS_OR_EQUAL will cause your computer to go to the blue screen of death but do not worry there are solutions around this and we are here to instruct you on how to solve this.

1.  Uninstall and install network drivers

   DRIVER_IRQL_NOT_LESS_OR_EQUAL is most commonly tied to bad network drivers, whatever that be a corruption of the driver files or their incompatibility. So first thing is to check if this is the case. Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Device Manager. In the Device Manager expand Network adapters, choose adapter, right-click on it and choose Uninstall. Install latest driver or reboot so Windows will install the driver automatically

2. Update driver

   If you do not want to reinstall the driver or you are unable to for whatever reason updating the driver might do the trick. To update driver: Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Device Manager. In the Device Manager expand Network adapters, choose adapter, right-click on it and choose Update Driver.

3. Fix via Command prompt

   If both of the beforementioned solutions fail, try running the command prompt and fix the issue from there. Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Command Prompt (administrator) In command prompt type next line and press ENTERDEL /F /S /Q /A “C:\Windows\System32\drivers\mfewfpk.sys Reboot the system

4. Scan your PC for malware

   Sometimes corruption in the system is caused by malware, Scan your system for malware, viruses, etc.

5. Check connections or other hardware issues

   If all methods fail, open your PC case and check to see if connections everywhere are properly connected and tight. Clean your PC and turn it back ON

6. Use system restore

   If anything fails, use Windows system restore and bring back computer into a state where everything was working fine.

Copy & Paste is an essential part of Operating and working on a computer. We copy and paste a lot of different stuff through our workday, moving stuff from application to application. In an earlier article today we have explored troubleshooting and how to repair copy-paste stopped responses, this time we are going to focus on a little feature of Windows 10 called Clipboard history. Clipboard history is a built-in feature in Windows 10 which lets you store multiple copies of different types and then selectively pasting them into another application. Let's say you have multiple copies of different text from different websites and you then paste everything or just some into a Word processor. If this feature sounds interesting to you then let's turn it on. Press the start button and then on settings. In settings window click on System in system dialog click on the clipboard and on the right screen turn ON CLipboard history.