You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070070.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Troubleshoot Windows Update error code 0x80070070
2
+
title: Troubleshoot Windows Update Error Code 0x80070070
3
3
description: Learn how to fix Windows Update error code 0x80070070, which typically indicates insufficient disk space.
4
4
ms.date: 12/01/2025
5
5
manager: dcscontentpm
@@ -17,19 +17,19 @@ appliesto:
17
17
---
18
18
# Troubleshoot Windows Update error code 0x80070070
19
19
20
-
This article describes how to fix Windows Update error code 0x80070070, which typically indicates insufficient disk space.
20
+
This article discusses how to fix Windows Update error code 0x80070070. This error typically indicates insufficient disk space.
21
21
22
22
## Symptoms
23
23
24
-
When you try to install an update, the update process stops before Windows Update finishes downloading the update. You see an error message that resembles the following example:
24
+
When you try to install an update, the update process stops before Windows Update finishes downloading the update. When this issue occurs, you receive an error message that resembles the following example:
25
25
26
26
> Updates are available, but we currently require additional space for downloading. Let's clear some space by removing any unnecessary files and apps, and we'll try again.
27
27
28
-
If you use Event Viewer to review the Microsoft-Windows-WindowsUpdateClient/Operational log, you find an event that lists the same message.
28
+
If you use Event Viewer to review the Microsoft-Windows-WindowsUpdateClient/Operational log, you find an event that includes the same message.
29
29
30
-
If you're working with an Azure virtual machine (VM), you can use Azure PowerShell cmdlets to collect Windows Update log information.
30
+
If you're working on an Azure virtual machine (VM), you can use Azure PowerShell cmdlets to collect Windows Update log information.
31
31
32
-
For example, to generate a WindowsUpdate.log file on the desktop, open the Azure Serial Console to a PowerShell command prompt and then run the `Get-WindowsUpdatelog` cmdlet.
32
+
For example, to generate a WindowsUpdate.log file on the desktop, open a PowerShell command prompt in the Azure Serial Console, and then run the `Get-WindowsUpdatelog` cmdlet.
33
33
34
34
To generate a log file that you can use offline, run the following cmdlet:
> In this cmdlet, \<OfflineLogPath> is the path to the offline folder where you want to place the log file.
41
+
> In this cmdlet, \<OfflineLogPath> is the path to the offline folder in which you want to put the log file.
42
42
43
-
In the log data, look for reports of failed downloads, and for error 0x80070070. Note the destination of the attempted download especially if you use a non-standard folder (other than C:\Windows) for the operating system. Check that the update was downloaded to the correct location.
43
+
In the log data, look for reports of failed downloads. Also look for error 0x80070070. Note the destination of the attempted download, especially if you use a nonstandard folder (other than C:\Windows) for the operating system. Check that the update was downloaded to the correct location.
44
44
45
45
```output
46
46
Windows failed to download from http://au.download.windowsupdate.com/c/msdownload/update/software/secu/2024/01/winreupdateinstaller_2401b_amd64_db08130ebf8845056f4677e8ef6d85ec048bf7b4.exe
@@ -49,7 +49,7 @@ to local path = C:\Windows\SoftwareDistribution\Download\f8c37f82eee991ffa34047c
49
49
50
50
## Cause
51
51
52
-
The error occurs because there's not enough disk space on your physical computer or VM to store Windows updates for installation.
52
+
The error occurs because not enough disk space exists on your physical computer or VM to store Windows updates for installation.
53
53
54
54
## Resolution
55
55
@@ -59,14 +59,14 @@ For best results, your operating system disk should have at least 20 GB of avail
59
59
> Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
60
60
61
61
1. If the affected computer is a VM, check the disk quota settings to make sure that the operating system disk doesn't have any quotas.
62
-
1. Check the amount of free space on your operating system disk (for example, open File Explorer, right-click **Local disk (C:)** and then select **Properties**).
63
-
1. Free up space on the operating system disk. For example, use the following techniques to increase the amount of available space:
62
+
1. Check the amount of free space on your operating system disk. For example, open File Explorer, right-click **Local disk (C:)**, and then select **Properties**.
63
+
1. Free up space on the operating system disk. For example, use the following methods to increase the amount of available space:
64
64
65
65
- Uninstall unused apps.
66
66
- Delete or archive files that you don't need.
67
-
- Move files to another disk, or to another computer entirely.
67
+
- Move files to another disk or to another computer.
68
68
69
-
1. If you can't free up enough space by removing files and apps, consider the following approaches:
69
+
1. If you can't free up enough space by removing files and apps, consider the following methods:
70
70
71
71
- For a VM, extend the operating system disk.
72
72
- For a physical computer, use an external drive during the update process. For more information, see [Updating Windows using an external storage device](https://support.microsoft.com/windows/updating-windows-using-an-external-storage-device-f980fac4-91b8-4225-b076-f66c28f21768).
0 commit comments