Announcing Windows 10 Insider Preview Build 16184 PC and 15208 Mobile Insider

John Pombrio said:

I had a lot of troubles due to a corrupted Win 10. Run these two commands in a Administrator cmd window to make sure that Windows is clean:
chkdsk /r
sfc /scannow

I did that it found no errors and I am done with using this build.

fdegrove said:

If you have WinRE at the physical end of the drive then that's no problem as you can still expand the system drive, space allowing.
But since some always have a DATA partition behind the system drive it would make extending the system drive not that easy at all.

The thing with WinRE partition on UEFI / GPT setup is that it can expand itself automatically but only "backwards", being only partition type that can do this. However, it can only expand automatically if located directly after C: partition, "steal" space from it and therefore it has to be directly after C: before any additional data partitions.

The above in pictures, here's a sample using small SSD as system disk. Clean install Windows 10 partitioning the disk correctly, recovery partition after Windows partition:



The same disk after a build upgrade, recovery partition needed 58 MB more space expanding backwards, taking necessary additional space from C: partition:



(Above screenshots from Disk Management which does not show hidden and not formatted MSR partition between EFI and Windows partitions.)

When partitioning a larger system disk this should be thought through before installing Windows. Here's for instance the partition layout before starting installation on a correctly partitioned 512 GB disk with Windows and Data partitions. Windows partition C: has been given 200 GB, enough space to avoid need to expand it later, followed by recovery partition and then last the Data partition:



This makes of course even more sense if you also use Sysprep to relocate the complete Users folder to another drive, allowing C: to be used for Windows and software installs only.

dencal said:

Kari....another Disk Management setup if its any help.. consisting of 2 SSD,s in Raid 0 and a HDD backup.

Thanks :)

John Pombrio said:

I had a lot of troubles due to a corrupted Win 10. Run these two commands in a Administrator cmd window to make sure that Windows is clean:chkdsk /rsfc /scannow

Thanks John for the reply.
First the check disk finished fine, with no problems at all.
Then I tried running sfc scan, and it does the verification part without any problems, but then it gives this error message: "Windows Resource Protection could not start the repair service." But remember, I loaded this as a clean build from an iso, just a few days ago. This was not an upgrade. So why would it NOT be clean? I have tried running it within the system on an admin cprompt, and then I booted into the cprompt outside the os, and it gave me the same error. So is there anyway to overcome this error, or am I stuck with loading from iso every time?

@Kari - another example of GPT