We Couldn't Install Windows Technical Preview 0x80070070 - 0x20005 -- What is it?
Some Windows users have been experiencing errors in an attempt to upgrade to Windows 10 OS. This includes the “We Couldn’t Install Windows Technical Preview 0x80070070 – 0x20005” error code. If you’re one of the many users who’ve encountered this error, you might want to check the available space on your device. Error code 0x80070070 – 0x20005 occurs when you do not have the required space to be able to install the upgrade.
Solution
Error Causes
Just like the other alternatives of error code 0x80070070 – 0x20005 such as 0x80070070 – 0x50011, 0x80070070 – 0x50012, and 0x80070070 – 0x60000, We Couldn't Install Windows Technical Preview 0x80070070 - 0x20005 is most likely caused by the following:
- Insufficient disk space in your computer
- Incomplete installation or improper deletion of applications
- The device is infected with virus or malware
Further Information and Manual Repair
In order to upgrade to Windows 10, you need to have at least 40 to 50 GB of free space in your device. Thus, you need to free up some space in order to successfully upgrade your system to Windows 10. See below for the manual methods you can employ to solve your problem.
NOTE: It would be best to seek help from an experienced technician if you are not confident enough to perform the manual methods yourself or you can alternatively make use of an automated tool.
Method One: Clean Up Your Device
- Click Start then browse Afterwards, click on This PC.
- Right-click on Local Disk (C:) then choose
- Under the General tab, click on Disk Cleanup.
- Once the Disk Cleanup window appears, check all items you want to clear down, making sure that the recycle bin is empty and clear any temp files, as well as error logs. Click OK once you’re done.
- Repeating the same process above, clear down your system files as well to ensure that the old OS files from your previous system are taken down by clicking on Clean up system files in the Disk Cleanup window.
Method Two: Uninstall Unused Applications
Sometimes, there are unused applications just lying around your device. This may take up your needed space from your device for a system upgrade. Uninstalling these applications can make space that will eventually elude error code 0x80070070 – 0x20005 along with its alternatives – code 0x80070070 – 0x50011, code 0x80070070 – 0x50012, and code 0x80070070 – 0x60000.
- Open the Control Panel then select Programs and Features.
- Check on unused applications on your device
- Right-click on the unused application then select
Method Three: Remove or Archive Files
If there are tons of images, media, videos, or documents that you rarely use but will still be needing in the future, you can move these files to another drive where Windows 10 will not be installed on.
If there are no secondary drives in your device, consider using a USB Drive or external hard disk. Another option you can do is making use of cloud storage programs like One Drive or Google Drive. In this way, you’ll still have access to these files even if it’s not in a physical location while making larger space in your device.
Method Four: Scan Your Device For Viruses
Most Windows users download applications or software regularly. These applications or software might come from unsafe sites where you might have accidentally downloaded a virus or malware along with the legit application or software you intended to download.
With that said, it is highly recommended to download and install in your device a reliable and powerful antivirus. Using an antivirus, you can now perform an overall scan of your device’s system. Once you’re able to detect and remove any suspected virus or malware, you’ll now be able to get rid of the error code 0x80070070 – 0x20005. After solving the issue, you can now resume upgrading to Windows 10.
Method Five: Download An Automated Tool
Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!
Like in Windows 10, Windows 11 will also support God mode to be enabled and used. For those readers that do know what God mode is, let me explain it in simple terms. God mode is the icon on the desktop that once clicked will open and let you adjust every option in the control panel and some hidden features for Windows inside one application.

Once the device window opens, click once on printers and scanners, and on the right window go to the bottom and uncheck Let windows manage my default printer.
Unchecking that box will let Windows know that we do not wish anymore for him to set our default printers according to their use. Once the checkbox is clear go up to your printer list and click on the printer you wish to use as the default one. I will choose Microsoft Print to PDF as my default printer and click on it. Once the printer is clicked option menu will appear.
When the option menu appears under the printer name, click on Manage which will take you to the printer management screen. When you are on the manage screen, click on the Set as default button, and you are done.
The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains.
Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue.
A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers.
Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine. 