How to Repair Windows 10 Upgrade Error Code 0x80070070 – 0x50011

Hello everyone, last time we were talking about disk cleanup and its benefits, but as you need to keep your System clean you should also clean and keep your hardware clean as well. Many system issues could be traced and could happen due to dirty PC. In this article, we will give you tips on how to perform safely cleaning on your computer and hopefully point good sides to it so you can develop a healthy habit of regularly cleaning it and keeping it tidy. Keeping your PC clean is not rocket science and you can do it with things you already and probably have in your house. One thing that I would recommend tho to purchase is antistatic gloves since they could prevent any kind of electrostatic discharges thus protecting your electric components. If you have the option to disconnect your PC and get it outdoors, I would highly recommend this approach since all the dust will be dusted outside and not in the room where your computer is. If you can not it is still ok, but since some portion of dust will be set in the room, you might need to dust your room after cleaning your computer.

Cleaning outside case & redusting inside

The first thing after disconnecting your computer is to dust it from outside, here you will need a vacuum cleaner and a brush, gently brush outside dust from your casing and vacuum it with your vacuum cleaner. You can use dustcloth for larger parts but use the brush for fans and connectors. After you have done cleaning the outside part, open the side of your computer casing, put on your antistatic gloves, and get a fine and soft brush, repeat dusting and vacuuming of the inner parts of your computer. If your computer is not regularly been cleaned this part will take a little longer since there would be excess dust inside and it will take a longer time to vacuum it all but keep going until you are left with no dirt.

Cleaning it inside

Fans are troublesome to clean since they will rotate when brushed and that could make you miss certain sports, in order to battle this get a tape and stick the fan into one position, brush areas that you can reach, then unstick it, rotate the head, stick it again in another position and dust off remaining areas which you could not reach before. If your computer is very dirty and some hard dirt is at bottom of the connectors, disconnect desired component and clean the connection properly. plug it back in immediately after cleaning to avoid connecting it somewhere else. Harder stains that could not be dusted could be cleaned with little alcohol. Get your dustcloth just a little wet with alcohol, just a corner, and gently wipe out sticky dust or spills if they are present. Leave it 10 minutes for alcohol to evaporate before plugging it back into an electric socket.

Thermal paste and cable management

If you have money and expertise, every 2 years would be a good idea to change the thermal paste on your processor, all you need to do is buy it from your local computer store online, remove the CPU fan clean the CPU and bottom of the fan and apply new thermal paste, place fan back and lock it. If you do not have expertise in this area, call someone who has to show you how it is done. When cleaning it would be a good idea if you do not have any cable management to do it now, nice and tidy cables not only look good, they also improve your air circulation inside your casing making your computer cooling better. once you are done with it, close back the casing side and plug it back in the wall.

Peripherals

When you are cleaning your computer, do yourself a favor and clean your keyboard, mouse, and screen as well. the keyboard can be quickly cleaned with compressed air in the can and screen and mouse with dustcloth. That's it, remember, keep your PC clean and tidy and enjoy the benefits of non-hardware malfunctions caused by dirt and dust.

Installing Windows updates, installing a new driver from the manufacturer, or even just installing an application or game can cause sometimes certain components of your computer to stop working properly or introduce issues that were not present just before mentioned installation. Luckily for all of us, Microsoft seems aware of this potential issue and we have the option to roll back an older driver which performed well and had no issues at all. In order to do this first press ⊞ WINDOWS + X to open the hidden start menu and click on Device Manager. From the Device Manager choose the troublesome device and right-click on it, choose properties. Device properties floating Window will appear. Click on the top tab which says, Driver. From the Driver tab, click on Roll Back Driver. Note that if the device is working properly, the Roll Back Driver button will be greyed out and you will not be able to click on it meaning that chosen device is not the issue. If the device is not working properly and you can click on Roll Back driver, do it, choose the previous version, and reboot your computer. You can use this method to get back to the previous driver version for any device that is causing issues in your computer.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

intel's first gaming card that will hit the market soon has been shown in its innovation event, the Intel Arc A770. In its core ticks ACM-G10, coming with 32 Xe-cores and all the way up to 16GB of GDDR6 memory (the basic entry-level version will have 8GB of GDDR6). The card will support ray tracing and supersampling with Intel's XeSS.

This is Intel's first gaming desktop GPU and after testing with some YouTube channels it turned out that the card itself sits somewhere between nVIDIA RTX 3060 Ti and an RTX 3070 so it will still be low in performance compared with the new RTX 4090 or AMD's new RDNA3 upcoming lineup. But as stated this is Intel's first gaming graphics card and having this kind of performance is no small feat for the first-time product.

One thing that is really great tho and that is going for Arc A770 GPU is its price! The Limited Edition card will cost $329 which is at this moment most cheapest GPU currently on the market in that performance range. nVIDIA is between $500 and $700 for comparison and if Intel can hold on to its performance with almost half the price card could be a great hit among gamers. GPU itself will launch on October 12th.

When clean Windows is installed or when you place new hardware in your computer usually Windows itself detects the device and installs its driver. The question that comes now is, do you keep that driver or do you install the manufacturer's one. In order to answer this question let's analyze what is difference between the two drivers and other factors which could influence your decision.

Difference between drivers

First of all, know that drivers Windows installs are also drivers from the device manufacturer which have gone through Microsoft quality control in order to be included in Windows itself. Now naturally question which occurs, what is the difference, well answer to that would be this: in Windows, you have stripped down driver, just a driver in order for Windows to know what device is plugged and how to use it, meaning that for example if you install printer device, you will be able to print documents and Windows will know it is a printer but ... You will not get the control panel for that printer where you can adjust the printer itself and all of its features like let's say paperweight, etc. So if you need these kinds of features in that case it would be better to install a complete driver suite from the manufacturer and get the whole package. Windows will recognize the RAZER mouse for example but you will not be able to change its colors of program custom buttons on it until you install RAZER drivers. One more important thing to note is that drivers which are in Windows are less updated than drivers from the manufacturer's site. That being said, if you prefer and want to have the latest drivers you will prefer to get them again from the manufacturer.

Conclusion

So it seems that manufacturer's drivers are always in some form of advantage and that you will always want them and most of the time this is true, as a matter of fact, the only time I could think that you could use bare down Windows drivers is when new drivers update breaks something in Windows and device start behaving improperly. in this particular case, it is better to roll back to the previous Windows driver which has passed Microsoft quality control and is working for sure. In any other case, you are better off with the latest manufacturers drivers If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

If you open any program in your Windows 10 PC such as Outlook and suddenly get an error message saying, “Failed to register a VB Script dll. Reinstall or run Regsvr32.exe Vbscript.dll to self-register”, read on, as this post will guide you on what you can do to fix it. The obvious solution to this problem is by re-registering the “vbscript.dll” file on your computer. Refer to the instructions given below to re-register the VB Script DLL file and to fix the error.

• Step 1: Open the Command Prompt as an administrator from the WinX Menu.
• Step 2: After opening Command Prompt, type in the following command and tap Enter on your keyboard.

regsvr32.exe vbscript.dll

• Step 3: Once you enter the command, it will re-register the VB Script DLL file using the Windows OS tool called Regsvr32 or regsvr32.exe. This tool is a command-line utility used to register and unregister OLE controls such as DLL and ActiveX (OCX) controls in the Windows environment. After the execution of the command, you should see the following pop-up on your screen which means the re-registering of the concerned DLL file has succeeded.

On the other hand, if re-registering the DLL file didn’t work, then you can try logging in using an administrator account and then register the DLL file again or you could also use the System File Checker to figure out what the problem really is and automatically fix it. 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 with good system files. To run the SFC command, follow the steps given below.

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

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.

Something we are used to doing in a certain way inside Windows 10 is slightly changed in Windows 11. One of those things is how you open task manager, well kind of. Option to right-click on the taskbar and launch task manager is gone but do not worry there are other same and simple ways you can launch it.

1. Press CTRL + SHIFT + ESC or CTRL + ALT + DEL
2. Right-click on the START button
3. Type task manager in start search on top in the start menu
4. Type taskmgr in command prompt
5. Press ⊞ WINDOWS + R to open run dialog and type in taskmgr

And that’s it, now depending on your situation, you might use different methods to evoke task manager.

Error Code 0x8024002e - What is it?

Windows 10 error code 0x8024002e is related to the Windows update service. When you see the error code displayed on your screen, it means that the Windows update service has been blocked or not working. As a result of this error code, your computer might lag and the system may freeze while performing normal operations. The error may read as follows:

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

Common symptoms include:

• Slow computer performance
• System freezes while performing normal operations or freezes while multitasking
• BSOD error is showing
• Some unwanted files get opened automatically
• Updating is not possible

Solution

Error Causes

This error code appears because of the following reasons:

• Incomplete installation of the Windows operating system
• Incorrect registry entry
• Corrupt or damaged system files
• The computer has come under a virus attack
• Miscommunication between the computer and the Windows Automatic Update service

The decline in RAM or outdated Hard Disk Drive

Further Information and Manual Repair

Method 1:

• Remove any external media connected to the computer
• Crash reboot your PC 2 to 3 times.
• Now check if you are still having the problem.

If the problem still persists, try the following methods if you are able to boot to the desktop and check for the problem.

Method 2:

Changing Windows Update property to automatic: You might see this error if your Windows update property is set to manual. Follow the steps below to change it to automatic. Open Task Manager.

1. Click on the Services tab. Find “Open Services” at the bottom of the window.
2. A new window will pop up. Scroll down and find “Windows Update” from the list. Double click on the Windows Update. It will open its properties.
3. Select Automatic for ‘Startup Type.’ Click Apply, Start, and OK.

Now, try the Windows Update and check if you are still getting the error message. If the problem isn’t resolved, reboot your PC for the changes to take effect and then try again.

Method 3:

Disable Antivirus program: If you have any antivirus installed on your PC, you might need to disable it first and see if that helps. Although, most of the antivirus makers have made changes to work smoothly with Windows 10, it is a new Operating System and some antivirus may cause conflict. Disable the antivirus and check for updates to see if it is preventing you from updating your system and displaying the error code 0x8024002e.

Method 4:

Run inbuilt Windows update troubleshooter. Follow the steps given below:

1. Press Windows + W keys on your keyboard to enable the search option.
2. In the Search box type Troubleshooting.
3. Click on View all
4. Click on Windows update and follow the prompts to run the troubleshooter.

If the issue persists, try Method 5

Method 5:

Run the System File Checker tool (sfc.exe):

1. Open Command prompt.
2. Type sfc /scannow and hit Enter.
3. The sfc /scannow will scan all protected system files and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%System32dllcache. The %WinDir% has the Windows Operating System folder. For example, C:\Windows.

Do not close the Command prompt window until the verification is 100% complete. The command prompt will show the scan results when it is done. After it is done, you may receive one of the following messages:

“Windows Resource Protection did not find any integrity violations.” This means you do not have any missing or damaged system files.

OR you may receive a message saying:

“Windows Resource Protection could not perform the requested operation.”

To resolve this problem, run the System File Checker in safe mode and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%WinSxSTemp.

OR you may also receive a message saying, “Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log%WinDir%LogsCBSCBS.log.” OR you may receive a message saying, “Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log%WinDir%LogsCBSCBS.log.”

You might be familiar with the Encryption File System or EFS algorithm if you rather keep your files and folders encrypted. Encryption File System is a built-in feature in Windows 10 which allows users to secure their important files. Although there is an alternative way for you to secure your data on your Windows 10 computer, you can’t ignore the fact that the main advantage of an Encryption File System over BitLocker is that the former can help you encrypt a particular folder rather than encrypting the whole hard drive partition. If you move a file inside a folder encrypted with the Encrypting File System it will automatically get encrypted. There are some users who like this feature but unsurprisingly, there are some that don’t. So if whether you want your files encrypted when you place them in an encrypted folder or if you want to keep it as it is, read on as to how you can do it either way. You can enable or disable automatic encryption of files moved to encrypted folders in Windows 10 using the Registry Editor or the Group Policy Editor. Before you proceed, make sure to create a System Restore Point first because the modifications you’re about to make in your computer might affect its overall functioning so if anything goes wrong, you can always undo the changes. Once you have that covered, refer to the options given below to enable or disable automatic encryption in Windows 10.

Option 1 – Enable or disable automatic encryption using Registry Editor

• Press the Win key + R key at the same time to open the Run dialog box.
• Then type “Regedit” in the field and press Enter to open the Registry Editor and if a User Account Control or UAC prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this key location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer
• Next, right-click on Explorer and select New > DWORD (32-bit) Value and then name the newly create DWORD to “NoEncryptOnMove” and press Enter to save it.
• After that, double click on the NoEncryptOnMove DWORD and set its value to the following preferences:
  • 1 – Disable Auto Encryption of files moved to encrypted folders.
  • 0 – Enable Auto Encryption of files moved to encrypted folders.

• Now close the Registry Editor and restart your computer to successfully apply the changes made.

Option 2 – Enable or disable automatic encryption using the Group Policy Editor

• Press the Win + R keys to open the Run box and type “gpedit.msc” in the field and press Enter to open the Group Policy Editor.
• After that, navigate to this path: Computer ConfigurationAdministrative TemplatesSystem
• Next, look for the “Do not automatically encrypt files moved to encrypted folders” option and double click on it to set the policy. From there, you will see the following description:

“This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder. If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder. If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder. This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.”

• Now select one of the radio buttons below depending on your preference:
  • Not Configured or Disabled: Enable Auto Encrypt of files moved to EFS Encrypted folders.
  • Enabled: Disable Auto Encrypt of files moved to EFS Encrypted folders.
• Then click on the Apply and OK buttons to save the changes made.
• Exit the Group Policy Editor and restart your computer.

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.