After the update KB5063878 for Windows 11 my secondary 8TB Seagate Barracuda (ST8000DMZ04/004, GPT/NTFS) was instantly corrupted and turned RAW. This is not my OS drive – it is a dedicated storage drive with professional projects and databases, now completely inaccessible. Windows Explorer still lists folders, but all files fail to open. This is a critical data loss scenario triggered directly by KB5063878, and I need acknowledgement and a real solution for recovery.
System configuration:
OS: Windows 11 (fully updated before KB5063878).
Update: KB5063878 (triggered the issue).
CPU: AMD Ryzen 9 5950X (16 cores / 32 threads).
RAM: 128 GB.
Storage (affected):
- Seagate Barracuda Compute 8TB (ST8000DMZ04/004, GPT/NTFS) – secondary drive for professional data, not the OS drive.
- Storage (OS): NVMe SSD, not affected.
Condition at the time of failure:
Hibernation and Fast Startup were enabled. With 128GB RAM, hiberfil.sys (~100+ GB) was located on the 8TB secondary disk. After applying KB5063878 and rebooting, the 8TB drive immediately showed as RAW instead of GPT/NTFS.
Symptoms:
Windows Explorer still shows folder names, but all files fail to open.
CHKDSK fails with: “The type of the file system is RAW. CHKDSK is not available for RAW drives.”
Windows Disk Management detects the disk but marks it as invalid.
Linux (Ubuntu) also cannot mount the drive.
Recovery tools (R-Studio, DMDE, UFS Explorer) detect sectors but report corrupt MBR and invalid partitions.
Attempts to fix:
Rollback of KB5063878: did not restore the drive.
Third-party recovery scans confirm sectors are present, but the NTFS structure is corrupted.
No hardware issues: BIOS and SMART detect the disk normally.
Impact:
8TB of professional data (SQL Server .mdf/.ldf, DTS packages, Visual Studio projects, sensitive archives) at risk. This is software-induced data loss caused by KB5063878 in combination with hibernation/fast startup on large-capacity GPT/NTFS drives.
I can see my files and navigate thorough them, but when I try to use the opener application indicates that this file or folder don't exist, only 3 files are readable, one of them is an application that run fine from the disk, the same behavior when load the disk on windows 10.
I am reporting this now because since the moment KB5063878 corrupted my 8TB Seagate Barracuda drive I have been forced to focus on urgent attempts to recover my data, without success. The projects stored on this drive are critical, and the time pressure has prevented me from contacting support earlier. At this stage, I urgently request official acknowledgement of this bug and escalation to the Windows engineering team. I need a real technical solution to recover my existing GPT/NTFS data, not just a patch for future cases or generic suggestions. The damage was caused directly by KB5063878 combined with hibernation/fast startup, and my priority is full data recovery.