Removing Dell Recovery and Diagnostics partitions from a Dell Inspiron 5770

I have a five-year-old Dell Inspiron 5770 and want to free up space on the 256GB SSD. In another thread, I've been getting help with partition issues on drive cloned with Samsung Magician, and it inspired me to clean up this drive, too.

I see that the Dell Recovery partition takes up 11GB and the Dell Diagnostics partition 1GB. I have never used the Dell Diagnostics and will never want to revert back to the factory state. These partitions come after the WinRE partition, as in the attached screenshot. Without messing anything up, can I:

1. Delete both Dell partitions (5 and 6)
2. Save the winre.wim file from the WinRE partition to the Recovery folder in System32 and then delete that partition
3. Extend my C: drive
4. Then re-create the WinRE partition after Drive C with DiskGenius and reagentc?

I do have a recent Macrium backup of the drive.

Please run: disk par info and tuneup plus > post share links

zbook said:

Please run: disk par info and tuneup plus > post share links

https://www.tenforums.com/attachments/bsod-crashes-debugging/355861d1640707960-batch-files-use-bsod-debugging-diskparinfo.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Click to expand...

I'm not sure why you're requesting I run these programs. I'm asking about WinRE, not experiencing a BSOD. In any case, I did the above, except I recreated the WinRE partition after Drive C: using Disk Management and diskpart rather than Disk Genius. It's all working fine.

The scripts required names and are used for non-BSODs.

zbook said:

The scripts required names and are used for non-BSODs.

Click to expand...

I looked through the scripts and see what they do, gather information about system health, partitions, and boot records. If I ever have a problem relevant to these issues, I'll be sure to run them. In this case, I was just trying to get verification that what I was proposing made sense, not trying to debug a problem. Anyway, I went ahead and everything works fine.

The diskpar info script was designed to run bcdedit, reagentc, diskpart, disk, volume, partition commands, run in the background, and provide a text result.

zbook said:

The diskpar info script was designed to run bcdedit, reagentc, diskpart, disk, volume, partition commands, run in the background, and provide a text result.

Click to expand...

Yes, I see that. I read through both of the scripts. They seem like a quick way to gather a lot of information, though they are not relevant to my current question.