Windows 10: Upgrade from 1607 to 1703, error 0xc1900104

I read online it could indicate that the System Reserved partition ran out of space.

Checking the file "C:\$WINDOWS.~BT\Sources\Panther\setupact.log" I found this line:

Here it is the output of diskpart.exe

Here it is a screenshot of diskmgmt.msc




I managed to free ~100 MB, now it's marked as raw (unallocated space) and it is next to the SRP.
I wish I could merge this space with the SRP but I don't know how to.
As you can see the diskmgmt utility doesn't recognise the SRP while the diskpart program does (it's the 16MB partition marked as hidden, number 3).
What should I do?
Note: I can use Linux utilities but I would like to use Windows ones first if avaiable, I don't want to mess with my installations.
Note: I am currently dual booting with Arch Linux using GRUB on the EFI partition. Arch Linux is installed on Volume 5 (I don't know why is marked as hidden and raw from diskpart and as recovery partition from diskmgmt).

:)

 

Upgrade from 1607 to 1703, error 0xc1900104

Hi,

The error may occur if the System Reserved Partition (SRP) is full often cause by some third-party antivirus and security apps that write to the SRP.

As an initial troubleshooting, we recommend checking this
article for more information on how to resolve error 0xc1900104.

We also suggest checking the suggested troubleshooting on this
thread found on TechNet which was found similar and helpful in resolving the issue as well.

Update us with the outcome so we can provide further assistance.

 

Upgrade from 1607 to 1703, error 0xc1900104

I followed the first
article and now I am donwloading the upgrade so I guess it was succesfull.

I am using a GPT partitioning scheme and File Explorer didn't let me change directory (I guess the Y: device/drive was the problem). I had to manually change directory withing the cmd, here are the commands:

Microsoft Windows [Version 10.0.14393]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\system32>mountvol y: /s

C:\Windows\system32>taskkill /im explorer.exe /f

SUCCESS: The process "explorer.exe" with PID 3528 has been terminated.

C:\Windows\system32>explorer.exe

C:\Windows\system32>Y:

Y:\>ls

EFI grub initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux

Y:\>cd EFI

Y:\EFI>cd Microsoft

Y:\EFI\Microsoft>cd Boot

Y:\EFI\Microsoft\Boot>ls

BCD Resources da-DK es-MX hu-HU kd_02_14e4.dll kd_0C_8086.dll nb-NO ro-RO sv-SE

BCD.LOG bg-BG de-DE et-EE it-IT kd_02_15b3.dll kdstub.dll nl-NL ru-RU tr-TR

BCD.LOG1 boot.stl el-GR fi-FI ja-JP kd_02_1969.dll ko-KR pl-PL sk-SK uk-UA

BCD.LOG2 bootmgfw.efi en-GB fr-CA kd_02_10df.dll kd_02_19a2.dll lt-LT pt-BR sl-SI zh-CN

BOOTSTAT.DAT bootmgr.efi en-US fr-FR kd_02_10ec.dll kd_02_8086.dll lv-LV pt-PT sr-Latn-CS zh-HK

Fonts cs-CZ es-ES hr-HR kd_02_1137.dll kd_07_1415.dll memtest.efi qps-ploc sr-Latn-RS zh-TW

I then deleted all the language files with the command:

rm -r language_file

I changed directory with:

cd ..

I used the Windows utility to check file sizes:

dir /s

The output was:

Total Files Listed:

37 File(s) 18.163.793 bytes

14 Dir(s) 16.337.920 bytes free

Since from the log I needed ~15MB I tried to upgrade again and it was okay. I didn't delete the fonts files, their size was ~13MB by the way (the chineses, korean and japanese fonts were the biggest ones).

 

Good analysis: I generally recommend people have 500 Mb unallocated (it doesn't matter where) when upgrading or doing an in-place upgrade repair install.

Both can result in there being two Win 10 Recovery partitions on disk (the unused one is not deleted - presumably in case of reversion- but it never is deleted automatically).

Try shrinking C: that much.

Diskmgmt doesn't show the 16Mb System partition by design. For that use a 3rd party tool.

 

The file system of the partition is unknown on linux and Windows set it as "other", I didn't find any program that is able to expand it.

 

Minitool Partition Wizard is very often mentioned here.

 

I upgraded succesfully without touching the SRP, I followed the article in this thread.