summaryrefslogtreecommitdiffstats
path: root/content
diff options
context:
space:
mode:
authorbreadcat2020-08-16 11:47:24 +0100
committerbreadcat2020-08-16 11:47:24 +0100
commit5ef0038d52e2a3c37bea59ff47cbdcd67c1238a2 (patch)
tree820b61c845ca53496b283ad0ec408a62c4ae6e1e /content
parenta591a820c8c06471da73c773f8d7cac070eaa7b1 (diff)
downloadblog.minskio.co.uk-5ef0038d52e2a3c37bea59ff47cbdcd67c1238a2.tar.gz
blog.minskio.co.uk-5ef0038d52e2a3c37bea59ff47cbdcd67c1238a2.tar.bz2
blog.minskio.co.uk-5ef0038d52e2a3c37bea59ff47cbdcd67c1238a2.zip
New post
Diffstat (limited to 'content')
-rw-r--r--content/posts/wipe-windows-recovery-partition.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/content/posts/wipe-windows-recovery-partition.md b/content/posts/wipe-windows-recovery-partition.md
new file mode 100644
index 0000000..e42eca0
--- /dev/null
+++ b/content/posts/wipe-windows-recovery-partition.md
@@ -0,0 +1,23 @@
+---
+title: "Wiping your Windows recovery partition"
+date: 2020-08-14T03:42:00
+tags: [ "Guides", "Snippets", "Software", "Windows" ]
+---
+
+I recently replaced my Windows 10 LTSC installation with a stock(er) Windows 10 Pro install, one thing I noticed was an additional partition automatically being created. This partition was helpfully labelled as a recovery partition, and took up 512MB of ever so precious space. I did a bit of research into the matter and found out it wasn't strictly necessary, and personally when it comes to recovering an operating system I have no qualms performing a clean install.
+
+So, to remove this, first launch an admin command prompt (search for `cmd` in your start menu, right click, run as administrator) and run the following:
+
+```
+diskpart
+list disk
+select disk 0
+list partition
+select partition 4
+delete partition override
+```
+*in the example above, our recovery partition is #4*
+
+You can now expand your system partition into the empty space.
+
+Launch `diskmgmt.msc`, right click your system partition, then extend volume.