7 Ways to Fix Error 0x80070020 in Windows 10

Each time you execute a command on your computer, it takes into account a number of files and space for the code in the background for the command to be executed. Thus, executing the command is not that easy which is why you could encounter some errors along the way due to various limitations or poor allocation of memory, and so on. One of the errors you might encounter when executing a command on Windows 10 and Windows Server is the “Not enough storage is available to process this command”. There are several potential fixes you can check out to fix this error. To fix this error, you can try to delete the temporary files in your computer, run the DISM tool or apply some registry tweaks. For more details, refer to each one of the given options below.

Option 1 – Try to delete the temporary files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
• Next, find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
  • Windows Upgrade Log Files
  • System created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clean now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Option 2 – Run the DISM tool

You can also run the DISM Tool as it could also help in fixing the “Not enough storage is available to process this command” error in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” that could help in fixing error 0x80246019.

• You can run the DISM tool via Advanced Startup Options or you could boot your computer into a Clean Boot State and then select Command Prompt.
• 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, restart your computer and try again. If it didn’t work, you can try to use the “/StartComponentCleanup” parameter: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 3 – Try to use the Registry Editor

The memory range allocated for the tasks and commands to be executed is associated with the IRPStackSize DWORD. Thus, to fix the error, you need to extend the range by applying some registry tweak. Before you proceed, make sure that you create a System Restore point first. Once you’re done, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
• From there, look for the DWORD named “IRPStackSize” and right-click on it. If you can’t find this DWORD, just right-click on any empty space and select New > DWORD (32-bit) Value.
• Input “IRPStackSize” as the DWORD name and double click on it and set its Value data to be greater than its default value. Note that the maximum value allowed is “0xc” and the range starts from “0x1”.
• Now click on OK and exit the Registry Editor and then restart your computer and see if the error is fixed.

Kernel32.dll Error - What is it?

To understand Kernel32.dll error properly, here’s what you need to know first: in the Windows operating system, the system32 directory plays a vital role. Inside this directory, there is an element called Kernel32.dll. A DLL (dynamic link library) is a library that contains codes and data that are used by more than one program at the same time. The role of the Kernel32.dll file is to handle memory management and I/O (input and output) operations. Malfunctioning of this file results in a Kernel32.dll error message which leads to program or application failure.

Error Causes

Kernel32.dll files can be attributed to several reasons like:

• Missing or damaged Kernel32.dll files
• Registry corruption
• .Dll files misconfiguration if programs are installed or uninstalled.
• Viral infection or malware attack

It is advisable to repair the Kernel32.dll error immediately to avoid inconvenience and serious computer damages like program lockouts, system failure, freeze, and crash.

Further Information and Manual Repair

All causes for the Kernel32.dll error are linked with the registry. The registry is the major database of your system that stores all the activities you perform on your system. It saves both important data and unnecessary files in the RAM (Random Access Memory) including the junk files, temporary internet files, and obsolete files such as files of the deleted/uninstalled programs. These files accumulate a lot of memory space. It leads to disk fragmentation, data overload, missing and damaged DLL files, and eventually registry corruption. Other reasons for registry issues that trigger Kernel32.dll errors on your system could be malicious software like viruses, adware, and malware. These also corrupt the registry and damaged DLL files.

Kernel32.dll Error Solutions

There are two ways to resolve the Kernel32.dll error on your PC, one is to install two separate tools registry cleaner and an antivirus and run them individually to scan your system and repair it. This option is time-consuming and besides if antivirus software is notorious for slowing down systems. So by downloading a separate antivirus you may have to sacrifice your system’s speed.

Runtime Error 217 can be a big problem if you use your computer for business purposes and you have confidential data/documents stored on your system. This runtime error is quite dangerous. It can slow down your PC performance, lead to system failure and crash, make your system vulnerable to hacker’s attack, and also corrupt important files on your system.

Solution

Error Causes

There is no one particular cause behind the Runtime Error 217. This error can be attributed to several factors such as:

• Corrupt, missing, or faulty register DLLs of programs. This is usually the cause for Runtime Error 217 when installation is unsuccessful and the crucial system files fail to be registered within the registry.
• Exposure to Viruses like malware, adware, and spyware. Once a virus (es) gain access to your PC, you may experience Runtime Error 217. These malicious programs can damage your hard drive, boot sectors, memory banks, and registries.
• Outdated Msvcrt.dll (a Microsoft Visual C++ file) file called.
• Incorrect Regional settings

Further Information and Manual Repair

If you see Runtime Error 217 message pop up on your computer screen, you must fix and repair it right away before it becomes a big threat to you and your PC. Though Runtime Error 217 is alarming this does not mean that you need to panic. Keep calm and follow the recommended solutions to fix Runtime Error 217 given below.

• If the error occurs because you called the outdated Msvcrt.dll file, then you must update the file. This can be easily done by clicking the start menu, accessing the control panel, and then hitting the Windows update tab.
• When you experience Runtime Error 217 due to incorrect regional settings on your PC, then to resolve this issue simply go to the start menu and select Control Panel. Now in the control panel, you’ll find the option clock, click on it and go to the language and region settings. Choose your specific regional settings and save.
• If the cause of the Runtime Error 217 is incorrect registry entries and DLL files corruption, then to fix the error, you need to download a Runtime Error 217 fixer. After you download this repair tool, run it on your PC. It scans and detects corrupted files and repairs the error swiftly.
• Nonetheless, if the cause of this problem is a virus, then you need to install a powerful antivirus program. When you run it, the antivirus scans your PC for viruses. Once the scanning is complete the results are displayed on the screen. The results show exactly how many viruses you have on your PC. Once the scan is complete, delete all the files and click repair.

Regardless of whether you have experienced the Runtime Error 217 on your PC or not, it is advisable to install a powerful antivirus and run it every time you use your PC. By running it regularly, you can make sure that you are not exposed to viruses, malware, and spyware programs. Even if your PC gets infected by them, you can delete and remove them timely before the damage is done.

Error Fmod.dll - What is it?

This is a type of DLL error code. DLL is the abbreviation of Dynamic Link Library. DLL files contain small programs which are similar to executable files. One DLL file may be used to load and run several programs. Fmod.dll is created by Electronic Arts Inc. and associated with Crysis. This file is developed for the Windows OS. This error code occurs when you are unable to access, run and load programs supported by Crysis on your PC. Fmod.dll error code message is displayed in different formats such as:

• "Fmod_event.dll not found."
• "The file fmod_event.dll is missing."
• "This application failed to start because fmod_event.dll was not found. Re-installing the application may fix this problem."
• "Cannot start Crysis. A required component is missing: fmod_event.dll. Please install Crysis again."
• "Fmod_event.dll Access Violation."
• "Cannot register fmod_event.dll."
• "Cannot find C:\Windows\System32\fmod_event.dll."

Error Fmod.dll may pop up when you start-up or shut down the PC or even during the installation of a program.

Solution

Error Causes

Narrowing down to one cause for Fmod.dll error code is impossible virtually because this error may result due to different reasons on your system. Some of the common causes associated with this error code are:

• Viral Infection
• Hardware failure
• Missing, Corrupt, or Deleted Fmod.dll file
• Improper program installation
• Registry issues

No matter what the underlying cause of the reason may be, it is recommended to resolve the issue immediately to avoid serious PC threats.

Further Information and Manual Repair

To resolve this error on your system, try the methods discussed below:

Method 1 - Check the Recycle Bin

As mentioned above, Fmod.dll is a DLL file that is used to run and load a variety of programs on your system. There is a possibility that you uninstalled a program that was supported by the Fmod.dll file and accidentally deleted it. In such a scenario, the easiest way to resolve the Fmod.dll error code is to re-install the deleted file from the recycle bin. For this, go to the recycle bin and search for the file. If you find it reinstall if you can’t then simply download the Fmod.dll file from a reliable website.

Method 2 - Scan for Malware

Malware usually enters through phishing emails and downloads. These malicious programs then hide in your system disguising as either DLL or EXE files. The occurrence of fmod.dll file error may be due to malicious programs hiding in your system. Therefore scan your entire PC with a powerful anti-virus. An antivirus detects and removes all malicious software programs such as viruses, malware, Trojans, spyware, and adware. Try this, to resolve error code Fmod.dll and see the results.

Method 3 - Fix Hardware Problems

Fmod.dll file error may also pop on your screen due to hardware failure. If this is the reason, then we advise you to use the Device Manager an in-built tool in Windows 7 and 8 to fix hardware failures. For this go to the start menu then control panel. Now click on the ‘hardware and sound link’ and then click on the Device Manager. If you find any devices in red exclamation point, then this means this device is problematic. Uninstall the driver for that hardware device and then update the driver. Install the latest version to resolve. Remember, hardware problems are mostly related to outdated drivers.

Method 4 - Restore Points

Use System Restore, an in-built utility also known as the recovery tool, to restore points and ensure your PC is back to its previous working condition before the error code occurred. Simply put, it helps undo recent changes. You can find the System Restore tool in the System Tools folder.

Method 5 - Clean and Repair the Registry

The registry is that part of your PC that stores all the information, activities performed, and files including the junk files, invalid keys, bad entries, and cookies. When these files accumulate on your PC, they take up all the registry space and corrupt the important system and DLL files also stored in the registry, thereby generating such errors. Now you can clean the registry manually. But this process can be time-consuming and slightly technical, hence we advise you to download Restoro. This is a PC Fixer integrated with a registry cleaner. It is easy to use deployed with an intuitive interface. The registry cleaner scans the entire PC and removes all registry errors. It wipes out all the obsolete files and repairs the damaged DLL and system files. Click here to download Restoro.

Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap. The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP. Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted, "By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform." Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things. Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages: "DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures." Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface. Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally." Technicians on site don't know how to do that and senior network administrators aren't on site. It seems that it will all be down for a couple of more hours before the issue is resolved.

What is Error Code 29?

Code 29 is a Device Manager error commonly seen whenever a hardware device driver reports a problem. This error code indicates that the resources needed for operation are not available.

The computer hardware basically requires drivers to interface with the operating system. Drivers comprise multiple components and are supplemented with other resources provided by the BIOS (a physical chip on the motherboard).

The BIOS contains a set of basic input and output instructions for the computer system to boot, load drivers, and more.

Its firmware provides resources that drivers require to interface with other essential components. However, when the firmware fails to provide the requested resources, the device drivers stop functioning; this results in error codes like code 29.

Error code 29 is usually displayed in the following format:

“This device is disabled because the firmware of the device did not give it the required resources” Code 29

Solution

Error Causes

Error code 29 may be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• BIOS misconfiguration
• The device firmware is corrupt
• Previous attempt to update the driver failed

To avoid inconvenience and to ensure your computer keeps working at its optimal pace, it is recommended that you repair error code 29 on your PC immediately. Delay may limit you from using certain hardware attached to your system properly.

Further Information and Manual Repair

To repair error code 29, you don’t have to hire a professional and spend hundreds of dollars. Here are some quick and effective DIY methods that you can try to resolve this issue in minutes even if you don’t have any technical background.

Method 1 - Reboot Your PC

Sometimes, error codes like code 29 may pop up on your computer screen due to some temporary glitch with the hardware. Rebooting can resolve the issue easily.

Therefore, before you do anything, try restarting your PC. It could be all you need to repair code 29. However, if the error code continues to persist, try the other methods given below.

Method 2 - Clear the CMOS

This may sound technical but it isn’t. To begin, with CMOS is an acronym for Complimentary Metal Oxide Semiconductor.

It is a term that is used to describe motherboard memory that contains the BIOS settings. Clearing CMOS helps reset the BIOS settings to their default manufacturer levels. It’s easy to do and is an effective troubleshooting step to resolve error code 29.

To do this, simply:

1. Enter the BIOS setup utility  by restarting your PC
2. Watch for an entering setup message
3. Enter the BIOS access key. Usually, the key is F2 or F12. However, the key may differ from manufacturer to manufacturer. You may want to check the manufacturer’s website first to find out the BIOS access key before you restart your PC.
4. ‘Reset BIOS settings’ to their default factory levels.

Method 3 - Enable the Device in the BIOS

Error code 29 may appear if a device is disabled. In such a scenario, simply follow the same steps as discussed in method 2, and in the advanced BIOS settings, look for disabled devices.

Enable the devices in the BIOS so that you use them easily.

This will hopefully resolve the issue. If it doesn’t, then this means the error code 29 is caused by either corrupted or outdated drivers. Try method 4 to resolve this issue successfully.

Method 4 - Identify the Problematic Device Drivers and Update them

Whether the error code 29 is caused by a misconfigured, corrupted, or outdated driver, simply update the new driver version to resolve. When doing it manually, you will first have to find and identify the problematic device drivers in the Device Manager.

You can access the Device Manager by going to the start menu and then simply typing Device Manager in the search bar.

Access the Device Manager and the properties to identify problematic drivers. Problematic drivers are normally displayed with a yellow exclamation mark.

Once you have spotted problematic drivers, simply update new drivers to resolve them. Though there is nothing technical about it but it may be time-consuming.

Method 5 - Install Driver Assist to Update Drivers Automatically and Regularly

A good alternative to manual driver update is DriverFIX. Simply download and install DriverFIX on your PC to update all problematic drivers in seconds. This is a cutting-edge program designed to resolve all kinds of device driver problems.

It is user-friendly and compatible with all Windows versions.

The intelligent programming system deployed inside this software program enables it to identify and detect all problem drivers automatically thereby sparing you from the hassle.

Furthermore, it also matches the drivers with the latest and compatible versions and updates them on a regular basis.

It takes the guesswork out of finding misconfigured and corrupted drivers and fixes driver-related problems and error codes like code 29 right away.

Click here to download DriverFIX to repair Device Manager error code 29 on your system without any hassle.

Anytime when a new folder is created in Windows name "New Folder" is offered and set as the default name. If by any chance you would like to change this and set your own default name instead of the standard one, follow this guide. Please be aware that this guide will require you to change the registry of Windows, it is common practice to make a backup of your registry each time you want to manually change any values in it, just in case something goes wrong.

• In order to change the default new folder name first press ⊞ WINDOWS + R to open the run dialog, type in it RegEdit, and press ENTER
• In registry editor find the key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer

• Select the NamingTemplates key. If it is not present, you’ll need to create one.
• Right-click the NamingTemplates key to add a String Value.
• Assign it the following name: RenameNameTemplate.
• Double-click on the RenameNameTemplate data value to open the Edit String dialog box.
• In the Value Data field enter the new text you want to appear when you create a new folder. You have to make sure you are not using any of the following characters: \ / ? : * " > < |
• Close the Registry Editor and Exit.
• Now, when you create a new folder, it will be named Whatever you chose instead of the New folder.

And that is all to it, you now have your own personal new folder naming template.

There are times when you might notice that the Drive letter from the File Explorer is missing, right after you install an update in your Windows 10 computer. So if you are facing this issue right now, then you’ve come to the right place as this post will guide you on what to do to fix it. In case you don’t know, a drive letter represents a single alphabetic character which is through A-Z typically. This could be assigned to a physical disk partition, floppy disk drive or the removal device/ CD-ROM/ mapping network drive in your PC. In most cases, the drive letter “C:” is assigned to the first disk partition where the running Windows is installed. Thus, if the assigned letter is missing from either the Disk Management or the Windows File Explorer, it could result in inconveniences or will leave the partition inaccessible. To fix this problem, you can try to show the missing drive letters manually or make sure that the drive has a drive letter assigned in the Disk Management as well as assign the letter using a tweak in the Windows Registry. For more details, refer to the options provided below.

Option 1 – Try to show the missing drive letters manually

• Open the Folder Options from the Start Search and go to the View tab,
• Next, scroll down on the list of given options until you see the “Show drive letters” option and then check the box that’s marked against this option.
• After that, click on the Apply and OK buttons and then go back to the “This PC” window. You should now see the drive letters

Option 2 – Make sure that the drive has a drive letter assigned in Disk Management

As you know, every drive is assigned a drive letter in Disk Management. However, if it goes missing, you can still get it back through Disk Management. To do so, follow the steps below.

• Open Disk Management and from there, right-click on the menu of a partition or volume and you should see a function named “Change Drive Letter and Paths”.

Note: This function allows you to add the drive letter, remove the drive letter and change the drive letter. If the last option, namely, “Remove”, is selected and applied, the letter of the drive will be removed and won’t appear in Disk Management. Thus, this could be one of the reasons why a drive letter is missing.

• You need to click on “Add” to assign a letter to the selected drive in order to reverse the change. Note that you must assign the drive with the original letter because if not, the programs that rely on the original letter might not work as expected.
• If the original letter is already taken by a new drive, you need to change the letter of that new drive to another available letter.
• Then allocate the released letter of the targeted drive.

Option 3 – Try assigning the letter using a Registry tweak

The next thing you can do to fix the problem is to assign the letter using a tweak in the Windows Registry but before you do that, make sure that you create a System Restore point first, after that, follow these steps:

• Tap the Win + R keys to open Run and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMMountedDevices
• From there, check if a device is shown as being mounted at the specific drive letter and then right-click on that drive letter.
• Select the “Rename” option from the right-click menu to change the letter to any other available letter.
• Exit the Registry Editor and restart your computer.

Option 4 – Try to format the destination drive

Formatting the drive can also help you resolve the error. To format it, follow these steps:

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select initialize disk.
• Next, select the correct partition type and proceed.

CPU Not Compatible – What Is It

Some users wanting to upgrade to Windows 10 from Windows 7 or Windows 8.1 experienced errors with installation. One of these errors is CPU Not Compatible. When you click and run the “Get Windows 10” from your system tray bar, you’ll receive the “CPU is not compatible with Windows 10” error. When this happens, it might be good to check if there’s a bug or if your NX feature (a requirement for the Windows 10 installation) is enabled.

Solution

Error Causes

The “CPU is not compatible with Windows 10” error normally occurs when:

• NX feature is not enabled
• You experienced the Windows 10 bug

Further Information and Manual Repair

To successfully upgrade to Windows 10, your CPU must support Physical Address Extension (PAE), SSE2, and NX features. If any of these features are not activated on your system, it’ll cause the CPU not compatible error. However, some users still reported experiencing this error even though their CPU has these features activated. Normally, this is due to the bug that Windows acknowledged.

If any of these two scenarios apply to your computer, the following methods will help you fix the problem:

Method 1 – Check for bugs

The bug applies to some Windows 7 and Windows 8.1 systems. The bug occurs when the “Get Windows 10” app fails to recognize CPUs as being compatible. This produces a false negative result with a message, “Here’s why Windows 10 cannot be installed on this PC: The CPU isn’t supported”. To fix this bug, Microsoft released an update.

Unfortunately, the patch update (KB2976978 for Windows 8/8.1 and KB2952664 for Windows 7 SP1) to fix the bug may not be automatically downloaded to your computer. If this is the case, you need to verify first if the patch was installed correctly. To do this, follow the steps below:

1. Click ‘Start’ and type in View Installed Updates. The “View installed updates” icon should appear. Click the icon.

2. Go to the Search bar (Top right portion) then type the patch name for your system. Make sure that you type the correct patch name for your system since Windows 7 and Windows 8/8.1 have different names. If you find the patch, it means it’s already installed. You can now upgrade to Windows 10 without the CPU not-compatible error.

3. But, if you can’t find it you need to install the patch manually.

4. Go to Windows Update then click the “Check for Updates” button.

5. Browse through the available updates and look for KB2976978 for Windows 8/8.1 or KB2952664 for Windows 7 SP1

6. Download the right patch. You may need to reboot your system once it’s done.

7. The downloaded patch should be applied after a day or two with the Windows Task Scheduler. Once the patch is applied, you can now upgrade to Windows 10.

Method 2 – Check CPU features and activate them if needed

A major requirement for Windows 10 upgrade is for the CPU to have Physical Address Extension (PAE), SSE2, and NX features enabled on your system. If you receive the CPU not compatible error, one possible cause is that any of the mentioned features are not available OR not enabled on your system. Here’s how you can fix this:

1. Verify if your CPU supports the three instruction sets. You can use software that provides information like this. If all three are available, proceed to the next step.

2. Go to your computer’s BIOS. To do this, reboot your computer. You will need to press a key specific to your computer’s manufacturer (usually it’s F12, F8, F2, or DEL).

3. Look for the NX (No Execute Bit) settings. This is normally found in the “Advanced Configuration” menu, or something similar to this. Just take note that the NX setting can be named differently in BIOS. Some other names include EDB (Execute Disabled Bit), EVP (Enhanced Virus Protection), Execute Disabled Memory Protection or No Excuse Memory Protect.

4. Once you’re in the NX settings, make sure that it’s enabled.

5. Exit the BIOS and SAVE your changes.

6. Boot your computer normally, then try upgrading to Windows 10 again through the “Get Windows 10” app found in the system tray.

Method 3 – Force enabling NX Bit

If changing the settings in your BIOS doesn’t do the trick, your final option is to force enable the NX bit in your Windows system. However, this is only applicable IF and ONLY IF your CPU does support it. To force enable NX bit, do the following:

1. Click Start and go to command prompt (Type “cmd” – no quotes) and press enter.

2. Copy and paste the text below to the command prompt.bcdedit.exe /set {current} nx AlwaysOn

3. Execute the command. You will need to reboot your computer once this is done.

4. Download and install Windows 10

Method 4 – Use a trusted automated tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

Windows PowerShell is a powerful tool inside the Windows environment often overlooked by typical users which is a great mistake since it can offer a large array of functionality and usability and if used well can offer a unique working experience. Today we will be using PowerShell to turn the WEB camera off so it can not be accessed, completely disabling it for use. You might want to do this for security reasons or just want to learn few new things. Whatever your reason might be, I am welcoming you to this tutorial and please do keep reading.

Finding device ID

In order to disable the WEB camera first thing we need to do is to find a matching device ID. We will find this value inside the device manager, so press ⊞ WINDOWS + X to open the secret menu. In the menu choose device manager and click on it. When the device manager opens, expand the Imaging devices or Cameras section. Right-click Integrated Camera or the primary webcam, and click Properties. Go to the Details tab. Under the Property section, click to select Matching device ID from the drop-down. Right-click the value and select Copy The next step is to download and install Windows Driver Kit (WDK)

PowerShell script

Create and run a PowerShell script with the following parameters/values to disable the camera. Substitute the <FOLDER> placeholder with the actual name of the folder where your copy of Devcon is residing

$id = (Get-CimInstance Win32_PnPEntity |

where caption -match '<PRIMARY CAMERA>').pnpDeviceID

$ppid = "{0}{1}" -f '@',$id

Set-Location c:\<FOLDER>

Devcon status $ppid

Devcon disable $ppid

Devcon status $ppid

To enable the camera device, run the command below in PowerShell:

devcon enable $ppid