Tutorial  Updated

Xbox One Internal Hard Drive Upgrade or Repair: Build any size drive that works on any console

THREAD UPDATE FEBRUARY 26, 2020:

Script version 9 has been released!
Version 9 is now completely re-written using PowerShell 5.1 instead of Windows Batch.
As a result, the code structure and process error checking is much improved.
On the downside the new script only supports Windows 10 and above however, the old script is still included and slightly improved as well.

As it stands there are now 3 Windows scripts to choose from and are functionally equivalent:
create_xbox_drive_gui.bat - which includes a graphical interface and is the new primary Xbox One hard drive partitioning script using PowerShell 5.1 for Windows 10 and above
create_xbox_drive.bat - which includes a command line interface similar to the original script using PowerShell 5.1 for Windows 10 and above
create_xbox_drive_old.bat - the original Windows Batch script supporting Windows 7 and above

Also, there is a new COMMON ISSUES section at the bottom of this thread.

Anyone wanting the latest and greatest news about everything Xbox One hard drive related continue reading below.

WHAT THIS IS:

This is a set of scripts that allow you to create a standard/official 2TB, 1TB, or 500GB internal hard drive that works on any Xbox One, Xbox One S, or Xbox One X console and can be reset and remain at that appropriate size. In effect, all Xbox One consoles are potentially 2TB consoles.

Additionally the newer version 7 of the Windows and Linux partitioning scripts can copy your standard/official 2TB, 1TB, or 500GB internal hard drive's content to a new standard 2TB, 1TB, or 500GB HDD, SSD, or SSHD. Version 7 can also copy to non-standard drive sizes between 256GB and 5TB with minimum 138GB and maximum 1947GB of available storage respectively.

In short, you can go from any Xbox One internal standard/official drive size to any other 2.5" standard or non-standard drive size.

These scripts should support systems using any language but particularly on Windows 10 you'll need to have "English (United States)" installed but does not need to be the default language.

For standard sizes this is NOT a hack or mod, this is a script which creates the exact hard drive structure Microsoft uses on each 2TB, 1TB, or 500GB console it sells.

In the several years I've been doing hard drive upgrades and repairs on the Xbox One I'm not aware of a single person being banned for this practice. That said, USE AT YOUR OWN RISK.

INTRO:
I've sat on this particular iteration of the scripts for about a month just to be sure that others were getting the same results that I was able to achieve.

That said, I've had a YouTube channel for about 4 years with the channel's goal being to help people upgrade or replace their existing and potentially broken Xbox One hard drive.

Larger 5TB, 4TB, and 3TB 2.5" hard drives have been around for some time but Microsoft has only officially supported up to 2TB drive sizes and will likely never support anything beyond this. Internally speaking of course, externally you can attach up to 16TB.
Xbox One internal drives have a 2TB limit that you cannot get around. This is a bug or feature by Microsoft's design.

While a big feature of this script is the ability to change any Xbox One to a 2TB, 1TB, or 500GB standard console that can be "Reset" at any time, the big caveat of non-standard sizes is that performing a console "Reset" will incorrectly format a non-standard drive requiring the recreation of a standard 2TB, 1TB, or 500GB drive.
That being said, resetting your console should be a rare occurrence.

Reddit user A1DR1K sent a message to me on YouTube informing me that he had figured out how the Xbox One determines drive size and it isn't tied to the console itself but rather the disk GUID.
This is a big deal. With a properly partitioned drive any console can use any size drive at any time. Officially Microsoft has defined 2TB, 1TB, and 500GB drive sizes and the latest script now supports them all.

So without further ado the script:
xboxonehdd-master-9.zip or use Google Drive

WHAT YOU NEED:
Aside from the scripts to partition a 2TB, 1TB, or 500GB drive you'll need or need to do the following:
  1. You have to be willing to open your console and potentially void the 1 year or extended warranty.
  2. When doing a 'Repair or Replace' a 2.5" HDD, SSD, or SSHD SATA drive with a minimum capacity of 500GB. You can use a drive larger than 2TB but you can only partition it as 2TB.
  3. When doing an 'Upgrade' a working standard/official 2.5" 2TB, 1TB, or 500GB source drive.
  4. When doing an 'Upgrade' a 2.5" HDD, SSD, or SSHD SATA target drive. This can be 5TB, 4TB, 3TB or 256GB but it can also be a standard size as well. For example, maybe you just want to upgrade from 500GB to 2TB.
  5. A way to attach 1 or 2 2.5" HDD, SSD, or SSHD SATA drives to a Windows or Linux desktop or laptop. This can be a SATA to USB adapter or installing the SATA drive temporarily in said desktop or laptop. I recommend the USB3S2SAT3CB .
  6. When doing a 'Repair or Replace' an 8GB or larger NTFS USB Flash drive to extract the contents OSU1.zip to.
  7. When using Linux instead of Windows another 8GB or larger FAT32 USB Flash drive for creating an Ubuntu Live USB Flash Drive.
REPAIR, REPLACE, OR UPGRADE AN XBOX ONE DRIVE USING WINDOWS:
I've created a detailed walk through found within the xboxonehdd-master-9.zip file:
xboxonehdd-master\win\readme_windows.txt
Last Updated: 2019/10/23
Author: XFiX
https://gbatemp.net/threads/xbox-on...-size-drive-that-works-on-any-console.496212/
https://www.youtube.com/playlist?list=PLURaLwRqr6g14Pl8qLO0E4ELBBCHfFh1V

Creates a properly partitioned Xbox One hard drive. You'll want to source the
entire original drive files or use the latest OSU1 files.

FEATURES:
1. Create a Standard Xbox One 500GB, 1TB, or 2TB internal hard drive
2. Upgrade a Standard Xbox One drive to non-standard sizes including
as small as 138GB, as large as 1947GB, and other non-standard sizes
3. Set Standard Xbox One GUID values without formatting the drive
4. Backup "System Update" to current directory System_Update and more
5. Restore "System Update" from current directory System_Update and more
6. Check all partitions for file system errors using chkdsk
7. Wipe drive of all partitions and GUID values

This script is a direct replacement to create_xbox_drive.sh for Linux:
create_xbox_drive_old.bat is tested and works on Windows 7 and 10
create_xbox_drive.bat and create_xbox_drive_gui.bat are tested and only work
on Windows 10

You'll need some sort of USB to SATA device or have the ability to connect a
SATA drive directly to your PC. I recommend the USB3S2SAT3CB USB 3.0 to SATA
adapter cable.


NOTES AND WARNINGS:
NOTE 1: Xbox One internal drives have a 2TB limit that you cannot get around.
This is a bug or feature by Microsoft's design.
This is the video I made trying to fill a 5TB internal drive.

Version 7.0 and above max the "User Content" partition out at 1947GB.
Theoretically you can created a larger partition than this but you
cannot use the additional space.

NOTE 2: You need to run this script from an Administrator Command Prompt
using the "Run as administrator" feature.

NOTE 3: For this script to work on non-English Windows systems
C:\Windows\System32\en-US needs to be present.
Control Panel\All Control Panel Items\Language\Add languages
English (United States)

NOTE 4: Click "Cancel" or "X" on any "You need to format the disk in drive ?:
before you can use it." messages.

NOTE 5: diskmgmt.msc is your friend. Keep it open while running this script
to check progress and verify proper partitioning and formatting.

WARNING 1: E100 is bad. It is possible to do an offline update to resolve it
but this mostly isn't the case. E100 is the only know error that
actually refers to the Blu-ray drive. Under certain circumstances
during an Xbox One update the Blu-ray drive firmware can become
permanently corrupted. Any sort of Blu-ray drive failure involving
the daughterboard will brick your system since only the original
factory matching Xbox One motherboard and Blu-ray daughterboard can
be used together.
YOU CANNOT REPLACE A BLU-RAY DAUGHTERBOARD FROM ANOTHER SYSTEM!

WARNING 2: Only have one Xbox One or future Xbox One drive connected when
running this script to ensure the right drive gets formatted and
avoid Offline signature collisions!

This means disconnecting the SOURCE drive after:
(b) Replace/Upgrade keeping original drive data
but before:
(c) Fix GUID values without formatting the drive
When redoing the entire process run this step on the TARGET with
the SOURCE disconnected:
(g) Wipe drive of all partitions and GUID values

WARNING 3: Always use "Safely Remove Hardware and Eject Media" and "Eject" the
newly created drive.
If you receive the message: "Windows can't stop your
'Generic volume' device because a program is still using it."
Either shutdown your system and remove the drive or use
diskmgmt.msc right click the disk, select "Offline", then "Online"
and then "Safely Remove Hardware and Eject Media" and "Eject".

SCRIPT FUNCTIONS EXPLAINED:
(a) Replace/Upgrade without a working original drive (Standard Only) - used to fix systems when the original drive has failed
(b) Replace/Upgrade keeping original drive data (Standard and Non) - used to swap to a smaller or larger standard or non-standard drive
(c) Fix GUID values without formatting the drive (Standard and Non) - should be used after step (b) and after disconnecting the SOURCE drive
(d) Backup "System Update" to current directory (Standard and Non) - use before doing a Reset or Upgrade, better safe than sorry
(e) Restore "System Update" from current directory (Standard and Non) - use after doing a Reset or Upgrade, told you so
(f) Check all partitions for file system errors (Standard and Non) - optionally check for filesystem corruption or prepare for Clonezilla
(g) Wipe drive of all partitions and GUID values (Standard and Non) - used to blank a drive before rerunning step (b)
(h) CANCEL

PARTITION LAYOUT:
There are 5 partitions on an Xbox One drive. The 2nd partition 'User Content'
is what this selection refers to. The other 4 partitions are always the same
size regardless of the drive size.

All partitions are rounded to the nearest gibibyte (normally and not to be
confused with gigabyte). So options (d) through (g) will mostly do the right
thing. Options (a) through (c) are for wanting to force a particular size on
the target drive.

Most people should choose (a), (b), or (c). If you have a 256GB or 750GB you
should select (d). For 3TB, 4TB, or 5TB drives you should select (f).

(a) 500GB Standard (365GB) (779MB Unallocated)
(b) 1TB Standard (781GB) (50.51GB Unallocated)
(c) 2TB Standard (1662GB) (101.02GB Unallocated)
(d) Autosize Non-Standard w/ 500GB Disk GUID (1947GB MAX) - create an autosized 'User Content' resetting to 500GB
(e) Autosize Non-Standard w/ 1TB Disk GUID (1947GB MAX) - create an autosized 'User Content' resetting to 1TB
(f) Autosize Non-Standard w/ 2TB Disk GUID (1947GB MAX) - create an autosized 'User Content' resetting to 2TB


REPAIR AND UPGRADE PATHS:
Xbox One Internal Hard Drive Backup and Restore Upgrade

Menu roadmap:
(d) Backup "System Update" to current directory (Standard and Non)
(a) Replace/Upgrade without a working original drive (Standard Only)
(e) Restore "System Update" from current directory (Standard and Non)


Xbox One Internal Hard Drive Direct Copy Upgrade

Menu roadmap:
(b) Replace/Upgrade keeping original drive data (Standard and Non)
(c) Fix GUID values without formatting the drive (Standard and Non)


Xbox One Internal Hard Drive Repair or Replace Using

Menu roadmap:
(a) Replace/Upgrade without a working original drive (Standard Only)


EXAMPLE SCRIPT USAGE AND OUTPUT:
1. Unzip xboxonehdd-master-8.1.zip to the Desktop which will create an xboxonehdd-master directory
2. Open an Administrator Command Prompt:
Windows 7: Click "Start Menu -> All Programs -> Accessories" right click "Command Prompt" select "Run as administrator"
Windows 10 1607 and earlier: Right click "Start Menu" select "Command Prompt (Admin)"
Windows 10 1703 and later: Right click "Start Menu" select "Windows PowerShell (Admin)"
3. In the Command Prompt paste:
Command Prompt:
cd %USERPROFILE%\Desktop\xboxonehdd-master\win
Windows PowerShell:
cd $Env:USERPROFILE\Desktop\xboxonehdd-master\win
4. Then paste:
.\create_xbox_drive.bat

5. Follow all the prompts and be sure to select the appropriate drive. Example below:

**********************************************************************
* create_xbox_drive.ps1:
* This script creates a correctly formatted Xbox One HDD against the
* drive YOU select.
* USE AT YOUR OWN RISK
*
* Created 2019.10.08.8.1
* Last Updated 2019.10.22.8.1
* Now 2019.10.23 21:50:28
* PowerShell 5.1.18362.145
* Windows 10.0.18362
* PWD C:\Users\XFiX\Desktop\xboxonehdd-master\win
* System Type Intel64
* Language ID 0409
* Language UI en-US
**********************************************************************

* Administrative permissions confirmed *

* Are required drive letters available? Checking... *
* H: is free
* I: is free
* J: is free
* K: is free
* L: is free
* Found U: - Fixed Drive - Temp Content
* Found V: - Fixed Drive - User Content
* Found W: - Fixed Drive - System Support
* Found X: - Fixed Drive - System Update
* Found Y: - Fixed Drive - System Update 2

* WARNING: Any non-free drive letters above may interfere with this *
* script. Adjust the letters used in the 'Changeable drive *
* letters' section near the top of this script. *
* If you have an Xbox One drive attached non-free drive *
* letters are expected. *

Press any key to continue . . .

Select Xbox One drive creation type:
(a) Replace/Upgrade without a working original drive (Standard Only)
(b) Replace/Upgrade keeping original drive data (Standard and Non)
(c) Fix GUID values without formatting the drive (Standard and Non)
(d) Backup "System Update" to current directory (Standard and Non)
(e) Restore "System Update" from current directory (Standard and Non)
(f) Check all partitions for file system errors (Standard and Non)
(g) Wipe drive of all partitions and GUID values (Standard and Non)
(h) CANCEL

?: a
"a" was selected

* Scanning for connected USB/SATA drives . . . *
Disk Size Free Name
1 3726 GB 0 GB WDC WD40EZRX-00SPEB0
2 3726 GB 0 GB WDC WD40EZRX-00SPEB0
3 1863 GB 101 GB ASMT 2115

* Select TARGET Xbox One Drive . . . *
Enter c to CANCEL or use a Disk Number from the list above
?: 3
"3" was selected

GUID Dev Size Name
5B114955-4A1C-45C4-86DC-D95070008139 (2TB)
B3727DA5-A3AC-4B3D-9FD6-2EA54441011B U: 41 GB 'Temp Content'
869BB5E0-3356-4BE6-85F7-29323A675CC7 V: 1662 GB 'User Content'
C90D7A47-CCB9-4CBA-8C66-0459F6B85724 W: 40 GB 'System Support'
9A056AD7-32ED-4141-AEB1-AFB9BD5565DC X: 12 GB 'System Update'
24B2197C-9D01-45F9-A8E1-DBBCFA161EB2 Y: 7 GB 'System Update 2'


WARNING: This will erase all data on this disk. Continue [Y,N]?: y

* Disk 3 will be formatted as an Xbox One Drive . . . *

Select partition layout:
(a) 500GB Standard (365GB)
(b) 1TB Standard (781GB)
(c) 2TB Standard (1662GB)
(d) CANCEL

?: c
* Removing existing partitions with Clear-Disk . . . *

GUID Dev Size Name
A2A1044F-42EF-4279-B915-377EA82A63C3 (Unknown)

* Creating partition 1 with 44023414784 bytes . . .
* Creating partition 2 with 1784558911488 bytes . . .
* Creating partition 3 with 42949672960 bytes . . .
* Creating partition 4 with 12884901888 bytes . . .
* Creating partition 5 with 7516192768 bytes . . .

* Changing disk and partition GUID values with C:\Users\XFiX\Desktop\xboxonehdd-master\win\gdisk64 . . .

* Formatting and labeling partition 'Temp Content' . . .
* Formatting and labeling partition 'User Content' . . .
* Formatting and labeling partition 'System Support' . . .
* Formatting and labeling partition 'System Update' . . .
* Formatting and labeling partition 'System Update 2' . . .

GUID Dev Size Name
5B114955-4A1C-45C4-86DC-D95070008139 (2TB)
B3727DA5-A3AC-4B3D-9FD6-2EA54441011B U: 41 GB 'Temp Content'
869BB5E0-3356-4BE6-85F7-29323A675CC7 V: 1662 GB 'User Content'
C90D7A47-CCB9-4CBA-8C66-0459F6B85724 W: 40 GB 'System Support'
9A056AD7-32ED-4141-AEB1-AFB9BD5565DC X: 12 GB 'System Update'
24B2197C-9D01-45F9-A8E1-DBBCFA161EB2 Y: 7 GB 'System Update 2'

* Found Drive X: 'System Update'

* Script execution complete.
* Ended: 2019.10.23 21:51:50
* Script ran for 81 seconds

Press any key to continue . . .

6. The last bit of output should look like the following, except for the
first line depending on the drive size, if not run the script again:
A2344BDB-D6DE-4766-9EB5-4109A12228E5 (500GB)
25E8A1B2-0B2A-4474-93FA-35B847D97EE5 (1TB)

GUID Dev Size Name
5B114955-4A1C-45C4-86DC-D95070008139 (2TB)
B3727DA5-A3AC-4B3D-9FD6-2EA54441011B U: 41 GB 'Temp Content'
869BB5E0-3356-4BE6-85F7-29323A675CC7 V: 365 GB 'User Content'
C90D7A47-CCB9-4CBA-8C66-0459F6B85724 W: 40 GB 'System Support'
9A056AD7-32ED-4141-AEB1-AFB9BD5565DC X: 12 GB 'System Update'
24B2197C-9D01-45F9-A8E1-DBBCFA161EB2 Y: 7168 MB 'System Update 2'

7. To view the log file paste this:
Command Prompt:
notepad %TEMP%\create_xbox_drive.log
notepad %TEMP%\create_xbox_drive_cli.log
notepad %TEMP%\create_xbox_drive_gui.log
notepad %TEMP%\RoboCopy-Temp_Content.log
notepad %TEMP%\RoboCopy-User_Content.log
notepad %TEMP%\RoboCopy-System_Support.log
notepad %TEMP%\RoboCopy-System_Update.log
notepad %TEMP%\RoboCopy-System_Update_2.log
Windows PowerShell:
notepad $Env:TEMP\create_xbox_drive.log
notepad $Env:TEMP\create_xbox_drive_cli.log
notepad $Env:TEMP\create_xbox_drive_gui.log
notepad $Env:TEMP\RoboCopy-Temp_Content.log
notepad $Env:TEMP\RoboCopy-User_Content.log
notepad $Env:TEMP\RoboCopy-System_Support.log
notepad $Env:TEMP\RoboCopy-System_Update.log
notepad $Env:TEMP\RoboCopy-System_Update_2.log

8. OPTIONAL (skip if OSU1 doesn't match the last successful update):
Download the latest OSU1.zip which contains the files:

$SystemUpdate/host.xvd
$SystemUpdate/SettingsTemplate.xvd
$SystemUpdate/system.xvd
$SystemUpdate/systemaux.xvd
$SystemUpdate/systemmisc.xvd
$SystemUpdate/systemtools.xvd
$SystemUpdate/updater.xvd

Place them in the 'System Update' partition as:

A/host.xvd
A/SettingsTemplate.xvd
A/system.xvd
A/systemaux.xvd
A/systemmisc.xvd
A/systemtools.xvd
B/host.xvd
B/SettingsTemplate.xvd
B/system.xvd
B/systemaux.xvd
B/systemmisc.xvd
B/systemtools.xvd
updater.xvd

Also I walk you through the entire process in the following videos:

Repair or Replace Using Windows:


Direct Copy Upgrade Using Windows:


Backup and Restore Upgrade Using Windows:


REPAIR, REPLACE, OR UPGRADE AN XBOX ONE DRIVE USING LINUX:
I've created a detailed walk through found within the xboxonehdd-master-8.zip file:
xboxonehdd-master/linux/readme_linux.txt
Last Updated: 2018/11/16
Author: XFiX
https://gbatemp.net/threads/xbox-on...-size-drive-that-works-on-any-console.496212/
https://www.youtube.com/playlist?list=PLURaLwRqr6g14Pl8qLO0E4ELBBCHfFh1V

Creates a properly partitioned Xbox One hard drive. You'll want to source the
entire original drive files or use the latest OSU1 files.

FEATURES:
1. Wipe drive of all partitions and GUID values
2. Create a Standard Xbox One 500GB, 1TB, or 2TB internal hard drive
3. Upgrade a Standard Xbox One drive to non-standard sizes including
as small as 138GB, as large as 1947GB, and other non-standard sizes
4. Set Standard Xbox One GUID values w/o formatting the drive

Make an "UBUNTU FAT32" flash drive with ubuntu-17.10.1-desktop-amd64.iso or
newer created with LinuxLive USB Creator 2.9.4.exe

Download Linux Live USB Creator:
http://www.linuxliveusb.com/en/download

Download Ubuntu Desktop:
https://www.ubuntu.com/download/desktop

You'll need some sort of USB to SATA device or have the ability to connect a
SATA drive directly to your PC. I recommend the USB3S2SAT3CB USB 3.0 to SATA
adapter cable.


NOTES AND WARNINGS:
NOTE 1: Xbox One internal drives have a 2TB limit that you cannot get around.
This is a bug or feature by Microsoft's design.
This is the video I made trying to fill a 5TB internal drive.

Version 7.0 and above max the "User Content" partition out at 1947GB.
Theoretically you can created a larger partition than this but you
cannot use the additional space.

WARNING 1: E100 is bad. It is possible to do an offline update to resolve it
but this mostly isn't the case. E100 is the only know error that
actually refers to the Blu-ray drive. Under certain circumstances
during an Xbox One update the Blu-ray drive firmware can become
permanently corrupted. Any sort of Blu-ray drive failure involving
the daughterboard will brick your system since only the original
factory matching Xbox One motherboard and Blu-ray daughterboard can
be used together.
YOU CANNOT REPLACE A BLU-RAY DAUGHTERBOARD FROM ANOTHER SYSTEM!


REPAIR AND UPGRADE PATHS:
Xbox One Internal Hard Drive Direct Copy Upgrade


Xbox One Internal Hard Drive Repair or Replace



EXAMPLE SCRIPT USAGE AND OUTPUT:
1. Unzip xboxonehdd-master-7.zip to the root of the "UBUNTU FAT32" flash drive which will create an xboxonehdd-master directory
2. Boot the "UBUNTU FAT32" flash drive and choose "Try Ubuntu"
3. Right click the desktop and select "Open Terminal"
4. cd /media/cdrom/xboxonehdd-master/linux
5. Use the following command to find the drive you wish to partition, /dev/sdb in my case but your case may be different:
sudo ./list_part_info.sh

Current Drive List:
Disk /dev/sda: 480GB
Disk /dev/sdb: 2000GB
Disk /dev/sdc: 16.0GB

Usage: list_part_info.sh /dev/sd*

Examples:
list_part_info.sh /dev/sdb (List Disk Partition Information)

6. sudo ./create_xbox_drive.sh

Last Updated: 2018.05.10.7.0
Usage: create_xbox_drive.sh [options]

Options:
-c|--source Source drive to copy data to target drive -d with -s 2
-d|--drive Target drive to install Xbox filesystem
-s|--stage Install stage [0|1|2|3]
0 - will fully erase drive -d
1 - will erase and partition drive -d
2 - will copy source drive -c data to target drive -d
3 - will rewrite drive -d GUIDs
-t|--disktype Disk GUID to set [0|1|2]
0 - 500GB
1 - 1TB
2 - 2TB
-m|--mirror Mirror standard partition sizes specified with -t on drive -d
Not using this option will autosize 'User Content'
-h|--help Display help

Examples:
create_xbox_drive.sh -d /dev/sdb -s 0 (Erase a drive)
create_xbox_drive.sh -d /dev/sdb -s 1 -t 2 -m (Partition standard 2TB drive)
create_xbox_drive.sh -d /dev/sdb -s 3 -t 2 -m (Rewrite 2TB GUIDs)

7. First erase and partition the specified drive:

NOTE: Replace /dev/sdb with your drive, change -t 2 to -t 0 for
500GB drives and -t 1 for 1TB drives, and optionally use -m to force
standard Xbox One Partition sizes

sudo ./create_xbox_drive.sh -d /dev/sdb -s 1 -t 2 -m
8. OPTIONAL (skip if you don't have a working standard Xbox One drive):
Second if you have a working standard Xbox One drive you can copy the data
from that drive to the new drive with:

NOTE: Replace /dev/sda with your source drive, /dev/sdb with your target
drive, change -t 2 to -t 0 for 500GB drives and -t 1 for 1TB drives, and
optionally use -m to force standard Xbox One Partition sizes

sudo ./create_xbox_drive.sh -c /dev/sda -d /dev/sdb -s 2 -t 2 -m
9. Third rewrite the drive GUID values to Xbox One compatible ones:

NOTE: Again replace /dev/sdb with your drive, change -t 2 to -t 0 for
500GB drives and -t 1 for 1TB drives, and optionally use -m to force
standard Xbox One Partition sizes

sudo ./create_xbox_drive.sh -d /dev/sdb -s 3 -t 2 -m
10. Check to see that your newly created drive matches the output below:
5B114955-4A1C-45C4-86DC-D95070008139 /dev/sd* (2TB)
25E8A1B2-0B2A-4474-93FA-35B847D97EE5 /dev/sd* (1TB)
A2344BDB-D6DE-4766-9EB5-4109A12228E5 /dev/sd* (500GB)

sudo ./list_part_info.sh /dev/sdb
GUID Dev Size Name
5B114955-4A1C-45C4-86DC-D95070008139 /dev/sdb (2TB)
B3727DA5-A3AC-4B3D-9FD6-2EA54441011B /dev/sdb1 (41.0 GiB) 'Temp Content'
869BB5E0-3356-4BE6-85F7-29323A675CC7 /dev/sdb2 (1.6 TiB) 'User Content'
C90D7A47-CCB9-4CBA-8C66-0459F6B85724 /dev/sdb3 (40.0 GiB) 'System Support'
9A056AD7-32ED-4141-AEB1-AFB9BD5565DC /dev/sdb4 (12.0 GiB) 'System Update'
24B2197C-9D01-45F9-A8E1-DBBCFA161EB2 /dev/sdb5 (7.0 GiB) 'System Update 2'

11. OPTIONAL (skip if you are able to do step 8, also skip if OSU1 doesn't
match the last successful update):
Mount /media/ubuntu/System\ Update/ by right clicking the proper drive in
the left hand menu and select Open
12. OPTIONAL (skip if you are able to do step 8, also skip if OSU1 doesn't
match the last successful update):
Download the latest OSU1.zip which contains the files:

$SystemUpdate/host.xvd
$SystemUpdate/SettingsTemplate.xvd
$SystemUpdate/system.xvd
$SystemUpdate/systemaux.xvd
$SystemUpdate/systemmisc.xvd
$SystemUpdate/systemtools.xvd
$SystemUpdate/updater.xvd

Place them in the 'System Update' partition as:

A/host.xvd
A/SettingsTemplate.xvd
A/system.xvd
A/systemaux.xvd
A/systemmisc.xvd
A/systemtools.xvd
B/host.xvd
B/SettingsTemplate.xvd
B/system.xvd
B/systemaux.xvd
B/systemmisc.xvd
B/systemtools.xvd
updater.xvd

Also I walk you through the entire process in the following videos:

Repair or Replace Using Linux:


Direct Copy Upgrade Using Linux:


CONCLUSION:
While the PS4 will always have the advantage when it comes to internal hard drive upgrading and replacement in terms of difficulty.
Now the Xbox One can finally support the same functionality.

Finally, if you want to know if the Xbox One X is using Internal SATA3 over the Xbox One S and original models SATA2.
Perhaps you want to know how much faster an SSHD, SSD, or 7200RPM HDD would be in comparison to a stock 5400RPM HDD.

Look no further than lilhed's video:


COMMON ISSUES:
A couple quick points about the E101 error and offline updates:
  1. When doing an offline update using the contents of OSU1.zip extracted to an NTFS formatted USB drive and you are greeted with an E101 error 9 times out of 10 your system is part of the dashboard preview program and is newer than the current OSU1 version. The current OSU1 version is 10.0.17763.4088 as of 2019/04/09. If your version is newer than this you will have to wait until the OSU1.zip version is updated past your version. Alternatively, if you have another console in the dashboard preview program you could copy over it's "System Update" A and B folders.
  2. In 2019 OSU2.zip and OSU3.zip are useless. They haven't been updated in years and are for updating Xbox One OS 6.3 and day one consoles respectively. Don't waste your time with these.
The E100 error is a Blu-ray drive issue NOT the hard drive. Do NOT swap Blu-ray drives between systems.
You may see an E100 error during an offline update likely relating to a failed Blu-ray firmware update. Sometimes this can be resolved by forcing the offline update a second time.
For more information check out the following video:


Update May 14, 2019 E105 and E102 errors on Xbox One X models:
There does appear to be an epidemic with Xbox One X consoles suddenly producing E105 errors and then E102 when trying to force an OSU1 offline update.
This does appear to be file/data corruption rather than a physical hardware issue and I believe there is an OS bug in combination with increased system temperatures.
Often leaving the system off for a while resolves the bad behavior only to resurface when the system heats up again.
If under warranty call Microsoft, if not I would suggest 3 things if you have the means.
  1. Wipe the disk and start with a cleanly formatted Xbox One disk.
  2. Many have mentioned doing step 1 with a new HDD or SSHD only fixes the issue temporarily. In which case upgrading to an SSD may help. SSD drives produce and are less affected by heat.
  3. Change the (APU) thermal paste. I recommend Arctic Silver 5 but any high quality paste will do.
 
Last edited by tai1976,

Rj.MoG

Well-Known Member
Member
Joined
Jun 8, 2015
Messages
377
Trophies
0
Age
32
XP
1,479
Country
United States

ford22

Member
Newcomer
Joined
Feb 3, 2020
Messages
10
Trophies
0
Age
31
XP
49
Country
Poland
Hello, I want to know if someone has a backup, maybe I will drop quality files to me because I have been deleted, all files have not been lost.
 

Rj.MoG

Well-Known Member
Member
Joined
Jun 8, 2015
Messages
377
Trophies
0
Age
32
XP
1,479
Country
United States
Gotcha, you're correct. Makes sense as my friend's console stopped working on January 1, so he was exactly 1 update behind.
I bought an Xbox used, updated it, removed the files off the HDD and returned it. My xbone works fine now
Hello, I want to know if someone has a backup, maybe I will drop quality files to me because I have been deleted, all files have not been lost.
Backup of what??
 

CaptainProton

New Member
Newbie
Joined
Feb 8, 2020
Messages
1
Trophies
0
Age
40
XP
45
Country
United States
So I recently completed following the steps as best as I could. I am using a Samsung 960GB SSD, so I had to pick one of the non-standard options, and while it looked like it went through the process successfully and I was able to update the disk using the USB drive I create with the system update, the XBOX is only showing something in the realm of 377GB for the available capacity and not the 794 that should be available per the partitioning performed.



**********************************************************************
* create_xbox_drive.bat: *
* This script creates a correctly formatted Xbox One HDD against the *
* drive YOU select. *
* USE AT YOUR OWN RISK *
* *
* Created 2016.06.30.2.0 *
* Last Updated 2018.11.13.8.0 *
* Language ID 0409 *
* Language UI en-US *
**********************************************************************

* Administrative permissions required. Detecting permissions... *
* Administrative permissions confirmed *

* Are required drive letters available? Checking... *
* H: is free
* I: is free
* J: is free
* K: is free
* L: is free
* U: is free
* V: is free
* W: is free
* X: is free
* Y: is free

* WARNING: Any non-free drive letters above may interfere with this *
* script. Adjust the letters used in the "Changeable drive *
* letters" section near the top of this script. *
* If you have an Xbox One drive attached non-free drive *
* letters are expected. *


Press any key to continue . . .
"This is a 64 Bit Operating System"

Select Xbox One drive creation type:
(a) Replace/Upgrade w/o a working original drive (Standard Only)
(b) Replace/Upgrade keeping original drive data (Standard and Non)
(c) Fix GUID values w/o formatting the drive (Standard and Non)
(d) Backup "System Update" to current directory (Standard and Non)
(e) Restore "System Update" from current directory (Standard and Non)
(f) Check all partitions for file system errors (Standard and Non)
(g) Wipe drive of all partitions and GUID values (Standard and Non)
(h) CANCEL

?b


* Scanning for connected USB/SATA drives . . . *

Microsoft DiskPart version 10.0.19559.1000

Copyright (C) Microsoft Corporation.

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 93 GB *
Disk 1 Online 894 GB 894 GB *

* Select SOURCE Xbox One Drive . . . *
Enter 2 to CANCEL or use a Disk Number from the list above
?1

* Does selected disk contain C: Checking... *
* Does not contain C: can continue *

* Assigning drive letters with C:\WINDOWS\system32\diskpart . . . *
* Scanning for connected USB/SATA drives . . . *

Microsoft DiskPart version 10.0.19559.1000

Copyright (C) Microsoft Corporation.

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 93 GB *
Disk 1 Online 894 GB 894 GB *

* Select TARGET Xbox One Drive . . . *
Enter 2 to CANCEL or use a Disk Number from the list above
?1

* Does selected disk contain C: Checking... *
* Does not contain C: can continue *


GUID Dev Size Name
B85EB70C-81C5-413E-AE35-62F7F77BA358

WARNING: This will erase all data on this disk. Continue [Y,N]?Y

* Disk 1 will be formatted as an Xbox One . . . *


Select partition layout:
(a) 500GB Standard (365GB)
(b) 1TB Standard (781GB)
(c) 2TB Standard (1662GB)
(d) Autosize Non-Standard w/ 500GB Disk GUID (1947GB MAX)
(e) Autosize Non-Standard w/ 1TB Disk GUID (1947GB MAX)
(f) Autosize Non-Standard w/ 2TB Disk GUID (1947GB MAX)
(g) CANCEL

?e

* Removing existing partitions with gdisk64 . . . *
* Creating new partitions with gdisk64 . . . *
* Updating GUID values with gdisk64 . . . *



Microsoft DiskPart version 10.0.19559.1000

Copyright (C) Microsoft Corporation.

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 836 GB Healthy Boot
Volume 1 SYSTEM FAT32 Partition 100 MB Healthy System
Volume 2 D Temp Conten NTFS Partition 41 GB Healthy
Volume 3 E User Conten NTFS Partition 794 GB Healthy
Volume 4 F RAW Partition 40 GB Healthy
Volume 5 G RAW Partition 12 GB Healthy
Volume 6 H RAW Partition 7168 MB Healthy

* Formatting new partitions with C:\WINDOWS\system32\format . . . *
* Formatting with C:\WINDOWS\system32\diskpart . . . *
* Assigning drive letters with C:\WINDOWS\system32\diskpart . . . *

WARNING: About to copy to the TARGET disk. Continue [Y,N]?Y

* Missing 'Temp Content' U:
* Missing 'User Content' V:
* Missing 'System Support' W:
* Missing 'System Update' X:
* Missing 'System Update 2' Y:
* Something is missing, cannot copy data

Microsoft DiskPart version 10.0.19559.1000

Copyright (C) Microsoft Corporation.

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 836 GB Healthy Boot
Volume 1 SYSTEM FAT32 Partition 100 MB Healthy System
Volume 2 H DTemp Conte NTFS Partition 41 GB Healthy
Volume 3 I DUser Conte NTFS Partition 794 GB Healthy
Volume 4 J DSystem Sup NTFS Partition 40 GB Healthy
Volume 5 K DSystem Upd NTFS Partition 12 GB Healthy
Volume 6 L DSystem Upd NTFS Partition 7168 MB Healthy


* Missing Drive X: 'System Update'. *

* Script execution complete. *

Press any key to continue . . .










Is there a different combination of options I should have selected for setting up this disk? I have no means of connecting both the original disk and the new one simultaneously, though "B" was the only option for non-standard disk sizes that allowed me to partition the disk appropriately.

Any suggestions or is this a hard issue with using a 960GB disk rather than a normal 1TB? Considering since version 7 of the script, it says it's compatible with non-standard sizes, so this shouldn't be an issue anymore, correct?
 

djinc91

The Canadian
Member
Joined
May 19, 2019
Messages
141
Trophies
0
XP
1,110
Country
Canada
Any suggestions or is this a hard issue with using a 960GB disk rather than a normal 1TB? Considering since version 7 of the script, it says it's compatible with non-standard sizes, so this shouldn't be an issue anymore, correct?
While it should be possible to get your non-standard sized drive working, it is better to avoid them if possible as if you ever need to perform a system reset through the console or OSU1 you will likely find it will reformat your drive to the incorrect size or not successfully format it at all.

If you are willing to live with that then we can continue. I would try to format the drive again within windows so it is a blank NTFS drive then run the script again. Your chosen settings look correct however the drives should be U V W X Y and the output appears to be H I J K L. If you run the script again and get these drive letters I would try changing them manually through Windows afterwards and see if it works.
 

Flinox

Member
Newcomer
Joined
Feb 9, 2020
Messages
7
Trophies
0
Age
43
XP
46
Country
Brazil
Hello guys,

I have a problem with an update of omega ring version of xbox inside program and my xbox got stuck on the screen
"Something Went Wrong" error E101 00000504 8B050041, then I try the troubleshoot to do the factory reset and I get the
error E106 00000009 C0000102 and I get stuck in that loop. The OS system version is 19h1_release_xbox_dev_2002.200128-2000.

I tried to apply the OSU1 offline update solution, but after I found out it will not work for
who is part of the xbox inside program, because the OSU1 is the current retail version and what I have on my xbox
is a higher version ( because I'm part of xbox inside program ).

I recently read this post on common issues about replacing XBOX internal HD that after an OSU1 on a console that is part of
Xbox inside program, one of the alternatives to fix this would be to have another Xbox that is also part of the
program and copy the entire contents of the $SystemUpdate partition and take it to the same partition on the bricked console.

Has anyone ever experienced this? Does anyone know if this solution works?
Would anyone have this contents of $SystemUpdate from a console that is in the xbox inside program
and have OS version 19h1_release_xbox_dev_2002.200128-2000 or higher to share?

I appreciate that!

Thank you guys.
 

djinc91

The Canadian
Member
Joined
May 19, 2019
Messages
141
Trophies
0
XP
1,110
Country
Canada
Has anyone ever experienced this? Does anyone know if this solution works?
Yes, it is ridiculously common, stay away from insider previews etc. and yes that solution works as long as it it matched with the same hardware revision (OG, S, X)
If nobody has the software you'll just have to wait for an update from Microsoft.
 
  • Like
Reactions: Flinox

Flinox

Member
Newcomer
Joined
Feb 9, 2020
Messages
7
Trophies
0
Age
43
XP
46
Country
Brazil
Yes, it is ridiculously common, stay away from insider previews etc. and yes that solution works as long as it it matched with the same hardware revision (OG, S, X)
If nobody has the software you'll just have to wait for an update from Microsoft.

Lessons learned !!
Well, I will wait for an update !!

Thank you !!
 

BDGums

Member
Newcomer
Joined
Feb 11, 2020
Messages
7
Trophies
0
Age
52
XP
48
Country
United States
Hello all, brand newbie here...not a gamer but a father trying to help my daughter fix her Xbox One S (1 TB). I came across this thread during my research and have successfully partitioned a new HDD (2 TB Firecuda), however, I am still having problems getting the Xbox up and running. I am hopeful that someone can offer some insight on what to do next, whether it be suggesting additional steps to try or recommending throwing in the towel and sending the unit back to Microsoft.


BACKGROUND

My daughter's lightly used (new Xmas 2019, prolly <15 hrs/week for Minecraft and occasional Left 4 Dead) came down with the E200 error ~3-4 weeks ago, not exactly sure when as I didn't find out about it until well after my wife had started trying to fix it herself by attempting an offline system update per the Microsoft web instructions. Whatever she did, the offline update would always get stuck at 66% applying/86% total and would return to the "Something went wrong" screen.

I tried the offline update myself, confirmed the USB drive was formatted NTFS, reformatted the USB drive, re-downloaded/re-extracted OSU1 with no luck. Also tried re-setting the console to system defaults (both save games option and erase everything option), as well as leaving the console unplugged for 24+ hours multiple times. Always the same result - returning to the something went wrong screen after stalling at 66%/86%.

A bit of research turned up a suggestion that E200 was related to a hard drive fault (although in hindsight this does not seem to be the case). Initially, I pulled the original HDD (1 TB), connected it to a W10 PC via USB>SATA adapter and "repaired" all of the Xbox partitions. Peculiar to note, when repairing the partitions, W10 would initially throw a dialogue that the partitions did not need to be repaired, however, once I clicked to proceed, another dialogue would indicate that indeed there were errors repaired (the repair process was always fairly quick, <60"). Following the repairs, the original HDD was returned to the Xbox and another attempt at an offline update was conducted with the same results as outlined above.

Ultimately, I came across this thread and decided to give a new HDD a shot, so I purchased a 2 TB Firecuda. I was able to successfully partition the new HDD per the OP's instructions using W10. I confirmed the GUID's of the new partitions matched exactly to the GUID's listed in the readme.txt as well as the partition sizes. Unfortunately, once the offline update was conducted, it would still stall at 66%/86% and return to the something went wrong screen. I have tried this multiple times, reformatting the HDD several times. For my most recent attempt, I re-downloaded OSU1, extracted the files to a different, freshly NTFS formatted USB drive, and re-formatted the HDD again before running the script. For this most recent attempt, I stepped through the video, pausing at each step and comparing the video results to the results I was getting.

A summary of my most recent attempt is below. I noted some minor deviations during my attempt from what I observed in the video - these deviations are underlined/in italics below. To be clear, these deviations are not things that I did differently from the directions, but a different response from the system update process.

1) Successfully partition new 2 TB Firecuda drive using W10 and the scripts from Ver9 of xboxonehdd-master;
2) Attach partitioned HDD to Xbox (system had been unplugged >24hrs)
3) Reconnect power cord and turn system on
4*) First screen to appear is a brief flash to the "Step 3: Applying Update" screen which is at ~35%/72%
5) The above screen quickly switches to the "something went wrong" screen and displays an E106 error.
6) Select the "Troubleshoot" menu
7) Select "Reset" > "Remove Everything"
8*) Unlike the video, the system does reboot on its own and returns to the Step 3: Applying Update screen at 35%/72%, and then reboots again
9) Hold power button 10+ seconds to turn off
10) Power back on, screen briefly returns to "Step 3: Applying Update" at ~35%/72%, but then quickly goes to the something went wrong screen (E106)
11) Select troubleshoot menu
12) Insert flash drive w/ OSU1, select offline update
13) Offline update starts from "Step 1: Downloading Update"
14) Update gets all the way to Step 3: Applying Update, 66%/86% - but then as before, returns to the "Something went wrong screen," although now it is showing an E200 error.

I am at a loss as to what I should do next. Any chance there is something else to try or do I just need send it back to Microsoft?

If you managed to make it this far, thanks for reading. Also, thanks in advance for any potential suggestions.
 

djinc91

The Canadian
Member
Joined
May 19, 2019
Messages
141
Trophies
0
XP
1,110
Country
Canada
I have only used version 8 of the script but are you putting the files from the OSU1 into the system update partition as per the end of the script readme?
 

BDGums

Member
Newcomer
Joined
Feb 11, 2020
Messages
7
Trophies
0
Age
52
XP
48
Country
United States
I have only used version 8 of the script but are you putting the files from the OSU1 into the system update partition as per the end of the script readme?

Not for the most recent attempt. In the video, the OP actually mentions to not do that anymore. At any rate, I did try it that way during the first few attempts and the result was the same.

With respect to Ver8 vs Ver9 - I kept getting "System Update" missing with Ver8. The Ver8 script would act like it completed, but at the end, the partitions wouldn't be formatted. Ver9 worked just fine the 1st time through.
 

Rj.MoG

Well-Known Member
Member
Joined
Jun 8, 2015
Messages
377
Trophies
0
Age
32
XP
1,479
Country
United States
Hello all, brand newbie here...not a gamer but a father trying to help my daughter fix her Xbox One S (1 TB). I came across this thread during my research and have successfully partitioned a new HDD (2 TB Firecuda), however, I am still having problems getting the Xbox up and running. I am hopeful that someone can offer some insight on what to do next, whether it be suggesting additional steps to try or recommending throwing in the towel and sending the unit back to Microsoft.


BACKGROUND

My daughter's lightly used (new Xmas 2019, prolly <15 hrs/week for Minecraft and occasional Left 4 Dead) came down with the E200 error ~3-4 weeks ago, not exactly sure when as I didn't find out about it until well after my wife had started trying to fix it herself by attempting an offline system update per the Microsoft web instructions. Whatever she did, the offline update would always get stuck at 66% applying/86% total and would return to the "Something went wrong" screen.

I tried the offline update myself, confirmed the USB drive was formatted NTFS, reformatted the USB drive, re-downloaded/re-extracted OSU1 with no luck. Also tried re-setting the console to system defaults (both save games option and erase everything option), as well as leaving the console unplugged for 24+ hours multiple times. Always the same result - returning to the something went wrong screen after stalling at 66%/86%.

A bit of research turned up a suggestion that E200 was related to a hard drive fault (although in hindsight this does not seem to be the case). Initially, I pulled the original HDD (1 TB), connected it to a W10 PC via USB>SATA adapter and "repaired" all of the Xbox partitions. Peculiar to note, when repairing the partitions, W10 would initially throw a dialogue that the partitions did not need to be repaired, however, once I clicked to proceed, another dialogue would indicate that indeed there were errors repaired (the repair process was always fairly quick, <60"). Following the repairs, the original HDD was returned to the Xbox and another attempt at an offline update was conducted with the same results as outlined above.

Ultimately, I came across this thread and decided to give a new HDD a shot, so I purchased a 2 TB Firecuda. I was able to successfully partition the new HDD per the OP's instructions using W10. I confirmed the GUID's of the new partitions matched exactly to the GUID's listed in the readme.txt as well as the partition sizes. Unfortunately, once the offline update was conducted, it would still stall at 66%/86% and return to the something went wrong screen. I have tried this multiple times, reformatting the HDD several times. For my most recent attempt, I re-downloaded OSU1, extracted the files to a different, freshly NTFS formatted USB drive, and re-formatted the HDD again before running the script. For this most recent attempt, I stepped through the video, pausing at each step and comparing the video results to the results I was getting.

A summary of my most recent attempt is below. I noted some minor deviations during my attempt from what I observed in the video - these deviations are underlined/in italics below. To be clear, these deviations are not things that I did differently from the directions, but a different response from the system update process.

1) Successfully partition new 2 TB Firecuda drive using W10 and the scripts from Ver9 of xboxonehdd-master;
2) Attach partitioned HDD to Xbox (system had been unplugged >24hrs)
3) Reconnect power cord and turn system on
4*) First screen to appear is a brief flash to the "Step 3: Applying Update" screen which is at ~35%/72%
5) The above screen quickly switches to the "something went wrong" screen and displays an E106 error.
6) Select the "Troubleshoot" menu
7) Select "Reset" > "Remove Everything"
8*) Unlike the video, the system does reboot on its own and returns to the Step 3: Applying Update screen at 35%/72%, and then reboots again
9) Hold power button 10+ seconds to turn off
10) Power back on, screen briefly returns to "Step 3: Applying Update" at ~35%/72%, but then quickly goes to the something went wrong screen (E106)
11) Select troubleshoot menu
12) Insert flash drive w/ OSU1, select offline update
13) Offline update starts from "Step 1: Downloading Update"
14) Update gets all the way to Step 3: Applying Update, 66%/86% - but then as before, returns to the "Something went wrong screen," although now it is showing an E200 error.

I am at a loss as to what I should do next. Any chance there is something else to try or do I just need send it back to Microsoft?

If you managed to make it this far, thanks for reading. Also, thanks in advance for any potential suggestions.
The OSU files are out of date. Find the latest ones on digiex
 

BDGums

Member
Newcomer
Joined
Feb 11, 2020
Messages
7
Trophies
0
Age
52
XP
48
Country
United States
Thanks for the comment. FWIW - the date on the OSU1 files I obtained from the Microsoft website is December 2019. I am downloading the files from Digiex now, but it appears that those are also December 2019.

I have seen discussions regarding offline update problems with the insider program, and I admittedly know nothing about the insider program. That said, I don't believe my daughter's console is part of said program, but honestly I would not know how to tell. At any rate, not sure if this helps, but the OS version listed on the error screen is:

OS Version: 18363.8131.amd64fre.19h1_release_xbox_dev_1911.191213-0400
 

Rj.MoG

Well-Known Member
Member
Joined
Jun 8, 2015
Messages
377
Trophies
0
Age
32
XP
1,479
Country
United States
Thanks for the comment. FWIW - the date on the OSU1 files I obtained from the Microsoft website is December 2019. I am downloading the files from Digiex now, but it appears that those are also December 2019.

I have seen discussions regarding offline update problems with the insider program, and I admittedly know nothing about the insider program. That said, I don't believe my daughter's console is part of said program, but honestly I would not know how to tell. At any rate, not sure if this helps, but the OS version listed on the error screen is:

OS Version: 18363.8131.amd64fre.19h1_release_xbox_dev_1911.191213-0400
Below are the 8131 files

https://mega.nz/#!TX5iiYLY!69lwaT2IqO66uJ8QKWMKxp_OAfgfwRB5zqnYgLIMjbc
 

BDGums

Member
Newcomer
Joined
Feb 11, 2020
Messages
7
Trophies
0
Age
52
XP
48
Country
United States
Excellent. Thank you. I will download these when I get home tonight. Will post back with the results. Fingers crossed.
Thanks again.
 

ford22

Member
Newcomer
Joined
Feb 3, 2020
Messages
10
Trophies
0
Age
31
XP
49
Country
Poland
Hello, I want you to upload from onedrive from the system folder windows to xbox one X and where should I upload because I'm missing and that's why I don't know you can throw

--------------------- MERGED ---------------------------

please send
 

BDGums

Member
Newcomer
Joined
Feb 11, 2020
Messages
7
Trophies
0
Age
52
XP
48
Country
United States
Just a quick update - tried the offline update with the "New Files" linked above with no luck. Given that OSU1 contains many more files than the 7 "New Files", I suspect I have likely missed something or did something out of order. I tried numerous ways to use these files and documented the results at each step. I am still typing up the summary but will post it later tonight when I get home. Thanks again.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Maximumbeans @ Maximumbeans: butte