Low Disk Space on Recovery Drive Windows 10 — The Saga (And the Real Fix)

-

A few months after a major Windows 10 update, I started getting the most annoying notification ever:

The message appeared randomly. No pattern. No clear cause. Just constant irritation.

The Situation

My system looked like this:

Disk D: is removable. C: and E: live on the same HDD. Siblings. So my logical plan was simple: shrink C:, extend E:, silence the warning.

Disk Management Reality

I opened Disk Management and saw this:

E: did not have the same options as other partitions. No “Extend Volume…” available.

The “Smart” Attempt

I shrank C: by 2GB using “Shrink Volume…”. Unallocated space appeared between C: and E:.

Then began the classic “dance with tambourine around the campfire”:

  • Move partition
  • Merge attempt
  • Allocate space
  • Retry

Nothing worked.

Third-Party Tools Trial

Search results pointed to third-party partition managers. I tested multiple vendors, including Paragon Hard Disk Manager and Macrium Reflect.

None of them allowed resizing or merging that recovery partition.

The Actual Working Solution

The only tool that successfully handled the operation was:

AOMEI Partition Assistant

Free edition. Operation completed in about 30 seconds.

After all the experiments, the fix turned out to be trivial.

Conclusion

Windows built-in Disk Management has strict structural limitations when dealing with recovery partitions. Some third-party tools also fail due to partition type restrictions.

In this case, a dedicated partition manager was required.

It was a long road for such a simple result.

P.S. The backup story that followed? That is another saga.

Comments

Post a Comment

Popular posts from this blog

Decimal number issue from server to client. Wow! Didn't expect this @_@

-
Image
Chapter 17   where a poor Decimal Number came from Server Side to JavaScript I worked on a page for days, adjusting the UI with CSS and HTML. Everything looked fine… until I started testing multi-lingual support. English — OK. Spanish — OK. Chinese — OK. Even right-to-left Hebrew (crooked and askew, but working). But Russian? Nope. In Russian the page stopped working completely: only static texts and images were visible. Nothing dynamic rendered. Of course it was a JavaScript error. Firefox DevTools showed this: That error led me to this JS code: I stared at those lines and saw nothing wrong — no missing variables, no typos, nothing obvious. I went to the original project code to find the exact non-rendered rows and noticed a server variable embedded into the client-side script: Which naturally led me to the server-side C# code responsible for generating that value: Nothing looked wrong there either. So I did what every developer does in ...
Read more

Shrinking node_modules for AWS Lambda (My First “npm shock” and a Practical Fix)

-
Image
I’m a newbie in Node.js and not really familiar with the whole npm ecosystem. I honestly didn’t expect that a single npm install would explode into ~10MB spread across ~30 different folders. After a few minutes of staring at it, I realized what’s actually inside those folders: not just runtime code. What shocked me Inside node_modules you get everything: README files source files tests examples docs And then the next level of madness: modules inside modules . Duplicated dependencies nested multiple levels deep (e.g. inherits , core-util-is , tedious …), even if they already exist elsewhere in the project tree. Here’s a typical example: I’m in node_modules → package bl , and there’s another node_modules folder inside it, plus test , README and other “junk”… all for a ~10KB JS file. The obvious assumption (that turned out wrong) Once I accepted the chaos, I assumed there must be a “build for production” command that would “compile” depende...
Read more