
Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.
“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.
Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.
To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.
Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.
NOTE: While in Admin mode, some apps like OneNote will not run.
Doing this method will make a permanent, but small increase in the free space of the device’s SRP.
a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter.
b. Select System Reserve partition then right-click on it.
c. Choose Change Drive Letter and Paths then select Add.
d. Type Y for the drive letter then click OK.
e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
f. Type Y: at the command prompt then press Enter.
g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.
NOTE: Ensure that the space and period after “f” is included in order for the command to work properly
h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.
NOTE: Ensure that all files are marked as successful and that no files are marked as failed.
i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.
NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.
j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For example: de-DE is the German language while en-US is the U.S. English language.
2. Truncate the NTFS Log:
a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.
b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.
c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.
3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:
a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.
NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.
b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.
a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.
b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.
c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.
This method makes a larger, but temporary, increase in the SRP free space.
1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.
2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.
3. Select Add then type Y for the drive letter, click
4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .
NOTE: Ensure that space and period after “f” are included in order for the command to work properly.
NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.
Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.
Error Code 0xC1900101, 0x4000D is not very common among the many error codes emerging when updating to Windows 10. It is specific to Windows 7 users who try to upgrade to Windows 10 system.
This error hinders Windows 7 users to install the Windows 10 update. Once the update is launched, the process will go smoothly until a certain percentage (normally upon hitting 70% or more) and then it gets stuck. The user will then see a notification stating: “The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation.”
You’ll be able to get past the error after a while. The error message will disappear and continue with the configuration process. But, not for long as it will reoccur at around 90% of installation with another error message saying: “The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.”
You’re most likely to encounter Error Code 0xC1900101 – 0x4000D when you upgrade to Windows 10 using a USB drive. There are several reasons why this update-related error happens such as wrong update, incompatibility with an antivirus program, or incompatibilities with some software.
In attempting to fix error code-related problems, it is best to do manual repair methods. Employing repair methods manually can help users pinpoint the root causes of the issues they are encountering and apply permanent solutions to fix the problem.
While every Windows user can do most manual repair methods, there are certain cases where help from a Windows expert is needed. If you’re not confident in employing the manual repair methods yourself, you can always consider seeking help from a professional Windows technician who is equipped with enough knowledge to address any issues you are facing or you can just simply use a powerful automated tool.
In fixing Error Code 0xC1900101 – 0x4000D, you can try doing any of the following manual repair methods:
Error Code 0xC1900101-0x4000D probably occurs when there are programs running in the background of the system as you are in the process of updating. On that note, you must ensure that any programs running in the background must be disabled through Task Manager.
NOTE: If there are any processes you are unfamiliar with, you can always right-click that process then “search online.” Be careful not to end “Windows process” tasks under the “Type” column as it might cause further problems.
Anti-malware tools normally trigger problems since they consist of files that are possibly incompatible with some software. If Error Code 0xc1900101-0x4000d is caused by incompatibility with an antivirus program, follow the following steps:
In doing this method, you need to use the System Readiness tool.
NOTE: The process might take a while depending on the speed of your device.
Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!
“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. If you’d like to know more, you can search online later for this error: HAL_INITIALIZATION_FAILED HAL INITIALIZATION FAILED 0x0000005C”This kind of Blue Screen error indicates that there is a hardware or device driver problem in your PC. Aside from that, it also signifies that the initialization of the Hardware Abstraction Layer or HAL has failed. This happens only during the relatively short period that the Windows operating system is being initialized, specifically during phase 4 of Windows startup. What’s worse about this kind of Stop error is that it does not just go away after a computer reboot. You may have to boot your computer into Safe mode with Networking using the Advanced startup options which you can access by tapping the F2 or F8 key. Once you’ve accessed the Advanced startup options, follow the fixes prepared below.
chkdsk /f /r