Software tower · floor
How to fix windows update error assumes there is something to fix. In Microsoft’s own documentation, several of the most common cases are not repairs at all — the space is in a place you were not looking, the update is being withheld deliberately, or the error message is one Microsoft describes as inaccurate.
Start with the case that defeats the standard advice, because the standard advice is to free up disk space and here that does nothing.
This is the case that defeats every generic instruction. The drive has plenty of room, the
update still fails, and clearing forty gigabytes on C: changes nothing — because the
space the installer wants is in a small separate partition that File Explorer does not list.
Microsoft publishes a manual resize procedure and a script for exactly this. And on one of those updates Microsoft published something rarer still — a statement that
the error itself was wrong: “After installing this update, you might see the following
error message in the Windows Update settings page: 0x80070643 – ERROR_INSTALL_FAILURE.
This error message is not accurate and does not impact the update or device
functionality. Although the error message suggests the update did not complete, the WinRE
update is typically applied successfully after the device restarts.”From Microsoft’s article on a Windows Recovery Environment update, said twice on
the same page: “This update requires 250 MB of free space in the recovery
partition to install successfully.” And in the prerequisites: “The PC must have
250 MB of free space in the recovery partition to apply this update successfully.”
Two things follow. If the failure is this one, gigabytes freed on C: will not help, and the number to look for is small — two hundred and fifty megabytes, in a partition the file manager does not show. And if you have seen 0x80070643 after a recovery-environment update, Microsoft’s own note says the message may be wrong and the update may already have worked.
That leads to the other number problem, the one that makes the whole subject feel incoherent.
Windows sets space aside in advance — the same post says it “will start at about
7GB”, adding that “the amount of reserved space will vary over time based on
how you use your device”. So the modest figure quoted for a monthly update and the large
figure quoted for an upgrade are not a contradiction: one is space that has already been
reserved on your behalf, the other is what a whole new version of Windows needs. Reading
them as two answers to one question is what makes the advice feel incoherent. Whether your machine has it is checkable rather than guessable. Microsoft documents the
command: DISM.exe /Online /Get-ReservedStorageState. And it publishes where it does not
apply: “For devices that connect directly to Windows Update (WU), reserved storage works
out of the box. However, on IT managed devices using endpoint management tools such as
Windows Server Update Services or Configuration Manager, reserved storage doesn’t work
automatically.” A note on sourcing: the 7 GB figure and the two sentences above come from a Microsoft blog
post, not from a support article. The DISM command and the managed-device exception are from
Microsoft Learn documentation.On Microsoft’s own blog, describing reserved storage: “On devices with
reserved storage, update will use the reserved space first.” And: “When it’s
time for an update, the temporary unneeded OS files in the reserved storage will be deleted and
update will use the full reserve area. This will enable most PCs to download and install an
update without having to free up any of your disk space, even when you have minimal free disk
space.”
Then the case where the machine is behaving correctly and the update simply will not come.
That is the sentence worth the whole page for some readers. An update that will not arrive
is not always a fault: it can be Microsoft deliberately keeping it away from your hardware
because of a known problem, and the published advice is to wait rather than to force it. The
holds have identifiers — Microsoft refers to “safeguard holds by their 8-digit
identifiers” — and it publishes a Windows release health dashboard where known
issues for each release are listed.“Safeguard holds prevent a device with a known issue from being offered a new
operating system version.” What you see: “the Windows Update page in the Settings
app displays a message stating that an update is on its way, but not ready for the device…
This message means that the device is protected by one or more safeguard holds.”
And Microsoft’s own instruction: “We recommend that you don’t attempt to
manually update until issues have been resolved and holds released.”
The remaining number people quote at each other is ten days, and it is worth being exact about because it is neither a rule nor fixed.
“The option to go back to your previous version of Windows is only available for a
limited time after upgrading. In most cases, you have 10 days to go back.” Note the words in most cases. Microsoft does not present ten days as a rule. The window is a setting: “Sets the number of days after an upgrade that an uninstall
can be initiated.” via DISM /Online /Set-OSUninstallWindow /Value:<days>. And the bounds: “If you specify a value less than two or greater than 60”,
the system falls back to its default. “Ten days after you upgrade to Windows, your previous version of Windows is
automatically deleted from your PC.” Which is also why the drive looks fuller than usual until then.What the support page says
with a caveat
What the documentation says
2 to 60
What happens at the end
automatic
So “you have ten days” is a default with a caveat attached by Microsoft itself, and a value an administrator can set anywhere between two and sixty. On a work machine the window you actually have may not be ten days at all — and the page that tells you ten does not mention that it can be changed.
A note on sourcing, because it matters on this page more than most. The 250 MB figure, the safeguard holds, the uninstall window and the end-of-support date all come from Microsoft’s support articles and its Learn documentation. The reserved-storage figure of about 7 GB comes from a Microsoft blog post, which is first-party but not documentation, and this page says so where it uses it rather than letting it pass as a specification.
A note on the results. Google did not return readable search results while this page was written, so this page makes no claim about what is on Google’s first page for this question.
What this page will not do is give you a single sequence of steps. Microsoft publishes several, they are written for different failures, and the useful work here is telling you which failure you have before you start.
It will not tell you to empty the update cache as a first move. Microsoft puts a destructive version of that in its ordinary numbered list and a reversible version behind an advanced warning, which is a good reason to know which one you are being shown.
And it will not recommend a registry cleaner, a driver updater or a repair tool. Every check above is Microsoft’s own, and none of those products has been tested here.
Three ways in. If you have already cleared plenty of disk space and it still fails, take the first.
A recovery partition that needs 250 MB while the main drive has plenty, and an error message Microsoft itself describes as inaccurate.
Safeguard holds keep an update away from hardware with a known issue, and Microsoft advises against forcing it. The message in Settings is the signal.
Microsoft says “in most cases”, documents a range from two to sixty days, and deletes the previous version automatically when the window closes.
It will not give you one sequence of steps. Microsoft publishes several, written for different failures, and knowing which failure you have is the work.
It will not tell you to clear the update cache first. There is a destructive version of that step and a reversible one, and they are not presented with the same warning.
It will not recommend a repair tool, a driver updater or a registry cleaner. Every check above is Microsoft’s own and costs nothing.
And it carries no affiliate links, which in a category full of one-click fixers is the whole business model this page declines. What holds instead is simple: every figure above is quoted from Microsoft, each labelled by where it comes from — support article, Learn documentation or company blog — because on this question the source decides how much the number is worth.
Founder and editor of AI Tools Primer, writing from Palermo, Italy. Thirty-five years of taking computers apart, starting with a Commodore 64 — the long version is on the about page.
Something wrong on this page? Write to aitoolsprimer@gmail.com and it gets fixed.
Written on 23 August 2026.
No affiliate links and no paid placements anywhere on this site. Nobody pays to appear here, and no company has seen this page before you did.
This is general information, not professional advice. Where a page touches money, health, safety or the law, it names its source and the date it was read — and your situation may still differ. See the privacy page and the cookie policy.